downloadrpd command to download the repository used by the service instance.
This command downloads the repository from the Oracle Business Intelligence archive (BAR) file for the service instance. Oracle recommends working with the downloaded repository for offline diagnostic and development purposes such as testing, only. Note that in all other repository development and maintenance situations, you should use BAR to utilize BAR's repository upgrade and patching capabilities and benefits.
You execute the utility through a launcher script,
datamodel.sh on UNIX and
datamodel.cmd on Windows.
If the domain is installed in default folder then the location of the launcher script looks like the following:
datamodel.cmd on Windows
If the client install doesn't have domain names, the launcher script location is as follows:
See What You Need to Know Before Using the Command for more information.
downloadrpd command takes the following parameters:
downloadrpd -O RPDname [-W RPDpwd] -SI service_instance -U cred_username [-P cred_password] [-S hostname] [-N port_number] [-SSL] [-H]
O specifies the name of the repository that you want to download.
W specifies the password for the repository. If you do not supply the password, a prompt displays 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 specifies the name of the service instance.
U specifies a valid user's 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, a prompt displays for the password when the command is run.
S specifies 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 Oracle WebLogic ServerWebLogic 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. Use
-H or run
.sh without any parameters to display the help content.
datamodel.sh downloadrpd -O sampleapplite.rpd -SI bi -U weblogic -S server1.example.com -N 7777 -SSL
You can learn about the download and upload repository commands, and to the list and update connection pool, rename and delete users and application roles, list and update repository commands.
For either the Oracle BI EE installation or client installation, you must have Oracle BI EE BI Service Administrator privileges to run the command line utility and issue any of the commands.
Passwords in Commands
The commands provide options for including a user's password and a repository passwords. If you do not supply passwords, then you will be prompted for passwords when you run the command.
For security purposes, Oracle recommends that you include passwords in the command only if you are using automated scripting to run the command.
Trust Store Key File for SSL
WebLogic Server provides Secure Sockets Layer (SSL) support for encrypting data transmitted between WebLogic Server clients and servers, Java clients, Web browsers, and other servers. When using SSL, you must use the WebLogic Server's trusted keys file if the server is using a self-signed certificate. This is the case when a domain is first created, as the server's identity certificate is generated when the domain is created.
If you replace the WebLogic Server's default self-signed identity certificate with a certificate signed by a recognized signing authority, then the standard Java trusted certificate list validates it and the extra settings are not needed.
The location of the WebLogic Server's trusted key file is:
The default password for the
DemoTrust.jks file is:
The location of the trusted key file and its password are passed to the system properties
javax.net.ssl.trustStorePassword. For example,
java \ -Djavax.net.ssl.trustStore=$ORACLE_HOME/wlserver/server/lib/DemoTrust.jks \ -Djavax.net.ssl.trustStorePassword=DemoTrustKeyStorePassPhrase \ -jar bi-commandline-tools.jar <args…>
Upon installation, the data-model-cmd.sh and data-model-cmd.cmd scripts are delivered with the trusted key file locations included. For Oracle BI EE installations, you do not need to update the trusted key file locations.
For Oracle BI EE client installation, you must put the trusted keys file in the correct location. To do this, Oracle suggests that you copy and paste the files from the WebLogic Server to the proper location.
Hostname, Port Number, and Use of SSL
For Oracle BI EE installations, the command line utility by default queries the Oracle BI EE endpoint manager which provides the host name, port number, and whether SSL is available. Therefore for Oracle BI EE installations, the user does not need to include these options in the command.
For Oracle BI EE client installation, you must include the
S (Oracle BI EE host name),
N (Oracle BI EE port number), and
SSL (use SSL to connect to the WebLogic Server to run the command) options in the commands.