OBIEE 10G/11G - BI Server Command-line Utilities

You can use a variety of command-line utilities with the Oracle BI Server to make programmatic changes to your repository file, run sample queries, delete unwanted repository objects, and perform other tasks.

OBIEE have several executables files which permit you to automate some actions.

In 11g, before running any of the Oracle BI Server command-line utilities, you must first run bi-init.cmd (or bi-init.sh on UNIX)

Utility	11G	Description	Note
nqcmd.exe	nQcmd.exe	-	To run queries against other ODBC data sources than the Oracle BI Server.
OBIEE 11G/10g - Connection Pool Password Change	10G/11G	Utility to change the passwords	-
nqsecudmlgen.exe	nQSecUDMLGen.exe	-	-
nqsshutdown.exe	nQSShutDown.exe	Utility to shut down the Oracle BI Server	-
nqudmlcli.exe	nQUDMLCli.exe	-	-
nqudmlexec.exe	nQUDMLExec.exe	udml Executor	This command line tool can modify the RPD file by combining the fragment you define in the UDML file with the input repository and generate a output repository.
nqudmlgen.exe	nQUDMLGen.exe	udml Generator	can generate the entire repository in a text format
SchConfig.exe	SchConfig.exe	-	You may use the schconfig utility to configure Oracle BI Scheduler.
schshutdown.exe	SchShutdown.exe	-	-
-	SASchInvoke.exe	-	-
admintool.exe	admintool.exe	-	-
nqlogviewer	-	-	-
patchrpd	11G	Used to generate and apply an XML patch file. This utility is especially useful for patching repository files on Linux or UNIX systems
prunerpd	11G	Used to delete unwanted repository objects from your repository file, such as databases, tables, columns, initialization blocks, and variables.
sametaexport	11G	Used to exchange metadata (dimension, hierachy) with the Oracle Database and DB2
extractprojects	11G	Used to extract projects from a given repository.
equalizerpds	10G/11G	Used to equalize objects
nqgenoldverrpd	11G	Repository Downgrade utility
XML utilities (11G) Used to leverage the Oracle BI Server XML API
biserverxmlgen	11g	generates XML from an existing RPD
biserverxmlexec	11g	executes the XML in offline mode to create or modify a repository file
biserverxmlcli	11g	executes the XML against the Oracle BI Server

Where are they located ?

OS	Directory 10G	Directory 11G
Windows	OracleBI_HOME\server\Bin	ORACLE_HOME\bifoundation\server\bin
Unix	$INSTALLDIR/Bin

-Asifkhan P.

Agents (or iBots) in OBIEE 11g

Oracle BI delivers:

• Oracle BI delivers are useful to create schedules (or) Agents.
• Automates Business Intelligence
• Creates alerts based on Business Intelligence results
• Detects specific results and immediately notifies the appropriate person or group through Web, wireless, mobile, and voice communications channels.

1) Configuring scheduler tables:

• In 11g configuring of Oracle BI Scheduler Server will be done with the installation Of OBIEE 11g product [in 10g it is manual process]
• Scheduler tables by default created in a schema DEV_BIPLATFORM with installation of RCU(Repository Creation Utility).

2) Scheduler tables are

• S_NQ_JOB
• S_NQ_JOB_PARAM
• S_NQ_INSTANCE
• S_NQ_ERR_MSG

3) Creating delivery device:
Device will be created by each & every user his own

Process:
1) Login to Analytics by using weblogic user
2) Click on weblogic --> click on my account --> click on delivery options --> Click
on Create Device --> name : Testing --> Device Type : HTML
Email --> Adress/Number xyz@gmail.com --> Click on ok

4) Develop a Agent:

Process:
click on New --> under Actionable Intelligence --> click on Agent --> click on
Schedule tab --> select frequency as once --> click on select date & time --> give
10 mins forward from current time --> select Delivery Content tab --> select
Analysis --> click on browse --> select agent report --> click on ok --> Save into
Shared Folder folder with the name of first agent

Other Related Posts:
Find the Status of the iBot Develiry through Back-End Table


-Asifkhan P.

Configure Write Back In OBIEE 11g

  Write back is a feature that allows users to type values into the dashboard and then copy them back to the underlying source database.

