Undeploying SAS Web Applications and Stopping the Web Application Servers :: Planning for Maintenance Releases and Product Upgrades for SAS(R) 9.2

Why You Need to Undeploy the SAS Web Applications

When you apply the third maintenance release for SAS 9.2, SAS automatically performs these tasks:

rebuilds all SAS Web applications
configures and restarts your Web application servers

In order to apply the third maintenance release, you must undeploy any SAS Web applications on the tier where you are applying the maintenance release and stop any Web application servers that run SAS Web applications. For more information, see the following topics:

Oracle WebLogic Server

Complete these steps:

Stop and delete all SAS Web applications.
1. Open the WebLogic Administration Console.
2. In the Domain Structure panel, select Deployments.
3. In the Change Center panel, click Lock and Edit.
4. In the Summary of Deployments panel, select the check boxes for all SAS Web applications. Then select StopForce Stop Now.
5. In the Force Stop Application Assistance panel, click Yes.
6. In the Summary of Deployments panel, refresh the view until all selected applications show a Prepared state.
  
  Note: The SAS managed servers should still be running.
7. In the Summary of Deployments panel, select the check boxes for all the SAS Web applications, and then click Delete.
8. In the Delete Application Assistant panel, click Yes. A message confirms the deletion of the selected deployments.
9. In the Change Center panel, click Activate Changes.
Stop the managed servers for the Web applications (such as SASServer1 and SASServer2). For more information, see “Starting or Stopping an Oracle WebLogic Server” in the SAS Intelligence Platform: System Administration Guide.
Stop the Administration Server and the Node Manager.

WebSphere Application Server

Complete these steps:

Stop all SAS Web applications. In the WebSphere Administrative Console, select the check box for each SAS Web application, and then click Stop.
Uninstall all SAS Web applications.
- In the WebSphere Administrative Console, select the check box for each SAS Web application, and then click Uninstall.
- After the SAS Web application is uninstalled, click Review, select the Synchronize changes with nodes check box, and then click Save.
Stop the application servers for the SAS Web applications (such as SASServer1). For more information, see “Starting or Stopping an IBM WebSphere Application Server or an IBM WebSphere Application Server Network Deployment” in the SAS Intelligence Platform: System Administration Guide.
Note: Do not stop the WebSphere Deployment Manager (dmgr) server and nodeagent server. These servers must be running when you apply the third maintenance release for SAS 9.2.
- the dmgr server
  
  In the <WAS_INSTALL_ROOT>/profiles/<dmgr-profilename>/bin directory, run startManager.bat in Windows environments or execute startManager.sh in UNIX environments.
  
  By default, <dmgr-profilename> is SASDmgr01.
- the nodeagent server
  
  In the <WAS_INSTALL_ROOT>/profiles/<node-profilename>/bin directory, run startNode.bat in Windows environments or execute startNode.sh in UNIX environments.
  
  The default for <node-profilename> depends on your current SAS 9.2 deployment.
  
  For an existing SAS 9.2 (TS2M0) deployment, <node-profilename> is SASAppSrv01.
  
  If you are running the second maintenance release for SAS 9.2 (TS2M2), <node-profilename> is SASmachine-name01.

JBoss Application Server

Complete these steps:

Stop the JBoss application server. For more information, see “Starting or Stopping a JBoss Application Server” in the SAS Intelligence Platform: System Administration Guide.
Create a backup of the JBoss-home-directory/server/SASServern/deploy_sas directory.
1. Delete the JBoss-home-directory/server/SASServern/tmp directory and all of its contents.
2. Copy the contents of the JBoss-home-directory/server/SASServern directory to a SASServern_premaint directory.
  
  Note: If a SASServern_premaint directory does not exist, then this directory is created when you run the cp —R command in UNIX environments or the xcopy in Windows environments.
  
  On UNIX, enter the following commands at the UNIX prompt:
  cd <JBoss-home-directory>/server cp -R SASServer<n> SASServer<n>_premaint
  On Windows, you can copy the files by using Windows Explorer or by entering the following commands at a DOS prompt:
  cd <JBoss-home-directory>\server xcopy /E /I SASServer<n> SASServer<n>_premaint
Delete the EAR files for all SAS Web applications from the JBoss-home-directory/server/SASServern/deploy_sas directory.
If you have configured your environment to use restrictive policies, then disable restrictive policy handling for JBoss. For more information, see “Configuring and Deploying Restrictive Policy Files” in the SAS Intelligence Platform: Web Application Administration Guide.

Note: If you have multiple servers (such as SASServer1 and SASServer2), then you must disable the restrictive policy files on all these servers.

To manually disable the use of SAS restrictive policy files:
1. On Windows, open the JBoss-home-directory\bin\SASServer1.bat file. On UNIX, open the JBoss-home-directory/bin/SASServer1.sh file.
2. In the start_as_script section, remove the following parameters from the JAVA_OPTS line.
  
  –Djava.security.manager
  
  –Djava.security.policy=JBoss-home-directory\server\SASServer1\sas.restrictive.permissions.policy
If JBoss is running as a Windows service:
1. On Windows, open the JBoss-home-directory\server\SASServer1\wrapper.conf file.
2. Remove the following parameters from the wrapper.conf file.
  
  wrapper.java.additional.##=–Djava.security.manager
  
  wrapper.java.additional.##=Djava.security.policy=JBoss-home-directory\server\SASServer1\conf\sas.restrictive.permissions.policy
When you apply the maintenance release, the restrictive policy file might be re-created automatically, or you might have to create this file manually. For more information, see Restore Restrictive Policy Settings.
To prevent issues when you are compiling the JSP pages in the updated applications, delete the contents of the JBoss-home-directory/server/SASServern/work directory.