Repository Upload Procedure in OBIEE 11G and 12C

Start Here

Get in touch with a
TriCore Solutions specialist

Blog | Dec 9, 2016

Repository Upload Procedure in OBIEE 11G and 12C

In this blog I will discuss procedures OBIEE administrators should follow in uploading a repository .rpd file in both OBIEE 11G and OBIEE 12C versions under Unix/Linux environments. This step by step approach will help OBIEE Users and Administrators to understand the main difference in process we have performed in the previous versions of 11G and latest version of 12C.

Introduction:
In my earlier blog we reviewed step by step procedures to help both OBIEE administrators and users for starting and stopping servers in Unix/Linux environments. In this blog I will discuss procedures OBIEE administrators should follow in uploading a repository .rpd file in both OBIEE 11G and OBIEE 12C versions under Unix/Linux environments. This step by step approach will help OBIEE Users and Administrators to understand the main difference in process we have performed in the previous versions of 11G and latest version of 12C.

Enterprise Manager EM URL http://localhost:7001/em was used earlier in OBIEE 11G for uploading the repository .rpd file. The intended deployment process carried for OBIEE11G Users/Administrators is to go within DeploymentàUpload BI Server Repositoryà upload new file and then Restart BI Services to upload latest RPD.

obiee support

In OBIEE 12C, the upload format has been replaced. The .rpd file is uploaded through the Weblogic Scripting command “Uploadrpd” to upload repository file in the Oracle BI Server.

In Unix/Linux, we can get the “data-model-cmd.sh” script to execute at the below location:

<Oracle_Home>/user_projects/domains/bi/bitools/bin

(Note: the Oracle Home <Oracle_Home> which we are using in OBIEE 12C is referred to as Middleware Home <MW_HOME> in OBIEE11G. References can be found at “New and Deprecated Terminology for 12c (12.1.2)” in “https://docs.oracle.com/middleware/1212/core/ASCON/whatsnew.htm#ASCON11224” )

Given below is the command I used to upload the RPD file (i.e., OBIEE12CBusinessIntelligence.rpd) in OBIEE12C within Unix/Linux environments. OSuser@LocalHostDetails bin]$ ./data-model-cmd.sh uploadrpd -I /tmp/OBIEE12CBusinessIntelligence.rpd -SI ssi -U Username -P Password -S LocalHostDetails.com -N PortNo9502

RPD Password: <Enter the RPD Password>

Service Instance: <Enter the RPD Password basically it would be ssi>

Operation successful.

RPD upload completed successfully.

[OSuser@LocalHostDetails bin]$ 

Please note:- In the above command I have copied my uploaded OBIEE12C .rpd file (i.e., OBIEE12CBusinessIntelligence.rpd) in /tmp directory in Unix environment, you can copy this rpd to your required convenient location and the path details after “–I” in the script. 

With the above process we have seen the upload is done to Oracle BI Server in OBIEE12C. Here, unlike in OBIEE11G we are not restarting BI Services to reflect the changes. The script above once executed will automatically refresh the services needed for deployment. The description for terminologies used in the script above is as follows.

  • “I” specifies the name of the repository that you want to upload.
  • “W” is the repository’s password. If you do not supply the password, then you will be prompted for the password when the command is run. For security purposes, Oracle recommends that you include a password in the command only if you are using automated scripting to run the command.
  • “SI” denotes the name of the service instance.
  • “U” specifies a valid user name to be used for Oracle BI EE authentication.
  • “P” specifies the password corresponding to the user’s name that you specified for “U”. If you do not supply the password, then you will be prompted for the password when the command is run. For security purposes, Oracle recommends that you include a password in the command only if you are using automated scripting to run the command.
  • “S” denotes the Oracle BI EE host name. Only include this option when you are running the command from a client installation.
  • “N” specifies the Oracle BI EE port number. Only include this option when you are running the command from a client installation.
  • “SSL” specifies to use SSL to connect to the WebLogic Server to run the command. Only include this option when you are running the command from a client installation.
  • “H” displays the usage information and exits the command.

Below are few screen shots of OBIEE 12C sample rpd opening from 12C version of Administration tool:

oracle bi admin

repository_upload_2.png
Conclusion:
The procedures discussed above can be followed by OBIEE administrators to upload repository .rpd file in OBIEE 11G and OBIEE 12C mainly in Unix/Linux Environments. The steps described above can be a quick reference for the users or administrators trying to upgrade their existing versions of OBIEE 11G environment to the latest OBIEE 12C. For any questions on the steps discuss click below:

Ask Kanthikiran