Follow the steps to enable it in your environment......

Step1: Enable Writeback at system level.

Add the following line between the tags <WebConfig> and </WebConfig> in the instanceconfig.xml located under $INSTANCE_HOME/config/OracleBIPresentationServicesComponent/coreapplication_obips1:

<LightWriteback>true</LightWriteback>

Step2: Create Template for write back.

Create your own xml for your report and save the file in below location with any name with .xml format.
Path: $INSTANCE_HOME\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\customMessages

Sample File :  emp.xml

<?xml version="1.0" encoding="utf-8" ?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web/message/v1">
   <WebMessageTable lang="en-us" system="WriteBack" table="Messages">
      <WebMessage name="SetWriteBackValue">
         <XML>
            <writeBack connectionPool="OBIEEDB_POOL">
              <update>UPDATE SCOTT.EMP SET SAL=@2 WHERE ENAME='@1'</update>
    </writeBack>
         </XML>
      </WebMessage>
   </WebMessageTable>
</WebMessageTables>


Note: OBIEE 11.1.1.5 and above versions already has a template SQL for write back under above location with name writebacktemplate.xml. 


Step 3 : Give the permissions
check and give the write back permissions to the user in Analytics->Administration> Manage Privilege as shown below:

Step 4:  Enable Writable option at logical column level.

Step 5 : Allow Execute Direct Database Requests to the user.

Step 6 : Bounce your OBIPS and OBIS to reflect your changes.

Step 7 :  Now create report with ENAME, SAL columns and go to SAL column properties --> Write Back tab --> and select Enable Write Back check box.

Step 8 :  Finally edit table view properties and check the tab 'Enable write back'.In the template name field,make sure that you have provided the SetWriteBackValue  as documented in WebMessage Tag in emp.xml file

Step 9 :  Then click Update , modify values and click Apply  button. That set, updated values should have gone to database , if you have done above steps correctly :).

Other Related Posts : 
Write-Back Limitations in OBIEE 11G
OBIEE 11g: Writeback Done Button Does Not Refresh Data Displayed


-Asifkhan P.

OBIEE 11g: Writeback Done Button Does Not Refresh Data Displayed

Today I faced this issue in 11g....

After implementing writeback, data is not refreshing at front-end (i.e. report or dashboard), but data is updated in database. To get updated data, we need to purge OBIPS and OBIS cache.

This is a bug in OBIEE 11g, here is metalink prof....


APPLIES TO:

Business Intelligence Server Enterprise Edition - Version: 11.1.1.5.0 [1308] and later   [Release: 11g and later ]
Business Intelligence Suite Enterprise Edition - Version: 11.1.1.5.0 [1308] and later    [Release: 11g and later]
Information in this document applies to any platform.

SYMPTOMS

In OBIEE 10g, after you click on the Update button you could see the results of the writeback in the dashboard. Now, in 11g it does not seem to refresh. You can see the new data in the database but not in the dashboard.

CAUSE
This is expected behavior in 11g. In 11g dashboards do partial refresh because it's more efficient. 

SOLUTION
A dashboard page refresh (from top right Page Options) refreshes all the dashboard's content and shows the new data. 

There is an enhancement request to re-introduce the functionality of OBIEE 10g.  For more information see Bug 13058029 - write back auto-refresh in 11g.

Other Related Posts : 
Configure Write Back In OBIEE 11g
Write-Back Limitations in OBIEE 11G

-Asifkhan P.

OBIEE 11G: Setting Loopback Adaptor

A pre-requisite for installing OBIEE 11g is configuring a Loopback Adapter. The Loop back adapter assigns the system(server) a Static IP. If a static address is not assigned there will be issues in starting OPMN services, should the IP change for some reason. Give below are the steps for configuring the loop back adapter on a Windows 32 bit system :

1. Opening Device Manager

   a. Click Start

   b. Right click on My Computer and select Properties 

   c. From the left pane, click on Device Manager

   d. In the new Device Manager window, select Network Adapters

2. Adding new Hardware 

    a. In the Device Manager window, click Action

    b. From the dropdown, click Add Legacy Hardware

    c. In the new pop-up screen click Next

    d. Choose Install the Hardware manually option and click Next

    e. Select Network Adapters from the list and click Next

    f. On the screen choose Microsoft on left side and Microsoft loopback adapter on right and click next

    g. Wait for the hardware installation to complete

    h. Click Finish to close the wizard? 

