Updating the quick publish target

If database information for your production server changes, you must update the quick publish target.

Note: By default, updating the quick publish target can only be done from within an authoring environment. If you want to use the quick publish feature from within a staging environment, you must create a quick publish target on the staging instance. For instructions on how to do this, see Manually creating a quick publishing target on a staging server.

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

Before you begin

To update 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 will also need the name of the JDBC data source entered on the authoring page of the Configuration Manager when you originally created the authoring server instance.

Procedure

If you have not done so, prepare the authoring server to connect to the production database:
1. Install a database client suitable for communication with your production database.
2. Catalog the remote production database on the authoring server so that is accessible from your authoring server.
Update the WebSphere Application Server settings for the JDBC providers for the production database.
Update the WebSphere Commerce settings:
1. Open the WebSphere Commerce configuration file in a text editor.
2. Find the ManagedFileUpdateEARConfiguration tag.
3. The ManagedFileUpdateEARConfiguration tag resembles the following text:
```
<ManagedFileUpdateEARConfiguration display="false">
   <ContentManagedFileEARUpdate Implementation="com.ibm.commerce.filepublish.util.ContentManagedFileEARUpdateImpl" />
   <ContentManagedFileHandler Implementation="com.ibm.commerce.filepublish.util.ContentManagedFileHandlerImpl" />
   <ProductionServerInformation applicationName="wcs_demo" />
   <ModuleInformation moduleName="Stores.war" />
   <EvaluationCriteria minNumOfFilesForUpdate="10"
                       minSecFromLastUpload="3600" />
</ManagedFileUpdateEARConfiguration>
```
4. Update the ProductionServerInformation and ModuleInformation elements:
  
  ProductionServerInformation
  
  Specify the WebSphere Commerce application name on the production server in the applicationName parameter. The WebSphere Commerce application name is WC_enterprise_application.
  
  ModuleInformation
  
  Specify the module name for your store in the moduleName parameter. The usual name for the stores module name is Stores.war. This name is unlikely to change unless you have extensive customization.
5. Save your changes.
6. Propagate your changes to the WebSphere Commerce configuration file.
Stop and restart the authoring server instance.