Running the CDV tool

About this task

The Windows console displays WorkBench startup information. Do not close the console while the WorkBench is running. Closing the console closes the tool, and your work is lost.

To start the Configuration Data Versioning Tool:

Procedure

  1. Start the Sterling Order Management System Software Development and Deployment WorkBench. On Microsoft Windows, run the ydk.cmd script for Windows (ydk.sh for UNIX/Linux) from the <INSTALL_DIR>\bin directory.
  2. From the Sterling Order Management System Software Development and Deployment WorkBench menu, choose Tools > Deployment > Configuration Data Version Deployment. This opens the Configuration Data Version Tool Logon dialog box.
  3. Choose the Source button and enter the values appropriate for the source database. Then choose the Target button and enter the values appropriate for the target database.

    When you are finished, close the dialog box. The values you specified are saved automatically and persist from one session to the next.

    If you change the name of either source or target database, the transformation settings are lost. To get back your old transformation settings, revert to the old source and target database name.

    In the Source database and Target database windows, specify the applicable values as described in Table 1.

    Table 1. Configuration deployment tool logon dialog box
    Field Detail
    Name Specify a logical database identifier. For the source, specify the database you want to copy data from. For the target, specify the database to write the data to.
    className Specify the class name of your database driver as follows:
    • If using Oracle, set to: oracle.jdbc.OracleDriver
    • If using Db2, set to: com.ibm.db2.jcc.DB2Driver
    • If using PostgreSQL, set to: org.postgresql.Driver
    jdbcURL Specify the URL to connect to the database:
    • If using Oracle, set to: jdbc:oracle:thin:@<DatabaseServerHostname/IPaddress><TNSListenerPortNumber>:<DatabaseSID>.
    • If using Db2, set to: jdbc:db2://<Database Server Hostname>:<Port Number>/<Database name>.
    • If using PostgreSQL, set to: jdbc:postgresql://localhost:5432/omdb
    dbType Specify the type of database you are running. Enter it in all lower case, as shown:
    • For Oracle, specify oracle
    • For Db2, specify db2
    • For PostgreSQL, specify postgresql
    • For an XML datasource, specify xml
    folder If using an XML datasource, specify the complete path of the folder location for the XML files.
    httpurl Only applicable for the target database. Specify a URL for the application server whose data cache is to be refreshed after data is deployed into the target database. Use the syntax: http://<hostname/ip-address>:<port-number>/<Application>/interop/InteropHttpServlet, where <hostname/IP-address> is the server address where the application is running, <port-number> is the port on which the application is running, and <Application> is the name of the application; for example, smcfs.
    schema Specify the schema owner as follows:
    • If you are using Oracle or Db2 database, and the user you specify is different from the Sterling Order Management System Software schema owner, specify the owner of the Sterling Order Management System Software schema.
    user Specify the user name associated with the database.
  4. In the Logon dialog box, enter the passwords associated with the user names and Click OK.
  5. The Compare screen displays. Select a From Version Label and a To Version Label and click OK.

    The system compares the two database versions. Once the comparison is complete, the system displays the Comparison Results screen. The results are grouped by table name onscreen.

  6. To see the details for any record included in the results, right-click and select Details. The Conflict Details screen displays. Field descriptions are in Table 2 below.
    Table 2. Configuration deployment versioning tool conflict details
    Field Detail
    The first row displays the name of the entity which contains the conflict (for example, YFS_ORGANIZATION), type of the conflict (for example, Record has been modified), and user key (for example, DEFAULT).
    Name Displays the name of the attribute whose values caused the conflict.
    Expected Old Value Displays the old value that is expected in the target database.
    Actual Old Value Displays the old value that actually exists in the target database.
    New Value Displays the new value that is obtained due to the change in the source database.
    Previous Click this button to view the previous record.
    Next Click this button to view the next record.
    Close Click this button to close the Conflict Details window.
    Changed Displays the name of the changed attribute along with it's old value and new value.
    Unchanged Displays the name of the unchanged attribute along with its existing value.

    There are three types of changes that can be displayed:

    • Modifications: The Record Details screen displays with a list of changed and unchanged attributes. For changed attributes, the old value and the new value will be displayed. (The old value is the existing value on the target database; new value is the value of the obtained change from the source database.)
    • Insertions: The Record Details screen displays with a list of attributes and their values to be inserted.
    • Deletions: The Record Details screen displays with a list of attributes of the entity.

    You can scroll through the records by using the Previous and Next buttons. When you are done reviewing the details for a record, click Close.