3. Setting up the Static IP
   a. Click Start and click on Control Panel
   b. Click and open Network and Sharing center
   c. Click on Change adapter Settings on the left pane? 
   d. Select the newly created Microsoft Loopback Adapter (can be identified from the 3rd line text) 
   e. Right Click and click Properties
   f. Select Internet Protocol Version 4(TCP/IPv4) and click on Properties button
   g. Select “Use the following IP address” and specify the IP address to be used. Oracle recommends the following non-routable addresses 
· IP Address: 10.10.10.10 or 192.168.x.x (x is any value between 0 and 255)
· Subnet mask: Enter 255.255.255.0
· Leave all the other fields empty 

4. Adding the IP to the Hosts File
   a. Open Windows Explorer
   b. Navigate to the Windows directory (generally “C:\Windows\System32\drivers\etc)
   c. Double Click to Open the Hosts File
   d. In the end, add the Static IP used in step 3g along with Machine and domain name

Format: 
 Loopback_adapter hostname.domainname hostname
 ex:   10.10.10.10   mycomputer.mydomain.com   mycomputer

OBIEE 10G/11G - How to get forgotten RPD password?

In OBIEE 10g, If you forgot the repository (RPD) password, we can easily get it with simple configuration change (AUTHENTICATION_TYPE = BYPASS_NQS) in NQSConfig.ini file.This was a security breach in OBI 10g versions and it didn’t have had fix for it. But it is a very dangerous security breach. If anyone gets the production RPD, he can simply bypass the rpd security and can deploy it to see the valuable data. As the OBI rpd doesn’t require someone to know the production Database password, the information theft is quite possible.

So unlike OBIEE 10G, The newer OBIEE 11G has a very tight security i.e. TWO level key authentication to open a RPD in online mode and one key (RPD password) in offline mode. Either of the modes cannot open the repository with some configuration changes. So be careful if you want to reuse the OBI repository, make sure that you have memorized the RPD password.  There is NO any reset process.

But however, you can get a password for an already deployed RPD. With the help of wlst script, you can get the forgotten OBI Repository password that is deployed earlier.

To know forgotten OBIEE11G Repository (RPD) password:

Login to weblogic EM (http://localhost:7001/em) and navigate to credentials store page.

Expand the key map: oracle.bi.enterprise. This is the key map which stores all the repository passwords that are deployed.

I would like to show you how to know the forgotten password of a deployed repository.From the list, to get the password of “SampleAppLite_BI0019” repository, follow these steps:

Open command prompt

C:\Users\asif>cd C:\Oracle\Middleware\oracle_common\common\bin

C:\Oracle\Middleware\oracle_common\common\bin>wlst.cmd

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

wls:/offline> connect("weblogic","weblogic$123","localhost:7001")
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'bifoundation_domain'.

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

wls:/bifoundation_domain/serverConfig> listCred("oracle.bi.enterprise","repository.SampleAppLite_BI0019")
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)

[Name : tempvalue, Description : null, expiry Date : null]
PASSWORD:Admin123
wls:/bifoundation_domain/serverConfig>

Hope this help you :)

Authentication: External table authentication:

You can maintain lists of users and their passwords in an external database table and use this table for authentication purposes. The external database table contains user names and passwords, and could contain other information, including group membership and display names used for Oracle BI Presentation Services users. 

External table authentication uses session variables that you define using the Variable Manager in the Administration Tool.

Session variables get their values when a user begins a session by logging on. Certain session variables, called system variables, have special uses. The variable USER is a system variable that is used with external table authentication.

To set up external table authentication:

