This chapter covers the following topics:
This section describes pre-configuration requirements for Oracle Rapid Planning. The tasks mentioned below need to be completed after applying Rapid Planning patch and before starting the installation.
Verify that WebLogic 11gR1 is installed.
Install or upgrade to WebLogic 11gR1 (10.3.6) and Oracle ADF to Patch Set 5 (11.1.1.6.0) for Rapid Planning User Interface (UI) and Engine domains before you upgrade Oracle Rapid Planning. Refer to Server Software Requirements for information on WebLogic and Oracle ADF library requirements for other Oracle Rapid Planning releases.
For release 12.2 and later, install a separate WebLogic Server in a different home to create the Oracle Rapid Planning domains. Define the UI and engine domains and start WebLogic Server from the different home.
Cross mount the location for logs and files written by the concurrent programs with the WebLogic Server used for Rapid Planning.
The following profiles should be set up in EBS at the site level (the EBS instance that the data source points to):
User Profile Name: MSC: Oracle Rapid Planning URL
Internal Profile Name: MSC_RP_HOST_URL
The port number provided in the profile value should be same as the port number for the User Interface Domain that is defined in Creating the User Interface Domain.
Syntax:
http://domain_name:port_number
Example:
http://rws60144rems.us.oracle.com:6087
User Profile Name: MSC: Rapid Planning UI Refresh Timeout
Internal Profile Name: MSC_RP_UI_TIMEOUT
The profile timeout value is in milliseconds. For example, provide profile value of 5000 to represent a 5 second timeout.
User Profile Name: MSC: Rapid Planning WebLogic Server Home
Internal Profile Name: MSC_RP_WLS_HOME
Provide the installation path to the <WLS_Home> directory.
Example:
/slot/user3536/wls/wlserver_10.3
Make sure the Rapid Planning WebLogic Server and Oracle E-Business Suite Server URLs are in the same domain/subdomain for proper Single Sign-On (SSO) authentication.
User Profile Name: MSC: Rapid Planning Scripts Home
Internal Profile Name: MSC_RP_SCRIPTS_HOME
This profile should point to the directory where all the WLST_scripts will be kept.
Example:
/slot/ems5910/appmgr/WLS/user_projects/domains/WLST_Scripts
After applying the respective patches for Rapid Planning User Interface, Rapid Planning Administration, and Rapid Planning Engine, verify that the following ZIP files appear in the directory path $MSC_TOP/dist/orp.
Example:
/slot/ems4928/appmgr/apps/apps_st/appl/msc/12.0.0/dist/orp
RPAdmin.zip
ui.zip
engine.zip
For 12.2.3 and above, if using Online Patching, there will be two APPL_TOPs, RUN tier and PATCH tier. Compare the ZIP files for both RUN and PATCH tier, and use the higher version for deployment.
For example, fs1 is assigned to one tier, either RUN or PATCH. Use the command ident /u01/R122_EBS/fs1/EBSapps/appl/msc/12.0.0/dist/orp/engine.zip to obtain the file version.
Create a folder named ORPTEMP in a user-defined directory (example: /tmp/ORPTEMP) on the host machine where WebLogic is installed. This folder is referenced as ORPTEMP in this document.
Copy the ZIP files to the folder ORPTEMP.
Extract all the ZIP files to the same folder.
Each extracted file contains a respective EAR file. The EAR files will be selected from this location during deployment.
Refer to the following topics in this guide for procedures to deploy the applications:
Configuring the JDBC Data Source for the User Interface Domain
Configure JDBC data source for RP domains. When upgrading to an Exadata release or setting up new configuration for Rapid Planning for Exadata, the JDBC data source needs to be updated. Delete the old data source and create a new one for Exadata.
The host name or URL should include the TNS entry for database RAC instead of single node.
Example of a TNS string:
(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES) (ADDRESS=(PROTOCOL=tcp)(HOST=DB_NODE_A_URL)(PORT=1234)) (ADDRESS=(PROTOCOL=tcp)(HOST=DB_NODE_B_URL)(PORT=1234))) (CONNECT_DATA= (SERVICE_NAME=VIS)))
Replace DB_NODE_A_URL and DB_NODE_B_URL with the URLs for the database nodes. This needs to be done for the RP Engine and the UI domain.
To copy the class files, run the script InitialEngineSetup.sh in the folder WLST_scripts.
Log in to the machine where EBS is installed with username as APPL manager user or APPL TOP owner.
Set the environment variable $MSC_TOP to the path where you copied the patch.
Example:
/slot/ems4928/appmgr/apps/apps_st/appl/msc/12.0.0
Set the environment variable $JAVA_TOP to the path having Java classes.
Example:
/slot/ems2947/appmgr/apps/apps_st/comn/java/classes
After unzipping the file RPAdmin.zip, all the scripts are located in the folder RPAdmin/WLST_scripts. Copy the folder WLST_scripts to the path where Engine domain has been created:
Example:
<WLS_HOME>/user_projects/domains
<WLS_HOME> refers to the name of the directory where WebLogic has been installed.
If the directory domains is not present, create it manually.
All scripts should be run from this path only.
Ensure that the copied WLST_Scripts folder and the contents have rwx permissions for the UNIX session user launching the WebLogic Server.
Example:
chmod 777 *
The WebLogic admin user should have write permissions on the <WLS_HOME> folder and subfolders.
Use the following steps to provide the Rapid Planning application access through EBS:
cd $FND_TOP/patch/115/bin
perl ojspCompile.pl --compile -s 'MscRPRedirect.jsp' --flush
After compiling, verify that the timestamp of file _mscrpredirect.class under $FMW_HOME/Oracle_EBS-app1/applications/oacore/html/WEB-INF/classes/_pages is current.
After compiling, restart the EBS Middle Tier.
Once the Rapid Planning patch is applied, assign Oracle Supply Chain Simulation Planner responsibility to the user account.
Assign Planning Organizations to Oracle Supply Chain Simulation Planner Responsibility.
Navigate to Advanced Planning Administrator > Admin > Organization Security.
Select Oracle Supply Chain Simulation Planner responsibility.
Assign Organizations by moving the required organizations to the Selected list.
Save the assignments.