Home | Previous | Next
6.3.4 Configure WXS infrastructure
Overview
We are going to install WXS into the same Network Deployment cell as WCS.
This is the simplest deployment, but introduces the operational consideration that WXS and Commerce will have to continue to run on the same patch level of WAS.
Configure WXS infrastructure
- Install Commerce on WAS ND v7.0.0.11 (or any supported release).
- Configure a Commerce cluster
- Enable dynamic cache service on cluster
- Install WAS ND on the WXS nodes and bring the code to the required fix level.
- Install WXS on top of the Commerce and the WAS installations.
There are two installation options for WXS...
- client
- server
With WXS 7.0 and lower, select the server option to install both client and server on Commerce nodes. Although WCS is a WXS client, the server installation contains required dynamic cache provider files.
With WXS version 7.1, you only need perform the client install on Commerce nodes.
Warning: For WXS v7.1.0.0, there is an issue where the dynamic cache provider uses the wrong grid name. This issue is resolved in WXS V7.1.0.1. The work around in the mean time is to move the following file to a temporary directory:
$WAS_HOME/lib/xsadmindynacachexc10.jar
This file is only needed if using the dynamic cache provider from the DataPower XC10 appliance. If you are using the WXS dynamic cache provider, the presence of this file causes a problem.
- Augment existing Commerce profiles
These typically include the following profiles:
- Deployment manager profile
This profile augmentation will enable the WXS-specific portions of the administrative console.
- Custom profiles containing Commerce application servers
- Create WXS custom profiles for the WXS nodes and federate them to the deployment manager.