1. Import information about the external table into the Physical layer.
2. Select Manage, then Variables in the Administration Tool to open the Variable Manager.
3. Select Initialization Blocks in the left pane.
4. Right-click in the right pane and select New Initialization Block.
5. In the Initialization Block dialog box, enter a name for the initialization block.
6. Select Database from the Data Source Connection list.
7. Click Browse to search for the name of the connection pool this block uses.
8. In the Initialization String area, enter the SQL statement that is issued at authentication time.
   The values returned by the database in the columns in the SQL statement is assigned to variables. The order of the variables and the order of the columns determines which columns are assigned to which variables. Consider the SQL in the following example:
   

   SELECT username, grp_name, SalesRep, 2 FROM securitylogons WHERE username = ':USER' and pwd = ':PASSWORD'
   

   This SQL contains two constraints in the WHERE clause:
   
   • :USER (note the colon) equals the name the user entered when logging on.
   • :PASSWORD (note the colon) equals the password the user entered.
   The query returns data only if the user name and password match values found in the specified table.
   You should test the SQL statement outside of the Oracle BI Server, substituting valid values for :USER and :PASSWORD to verify that a row of data returns.
9. If this query returns data, then the user is authenticated and session variables are populated. Because this query returns four columns, four session variables are populated. Create these variables (USER, GROUP, DISPLAYNAME, and LOGLEVEL) by clicking New in the Variables tab.
   If a variable is not in the desired order, click the variable you want to reorder and use the Up and Down buttons to move it.
10. Click OK to save the initialization block.

Test it by login in the analytics.

Order of Authentication:

First request goes to LDAP for authentication. If it failes then then request will go for External tables.

SSO integration with OBIEE

Steps to enable SSO with OBIEE. 

Environment details ...
SSO version:  v1.2
OAS version 10.1.3.3.0
OBIEE version 10.1.3.4.1

I.  Partner Application Registration:

Register the http://xyz.company.com/  url as parner application, then generate osso.conf file using iasobf command.

Eg: $ORACLE_HOME/Apache/Apache/bin/iasobf osso.txt osso.conf root

II. Application Server Side Changes:

 Then copy osso.conf fileplace the file under $ORACLE_HOME/Apache/Apache/conf/osso directory.

mod_osso.conf  Changes :

a.      To statically protect the application URL, add the following to $ORACLE_HOME/Apache/Apache/conf/mod_osso.conf in between <IfModule mod_osso.c>.

<Location /analytics>

    Header unset Pragma

    OssoSendCacheHeaders off

    require valid-user

    AuthType Basic

</Location>

2. Also make sure  OssoConfigFile is there and pointing to right osso.conf file.

           Eg: OssoConfigFile /sxrpam/oas/product/10.1.3.1/OracleAS_1/Apache/Apache/conf/osso/osso.conf

httpd.conf Changes :

1. Uncomment following fine in …./conf/ httpd.conf and make sure it is pointing right mod_osso.conf file.

include "/sxrpam/oas/product/10.1.3.1/OracleAS_1/Apache/Apache/conf/mod_osso.conf"

2. Make sure the Servername parameter in httpd.conf is set to machine alias name
   ServerName xyz001.domain.com

3. Give ServerName as url and port within <VirtualHost *:*> tag.

<VirtualHost *:*>

  ServerName xyz.company.com

  Port 80

 </VirtualHost>

III. OBIEE Side Changes 

To enable SSO Authenication for Oracle BI Presentation Server

Step 1:  Create the Oracle BI Server Impersonator User:

1 Open the Oracle BI Server repository file (.rpd) using Oracle BI Administration Tool.

2  Select Manage > Security to display the Security Manager.

3  Select Action > New > User to open the User dialog box.

4  Enter a name and password for this user.

     For example, Name = Impersonator and Password = secret

5 Click OK to create the user.

6 Make this user a member of the group Administrators.

Step 2:  Add Impersonator user credentials to Oracle BI Presentation Services Credential Store:

1 Open a command prompt window or command shell on the machine where Oracle BI Presentation Services has been installed.

2 Navigate to the directory OracleBI_HOME\web\bin on Windows.  This is the location for the CryptoTools utility.

3 Execute the CryptoTools utility to add the impersonator user credentials to the Oracle BI

Presentation Services Credential Store:

Syntax:

             cryptotools credstore -add -infile <OracleBIData>/web/config/credentialstore.xml

Eg:

            cryptotools credstore -add –infile <OracleBIData>/web/config/credentialstore.xml

>Credential Alias: impersonation

>Username: Impersonator

>Password: Impersonator

>Do you want to encrypt the password? y/n (n): secret

>Passphrase for encryption: Impersonator

>Do you want to write the passphrase to the xml? y/n (y):

