Administer > Manage WebSphere Commerce features > WebSphere Commerce integration with WebSphere Portal > Configure WebSphere Portal with WebSphere Commerce
Configure the WebSphere Commerce Server cluster
Before you begin
Ensure the time difference between the Deployment Manager node and all the WebSphere Commerce cluster nodes is less than five minutes. If the time difference is greater than five minutes, adjust the system clock and restart all related Java processes.
Procedure
- Install WebSphere Commerce server and create an instance. Verify the required stores are published to the WebSphere Commerce server and that the store is working.
Use the Deployment Manager administrator user name and password for the WebSphere Commerce configuration manager. This can make simplify the WebSphere Commerce node federation, as if administrators are different, disable WebSphere Commerce global security and WebSphere Commerce security in the Configuration Manager to continue.
- Disable security from the Configuration Manager and WebSphere Application Server Administration Console for the newly created WCS instance.
- Optional: Create another node group for all WebSphere Commerce nodes using the Deployment Manager Integrated Solution Console.
- Restart the WebSphere Commerce server. Note the JMX RMI port number from the SystemOut.log when the server starts successfully.
- After the WebSphere Commerce is started, ensure that Administrative Security has been disabled by logging on to the WebSphere Application Server Administrative Console.
- Run the WebSphere Commerce integration wizard and complete the following task:
Enter the following values into the Integration wizard:
Integration wizard values
Field Value Realm Name defaultWIMFileBasedRealm WebSphere Application Server Primary Administrative User Deployment Manager user name WebSphere Application Server Primary Administrative User Password Deployment Manager user password
The background process issued from the WebSphere Commerce Integration wizard for enabling WebSphere Application Server security with Federated Repositories can take up to 30 minutes to complete.
- Stop the WebSphere Commerce server.
- From the node of the WebSphere Commerce server, federate a new managed node for WebSphere Commerce to the Deployment Manager.
This process can take from 15 minutes up to an hour of time. It is therefore important to disable the SOAP timeout on the WebSphere Commerce server profile. See Federate WebSphere Commerce for more information.
The following tasks are involved with federating WebSphere Commerce:
- Start the Deployment Manager.
- Update the addNode command from the WebSphere Commerce profile.
- Update the JVM setting of the Deployment Manager.
- Update the SOAP timeout from the WebSphere Commerce profile.
- Executing the addNode command with the includeapps option, now that the entire setup is using the cell-level security. For example: addNode DM_hostname DM_port -includeapps -username DM_wasuser -password DM_password
- Re-configuring the cell-level documents, such as web server mapping and virtual hosts with the WebSphere Application Server admin user name and password. For example: config_ant -DinstanceName=WCInstanceName ReconfigureCell -DWASAdminUser=DM_wasuser -DWASAdminPassword=DM_password
- Regenerate the web server plugins. After regenerating and propagating the web server plugin, ensure the WebSphere Commerce web server configuration file has the WebSphere Application Server plugin pointing to the cell level Web server plugin-cfg.xml file.
- Verify the node agent on the WebSphere Commerce server node is started.
- Optional: From the Deployment Manager Integrated Solution Console, assign the WebSphere Commerce node to the WebSphere Commerce node group, and then remove the WebSphere Commerce node from the WebSphere Portal default node group. See Add managed nodes for more information.
- From the Deployment Manager Integrated Solution Console, create a new cluster called CommerceCluster by converting the existing WebSphere Commerce server1 application server.