Take the following steps to brand the driver using the command line.

Note: For the Autonomous REST Connector: The branding described in this section requires the driver to be unlocked by the application. If the end users' application cannot be modified to pass the password, such as the case with a third-party application or BI tool, you may brand the driver by locking the API. See "Locking the Autonomous REST Connector to an API" for details.
Note: The MongoDB driver is used as an example in this topic. However, these instructions apply to all drivers listed in the introduction.
  1. At a command prompt, change to the directory containing the temporary installer and supporting zip files.
    Important: The installer directory must include the supporting installation zip files.
  2. Run the installer using the appropriate command.
    Important: If running the Java installer on Windows, you must either select a non-system directory as the installation directory or turn off User Account Controls.
    • Java installer: java -jar PROGRESS_DATADIRECT_JDBC_INSTALL.jar -i console
    • Windows installer: PROGRESS_DATADIRECT_JDBC_INSTALL.exe -i console
  3. The Introduction step appears. Press ENTER.
    Note: The installer prompts you to answer questions regarding the installation. To accept the default value, press ENTER. To return to the previous step, type back and press ENTER.
  4. The product license agreement appears. Press ENTER multiple times to page to the end of the agreement. At the end, you are asked to accept the agreement:
    • To accept the license agreement and continue with the installation, type Y and press ENTER.
    • To end the installation, type N and press ENTER.
  5. You are prompted for the installation directory.
    • Press ENTER to accept the default directory.
    • Type the full path to the installation directory and press ENTER. You are prompted to confirm the installation directory. If correct, type Y and press ENTER.
  6. You are prompted for the type of installation. Type 2 for a licensed or OEM install and press ENTER.
  7. You are prompted for the OEM IPE key (or Control Number) that was provided by Progress DataDirect. Type the OEM IPE key and press ENTER.
    Note: If you were issued multiple product keys, you can type them sequentially, separating the keys with a space. For example: xxxxkey1 xxxxkey2 xxxxkey3.
  8. The DataDirect Installer Customer Experience Improvement Program step appears. By choosing to participate in the program, you permit the installer to gather data about your installation, such as environment information and error details, that will be used to improve our products. Choose one of the following:
    • If you would like to participate in the program, enter 1.
    • If you do not want to participate in the program, enter 2.

    For more information about data collection, refer to the Progress Privacy Policy.

  9. You are prompted for the serial number provided by Progress DataDirect. Type the serial number and press ENTER.
    • If you are installing a 5.1.4 version of the product, skip to Step 12.
    • If you are installing a 6.0 version of the product, proceed to the next step.
  10. You are prompted to specify a branded or unbranded type of installation.
    • Type 1 to specify a branded installation, and skip to Step 12.
    • Type 2 to specify an unbranded installation, and proceed to the next step.
  11. The installer prompts you for product registration information. Enter the requested information; then, press ENTER and skip to Step 17.
  12. You are prompted for the vendor file prefix. Type the character file prefix (maximum of 2 characters) you registered on the Progress DataDirect OEM Partner website and press ENTER.
    This prefix is added to DataDirect file names. For example, if dx is your file prefix for the MongoDB driver, mongodb.jar becomes dxmongodb.jar.
    Note: The value dd is a reserved file prefix. Specifying this value returns an error.
  13. You are prompted for the vendor package prefix. Type a package prefix for the branded drivers (maximum of 64 characters) and press ENTER.

    To avoid package name conflicts, the package prefix should adhere to the package naming conventions defined in the Java Language Specification. The package prefix replaces the DataDirect prefix of com.ddtek in all the classes within the driver jar file when you brand a driver. For example, if com.xyzcompany.xyzdivision is your package prefix for the MongoDB driver, the MongoDB driver class:

    com.ddtek.jdbc.mongodb.MongoDBDriver

    becomes:

    com.xyzcompany.xyzdivision.jdbc.mongodb.MongoDBDriver
    Note: The value com.ddtek is a reserved package prefix. Specifying com.ddtek as part of this value returns an error.
  14. You are prompted for the vendor subprotocol prefix. Type a vendor subprotocol prefix and press ENTER.

    Progress DataDirect drivers are registered with a URL subprotocol of the form datadirect:drivername, for example, datadirect:mongodb. To replace datadirect in the subprotocol of a branded driver with your company name, type a prefix (maximum of 32 characters) in this field. For example, if xyzcompany is your subprotocol prefix for the MongoDB driver, the URL:

    jdbc:datadirect:mongodb://server1:27017

    becomes:

    jdbc:xyzcompany:mongodb://server1:27017
    Note: Contact Oracle to register JDBC subprotocol names.
    Note: The subprotocol cannot start with Progress DataDirect or contain datadirect. Specifying either of these reserved values returns an error.
  15. You are prompted for the vendor message prefix. Type a message prefix for the branded drivers (maximum of 32 characters) and press ENTER.

    After branding, driver error messages are displayed with this prefix. For example, if xyzcompany is your message prefix for the MongoDB driver, the driver error message:

    [DataDirect][MongoDB JDBC Driver] Object has been closed

    becomes:

    [xyzcompany][MongoDB JDBC Driver] Object has been closed
    Note: The message prefix cannot start with Progress DataDirect or contain datadirect. Specifying either of these reserved values returns an error.
  16. You are prompted for the vendor password. Type the password (maximum of 128 characters) you registered on the Progress DataDirect OEM Partner website and press ENTER.

    The password is case-sensitive. This password is locked into the branded drivers to prevent unauthorized applications from using the branded drivers.

  17. A pre-installation summary provides installation information. You are prompted to accept or change the information:
    • Press ENTER to accept the information and begin the installation.
    • To change the information, type back; then, press ENTER. You are prompted for the information again.
  18. After completion of the installation, a message appears indicating that you have installed the software successfully. This completes the installation. Press ENTER to exit the installer.

Refer to the installation log file for a record of any problems that may have occurred during the installation. See Installation Log File for details.