Step 3:  Configure the Oracle BI Presentation Services to identify the Credential Store and decryption passphrase.    (Updates instanceconfig.xml file)

1 Open the instanceconfig.xml file for editing.

2 Locate the <CredentialStore> node within this file.

Specify attribute values as shown below. If the <CredentialStore> node does not exist, create

this element with sub-elements and attributes with attribute values as shown in the following

example.

<WebConfig>

<ServerInstance>

<!-- other settings ... -->

<CredentialStore>

<CredentialStorage type="file" path="/OracleBIData/web/config/credentialstore.xml" passphrase="secret"/>

</CredentialStore>

<!-- other settings ... -->

</ServerInstance>

</WebConfig>

Step 4:  Configure BI Presentation Services to operate in SSO environment: (Also updates instanceconfig.xml file). In environments where Single Sign-On (SSO) is enabled, you can configure log out and log on links to appear on Oracle BI Presentation Services screens.

1 Open instanceconfig.xml for editing. Locate the <Auth> element. If this does not exist, create

this element, sub-elements and parameters as shown in the following example:

<!-- other settings ... -->

<Auth>

<SSO enabled="true">

<ParamList>

<Param name="IMPERSONATE" source="serverVariable" nameInSource="REMOTE_USER"/>

</ParamList>

<LogoffUrl>https://ls_logout </LogoffUrl>

<LogonUrl>https://ls_login </LogonUrl>

</SSO>

</Auth>

<!-- other settings ... -->

Multi User Development Environment (MUDE)

The Multiuser Development feature enables over one hundred development users to work in parallel on a shared, enterprise repository. 

Setup of MUDE

We have 3 steps
1. Creating projects.
2. Copy RPD into shared path & rename RPD.
3. Define multi user directions.

Step 1: Creating Projects

1. A piece of RPD is called as project.
2. RPD will be divided into projects based on Business Model or subject area.
3. On one project two or more members can work.
Process:
Open RPD in offline mode --> Go to manage menu -->  Click on projects -->  Click on
action menu --> Click on new project -->  name it as sales -->  Expand Business Models
-->  expand subject area supplier sales -->  select sales fact --> Click on add -->  expand
presentation -->  select supplier sales -->  Click on add -->  Click on ok

Step 2: Creating a shared folder and moving RPD into shared folder

1. Create a shared folder in C:\Documents and Settings\All Users\Documents with
the name of SHARED_RPD
2. Copy above RPD from repositories folder to C:\Documents and Settings\All
Users\Documents\ SHARED_RPD
3. Rename RPD in shared_rpd folder as shared.rpd

Step 3: Define Multi user directory

Go to administrator tool -->  tools menu -->  Click on options -->  Under "Multiuser development directory" --> Click on browse and
point it to C:\Documents and Settings\All Users\Documents\ SHARED_RPD -->  provide
some name as RRITEC(we can provide any name ) -->  Click on ok

Using MUDE Environment :

In using we have below steps.
1) Check out.
2) Change metadata.
3) Publish.
4) Move RPD from shared folder to repository folder.
5) Test.

Step 1: Check out

1. Open administration tool -->  go to file menu --> go to multi user --> Click on
check out --> repository password Click on ok --> name it as
USER1RPD --> save
2. open another instance of administration tool --> go to multi user --> Click on
check out --> password: --> name it as USER2RPD -->save.

Step 2: Change Metadata

1. In USER1RPD --> Right click on sales facts fact table --> click on new object -->
Click on logical column --> name it as user1_column --> click on column source
--> select Derived from existing columns using an expression -->type 1 -->
Click on ok
2. Drag and drop into presentation layer sales facts --> save.
3. In USER2RPD -->Right click on sales facts fact table --> click on new object -->
Click on logical column --> name it as user2_column --> click on column source
--> select Derived from existing columns using an expression --> type 2 -->
Click on ok
4. Drag and drop into presentation layer sales facts --> save.

Step 3: Publish

1. In USER1RPD -->Go to file menu --> Click on multi user -->Click on publish to
network
2. In USER2RPD --> Go to file menu --> Click on multi user --> Click on publish to
network

Step 4: Move RPD from shared folder to repository folder

