Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Administering
Configuring a cloned WebSphere Commerce environment
A cloned virtual environment creates a separate copy of the original web server, application server, and database. After you clone a WebSphere Commerce virtual environment, you need to configure the clone to differentiate from the original environment.
Updating JNDI bindings
In some cases, changing the host name requires updating some JNDI bindings. Review the current bindings and update as needed.

Updating JNDI bindings in a cloned environment

In some cases, changing the host name requires updating some JNDI bindings. Review the current bindings and update as needed.

Procedure

In the WebSphere Application Server admin client, select Environment > Naming > Name space bindings.
Select a binding.
For example, com.ibm.commerce.foundation.server.services.commerce.hostname
If the string value contains the old host name, update the value to the new webserver host name.
Repeat step 2 and step 3 for all configured bindings, including any bindings on the WebSphere Commerce search application.
For example, also update the com.ibm.commerce.foundation.server.services.search.hostname binding.
Save all changes.