Redeploying the SAS Web Applications

Redeploying Web Applications

When the SAS Deployment Manager rebuilds SAS Web applications, the rebuilt EAR files are placed in the SAS-config-dir\Lev1\Web\Staging directory. All EAR files are placed in a single directory even if your deployment includes multiple Web application servers (for example, SASServer1 and SASServer2).

If you have Web application servers that were installed and configured by the SAS Deployment Wizard in your environment, make a note of the server names and the Web applications that are installed on each server. For example, if you have six applications located on SASServer1 and three Web applications located on SASServer2, make a list of the applications that are installed on each of these servers. Alternatively, you can refer to your Instructions.html file, which specifies the following:

the list of Web applications to be deployed
the location of the applications
the Web application server where each application should be deployed

When you redeploy the SAS Web applications, you can refer to your list or the Instructions.html file, to ensure that you redeploy each Web application to the correct server.

JBoss Application Server

JBoss is configured to run the SAS Web applications from exploded EAR files. To redeploy a SAS Web application to JBoss, follow these steps:

Shut down JBoss.
Create a directory where you can store unused EAR files. Do not create this directory below the deployment directory or below the JBOSS_HOME\server\SASServer1\deploy_sas. Instead, choose a different location to store these unused EAR files.
Move the unused application EAR files from the deploy_sas directory to the directory that you created for unused EAR files.
If applicable, repeat the previous step for each JBoss application server.
Copy the rebuilt EAR files for the applications that are deployed on this server from the SAS-config-dir\Lev1\Web\Staging\exploded directory to the JBOSS_HOME\server\SASServer1\deploy_sas directory.

For Windows deployments, you can use the xcopy /e /i command for each Web application to copy an exploded EAR file to the deploy_sas directory. The following example shows how to copy SAS BI Dashboard:
```
xcopy /e /i SAS-config-dir\Lev1\Web\Staging\exploded\sas.bidashboard4.3.ear 
sas.bidashboard4.3.ear
```
For UNIX deployments, you can use the cp -r command for each Web application to copy an exploded EAR file to the deploy_sas directory. The following example shows how to copy SAS BI Dashboard:
```
cp -r SAS-config-dir/Lev1/Web/Staging/exploded/sas.bidashboard4.3.ear .
```
Repeat the previous step for any additional JBoss application servers (for example, SASServer2).
Start JBoss.

For complete deployment instructions, see the JBoss documentation at http://www.jboss.org/docs.

Oracle WebLogic Server

Redeploying SAS Applications Using the WebLogic Administration Console

There are a number of ways to redeploy applications in WebLogic Server. The following steps describe how to redeploy Web applications with the WebLogic Server Administration Console:

Stop and delete all SAS applications. See Stop and Delete All SAS Applications.
Shut down the SAS managed servers. See Stop the Managed Servers.
Reinstall the SAS applications. See Reinstall the SAS Applications.
Restart the managed servers. See Start the Managed Servers.
Start the SAS applications. See Start the SAS Applications.

For complete deployment instructions about WebLogic, see the WebLogic documentation at http://www.oracle.com/technology/documentation/index.html.

Stop and Delete All SAS Applications

To stop and delete all SAS applications, follow these steps:

In the WebLogic Administration Console, select Deployments in the Domain Structure panel.
In the Deployments panel, select all applications by selecting the check box next to Name.
On the Stop menu, select Force Stop Now.
In the Summary of Deployments tab, select Yes.
Wait until all applications are displayed in Prepared state. Refresh the view as needed until all applications reach the Prepared state.
When the managed servers are running, delete all applications by selecting Lock and Edit in the Change Center panel.
In the Deployments panel, select all applications by selecting the check box next to Name.
Click Delete.
In the Delete Application Assistant panel, select Yes.
When the message "Selected deployments were deleted," is displayed, select Activate Changes in the Delete Application Assistant panel.

Stop the Managed Servers

It is recommended that you stop the managed servers. Leave the WebLogic administration server running.

To shut down the managed servers, use the WebLogic Server Administration Console and follow these steps:

In the Domain Structure panel, select EnvironmentServers in the Domain Structure.
Leave the administration server running; do not stop it. Then, for each other server, complete the following steps:
1. In the Summary of Servers table, select the server (for example, SASServer1).
2. Select the Control tab.
3. From the menu for Shutdown, select Force Shutdown Now.
4. Click Yes to the prompt Forcibly Shutdown Servers.
5. Verify that the server has been shut down.

Reinstall the SAS Applications

All Web applications should be deployed from the EAR files in the SAS-config-dir\Lev1\Web\Staging directory.

To redeploy the Web applications, use the WebLogic Server Administration Console and follow these steps:

