Manually creating a quick publishing target on a staging server

You can readily export production customer segments from a production instance into an authoring instance. The required quick publish connection will have been automatically created during the creation of the authoring instance. You can also export from a production instance into a staging instance, as long as the quick publish connection has been manually created. Use the following steps to manually create the quick publish connection on a staging instance.

Before you begin

Back up the original createInstance.properties created when the Configuration Manager was used to generate the staging instance.

About this task

Procedure

  1. Back up the original createInstance.properties file created when the Configuration Manager was used to generate the staging instance. The properties file is found in the following directory:
    • AIXLinuxWindowsWC_installdir/instances/instance_name/properties/createInstance.properties.
    • For IBM i OS operating systemWC_userdir/instances/instance_name/properties/createInstance.properties.
  2. Edit the createInstance.properties file and fill in the values for the following properties. These properties are normally used by an authoring instance and are not by default defined in a staging environment. The following are examples; use the values that are appropriate to your system.
    • isContentManagement=true Allows the ANT scripts to run.
    • cmDBUserID=db2user This is the production DB user that will end up in the JaasAuthData.
    • cmTargetApp=WC_demo
    • cmDatasourceName=WebSphere Commerce DB2 Publish DataSource stage2 The name of the quick publish datasource that will be created in the staging environnment.
    • cmDatabaseType=db2 Database type of the production database.
    • cmDBName=WCDB Database name of the production database.
    • cmDbServerName=WC8MLG.acme.com - Server name of the production database.
    • cmDbServerPort=50000 Port of the production database.
    • cmJdbcURL=jdbc:db2://WC8MLG.acme.com:50000/WCDB JDBC URL of the production database.
  3. Run the following ANT scripts to generate the quick publish data source.

    1. config_ant.bat -buildfile WC_installdir/components/Workspaces/xml/configureWorkspaces.xml 
      -DinstanceName=stage -DcmDBUserPwd=password CreatePublishJaasAuthData 1>..\logs\ant1.CreatePublishJaasAuthData.log 2>&1
      Where:
      cmDBUserPwd
      The password for the production database user.
      instanceName
      The instance name for the staging instance.
      For more information, see Ant target: CreatePublishJaasAuthData.
    2. Run the WC_installdir\bin\config_ant.bat command (for Windows), or the WC_installdir/bin/config_ant.sh command (in Linux). For example, in Windows:
      config_ant.bat -buildfile WC_installdir/components/Workspaces/xml/configureWorkspaces.xml 
      -DinstanceName=stage CreatePublishJDBCProvider 1>..\logs\ant2.CreatePublishJDBCProvider.log 2>&1
      Where:
      instanceName
      The instance name for the staging instance.
      For more information, see Ant target: CreatePublishJDBCProvider.

    3. config_ant.bat -buildfile WC_installdir/components/Workspaces/xml/configureWorkspaces.xml 
      -DinstanceName=stage -DdbUserPassword=stage CreatePublishDataSource 1>..\logs\ant3.CreatePublishDataSource.log 2>&1
      Where:
      instanceName
      The instance name for the staging instance.
      dbUserPassword
      The password for the staging database user.
      For more information, see Ant target: CreatePublishDataSource.
  4. Restart the server, and test the JDBC connection in the WebSphere Application Server administration console.
  5. Copy the original Jar file, WC_profiledir\stage\installedApps\WC_stage_cell\WC_stage.ear\Enablement-BusinessContextEngineAdvancedInterface.jar, to a backup file at C:\temp\Enablement-BusinessContextEngineAdvancedInterface.jar.
  6. Follow steps 1 to 21 in Deploying J2EE assets for an entire module. In Step 15, on the Install new application screen, select Step 4: Map resource references to resources. Modify Target Resource JNDI Name to reflect the correct publishing data source. Select the correct datasource name from the pulldown (for example, WebSphere Commerce DB2 Publish DataSource (stageInstanceName).
  7. Restart the server.

What to do next

Test exporting your customer segment, following the procedure described in Exporting customer segment information.