Using identifier, message, and item stores

Identifies how and why various collaboration objects persist, retrieve, update, and delete items to and from identifier, message, and item stores.

Local stores

Three local stores, or database tables, are used in the Product Information Management for Retailers solution. The stage of item processing determines when these stores are accessed, by which collaboration objects, and which actions (Create, Retrieve, Delete, Update) are performed on them.

Identifier store

The identifier store stores unique identifying information for each item, which is used by a UCCnetMessageReceive collaboration object to prevent duplicate Catalogue Item Notifications with NEW_ITEM, DATA_CHANGE, WITHDRAW, or DE_LIST commands from being processed. This collaboration object triggers an IdentifierStore collaboration object, which performs the actual Create action on the store. When error conditions are encountered, the UCCnetMessageSend collaboration object can also trigger an IdentifierStore collaboration object to delete the item from the identifier store.

Message store

The message store holds item information that is used by UCCnetMessageReceive and UCCnetMessageSend collaboration objects to build appropriate messages to be sent back to UCCnet. These collaboration objects trigger a MessageStore collaboration object, which performs the actual Create, Retrieve, and Delete actions on the store.

Item store

The item store saves a complete version of the Retail_Item business object. A complete version of the item might have to be stored and later merged with updated information for some of its attributes for the following reasons: ItemValidation, ItemCollector, ItemDispatcher, and Process_Reviewed_Item collaboration objects trigger an ItemStore collaboration object, which performs the actual Create, Retrieve, Update, and Delete actions on the store.

Parent topic: Solution Development Guide