When database information for your production
server changes, you must update the JDBC provider setting for the
quick publish target.
Note: 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 entered on
the Staging page of the Instance Creation wizard when you created
the authoring server instance.
Procedure
- Open the WebSphere Integrated Solutions Console.
- Select .
- If necessary, set the scope to the application server containing
WebSphere Commerce on your Authoring server.
For more information, see .
- Click the JDBC provider for the quick publish target.
- Click Data sources.
- 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.
- Update the data source information for the quick publish
target:
- Click OK and then save your changes
to the master configuration.
- Confirm the user ID and password required to access the
production database:
- Select .
- Click the JDBC provider for the quick publish target.
For example, demo - WebSphere Commerce JDBC Provider
for Publish.
- Click Data sources.
- 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.
- 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
- Under Related Items, click JAAS
- J2C authentication data.
- Click the entry you noted earlier.
For
example, WC_demo - authDataAlias for Publish.
- 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.
- Click OK and then save your changes
to the master configuration.
- Click Logout and follow any additional
prompts. If you are prompted about unsaved changes, save the changes
to the master configuration.