Usage Note 41750: How to change the time-out value for SAS® Solutions Services and SAS Financial Management portlets/tasks in the SAS Information Delivery Portal
When you change the time-out setting for the SAS Information Delivery Portal, as described in SAS Note 41326, you do not impact the time-out value for SAS Solutions Services and SAS Financial Management portlets and tasks.
To designate the time-out values, please follow these instructions:
- Open the <web.xml> file in a standard text editor from the following directories:
- <drive>:\SAS\Config\Lev1\Web\Staging\exploded\sas.portal4.x.ear\sas.portal.war\WEB-INF\
- <drive>:\SAS\Config\Lev1\Web\Staging\exploded\sas.financialmanagement5.x.ear\sas.financialmanagementwebapp.war\WEB-INF\
- <drive>:\SAS\Config\Lev1\Web\Staging\exploded\sas.solutionsservices5.x.ear\sas.solutionscommonapp.war\WEB-INF\
- Search the file for the string "<session-timeout>". The default value is 30 (minutes).
- Update this to your desired time-out value (in minutes). Save and close the files.
- Repeat steps 1 - 3 for the <web.xml.orig> files for the following directories:
- <drive>:\Program Files\SAS\SASInformationDeliveryPortal\4.x\Configurable\wars\sas.portal\WEB-INF\
- <drive>:\Program Files\SAS\SASFinancialManagementMidTier\5.x\Configurable\wars\sas.financialmanagementwebapp\WEB-INF\
- <drive>:\Program Files\SAS\SASSolutionsServicesMidTier\5.x\Configurable\wars\sas.solutionscommonapp\WEB-INF\
- Access the Oracle WebLogic Server Administration Console via:
http://:7501/console
The default log on credentials are
User name: weblogic
Password: AdminAdmin1
but these might be different at your site.
- Select 'Deployments' from the 'Domain Structure' panel.
A suggested best practice is to capture a screen shot of your deployments, including application name and deployment order, before continuing with the following steps.
- In 'Deployments', ensure that the 'Control' tab is selected.
- Select the box next to 'sas.portal4.x.ear'. Select 'Stop' and 'Force Stop Now', and select 'Yes' to continue.
- When you are returned to the Deployments panel and the State for 'sas.portal4.x.ear' is 'Prepared', select 'Lock and Edit' in the Change Center panel. Select the box next to 'sas.portal4.x.ear'. Select 'Delete' and select 'Yes' to continue.
- Repeat steps 8 - 9 for the 'sas.financialmanagement5.x.ear' and the 'sas.solutionsservices5.x.ear' deployments.
- Next, access
<drive>:\Program Files\SAS\SASDeploymentManager\9.x\
and double click on the <config.exe> file to launch the SAS Deployment Manager.
- After selecting the language to use, select 'Rebuild Web Applications' and then 'Next'.
- Select '<drive>:SAS\Config' for the Configuration Directory, and ensure that 'Lev1' is selected for the Configuration Level. Select 'Next'.
- Input the appropriate parameters to connect to the SAS Metadata Server at your site and then select 'Next'.
- To Select Web Applications to Rebuild, select the box next to 'Information Delivery Portal 4.x', 'Financial Mgmt 5.x', and 'Solutions Svc 5.x' and then select 'Next'.
- BEFORE SELECTING START IN THE NEXT WINDOW OF THE SAS DEPLOYMENT MANAGER, access
<drive>:\SAS\Config\Lev1\Web\Staging\
and delete the files
- sas.portal4.x.ear
- sas.financialmanagement5.x.ear
- sas.solutionsservices5.x.ear
- RETURN TO THE SAS DEPLOYMENT MANAGER, and select 'Start'.
- Once the deployment is complete, select 'Finish' and return to 'Deployments' in the Oracle WebLogic Server Administration Console.
- Select 'Install'.
- Ensure that the path is set to <<drive>:\SAS\Config\Lev1\Web\Staging>.
- Select the box next to 'sas.portal4.x.ear' and select 'Next'.
- Select 'Install this deployment as an application’ and 'Next'.
- Select 'SASServer1' under 'Available targets for sas' and 'Next'.
- In the Name box, input sas.portal4.x (for example, 'sas.portal4.3').
- At the bottom of the page, select ‘I will make the deployment accessible from the following location’, ensure that the location is designated as
<drive>:\SAS\Config\Lev1\Web\Staging\sas.portal4.x.ear
and then select 'Next'.
- Select ‘No, I will review the configuration later’, and then 'Finish'.
- When the message "The deployment has been successfully installed’ is returned, select 'Activate Changes' in the Change Center panel.
- Select the box next to 'sas.portal4.x.ear', select 'Start' and then 'Servicing all requests' and 'Yes' to continue.
- Once the State for 'sas.portal4.x.ear' is 'Active', repeat steps 19 - 28 to install and start the sas.financialmanagement5.x.ear and the
sas.solutionsservices5.x.ear. Note that both of these are deployed to ‘SASServer3’ under ‘Available targets for sas’. Please also note that the deployment order for sas.financialmanagement5.x.ear is 110 rather than the default value of 100.
Operating System and Release Information
SAS System | SAS Financial Management | Microsoft® Windows® for x64 | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Datacenter Edition | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Enterprise Edition | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Standard Edition | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 for x64 | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2008 for x64 | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows XP Professional | 5.1 | | 9.2 TS2M0 | |
Windows Vista | 5.1 | | 9.2 TS2M0 | |
Windows Vista for x64 | 5.1 | | 9.2 TS2M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Follow these instructions to set the time-out values for your SAS Solutions or SAS Financial Management portlets/tasks.
Date Modified: | 2011-08-10 19:13:57 |
Date Created: | 2010-12-03 14:55:41 |