Installing WebSphere Application Server Communications Enabled Application (CEA)

To enable coshopping, install and configure the Communications Enabled Application Feature Pack.

Important: When setting up your coshopping configuration, you must manually merge the Web server plugin files (plugin-cfg.xml) for the WebSphere Commerce profile and the CEA profile. Each time WAS regenerates the Web server plugin file, the manual merge is overridden and the CEA server stops working. For example, WAS regenerates the Web server plugin file when you install an interim fix (iFix). To get the CEA server working again, you must redo the manual merge.

Before you begin

Installing WebSphere Commerce feature packs.

Procedure

Install WebSphere Application Server Feature Pack for CEA Fix Pack 1.0.0.7 with iFix to update CEA dojo on the WebSphere Commerce Server.
1. Update to WebSphere Application Server Version 7.0 Test Environment to the following level:
  - 7.0.0.13
  - 7.0.0.17
2. Install WebSphere Application Server Feature Pack Version 1.0.0.0.
Augment the WebSphere Application Server profile.
1. Open a command line.
2. Go to the bin directory:
  - Go to the WAS_installdir/bin directory.
  - Go to the RAD_installdir\runtimes\base_v7\bin directory.
3. Determine your profileName. To find a list of possible profileName options, run:
  - manageProfiles.sh -listProfiles
  - manageprofiles.bat -listProfiles
  This command returns a list of the profileName options that can be augmented. select the WebSphere Application profile.
4. Run the manageprofiles command:
  - manageprofiles.bat -augment -profileName profileName -templatePath ..\profileTemplates\CEA\default.ceafep
  - manageprofiles.sh -augment -profileName profileName -templatePath ../profileTemplates/CEA/default.ceafep
Configure the WebSphere Commerce test server:
1. Open the WebSphere Application Server Administrative Console.
2. Click Servers > Server Type > WebSphere Application Server > server1 > Communications Enabled Applications (CEA)
3. Select Enable communications service.
4. Change Virtual Host to WC_default_host, Click OK, and save the configuration.
5. Click Environment > Virtual hosts > WC_default_host > Host Alias. Add the port for the SIP_DEFAULTHOST to the Virtual host. Ensure that a fully qualified domain name is used. You can check what the ports are for the SIP_DEFAULTHOST by selecting Servers > Server Type > WebSphere Application Server > server_name > Ports.
Configure the WebSphere Application Server:
1. Open the WebSphere Application Server Administrative Console.
2. Click Servers > Server Type > WebSphere Application Servers > server1 > Communications Enabled Applications (CEA).
3. Select Enable communications service.
4. Change Virtual Host to VH_demo. Click Ok.
5. Click Environment > Virtual hosts > VH_demo > Host Alias. Add the port for the SIP_DEFAULT to the Virtual host. Ensure that a fully qualified domain name is used. You can check what the ports are for the SIP_DEFAULTHOST by selecting Servers > Server Types > WebSphere Application Server > server_name > Ports.
6. Click Servers > Server Types > Web Servers > webserver1.
7. Go to WAS_installdir/profiles/instance_name/config/cells/WC_instance_name_cell/nodes/WC_instance_name_node/servers/webserver1/.
8. Copy the plugin-cfg.xml file. After you generate the plug-in using the WebSphere Commerce Administration Console, you must copy the file differences back to the generated plugin-cfg.xml file.
9. Click generate plugin.

Configure the web server.

Option	Description
IBM HTTP Server	Open the `WAS_installdir`/profiles/`instance_name`/config/cells/WC_`instance_name`_cell/nodes/WC_`instance_name`_node/servers/webserver1/plugin-cfg.xml file. Find the string: `<UriGroup Name="VH_instance_name_server1_WC_instance_name_node_Cluster_URIs">` Add `<UriAffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/commsvc.rest/"/>` For example, assuming the instance name is `demo`: `<UriGroup Name="VH_demo_server1_WC_demo_node_Cluster_URIs"> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/InitializationServlet/"/> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/webapp/wcs/stores/"/> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/commsvc.rest/"/>` Restart the IBM HTTP Server.
IIS Web Server	Open the `WAS_installdir/`profiles/`instance_name/`config/cells/WC_`instance_name`_cell/nodes/WC_`instance_name`_node/servers/webserver1/plugin-cfg.xml file. Find the string `<UriGroup Name="VH_instance_name_server1_WC_instance_name_node_Cluster_URIs"`. Add `<URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/commsvc.rest/"/>` For example, assuming the instance name is `demo`: `<UriGroup Name="VH_demo_server1_WC_demo_node_Cluster_URIs"> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/InitializationServlet/"/> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/webapp/wcs/stores/"/> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/commsvc.rest/"/>` Edit the plug-in-cfg.loc file. Open the `drive`:/WebSphere/Plugins/bin/IIS_webserver1/plugin-cfg.loc file. Replace the line `drive:\WebSphere\Plugins\config\webserver1\plugin-cfg.xml` with `WAS_installdir\profiles\instance_name\config\cells\WC_instance_name_node\servers\webserver1\plugin-cfg.xml` Restart the IIS web server.
SunOne Web Server	Open the `WAS_installdir`/profiles/`instance_name`/config/cells/WC_`instance_name`_cell/nodes/WC_`instance_name`_node/servers/webserver1/plugin-cfg.xml file. Find the string: `<UriGroup Name="VH_instance_name_server1_WC_instance_name_node_Cluster_URIs">` Add `<UriAffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/commsvc.rest/"/>` For example, assuming the instance name is `demo`: `<UriGroup Name="VH_demo_server1_WC_demo_node_Cluster_URIs"> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/InitializationServlet/"/> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/webapp/wcs/stores/"/> <URi AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/commsvc.rest/"/>` Add write/delete permission to the access control file for DELETE and PUT requests. When installing CEA and coshopping on a SunOne web server, a shopper can be required to enter a username and password when creating or ending a coshopping session. SunOne web servers do not allow DELETE/PUT requests by default, which coshopping uses when creating or ending a session. Refer to the SunOne documentation for instructions for adding write/delete permission. Restart the SunOne web Server.

Integrate the CEA dojo library with the WebSphere Commerce EAR file.
1. Go to WC_installdir/bin directory.
2. Run the following script:
  - config_ant.bat -DinstanceName=commerce_instance_name -DceadojoLocation=path_to_ceadojo -buildfile ..\components\store-enhancements\xml\Coshopping.xml
  - config_ant.sh -DinstanceName=commerce_instance_name -DceadojoLocation=path_to_ceadojo -buildfile ../components/store-enhancements/xml/Coshopping.xml
  ceadojoLocation is optional. If ceadojoLocation does not exist, the script will look at the default ceadojo path: WAS_installdir/feature_packs/cea/javascript/ceadojo
1. Stop the WebSphere Application test server.
2. Close the WebSphere Commerce development environment.
3. Go to WCDE_installdir\bin directory.
4. Run the setupCoshopping.bat command.

What to do next

After installing WebSphere Application Server CEA, publish the Madisons.sar and MadisonsEnhancements.sar store archives and select the coshopping store function to enable the coshopping feature for your store.