WebSphere Commerce federation
Federating your WebSphere Commerce environment requires WAS ND. After you federate, you can configure clustering.Federating WebSphere Commerce involves adding your WebSphere Commerce node to a cell managed by a WAS deployment manager. Federating has the following advantages:
- Manage multiple WebSphere Commerce instances from a single WebSphere Application Server Administrative Console.
- Allows you to cluster WebSphere Commerce. See the section on Clustering WebSphere Commerce.
After federating your stand alone WebSphere Commerce profile, the WAS Administrative Console for that profile is no longer accessible, and all administrative tasks are completed through the WAS ND Administrative Console. The WAS ND Administrative Console is a browser-based application, so it can be accessed from any machine.
For information on WAS clustering, refer to WAS documentation.
- AIX|Linux|Solaris|Windows:
- I5/OS:
Take note of the following considerations when federating WebSphere Commerce:
- Before federating WebSphere Commerce, it strongly recommended that you back up the WAS administrative configuration. Backing up the administrative configuration will allow you to restore the original configuration if federation fails during the federation process.
- AIX|Linux|Solaris|Windows:
- I5/OS:
- IBM recommends that you back up the entire profile.
- After federating WebSphere Commerce, all updates such as store publish go through the WAS Deployment Manager. For these functions to work properly your WAS Deployment Manager must be configured to accept the updated files for the application. By default WAS nodes are configured to automatically synchronize the applications when a change is made.
- AIX|Linux|Solaris|Windows:
- I5/OS:
Related Concepts
WAS ND clustering mechanism
Related tasks
Federating WebSphere Commerce
Change the process execution properties
Remove an application server node from a cell