Locate the Instructions.html file in the SAS-config-dir\Lev1\Documents directory, and make a note of the list of SAS applications and their associated servers. This information is available in the Web Application Server section. You need this information when you redeploy and install the EAR files.
In the Domain Structure panel, select Deployments.
Click Lock and Edit in the Change Center panel.
In the Summary of Deployments panel, click Install.
In the Install Application Assistant panel, browse and navigate to the SAS-config-dir\Lev1\Web\Staging directory.
In the Install Application Assistant panel, under Locate deployment to install and prepare for deployment, select an EAR file and click Next.
In the options available for Choose targeting style, retain the default (Install this deployment as an application), and click Next.
See the Instructions.html file to identify the server associated with the EAR file that you are deploying. Typically, for most SAS applications, the target server is SASServer1.
In the Install Application Assistant panel, under Select deployment targets, select the target server and click Next. Typically, SAS applications are deployed to SASServer1.
Under Optional Settings, General, enter a name for the EAR file or the directory for this deployment.
If the administration server and the managed server are on the same machine, under Source accessibility, select I will make the deployment accessible from the following location and click Next. Note that this is not a staged mode.
Under Review your choices and click Finish, select No, I will review the configuration later, and click Finish.
In the Change Center panel, select Activate Changes. The application should be displayed in a New state.
Repeat these steps to redeploy the other SAS Web applications.

Start the Managed Servers

To start the managed servers, use the WebLogic Server Administration Console and follow these steps:

In the Domain Structure panel, select EnvironmentServers.
In the Change Center panel, select Activate Changes.
On the Settings page, select the Control tab.
In the Servers table under Summary of Servers, click on the server name (for example, SASServer1).
In the Server Status table, click Start.
In the Server Life Cycle Assistant panel, click Yes.
In the Server Status table, verify that the task has been completed.
If applicable, repeat these steps for other managed servers.

Start the SAS Applications

To start the SAS Web applications use the WebLogic Server Administration Console and follow these steps:

In the Domain Structure panel, select Deployments. All SAS Web applications should be displayed in a Prepared state.
In the Deployments panel, select all applications by selecting the check box next to Name.
From the Start menu, select Servicing All Requests.
In the Start Application Assistant, select Yes.

IBM WebSphere Application Server

There are two methods to redeploy a SAS Web application to WebSphere Application Server. In the first method, you can update an installed application and select Replace the entire application. With this method, you can maintain all of the application settings, such as the class loader policy and mode for the EAR and WAR modules. For information about this operation, see the IBM WebSphere Application Server documentation at http://www.ibm.com/support/documentation/us/en.

In the second method, you undeploy and redeploy each application individually until all of the rebuilt Web applications have been redeployed.

Although you can redeploy the EAR files in any order of your choice, it is recommended that you follow the sequence of EAR files specified for WebSphere Application Server. See Deploying and Starting Web Applications in the Correct Order.

To redeploy a SAS Web application to WebSphere by undeploying and redeploying each application individually, follow these steps:

Uninstall and reinstall the Web application.
1. Shut down the WebSphere application server, but leave the dmgr and nodeagent running.
2. Follow the IBM WebSphere Application Server instructions for uninstalling and reinstalling a Web application. When you reinstall the application, specify the following two settings on the Select installation options page:
  
  Deploy enterprise beans
  
  Do not select this check box. SAS Web applications do not use Enterprise Java Beans.
  
  Deploy Web services
  
  Select this check box. This ensures that the Web services deploy tool is run.
Set the class loader order.
1. In the Integrated Solutions Console, select ApplicationsApplication TypesWebSphere enterprise applications. Then select the SAS Web application that you are redeploying.
2. Click Class loading and update detection.
3. For the Class loader order, select the Classes loaded with local class loader first (parent last) radio button.
4. Leave the WAR class loader policy set to Class loader for each WAR file in application.
5. Click OK.
6. Click Manage Modules.
7. For each module (WAR file) listed under Manage Modules, click the WAR file link. Then select Classes loaded with local class loader first (parent last) from the Class loader order list box.
8. After you have performed the previous step for each WAR file, click OK.
9. Select Startup behavior and specify a value for Startup order.
10. Save your changes.
Perform a Full Resynchronization.

Perform a full resynchronization of the dmgr server and nodeagent servers. This action ensures the WebSphere Master Repository and the Node Repository are updated and synchronized.
1. In the Integrated Solutions Console, select AdministrationNodes.
2. Select the check box for the application server node.
3. Click Full Resynchronize.

When you have completed these instructions, restart the application. (For the proper start-up sequence of the SAS Web applications, see Deploying and Starting Web Applications in the Correct Order.)