Usage Note 40282: Unconfiguring and reconfiguring SAS Shared Services for the support Web applications servers
This note explains how to remove the configuration and then reconfigure SAS Shared Services for the following Web application servers:
- JBoss application server
- IBM WebSphere
- Oracle WebLogic
On the JBoss Application Server
To remove the SAS Shared Services configuration on JBoss, complete the following steps:
- Stop the JBoss application server.
- Use the SAS® Deployment Manager to remove the SAS Shared Services configuration.
- After the SAS Deployment manager is finished, delete the sas.shared.alerts.par file that is located in the directory SAS_configuration_directory\Lev1\Web\Applications\SASPortlets4.2\Deployed.
- To reconfigure SAS Shared Services so that it uses the same database as before, delete any old databases (for example, Microsoft MySQL or Oracle) that still exist. For example, if you are reconfiguring SAS Shared Services to use the SAS® Table Server, you need to delete the files located in the directory SAS_configuration_directory\Lev1\SASTS\Content.
- Delete the SharedServices-ds.xml file that is in the directory JBoss_configuration_directory\server\SASServer1\deploy\.
- Delete the sas.shared9.2.ear file (or directory) that is in the directory JBoss_configuration_directory\server\SASServer1\deploy_sas\.
- Use the SAS® Deployment Wizard to reconfigure SAS Shared Services.
- Deploy the new sas.shared9.2.ear directory or file to the JBoss application server.
- Start the JBoss server.
On the IBM WebSphere Application Server
To rmove the SAS Shared Services configuration on WebSphere, complete the following steps:
- Stop SASServer1 (the WebSphere application server) or stop the SASPortal Web application.
- Use the SAS Deployment Manager to remove the SAS Shared Services configuration.
- After the SAS Deployment Manager is finished, delete the sas.shared.alerts.par file that is located in the directory SAS_configuration_directory\Lev1\Web\Applications\SASPortlets4.2\Deployed.
- Log on to the WebSphere Administration Console and do the following:
- Select Resources ► JDBC.
- Click the JDBC Providers link.
- Delete any SAS Shared Services providers and save your changes.
- To reconfigure SAS Shared Services so that it uses the same database as before, delete any old databases (for example, Microsoft MySQL or Oracle) that still exist. For example, if you are reconfiguring SAS Shared Services to use the SAS® Table Server, you need to delete the files located in the directory SAS_configuration_directory\Lev1\SASTS\Content.
- Restart SAS Server1.
- Use the SAS Deployment Wizard to reconfigure SAS Shared Services.
- Deploy the new sas.shared9.2.ear file to the WebSphere application server.
On the Oracle WebLogic Application Server
To remove the SAS Shared Services configuration on WebLogic, complete the following steps:
- Stop the WebLogic application server SASServer1, or stop the SASPortal Web application.
- Use the SAS Deployment Manager to remove the SAS Shared Services configuration.
- After the SAS Deployment Wizard is finished, delete the sas.shared.alerts.par file that is located in the directory SAS_configuration_diretory\Lev1\Web\Applications\SASPortlets4.2\Deployed.
- Log on to the WebLogic Administration Console and do the following:
- Select Services ►JDBC.
- Click the Data Sources link.
- Click the Lock & Edit” button.
- Delete Shared Services.
- Save your changes by clicking the Activate Changes button.
- To reconfigure SAS Shared Services so that it uses the same database as before, delete any old databases (for example, Microsoft MySQL or Oracle) that still exist. For example, if you are reconfiguring SAS Shared Services to use the SAS® Table Server, you need to delete the files located in the directory SAS_configuration_directory\Lev1\SASTS\Content.
- Restart the SASServer1 server.
- Use the SAS Deployment Wizard to reconfigure SAS Shared Services.
- Deploy the new sas.shared9.2.ear file to the WebLogic server.
Operating System and Release Information
| SAS System | SAS Enterprise BI Server | z/OS | 4.2 | | 9.2 TS2M2 | |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows XP 64-bit Edition | 4.2 | | 9.2 TS2M2 | |
| Microsoft® Windows® for x64 | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows Server 2003 Datacenter Edition | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows Server 2003 Enterprise Edition | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows Server 2003 Standard Edition | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows Server 2003 for x64 | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows Server 2008 | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows Server 2008 for x64 | 4.2 | | 9.2 TS2M2 | |
| Microsoft Windows XP Professional | 4.2 | | 9.2 TS2M2 | |
| Windows 7 Enterprise 32 bit | 4.2 | | 9.2 TS2M2 | |
| Windows 7 Enterprise x64 | 4.2 | | 9.2 TS2M2 | |
| Windows 7 Home Premium 32 bit | 4.2 | | 9.2 TS2M2 | |
| Windows 7 Home Premium x64 | 4.2 | | 9.2 TS2M2 | |
| Windows 7 Professional 32 bit | 4.2 | | 9.2 TS2M2 | |
| Windows 7 Professional x64 | 4.2 | | 9.2 TS2M2 | |
| Windows 7 Ultimate 32 bit | 4.2 | | 9.2 TS2M2 | |
| Windows 7 Ultimate x64 | 4.2 | | 9.2 TS2M2 | |
| Windows Vista | 4.2 | | 9.2 TS2M2 | |
| Windows Vista for x64 | 4.2 | | 9.2 TS2M2 | |
| 64-bit Enabled AIX | 4.2 | | 9.2 TS2M2 | |
| 64-bit Enabled HP-UX | 4.2 | | 9.2 TS2M2 | |
| 64-bit Enabled Solaris | 4.2 | | 9.2 TS2M2 | |
| HP-UX IPF | 4.2 | | 9.2 TS2M2 | |
| Linux | 4.2 | | 9.2 TS2M2 | |
| Linux for x64 | 4.2 | | 9.2 TS2M2 | |
| Solaris for x64 | 4.2 | | 9.2 TS2M2 | |
*
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.
| Date Modified: | 2011-04-15 14:53:46 |
| Date Created: | 2010-07-09 08:42:26 |