Install IWWCM integration for WebSphere Commerce on the WebSphere Commerce system
To install IBM Workplace Web Content Management integration for WebSphere Commerce on the WebSphere Commerce system, perform these steps on both the WebSphere Commerce authoring and production servers, unless specified otherwise.
- Copy the CommerceAssets.zip file to the WebSphere Commerce system.
- Create a backup of the current WebSphere Commerce application by exporting it.
- Extract the contents of the CommerceAssets.zip file to WC_installdir. After extracting the files, you should have the following files:
- WC_installdir/refapps/WWCM/SampleStore/IWWCMEnabled.zip
- WC_installdir/refapps/WWCM/schema/db2/iwwcm.sql
- WC_installdir/refapps/WWCM/schema/oracle/iwwcm.sql
- WC_installdir/refapps/WWCM/scripts/addIWWCMAliases.js
- WC_installdir/refapps/WWCM/wc.ear/partialAppsforEar.zip
- WC_installdir/refapps/WWCM/wc.ear.ext/db2/IWWCMIntegrationAssetsData.jar
- WC_installdir/refapps/WWCM/wc.ear.ext/oracle/IWWCMIntegrationAssetsData.jar
- WC_installdir/xml/policies/xml/iwwcmacpolicies.xml
The WWCM directory is WWCM_60.
- Update the partial EAR file.
- Stop WebSphere Commerce:
- Start the WAS Administration Console
- Click Applications > Enterprise Applications to see a list of installed applications.
- Select the WebSphere Commerce application, for example WC_demo , and click Stop.
- Update the WebSphere Commerce application with the completeAppsforEar.zip partial application file you created when updating the partial EAR file.
See the Updating applications topic in the WebSphere Application Server Information Center, noting the following information:
- Follow the instructions to update a partial application.
- The default name for the WebSphere Commerce application is wc_demo.
- Save the changes to the master WAS configuration.
- Ensure that WebSphere Commerce is stopped. If WebSphere Commerce is not stopped:
- Start the WAS Administration Console
- Click Applications > Enterprise Applications to see a list of installed applications.
- Select the WebSphere Commerce application, for example WC_demo , and click Stop.
- Update the WebSphere Commerce application with the IWWCMIntegrationAssetsData.jar file:
- Start the WAS wsadmin tool by entering the following command in a command prompt session:
WC_profiledir /bin/wsadmin
- At the wsadmin prompt, enter the following command:
$AdminApp update WC_enterprise_application modulefile { -operation addupdate -contents SRC_PATH -contenturi IWWCMIntegrationAssetsData.jar -nodeployejb -usedefaultbindings -defaultbinding.datasource.jndi " JNDI_NAME" -defaultbinding.cf.jndi " JNDI_NAME" -defaultbinding.cf.resauth Per_Connection_Factory }where the variables in the command are:
- WC_enterprise_application
- WC_instance. For example, given the instance demo, the value of WC_enterprise_application is WC_demo.
- SRC_PATH
- The full path to the IWWCMIntegrationAssetsData.jar file appropriate for the WebSphere Commerce database. Use a forward slash '/' , in the SRC_PATH.
WC_installdir/refapps/WWCM/wc.ear.ext/db2/IWWCMIntegrationAssetsData.jar
For Oracle, use... WC_installdir/refapps/WWCM/wc.ear.ext/oracle/IWWCMIntegrationAssetsData.jar
where instance is the name of the WebSphere Commerce instance. For example, demo.
You may encounter a warning message after you run the command. Ignore the message and continue with the installation.
$AdminConfig save
exit
(DB2) db2 -tvf iwwcm.sql
(Oracle) @iwwcm.sql
This update is only required for existing workspaces. Any workspaces you create later do not require this step.
Update the registries: Access Control Policies and Access Control Policy Groups.
Related concepts
IWWCM integration for WebSphere Commerce
Related tasks
Overview: Integrating WebSphere Commerce and IWWCM
Related reference
acpload utility