1. Copy RPD from shared folder C:\Documents and Settings\All Users\Documents\SHARED_RPD to repository folder C:\OBI11g.6\instances\instance2\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository

-Asifkkhan P.

Comparing Repositories Using the Compare Dialog and comparerpd

Comparing Repositories Using the Compare Dialog

This section explains how to use the Compare dialog in the Administration Tool.

To compare two repositories:

1. In the Administration Tool, open a repository in offline mode.
   The repository that you open in this step is referred to as the current repository. 
2. From the File menu, select Compare.
3. In the Select Original Repository dialog, select the repository you want to compare to the open repository. Select Repository from the submenu to select a binary repository file in RPD format, or select XML to select a set of MDS XML documents.
4. In the Open Offline dialog, enter the repository password and click OK.
5. Use the Compare repositories dialog to review the differences between the two repositories.
   Compare Repositories Dialog

   
   
   
   
   
   Compare Repositories Dialog: Change Column

   Change	Description
   Created	Object was created in the current repository and does not exist in the original repository.
   Deleted	Object exists in the original repository but has been deleted from the current repository.
   Modified	Object exists in the original repository but has been modified in the current repository.

   
   
   Compare Repositories Dialog: Buttons

   Button	Description
   Filter	Opens the Comparison Filter dialog to enable you to filter the objects that appear in the Compare repositories dialog by type of change and type of object. You can specify what you want to appear and what you want to be hidden. If you select Group created and deleted objects, the tool filters out the child objects of created and deleted objects, so that only the parent objects are shown. By default, all items are shown.
   Find	Search by an object Name and Type (such as Initialization Block).
   Select	Enables you to select a repository to compare with the current repository. Select Repository from the submenu to select a binary repository file in RPD format, or select XML to select a set of MDS XML documents.
   Find Again	Search again for the most recent Find value.
   Diff	Differences between the current repository and the original repository.
   Save	Saves a list of the differences between the two repositories.
   Stats	Provides the number of changes by Change type.
   View 1	Opens an object in the original repository in read-only mode.
   Edit 2	Opens an object in the current repository in read/write mode.
   View 2	Opens an object in the current repository in read-only mode. This button is only displayed when viewing MUD history, or when the current repository is open in read-only mode.
   Equalize	Opens the Equalize Objects dialog so that you can model changes to the Upgrade ID of the objects.
   Create Patch	Creates a patch file that contains the differences between the repositories.
   Mark	Marks the object you select. Boxes appear around created and modified objects. To remove marks, from the File menu, choose Turn off Compare Mode.

Comparing Repositories Using comparerpd

You can also compare repositories and create patch files using the comparerpd utility. This feature is especially useful when you want to compare repositories or generate patches on Linux and UNIX systems where the Administration Tool is not available. The compare utility is available on both Windows and UNIX systems.

Before running comparerpd, you must first run bi-init to launch a command prompt or shell window that is properly initialized.

Syntax 

The comparerpd utility takes the following parameters:

comparerpd [-P modified_rpd_password] -C modified_rpd_pathname 
[-W original_rpd_password] -G original_rpd_pathname {-O output_csv_file_name | 
-D output_patch_file_name | -M output_mds_xml_directory_name} -E -8

Where:

-P modified_rpd_password is the repository password for the modified repository, also called the customer or customized repository.

-C modified_rpd_pathname is the name and location of the modified repository.

-W original_rpd_password is the repository password for the original repository.

-G original_rpd_pathname is the name and location of the original repository.

-O output_csv_file_name is the name and location of a csv file where you want to store the repository object comparison output.

-D output_patch_file_name is the name and location of an XML patch file where you want to store the differences between the two repositories.

-M output_mds_xml_directory_name is the top-level directory where you want to store diff information in MDS XML format. 

For example:

comparerpd -C customer.rpd -G original.rpd -O diff.csv
Give password for customer repository: my_cust_password
Give password for original repository: my_orig_password

This example generates a comparison diff file in CSV format called diff.csv from the customer.rpd and original.rpd repositories.

comparerpd -C customer.rpd -G original.rpd -D my_patch.xml
Give password for customer repository: my_cust_password
Give password for original repository: my_orig_password

This example generates an XML patch file called my_patch.xml from the customer.rpd and original.rpd repositories.