Enable the quick publish target when creating the transaction server docker container

We need to rebuild the Transaction server Docker container...

• During initial setup

• If database information for the production environment has changed

Note that we can leverage Run Engine commands in the WebSphere Application Server to add a datasource for quick publish. We can use the add-datasource command in the Transaction server container.

Quick publish is not supported in WebSphere Commerce Developer.

Before beginning

To set up the transaction server with the quick publish target, have ready the following information about the production environment database:

• Database name

• Database user name (user ID)

• Database user password

• Fully qualified database server host name

• Database server port

Procedure

1. Open the WebSphere Integrated Solutions Console for our authoring server and select...
   Resources | JDBC Providers

2. Set the scope to the application server that contains WebSphere Commerce on your Authoring environment.

3. Click the JDBC provider for the quick publish target.

4. Click Data sources.

5. 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

6. Update the data source information for the quick publish target:

   • (AIX) (Linux) (Windows) (DB2) Change the value in the Database name field (under Common and required data source properties) to the name of the production environment database as cataloged on the authoring environment.

     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.

   • (IBM i) 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 environment 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 environment database.

        port

        Optional: The port used for database communication with the production environment 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.

   • (Oracle) Change the value in the URL field (under Oracle data source properties) to point at the production environment database.

     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 environment database.

     port

     The port used for database communication with the production environment database

     SID

     The Oracle SID of the production environment database.

7. Click OK and then save our changes to the master configuration.

8. Confirm the user ID and password 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 our changes to the master configuration.

9. Click Logout and follow any additional prompts.

   If we are prompted about unsaved changes, save the changes to the master configuration.

Related concepts
Authoring environment schema update tool

Related tasks
Enable Workspaces
Create an authoring environment
Synchronize an authoring environment with a production environment
Run the authoring environment update scripts on the WebSphere Commerce Server
Enable quick publish
Enable retry for quick publish
Enable e-mail notification for workspaces
Enable shopping flow preview for workspaces
Change workspaces locking policy

Related reference
Ant target: CM_updateWorkspacesTable
Ant target: CM_updateWorkspacesSchema
Troubleshooting: Update Workspace failing to update the workspace because of missing column for primary key