Description

IBM WebSphere Business Integration Collaborations for Consumer Products Item Synchronization 4.4.0 Second Fix Pack. Note: This Fix Pack includes the first Fix Pack for this release that was made available in September 2004.

Prerequisites

APARs Included

APAR JR20716  

Fix Pack 2 Enhancements 

The IBM WebSphere Business Integration Collaborations for Consumer Products Item Synchronization 4.4.0 Fix Pack 2 includes changes to business objects, maps, and collaborations 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. Refer to the UCCnet Release 2.4.0 Community Update document for more details.

In summary the enhancements include:

-        Support for publishToTargetMarket or publishToMarketGroups, in addition to, publishing based on global location number lists.

-        Updated the Hardlines extension business objects and mapping to support the new XSD message structure.

-        Fix to the register command to allow a user to map the effective date (instead of having it set to the current date)

  

APAR JR20306   (First Fix Pack which is included here – September 2004)

Fix Pack 1 Enhancements 

The IBM WebSphere Business Integration Collaborations for Consumer Products Item Synchronization 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 follow on from Release 2.3, 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, 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.

 

Files included in this Fix Pack: 

Business Object  changes: 

Map  changes: 

New mapping was added from Retail_Item.itemPublication.publishToMarketGroup to publicationCommandOperand.catalogueItemPublication.publishToMarketGroup and Retail_Item.itemPublication.publishToTargetMarket to publicationCommandOperand.catalogueItemPublication.publishToTargetMarket. These were added to map Retail_Item_to_UCCnetJMSXSD_envelope_publicationCommand_catalogueItem to support publishing to market groups or target markets. In addition, new mapping was added in Retail_Item.item.catalogueItem.tradeItem.tradeItemInformation.tradingPartnerNeutral to registerCommandOperand.registryCatalogueItem.dateInformation.effectiveDate.

Collaboration Template changes:

The above business objects, maps, and collaboration templates contain the modifications necessary to support the addition of the office supply extensions to the UCCnet schemas, the new hardlines extension schema, the Global Data Synchronization registry schema additions, and the support for publishToTargetMarket or publishToMarketGroups.  The CIN_CIP_Dispatcher collaboration now looks for a new Retail_Item child business object called Retail_itemPublication, which may contain publishToTargetMarket or publishToMarketGroup information.  If neither of these is present, the collaboration looks for a list of glns in the Retail_glnList business object. If a user wants to publish to a Market Group, then the message must specify a marketGroup and contentOwner gln in the publishToMarketGroup business object within the Retail_itemPublication business object. Similarly, a user may publish to target markets by specifying a valid value within targetMarketCountryCode business object, in the Retail_itemPublication business object.

UCCnet_processWorklist and UCCnet_requestWorklist collaborations were modified to support sending and receiving messages to UCCnet, based on the other changes within the Fix Packs.

 

Installation Instructions

JR20716

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 Consumer Products Item Synchronization 4.4.0 for reference, as needed.

1.      Unzip the ItemSync_4.4.0_FixPack2_WIN.zip file

  1. 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 Item Synchronization product.  You should preserve an ICL in your System Manager containing the previous complete installation version of the Item Sync product 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.
  2. Any custom modifications previously made to any of the business objects, maps, or templates will need to be made to the new imported versions of those objects.
  3. Compile all the maps and collaboration templates in the ICL containing the fix pack
  4. 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)
  5. Stop and delete all the maps running in the target ICS server
  6. Stop all running collaboration objects
  7. Deploy all the business objects from the ICL containing the fix pack objects to the target ICS server
  8. Deploy and compile all the maps from the ICL containing the fix pack objects to the target ICS server
  9. Deploy and compile the 3 updated collaboration templates from the ICL containing the fix pack objects to the target ICS server
  10. Restart the target ICS in the desired mode (design or production)
  11. 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 from the fix pack to the IBM WebSphere Interchange Server repository, stop all of the running maps and collaboration objects, 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 Item Synchronization product.