CoreMedia Digital Experience Platform 8 Developer Manual, Version 7.5.45-10
3.4. Customizing IBM WebSphere Commerce | 3.4.11. Deploying the CoreMedia Widgets

Stop the IBM WebSphere Commerce server in the IBM RAD environment.

Adapt the database settings in the Data Load environment configuration file (SAMPLEDATA-ZIP\workspace\DataLoad\dataload\common\wc-dataload-env.xml) from the CoreMedia LiveContext 2.0 WebSphere Commerce Project Sample Data Zip file to the settings of your WebSphere database.

You can retrieve your database settings from the IBM RAD environment configuration file WC/xml/config/wc-server.xml, at the following XML element:

<InstanceProperties>
   <Database>
     <DB>

For a DB2 database, the attribute schema in wc-dataload-env.xml corresponds to the attribute DBNode in wc-server-xml.

Find your store identifier in the IBM Management Center in Store Management. If you use the default IBM shop, the value is "Aurora".

Use the Data Load business object configuration files from the CoreMedia LiveContext 2.0 WebSphere Commerce Project Sample Data ZIP file for registering the widget definition (workspace\DataLoad\dataload\common\[store_name]\Widget\wc-loader-registerWidgetdef.xml) and for subscribing the widget definition (workspace\DataLoad\dataload\common\[store_name]\Widget\wc-loader-subscribeWidgetdef.xml) where store_name is the store identifier of your store ("AuroraESite", for instance).

Use the CSV input files from the CoreMedia LiveContext 2.0 WebSphere Commerce Project Sample Data ZIP file for registering the widget definition (workspace\DataLoad\dataload\common\[store_name]\Widget\registerWidgetdef.csv) and for subscribing the widget definition (workspace\DataLoad\dataload\common\[store_name]\Widget\subscribeWidgetdef.csv).

Configure the Data Load order configuration file (wc-dataload.xml). The Data Load file has pointers to the environment settings file, the business object configuration file and the input file.

<?xml version="1.0" encoding="UTF-8"?>

<_config:DataLoadConfiguration
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation=
      "http://www.ibm.com/xmlns/prod/commerce/foundation/config
        ../../../../xml/config/xsd/wc-dataload.xsd"
    xmlns:_config=
      "http://www.ibm.com/xmlns/prod/commerce/foundation/config">

  <_config:DataLoadEnvironment configFile="wc-dataload-env.xml"/>

  <_config:LoadOrder commitCount="100"
                     batchSize="1"
                     dataLoadMode="Replace">
    <_config:property name="firstTwoLinesAreHeader" value="true"/>
    <_config:property name="loadSEO" value="true"/>

    <!-- Configuration for the file to register a widget -->
    <_config:LoadItem
        name="RegisterWidgetDef"
        businessObjectConfigFile=
          "wc-loader-registerWidgetdef.xml">
      <_config:DataSourceLocation
          location="registerWidgetdef.csv"/>
    </_config:LoadItem>

    <!-- Configuration for the file to subscribe a store to a widget -->
    <_config:LoadItem
        name="SubscribeWidgetDef"
        businessObjectConfigFile=
          "wc-loader-subscribeWidgetdef.xml">
      <_config:DataSourceLocation
          location="subscribeWidgetdef.csv"/>
    </_config:LoadItem>
  </_config:LoadOrder>

</_config:DataLoadConfiguration>

Run the Data Load utility command syntax with the dataload.bat tool which is located in workspace\bin of the RAD environment. Give the absolute path to the wc-dataload.xml file. The call might look as follows:

..\bin\dataload.bat [path_to_your_dataload]\wc-dataload.xml

Stop the IBM WebSphere Commerce server in the IBM RAD environment.

Copy the custom access control policies files workspace/DataLoad/acp/common/CoreMediaContentDisplay.xml and workspace/DataLoad/acp/common/CoreMediaMicroSite.xml to the access control policies directory which is located in xml\policies\xml of the RAD environment.

Run the ACP Load utility with the acpload.bat tool which is located in workspace\bin of the RAD environment. Give the absolute path to the acp-filename.xml file. The call might look as follows:

..\bin\acpload.bat [path_to_your_acp_dir]\acp-filename.xml

The acpload documentation can be found here: https://www.ibm.com/support/knowledgecenter/SSZLC2_7.0.0/com.ibm.commerce.admin.doc/refs/raxacpload.htm.

	Note
	The acpload tool itself does not report any problems. So, check if the tool created 2 new XML files with the suffixes _xmltrans.xml and _idres.xml in ..\xml\policies\xml for each policy file. Also look into ..\logs\acpload.log and ..\logs\messages.txt for errors.

Merge the content of the file PageLayoutExtensionsLibrary.lzx from the WEBDEV/workspace/LOBTools/WebContent/WEB-INF/src/lzx/commerce/pagelayout folder into the corresponding file PageLayoutExtensionsLibrary.lzx in the WCS workspace. It is only one line of XML code.

Remove the file PageLayoutExtensionsLibrary.lzx from the Workspace archive and copy the LOBTools folder content into the LOBTools folder of the IBM RAD workspace.

Refresh the projects in the IBM RAD system so that the new files are recognized:

Rebuild the LOBTools:

This steps might take some time.

Republish the WCS Server workspace in order to apply the changes to the shop web application. In the server view (bottom left corner) right click on the server instance and select Publish from the context menu.