Description

Product Information Management for Retailers Solution 4.2.0.1 Fix Pack

Prerequisites

Fixes Included

4.2.0.1

UCCnet 2.2 DTD Updates

UCCnet version 2.2 includes changes to the DTDs that need to be reflected in the MQWF_Retail_Item, Retail_MQWF_WfMessage, Retail_Item_ASBO, DataStoreRetail_Item, andDataStoreUCCnetGBO_storable Business Objects. The Business Objects have all been modified to rename the size attribute to netContent and the sizeUnits attribute to netContentUnitOfMeasure in the UCCnet_envelope_itemDimensions, Retailer_itemDimensions, and MQWF_Structure_Retail_Item_itemDimensions child Business Objects. Also, the UCCnet_envelope_notificationDetail child Business Object has been updated to include a new publication failure notification message. The Retail_MQWF_WfMessage_to_Retail_Item, Retail_Item_to_MQWF_Retail_Item, andSub_Retailer_itemInformation_to_Retailer_itemInformation named maps have also been updated to reflect UCCnet 2.2 DTD changes. The Retail.fdl Workflow definition has also been updated to reflect theUCCnet 2.2 DTD changes. The Retail_MO_MQSeriesConnectorConfig Business Object has also been included because it was left out of the original solution package.

This fix pack should to be applied along with the following co-requisite fix packs:

Installation Instructions

These instructions cover installation of the following:

To install these fix packs do the following:

  1. Shutdown the WebSphere MQ Workflow client.
  2. Shutdown all the Connector Agents.
  3. Backup your PIM Integration Component Library (ICL). Right click on the ICL name,selection Export Repository File, click on the ICL name, select an output jar file nameand click on Finish.
  4. The MO_DataHandler_UCCnetXMLConfig business object contains the attribute DTDPath. You will either need to replace the UCCnet 2.1 DTDs in the same directory, or alter the DTDPath attribute to point to the directory where the UCCnet 2.2 DTDs are located. The DTDs for UCCnet 2.2 can be obtained from UCCnet.
  5. In the WebSphere Business Integration System Manager, load the following jar file into your PIM Integration Component Library (ICL):Right click on the ICL name, select Import Repository File, browse to where you have the files stored, select the file and click on Open. From the pull-down menu for Integration component library name, select your ICL name and click on Finish. The updates will be copied to your ICL, overlaying any duplicate objects.Repeat this for all three jar files.
  6. Using the WebSphere Business Integration System Monitor, stop all map and collaborations. Right click on each one and click on Stop.
  7. In System Manager, recompile all of the maps.
  8. Deploy all of the business objects to the ICS.
  9. Deploy and compile all of the maps to the ICS.
  10. Deploy all collaboration objects, and deploy and compile the collaboration templates to the ICS.
  11. Shutdown and restart the ICS.
  12. Before restarting the Connector Agents, you need to update the WebSphere MQ Workflow configuration. From the Windows Start Menu, select IBM WebSphere MQ Workflow -> WebSphere MQ Workflow Buildtime for your configuration (FMC is the default). Follow the original install directions for the section Configuring WebSphere MQ Workflow and WebSphere MQ (steps 1 and 2 only). Be sure to include any customization you may have done beyond the default solution. The modified fix pack version of the sample fdl can be found in
  13. Finally, restart the WebSphere MQ Workflow client, and then all of the Connector Agents.