Art of BI: Converting the OBIEE Repository File (.rpd) Into a XML (.xml) File
Author: Bill Anderson | | December 21, 2016
In comparison to 11g, the Oracle 12c release introduced a lot of changes both in features and the installation procedure. One of the changes was in the installation of Oracle Enterprise Metadata Management. The installation procedure has no instructions on how to convert the RPD to XML for 12c, even though it is almost the same as for 11g.
Some other changes related to the conversion process of RPD to XML for 12c in the installation of OEMM include:
- Downloading from and uploading to the server a repository file and making it available to the queries
- The inability to FTP the current RPD down from the server and use it for further modification
- The Enterprise Manager deployment tab to upload a repository has been replaced with one command-line utility, data-model-cmd.sh.
Steps for Converting the OBIEE 12c RPD to a XML file (Linux)
Step 1: Download the RPD file
The RPD file directory has also changed in 12c and the RPD now is located here:
To download the RPD:
1.Open a new cmd window
2.Change directories to the current RPD
You will need a password to copy the latest RPD file and open it in Administrator. This internal password is a new security feature designed to stop anyone from just copying the RPD file and editing it. To download an RPD file for editing you need to use a new utility called data-model-cmd.sh located in this directory: /OBIEE_HOME/user_projects/domains/bi/bitools/bin
There are some parameters you’ll need for this command, the minimum of which are:
Downloadrpd the instruction to download the RPD
-O rpdfilename the name you want to give to the RPD file you’re downloading
-SI OBIEE service instance, e.g. ssi
-U Weblogic administrator user-id
-P Weblogic administrator password
From that directory, run the download RPD command as follows:
/OBIEE_HOME/user_projects/domains/bi/bitools/bin/data-model-cmd.sh downloadrpd -O liverpd.rpd -SI ssi -U weblogic -P Admin123
This command will copy the RPD file to your directory. Upon running the command, it will prompt you to enter a password for this RPD file. It doesn’t ask you to confirm this, so make sure you know what you entered to avoid rerunning the command to download it again.
Step 2: Convert RPD to XML
Once downloaded, you will need to change directories in order to proceed with the conversion process using the steps below.
1. Change directories so you can run the script
2. Run the biserverxmlgen.sh script as follows:
./biserverxmlgen.sh –R /RPD_SAVED_DIRECTORY/liverpd.rpd –P Admin123 –O SampleAppRPD.xml –N –Q -8
3. This will create the XML file needed in this directory: /OBIEE_HOME/user_projects/domains/bi/bitools/bin
And you’re done! Hope this quick overview of how to download and convert the RPD file to XML in OBIEE 12c was helpful. Now you can utilize the converted XML for things like Oracle Enterprise Metadata Modeling and others.
By using this software script (“Script”), you are agreeing to the following terms and condition, as a legally enforceable contract, with Datavail Corporation (“Datavail”). If you do not agree with these terms, do not download or otherwise use the Script. You (which includes any entity whom you represent or for whom you use the Script) and Datavail agree as follows:
1. CONSIDERATION. As you are aware, you did not pay a fee to Datavail for the license to the Script. Consequently, your consideration for use of the Script is your agreement to these terms, including the various waivers, releases and limitations of your rights and Datavail’s liabilities, as setforth herein.
2. LICENSE. Subject to the terms herein, the Script is provided to you as a non-exclusive, revocable license to use internally and not to transfer, sub-license, copy, or create derivative works from the Script, not to use the Script in a service bureau and not to disclose the Script to any third parties. No title or other ownership of the Script (or intellectual property rights therein) is assigned to you.
3. USE AT YOUR OWN RISK; DISCLAIMER OF WARRANTIES. You agree that your use of the Script and any impacts on your software, databases, systems, networks or other property or services are solely and exclusively at your own risk. Datavail does not make any warranties, and hereby expressly disclaims any and all warranties, implied or express, including without limitation, the following: (1) performance of or results from the Script, (2) compatibility with any other software or hardware, (3) non-infringement or violation of third party’s intellectual property or other property rights, (4) fitness for a particular purpose, or (5) merchantability.
4. LIMITATION ON LIABILITY; RELEASE. DATAVAIL SHALL HAVE NO, AND YOU WAIVE ANY, LIABILITY OR DAMAGES UNDER THIS AGREEMENT.
You hereby release Datavail from any claims, causes of action, losses, damages, costs and expenses resulting from your downloading or other use of the Script.
5. AGREEMENT. These terms and conditions constitute your complete and exclusive legal agreement between you and Datavail.
The “ORA-12154: TNS:could not resolve the connect identifier specified” Oracle error is a commonly seen message for database administrators.
EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.
This blog reviews how you can generate scripts for SQL server logins, role assignments, and server permissions for a smooth migration.