Web Application Timeout Changes

0

Is the SAS Web Applications timeout of 30 minutes still too short? You can modify these by following editing the .xml files listed on page 15 of SAS Web Application Administration Guide. Here are the steps I took to update the Portal, SAS Web Report Studio and the SAS Stored Process Web Applications with a 90 minute timeout.
1. Stopped Tomcat
2. Edited the Files listed below & changed the code from: &ltsession-config;>&ltsession-timeout;>30</session-timeout></session-config>
to:
&ltsession-config;>&ltsession-timeout;>90</session-timeout></session-config>

a. Portal and STP: SAS-install-dir\Web\Portal2.0.1\PortalWEBINFweb.xml
b. WRS: web.xml.host.tomcat and web.xml.trusted.tomcat found in: SAS-install-dir\SASWebReportStudio\3.1\config\Source\Java\resources
3.Redeploy the SAS Web Applications:
a. Portal and STP: configure_wik.bat and tomcat_deploy.bat (found in: SAS-install-dir\Web\Portal2.0.1)
b. WRS: sas.wrs.config.bat and sas.wrs.tomcat.deploy.bat (found in: SAS-install-dir\SASWebReportStudio\3.1)
4. Restarted Tomcat

Share

About Author

Angela Hall

Senior Technical Architect

Angela offers tips on using the SAS Business Intelligence solutions. She manages a team of SAS Fraud Framework implementers within the SAS Solutions On-Demand organization. Angela also has co-written two books, 'Building BI using SAS, Content Development Examples' & 'The 50 Keys to Learning SAS Stored Processes'.

Comments are closed.

Back to Top