Upgrading the Repository Definition File (.rpd)

To upgrade the Primavera Analytics Repository Definition file (.rpd) from version 20 to Primavera Analytics Version 22, complete the following steps on the server where Oracle Analytics Server (OAS) is installed:

Go to the <Primavera Analytics unzipped directory>\obi\12c\rpd directory.
For details about the supported OAS version, refer to the Tested Configurations document.
Copy the OraclePrimaveraAnalytics.rpd file to a local folder on the server where you installed OAS. For example, C:\temp.
Open a terminal or command prompt window and go to your BI Domain tools folder.
For example, C:\Oracle\Middleware\Oracle_Home\user_projects\domains\bi\bitools\bin.
Use the data-model-cmd.cmd command (with Windows) or the data-model-cmd.sh command (with UNIX or Linux) in the terminal or command prompt to download the currently deployed Repository Definition file, as follows:
data-model-cmd.cmd downloadrpd –O C:\Temp\OraclePrimaveraAnalytics current.rpd –W <repository password> –U <username> –P <password> –SI <service instance>

Note: Use the datamodel.cmd command (with Windows) or datamodel.sh command (with UNIX or Linux).

For example:

data-model-cmd.cmd downloadrpd –O C:\Temp\OraclePrimaveraAnalytics_current.rpd –W Admin123 –U weblogic –P weblogic1 –SI ssi

A message displays: RPD Download completed successfully.
Use the equalizerpds.cmd command (with Windows) or the equalizerpds.sh command (with UNIX or Linux) in the terminal or command prompt to equalize your current RPD with the new RPD, as follows:
equalizerpds.cmd –B <current repository password> -C <path to current rpd> -E <new repository password> -F <path to new repository> -O <path to equalized repository>

For example:

equalizerpds.cmd –B Admin123 -C C:\Temp\OraclePrimaveraAnalytics_current.rpd -E Admin123 -F C:\Temp\OraclePrimaveraAnalytics.rpd -O C:\Temp\OraclePrimaveraAnalytics_equalized.rpd
Use the comparerpd.cmd command (with Windows) or the comparerpd.sh command (with UNIX or Linux) in the terminal or command prompt to generate a patch file with the differences between your existing RPD and the new equalized RPD, as follows:
comparerpd.cmd –W <new repository password> -C <path to new equalized rpd> -P <current repository password> -G <path to current repository> -D <patch file>

For example:

comparerpd.cmd –W Admin123 -C C:\Temp\OraclePrimaveraAnalytics_equalized.rpd -P Admin123 -G C:\Temp\OraclePrimaveraAnalytics_current.rpd -D C:\Temp\rpd_patch.xml
Use the biserverxmlexec.cmd command (with Windows) or the biserverxmlexec.sh command (with UNIX or Linux) to patch the existing Repository Definition file, as follows:
biserverxmlexec.cmd –P <repository password> -I <path to patch file> -B <path to downloaded repository> -O <output repository path name>

For example:

biserverxmlexec.cmd –P Admin123 –I C:\Temp\rpd_patch.xml –B C:\Temp\OraclePrimaveraAnalytics_current.rpd –O C:\Temp\OraclePrimaveraAnalytics_patched.rpd

Note: After you run this command, a new Repository Definition file is created in the location specified with the -O parameter. This is the file that gets deployed in the rest of this procedure.
Use the data-model-cmd.cmd command (with Windows) or the data-model-cmd.sh command (with UNIX or Linux) to upload the patched Repository Definition file, as follows:
data-model-cmd.cmd uploadrpd –I C:\Temp\OraclePrimaveraAnalytics_patched.rpd –W <repository_password> –U <username> –P <password> –SI <service_instance>

Note: Use the datamodel.cmd command (with Windows) or datamodel.sh command (with UNIX or Linux).

For example:

data-model-cmd.cmd uploadrpd –I C:\Temp\OraclePrimaveraAnalytics_patched.rpd –W Admin123 –U weblogic –P weblogic1 –SI ssi

You should receive a message: RPD Upload completed successfully.
Sign in to the OAS Enterprise Manager URL as a WebLogic Administrator. For example, weblogic:
http://<server>:<port>/em

where

<server> is the server name or IP address of the server where OAS is installed and running.

<port> is the listening port number for OAS.

/em is the default context for OAS Enterprise Manager.
Upon signing into OAS Enterprise Manager, the upper left corner of the screen will show the Target Navigation Tree icon. Click to expand, and then click the arrow icon next to the leaf node called Business Intelligence to expand this folder.
With the Business Intelligence leaf node expanded, the biinstance hyperlink should appear below the leaf node.
Click the biinstance hyperlink. This displays on the right portion of the screen with the properties and available configuration options for this deployment of OAS.
Click the Availability parent tab, and then click the Processes child tab.
Click the Restart All link to restart all components of this OAS deployment. When the confirmation window appears, click Yes. When the OAS deployment restarts, a message appears.
Click Close to close the message.
Click the user menu (For example, WebLogic, located in the upper right of the screen directly below the browser toolbar), then select Sign Out.

Related Topics