Updating the JDBC provider setting for the quick publish target

When database information for your production server changes, you must update the JDBC provider setting for the quick publish target.

WebSphere Commerce DeveloperNote: Quick publish is not supported in WebSphere Commerce Developer.

Before you begin

To update the JDBC provider setting for the quick publish target, have the following information about your production server database ready:

  • Database name
  • Database user name (user ID)
  • Database user password
  • Fully qualified database server host name
  • Database server port

You also need the name of the JDBC data source that is entered on the Staging page of the Instance Creation wizard when you created the authoring server instance.

Procedure

  1. Open the WebSphere Integrated Solutions Console.
  2. Select Resources > JDBC Providers.
  3. If necessary, set the scope to the application server that contains WebSphere Commerce on your Authoring server.
  4. Click the JDBC provider for the quick publish target.
  5. Click Data sources.
  6. Click the data source for the quick publish target. The required name for the data source is WebSphere Commerce DBMS_name Publish DataSource instance_name.
    For example, WebSphere Commerce DB2 Publish DataSource demo.
  7. Update the data source information for the quick publish target:
    • DB2AIXLinuxWindowsChange the value in the Database name field (under Common and required data source properties) to the name of the production server database as cataloged on the authoring server.
      Note: Ensure that you verify all the Common and required data source properties values:
      • Driver type value is 4
      • Server name is the fully qualified host name for the Production server
      • Database name and Port number must be accurate
      Make sure that the DB2 Universal data store helper class is selected.
    • For IBM i OS operating system Perform the following steps:
      1. Change the value in the Database name field (under DB2 UDB for iSeries (native or Toolbox) data source properties) to the name of the production server database.
      2. Click Custom properties.
      3. Click URL.
      4. Change the value in the Value field to point to the production database. The URL can have either of the following formats, depending on your JDBC driver:
        Native JDBC driver
        jdbc:db2://hostname:port:/ database_name jdbc:db2://hostname/ database_name
        IBM Toolbox for Java JDBC driver
        jdbc:as400://hostname:port:/ database_name jdbc:as400://hostname/ database_name
        Where:
        hostname
        The fully qualified host name of the machine hosting the production server database.
        port
        Optional: The port that is used for database communication with the production server database.
        database_name
        The name of the production database.
      5. Click OK.
      6. Return to the page for the data source for the quick publish target.
    • OracleChange the value in the URL field (under Oracle data source properties) to point at the production server database. Depending on the Oracle JDBC driver you use, the URL has the following format:
      Oracle thick JDBC driver
      jdbc:oracle:oci8:@hostname:port:SID
      Oracle thin JDBC driver
      jdbc:oracle:thin:@hostname:port:SID
      Where:
      hostname
      The fully qualified host name of the machine hosting the production server database.
      port
      The port used for database communication with the production server database
      SID
      The Oracle SID of the production server database.
  8. Click OK and then save your changes to the master configuration.
  9. Confirm the user ID and password that is required to access the production database:
    1. Select Resources > JDBC Providers.
    2. Click the JDBC provider for the quick publish target.
      For example, demo - WebSphere Commerce JDBC Provider for Publish.
    3. Click Data sources.
    4. Click the data source for the quick publish target. The default name for the data source is WebSphere Commerce DBMS_name Publish DataSource instance_name.
      For example, WebSphere Commerce DB2 Publish DataSource demo.
    5. Take note of the entry in the Component-managed authentication alias field. The default name for the authentication alias for the production database is WC_instance_name - authDataAlias for Publish
    6. Under Related Items, click JAAS - J2C authentication data.
    7. Click the entry that you noted earlier.
      For example, WC_demo - authDataAlias for Publish.
    8. Confirm that the User ID value is the correct user ID for the production database. If the user ID is not correct, change the user ID and enter the correct password for the user ID.
    9. Click OK and then save your changes to the master configuration.
  10. Click Logout and follow any additional prompts. If you are prompted about unsaved changes, save the changes to the master configuration.