SAS Real-Time Decision Manager :: Planning for Maintenance Releases and Product Upgrades for SAS(R) 9.2

Before You Upgrade: Stop the SAS Object Spawner and Create Backups

Before you apply the third maintenance release for SAS 9.2 and install SAS Real-Time Decision Manager 5.3, back up your metadata, SAS Real-Time Server configuration files, SAS Real-Time Decision Manager repositories, system resources, flows, events, and activities.

If you have configured a production environment with multiple configurations of SAS Real-Time Decision Server, then you must complete these steps:

On each SAS application server where a SAS Real-Time Decision Manager Server is configured, stop the SAS Object Spawner that has been configured for SAS Real-Time Decision Manager.
On the client machines where the SAS Real-Time Decision Manager Plug-in for SAS Management Console is installed, complete these steps:
1. In SAS Management Console, click the Folders tab.
2. Navigate to the System/Application/SAS Real-Time Decision Manager/Real-Time Decision Manager folder.
3. Right-click a repository folder and select Export SAS Package. The Export SAS Package dialog box appears.
4. Follow the steps in the Export SAS Package dialog box to export your SAS Real-Time activities, resources, events, global variables, and flows.
5. Repeat steps c and d for each repository folder.
6. Close SAS Management Console.
On the middle tier where SAS Real-Time Decision Manager Engine Server and SAS Real-Time Manager Design Server are installed, complete these steps:
1. Open the SAS-installation-directory\Lev1\Web\Staging directory.
2. Create backups of the sas.rtdm.designserver5.3.ear and sas.rtdm.engineserver.websphere5.3.ear files.

New Functionality: Performance Improvements to the SAS Real-Time Decision Server

SAS Real-Time Decision Manager 5.3 provides a significant improvement in real-time scoring throughput performance.

Post-Configuration Steps for SAS Real-Time Manager

When Post-Configuration Steps Are Required

Use the following table to determine what (if any) post-configuration steps you need to complete. To determine the product release number for SAS Real-Time Decision Manager, see the deployment registry report that you generated before you applied the third maintenance release. For more information, see Determining the Product Release Numbers for Products at Your Site.

When Post-Configuration Steps Are Required

Update Scenario	Are Post-Configuration Steps Required?
You are installing SAS Real-Time Decision Manager for the first time.	No
You are applying the third maintenance release, and the product release number for SAS Real-Time Decision Manager is 5.3.	Yes If you configured multiple SAS application servers in a production environment, then you must complete the post-configuration steps. For more information, see When SAS Real-Time Decision Server Is Configured by the SAS Deployment Wizard or When SAS Real-Time Decision Server Is Manually Configured.

When SAS Real-Time Decision Server Is Configured by the SAS Deployment Wizard

On each SAS application server tier where the SAS Real-Time Decision Engine server was installed and configured using the SAS Deployment Wizard, complete these steps:

Restart the Queue Manager that was configured for SAS Real-Time Decision Manager.
Note: If the Multiple DATA Step activity uses %LET statements to assign output variables, then you must add a %GLOBAL statement before the %LET statement. For example, if your current code is %let outputvariable=xyz;, then the modified code would be as follows:
```
%global outputvariable;
%let outputvariable=xyz;
```
Restart the SAS Object Spawner that was configured for SAS Real-Time Decision Manager.

When SAS Real-Time Decision Server Is Manually Configured

On each SAS application server tier where the SAS Real-Time Decision Server was installed, complete these steps:

In the SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3\Data\ModelMetadata directory, back up the model metadata.
In the SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3\SASActivityCode directory, back up the activity code.
From the SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3 directory, copy the updated ModelUpdate.sas and SCSingleData.sas files to each SAS application server where the SAS Real-Time Decision Server was manually configured.
Delete the contents of the SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3\Data\ModelMetadata directory.
From the SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3\SASActivityCode directory, copy the mm_allmodels.sas file to each SAS application server where the SAS Real-Time Decision Server was manually configured.
From the SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3\SASCode directory, copy all of the .sas files in this directory to each SAS application server where the SAS Real-Time Decision Server was manually configured.
From the SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3 directory, copy the MultipleDataStepStart.sas and AuditLogStart.sas files to each SAS application server where the SAS Real-Time Decision Server was manually configured.
If you created SAS Activity Code for multiple DATA steps, you must run the upgrade utility to upgrade your code in the SAS Activity Code directory for this maintenance release. A backup directory called SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3\SASActivityCode\migrationBackup is created. A backup copy of each updated SAS Activity Code file for multiple DATA steps is copied into this directory. No SAS Activity XML updates are required.

From the SAS-installation-directory\SASRealTimeDecisionManagerServerConfiguration-installation-directory directory, run the command for your operating environment:

Windows environment

UpgradeMDSActivity.exe SAS-configuration-directory\Lev1\Applications\SASRealTimeServerConfig5.3\SASActivityCode

UNIX environment

UpgradeMDSActivity SAS-configuration-directory/Lev1/Applications/SASRealTimeServerConfig5.3/SASActivityCode
Note: If the Multiple DATA Step activity uses %LET statements to assign output variables, then you must add a %GLOBAL statement before the %LET statement. For example, if your current code is %let outputvariable=xyz;, then the modified code would be as follows:
```
%global outputvariable;
%let outputvariable=xyz;
```
Restart the SAS Object Spawner that was configured for SAS Real-Time Decision Manager.
After all the SAS application servers have been updated, open the WebSphere Administrative Console on the middle-tier server. Restart the application server where the SAS Real-Time Decision Manager Design Server and the SAS Real-Time Decision Manager Engine Server are deployed.
Note: If the SAS Real-Time Decision Manager Engine Server is deployed in a cluster, then you must complete one of these steps:
- Restart the cluster.
- Open the WebSphere Administrative Console and restart the WebSphere application servers where the SAS Real-Time Decision Design Server and the SAS Real-Time Manager Engine Server are deployed.