WebSphere Extended Deployment provides support in the WebSphere
Commerce Server environment. This topic describes setting up WebSphere Extended
Deployment with WebSphere Commerce server. This topic sample topology of WebSphere
Commerce in an Extended deployment environment, the installation of Extended
deployment and WebSphere Commerce, and how to configure Extended deployment
to enhance WebSphere Commerce.
Before you begin
Ensure the following before you begin:
- Be consistent in installation paths across nodes to simplify configuration.
- Create the necessary system user IDs as required by WebSphere Commerce.
- Use database user IDs consistently, especially on AIX operating systems.
Be aware of the wasuser/wasgroup user
rights requirement. The profiles directory must be owned by wasuser/wasgroup.
The wcnonroot.sh script is available to assist in correcting
permissions.
- Before installing each component or fix pack, stop all Java processes.
- If you install any non-Express edition, install the WebSphere Application
Server Version 6.0.2 fix pack before creating a Commerce instance.
- When you are federating a node, the addNode command might require a large
Java virtual machine (JVM) heap size. The JVM heap size might need to be increased
on either the Deployment Manager or the Application Server node.
- When publishing a store the WC_demo.ear directory
that holds the WebSphere Commerce application is updated with store configuration
files. These files must be copied to the Web Server node manually.
- Install the DB2 Administration Client on the Deployment Manager if you
want to be able to test DB2 connections from the administration console or
perform database administration from the machine. You must also catalog the
database.
Procedure
- To install the WebSphere Application Server Deployment Manager,
perform the following steps:
- Install the Deployment Manager on a separate machine from other servers
and nodes.
- Run the installation of WebSphere Application Server Network Deployment.
- When prompted to create a profile, choose the Deployment Manager profile.
- Install any necessary WebSphere Application Server fix packs.
- Install WebSphere Application Server Extended Deployment.
- Install any WebSphere Application Server Extended Deployment fix packs
necessary.
- Install DB2 Administration Client.
- To install the ODR node, perform the following steps:
- The ODR must be a separate machine from other servers and nodes for performance
and security reasons.
- Install WebSphere Application Server Network Deployment.
- When prompted to create a profile, choose the Application Server profile.
- Install any necessary WebSphere Application Server fix packs.
- Install WebSphere Application Server Extended Deployment.
- Install any necessary WebSphere Application Server Extended Deployment
fix packs.
- Start the Deployment Manager.
- Federate the ODR node to the Deployment Manager.
- To install the Web Server node, perform the following steps:
- The IBM HTTP Server is the typical Web Server installed with WebSphere
Commerce.
- The Web Server node must on a separate machine from other servers and
nodes for performance and security reasons.
- Install the IBM HTTP Server 6.0 that is included with the WebSphere Application
Server.
- Install any necessary IBM HTTP Server fix packs.
- Install the IBM HTTP Server 6.0 WAS plug-in that is included with the
WebSphere Application Server.
- Install any necessary IBM HTTP Server WAS Plugin fix packs.
- The IBM HTTP Server must now be configured for the clustered environment.
- Install WebSphere Extended Deployment for Mixed
Server Environment to enable monitoring of the Web Server node.
- To install the database server node, perform the following steps:
- DB2 is the typical database installed with WebSphere Commerce.
- The database node can be vertically stacked with a WebSphere Commerce
Server node, but is not recommended.
- Install DB2 Enterprise Server Edition.
- Install any necessary DB2 fix packs.
- Optionally, install WebSphere Extended Deployment
for Mixed Server Environment to enable monitoring of the Database node.
For more information, refer to the DB2 documentation.
- To install the WebSphere Commerce Server node, perform the following
steps:
- Each WebSphere Commerce Server node services requests forwarded to it
by the ODR.
- WebSphere Commerce Server nodes can be vertically stacked if appropriate.
- Run the installation of WebSphere Application Server Network Deployment.
- When prompted to create a profile, choose the Application Server profile.
- Install any necessary WebSphere Application Server fix packs.
- Install WebSphere Application Server Extended Deployment.
- Install any necessary WebSphere Application Server Extended Deployment
fix packs.
- Install DB2 Administration Client. Catalog the database server node.
- Install WebSphere Commerce. The following command is required setup.exe
-W override.enableWAS6=true
- Choose custom installation and install WebSphere Commerce.
- Launch the WebSphere Commerce Configuration Manager. Create the demo instance.
Choose manual configuration for Web Server.
- Start the deployment manager.
- Federate the WebSphere Commerce Server node to the deployment manager,
using the -includeapps option.
- AIX: Launch the deployment manager console. Change the WebSphere Commerce
Server nodeagent process execution to start as wasuser / wasgroup.
Change the WebSphere Commerce Server WC_demo process execution to start as wasuser
/ wasgroup. Change the WebSphere Commerce Server WC_demo JVM arguments
to include -Xss5m. Store publish fails if this is not done.
- To add more WebSphere Commerce Server nodes, see: Adding WebSphere Commerce Server nodes
.