Starting the CDT in GUI mode

Edit online

To ensure a satisfactory user experience, use the procedure that is described here when you start the CDT in GUI mode.

About this task

Consider the following before you begin:

  • Most preference settings are tied to a specific source and target database combination. If you change the name of either the source or target database, any existing settings are not used. To return to your old settings, revert to the old source and target database name.
  • To run the UI for the Configuration Deployment Tool on a UNIX server from a windows client, the UNIX server must have XWindows installed on it.
  • 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 Deployment 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 Deployment. This opens the Configuration Deployment 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.

    In a sharded environment, you must migrate each configuration group, one at a time. if you are migrating HUB Data and Organization Driven Configuration Data, these two configuration groups must be your sources. These groups are displayed in the Deployment Explorer and are provided as part of Sterling Order Management System Software.

    Figure 1. Deployment explorer source-target file system

    Your configuration data is in the HUB Data and Organization Driven Configuration Data groups, so the target for each of these should be the Configuration Schema. If you are migrating Organization Driven Master Data, the target should be the Master Data Schema. To migrate Metadata, the target should be the Metadata schema.

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

    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.
    httpuser Specify the user name associated with the application server whose data cache is to be refreshed after data is deployed into the target database.
    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.

    The Deployment Explorer window displays.