This chapter describes the steps for upgrading to Oracle RTD Release 3.2 from Release 3.0.0.1. It consists of the following topics:
This section describes how to upgrade from Oracle RTD Release 3.0.0.1 to Oracle RTD Release 3.2.
The assumptions are:
Oracle RTD Release 3.0.0.1 was installed at C:\OracleBI\RTD.
The Oracle RTD Release 3.0.0.1 database was initialized.
The Model Snapshots tables, if used, were initialized.
Your Inline Services were deployed on Oracle RTD Release 3.0.0.1.
The Oracle RTD Release 3.0.0.1 Decision Studio workspace is at the default location. On Windows, the default location is %USERPROFILE%\Oracle RTD Studio, for example, C:\Documents and Settings\your user name\Oracle RTD Studio.
To shut down Oracle RTD Release 3.0.0.1:
Exit from Oracle RTD Decision Studio.
Exit from Oracle RTD Load Generator.
Open your J2EE application server's administration console.
Stop Oracle RTD.
To back up your existing database and configuration files:
Rename C:\OracleBI\RTD\ to C:\OracleBI\RTD.30.
Copy C:\Documents and Settings\your user name\Oracle RTD Studio to C:\Documents and Settings\your user name\Oracle RTD Studio.30.
Back up your Oracle RTD database.
Refer to your database vendor's documentation for information about backing up a database.
To unpack Oracle RTD Release 3.2:
Expand the Oracle RTD Release 3.2 distribution archive to the desired location, for example, C:\OracleBI\RTD.
To upgrade the Oracle RTD Decision Studio Workplace:
Start Oracle RTD Decision Studio.
If you have any compile errors, select Project > Clean > Clean all projects.
If you made changes to SDTablespaceMap.txt (located in RTD_HOME/scripts/sql/Oracle) in RTD 3.0.0.1, make sure to apply these changes in the RTD 3.2 version you are installing.
To upgrade your Oracle RTD database:
Start SDDBTool.
For information about SDDBTool, see Oracle Real-Time Decisions Installation and Administration Guide.
When the option to Initialize or Upgrade appears, select Upgrade.
If you had model snapshot tables in Release 3.0.0.1, then, from the RTD_HOME\scripts directory, run the command that creates the model snapshot tables:
sdexec com.sigmadynamics.tools.SDDBTool.SDDBTool -f -u -I InitSnapshotDb.ctl db_type db_host db_port db_name db_runtime_user db_admin_user db_admin_password
Note:
If you are using DC_Demo, you need to re-run InitAppDB for DC_Demo, as specified in section 2.4, "Populating the DC_Demo Example Data" in Oracle Real Time Decisions Installation and Administration Guide.
If necessary, upgrade the application server you are using. Ensure you are running a supported version of the application server.
To upgrade Oracle WebLogic Server, see Upgrading Oracle WebLogic Server.
To upgrade WebSphere, see the WebSphere Application Server documentation library at:
http://www-01.ibm.com/software/webservers/appserv/was/library/
Next, you will install Oracle RTD 3.2; however, before installing it, you need to undeploy Oracle RTD 3.0.0.1. You will then need to reapply all the changes you have made in the previous version:
The cluster configuration has changed and no longer uses JGroups. Follow the new cluster setup instructions in Oracle Real-Time Decisions Installation and Administration Guide.
Classpath arguments have changed. Review the new classpath settings in the Oracle Real-Time Decisions Installation and Administration Guide.
JMX MBean attributes have changed location and need to be specified again.
Custom Roles have to be recreated.
SSL has to be reconfigured.
You no longer are required to modify RTD.ear in order to add new data sources.
In order to see log files, configure this with JMX console because, with RTD Release 3.2, we deploy the RTD.ear file instead of expanding it.
Install a fresh version of Oracle Real Time Decision 3.2 but point it to the upgraded SDDS, rather than a new one. For instructions, see the Oracle Real Time Decisions Installation and Administration Guide.
Start Oracle RTD and verify that the inline services are loading properly, by either:
In the RTD server.log file, check that your existing Inline Services loaded successfully, by examining the [AppFactory] entries.
For example,
2007-11-26 17:42:46,725 INFO [AppFactory] Loaded Inline Service DC_Demo:4 in deployment state Development.
Alternatively, you can check the status of your Inline Services through JMX. In JConsole, navigate to Mbeans > Oracle RTD > Inline Service Manager > Inline Service Name.
Expand the Inline Service Name to show the deployment state of interest, and note the Status of the deployment state. If the Status attribute has a value of Loadable, then the Inline Service for that deployment state has been loaded properly and can now accept requests. If the server was unable to upgrade and load your existing Inline Service, the Status attribute will show a value of Failed.
In this case, you can deploy a working version of the Inline Service from the Decision Studio. If you no longer have the source code for an Inline Service, you can download the Inline Service, using Project > Download.
In Decision Studio, open up all your Inline Services.
Recompile the Inline Services, using Project > Download, then Clean all projects.
Deploy each Inline Service to the RTD Server.
This section describes issues known to exist with the upgrade processes described in this chapter.
Special chars (like "&" or "<") were not properly escaped in the response from an advisor (for example "&" is not transformed to "&") in Releases 3.0.0.1.10 PSU and 3.0.0.1.11 PSU.
If you implemented a workaround of escaping the response in the inline service for one of these versions, you should remove this workaround as part of your RTD 3.2.0.0.0 upgrade.
With this new release, 3.2, if a choice attribute includes XML there is no need to include it in a CDATA section.
Any XML in choice attributes will be escaped in the response to the client such that the client (e.g. Java Smart Client) receives it correctly.
If a CDATA section is included in the choice attribute value, then that CDATA section will also pass through to the client; that is, it will not be removed by the client's XML parser.
Issues in Release 3.0.0.1 with <Choice Group>.getChoice() have been fixed and the previously recommended workaround of using <Choice Group>.getPrototype() is no longer needed if you modify your Inline Service as described above. It is strongly advised you make the recommended changes to your Inline Services as <Choice Group>.getPrototype() is an internal method and has its own set of issues when used with a deep choice group hierarchy. For more details, see Section 8.1, "Improvement to Dynamic Choices Definition".