Description

IBM WebSphere Business Integration Collaborations for Retail Message Manager 4.4.0 Fix Pack.

Note: This second Fix Pack includes the first Fix Pack for the release above and would not need to be applied. The first Fix Pack was made available in September 2004 and combined with the IBM WebSphere Business Integration Collaborations for Product Information Management 1.1.0 Fix Pack. It is assumed this fix pack will be used along with APAR JR20717, the IBM WebSphere Business Integration Collaborations for Product Information Management 1.1.0.2 Fix Pack

Prerequisites

APARs Included

APAR JR20792  

Fix Pack 2 Enhancements

The IBM WebSphere Business Integration Collaborations for Product Information Management 1.1.0 and Retail Message Manager 4.4.0 Fix Packs include changes to business objects, maps, and collaboration templates to support the UCCnet release 2.4. Use of the majority of R2.4 functionality enhancements requires XML schema processing capabilities, which is enforced by the Trading Partner registration of a capability for XSD. 

In summary the enhancements include:

To reduce the use of the log file and to help performance, collaborations UCCnetMessageReceive and UCCnetMessageSend were altered by converting most logInfo() calls to trace() calls with a trace level of 4.

When an item’s status is set to “Accepted” (or “Review”), the item is sent back through ItemValidation for reprocessing by the approval process.  Changes were made to several collaborations so that the approval system can tell that it is being reprocessed, rather than being submitted for the first time.

·       A change to UCCnetMessageReceive checks the status of the Retail_Item returned from ItemValidation. If the status is blank or null, it will set the status to “REVIEW” to satisfy the UMS1 (collaboration object) expectation.  Otherwise the item_status value will be left as it is received.

·       ItemValidation no longer changes the item_status value. Now when an item is sent back through ItemDispatcher to the MQWorkflow approval process, it will contain whatever item_status value was sent to ItemValidation (Accepted, Review, or Reprocess).  These values are different from the item_status values sent by UCCnetMessageReceive (blank or null).

The Retail_Item Business Object was modified to include a new child business object containing all the attributes of the incoming envelope message header, into UCCnetMessageReceive collaboration.

Additional changes were made to incorporate UCCnet v2.4 release changes:

·       Added support for UCCnet_requestWorklist to be able to send Interconnect commands to UCCnet system.

·       Added validationErrorList element to the CatalogueItemNotification business object with mapping operation support.

·       Updated the Hardlines extension business objects to support the new XSD message structure.

·       Added errorList element to the catalogueItemPublication business object under the resultList in a response message.

Changed several maps that contained trace levels other than zero, to reset their trace level to allow a user to set them as needed.

 

APAR JR20308 (First Fix Pack which is included here)

Fix Pack 1 Enhancements  

The IBM WebSphere Business Integration Collaborations for Product Information Management 1.1.0 and Retail Message Manager 4.4.0 Fix Pack includes changes to business objects and maps to support the UCCnet release 2.3.1. Use of the majority of R2.3.1 functionality enhancements requires XML schema processing capabilities which is enforced by the Trading Partner registration of a capability for XSD. 

Release 2.3.1 is the next step as UCCnet migrates to define and establish a global registry, moving towards EAN.UCC Schema standards.

In summary the enhancements include:

          - Support for the initial deployment of the GDS Registry and interoperability of the UCCnet Data pool with the registry and other Data pools.

          - 4 new product types in CIN (Outbound to GDS Network and inbound to UCCnet)

          - Support of EAN.UCC 8 for EAN.UCC Code and EAN.UCC Type in CIN (Outbound to GDS Network and inbound to UCCnet)

          - A new Office extension, when used in conjunction with CIN, becomes an Office CIN (Can only be used between UCCnet suppliers and UCCnet retailers)

In detail, the current RCIR, CI and CIN schema messages that are received inbound from UCCnet subscribers are version 1.3 of the EAN.UCC schemas published in July of 2003.  These schemas were extended to include data sync support for an extension to the Trade Item schema to support attributes required by the office supply community of trading partners.  Additionally, there were other modifications that include adding the EAN.UCC Code (UPC and SSCC) and EAN.UCC Type (EDI qualifiers) in order that new subscribers can identify existing products in their legacy systems and match it to the GTIN that they are receiving for the first time.  UCCnet members will continue to send the current R2.3 production messages (UCCnet 1.3 schemas) to UCCnet with these extensions.

 

For more detail, consult the UCCnet Release 2.3.1 Community Update document on the UCCnet eRoom.

 

In addition to the UCCnet 2.3.1 enhancements, a fix was made for date/time fields within messages generated by Message Manager to correct the possibility of duplicate message IDs in responses to UCCnet services.

Files included in this Fix Pack:  

Business Object  changes:

Map  changes:

 Collaboration Template  changes:

The above business objects, maps, and collaboration templates contain the modifications necessary to support the addition of the office supply extensions and the modified hardlines extension to the UCCnet schemas, the Global Data Synchronization registry schema additions, the date/time fix for the duplicate message ID defect, the cleanup to the loginfo calls and trace levels, supporting the Interconnect command, and the additions for validationErrorList and errorList elements.

 

Installation Instructions

JR20792

Before installing this Fix Pack, backup all affected business objects, maps, and collaboration templates. Please see the installation instructions in the IBM WebSphere Business Integration Collaborations for Product Information Management Version 1.1.0 and Retail Message Manager 4.4.0 for reference, as needed.

  1. Unzip the MsgMgr_4.4.0_FixPack2_WIN.zip file
  2. Using the WebSphere Business Integration tooling, System Manager, import each of the unzipped .jar files into the appropriate Integration Component Library (ICL).  For ease of deployment, import the jar files into an ICL that already contains the full Message Manager/PIM products.  You should preserve an ICL in your System Manager containing the previous complete installation version of the Message Manager/PIM products as a backup.  Components in the fix pack jar files with the same names will overwrite the existing components in the ICL receiving the import.
  3. To update the UCCnet Message Manager, import all jar files.
  4. Any custom modifications previously made to any of the business objects, maps, or collaboration templates will need to be made to the new imported versions of those objects.
  5. Compile all the maps and collaboration templates in the ICL containing the fix pack
  6. If necessary, restart the target ICS server in design mode. (The ICS server must be running in design mode in order to delete the maps)
  7. Stop and delete all the maps running in the target ICS server
  8. Stop all running collaboration objects
  9. Deploy all the business objects from the ICL containing the fix pack objects to the target ICS server
  10. Deploy and compile all the maps from the ICL containing the fix pack objects to the target ICS server
  11. Deploy and compile the updated collaboration templates from the ICL containing the fix pack objects to the target ICS server 
  12. Restart the target ICS in the desired mode (design or production)
  13. Verify that all the collaboration objects and maps are running on the target ICS server

 

Uninstall Instructions

To uninstall this Fix Pack, follow these steps:

 

  1. If you have deployed any of the business objects, maps, or collaboration templates to the IBM WebSphere Interchange Server repository, stop any of the running maps, using the System Manager toolset.
  2. Delete all of the business objects (except for the business objects with names which begin with MO_), maps, and collaboration templates from the target Interchange Server repository using the System Manager.
  3. If desired, delete the ICL from the System Manager containing the fix pack components.
  4. Deploy the business objects, maps, and collaboration templates to the target ICS server from the backup System Manager ICL containing the previous full version of the Message Manager and PIM products.