Recovering from error conditions

Removing an existing item from the process that ended in error so it can be reprocessed.

Description

After determining the nature of the error and correcting it, the existing item must be removed from the process that ended in error so it can be reprocessed. Unless the item is to be restarted by using a test connector , the item must be removed from every store and from the business review/approval process before processing can be restarted.

Removing an item from processing

  1. Remove the item from the business review/approval process (WebSphere® MQ Workflow in the context of the Product Information Management for Retailers solution) by referring to WebSphere MQ Workflow documentation that describes how to remove the instance of the WebSphere MQ Workflow process that ended in error.
  2. Delete the item from the item store by finding the value of its internals.correlationID attribute in the log file. Use this value as the key to the item store and find and delete the Retail_Item record.
  3. Delete the item from the message store finding the value of the correlationID attribute of the related UCCnetGBO_storable business object in the log file. Use this value as the key to the message store and find and delete the record.
  4. If the original request was a NEW_ITEM, DATA_CHANGE, WITHDRAW, or DE_LIST, delete the item from the identifier store by finding in the log file the values of the gtin, version, and topic attributes of the related UCCnetGBO_identifier business object for DTD processing or the gtin, topic, dataRecipientGLN, dataSourceGLN, targetMarket, and uniqueCreatorID attributes of the related UCCnetGBO_identifier business object for XSD processing. Use these values as the key to the identifier store and find and delete the record.

Restarting item processing

To restart item processing, do one of the following:
  • Regenerate the message from UCCnet by obtaining the GTIN and trading partner GLN from the log entries related to the item and using the UCCnet Graphical User Interface (GUI) to request a republication of the item. This action causes a message to arrive for the item and the item is processed normally.
  • Regenerate the message from the UCCnet backup area. The original message containing the failed item can be copied from the UCCnet staging directory to the connector processing directory.
  • Use a test connector to restart the item from the item store if the following conditions exist:
    • The item failed in the back-end process
    • The item was synchronized
    • No message was sent to UCCnet
    • The item still exists in the item, identifier, and message stores
    To use a test connector to restart the item, do the following:
    1. Do not delete the item from the item store, message store, or identifier store.
    2. Start a test connector and connect it to an ItemCollector collaboration object flow. This requires configuring a set of collaboration objects and connectors to imitate a normal back-end flow.
    3. Create a Retail_Item business object in the test connector and set the value of its internals.correlationID attribute equal to the value of the internals.correlationID attribute for the item found in the log.
    4. Send the item. The ItemCollector collaboration object receives it and processes it normally.

Parent topic: Handling solution processing errors