Global Data Synchronization (GDS) administration

According to your requirements, the following configurations are required to be performed. The configurations take place in the Product Master, however, the settings reflect in the GDS. Ensure that you are logged in to InfoSphere Master Data Management Collaboration Server - Collaborative Edition user interface.

Ensure that you are logged in to the Product Master user interface.

The general GDS administration steps are applicable for Supply side GDS administration. The system administrators must complete certain configuration settings to make the GDS solution available according to the requirements. The administrator has access to all the features of GDS and user management

Processing CINs from the data pool

A CIN XML from data pool passes through various stages in the GDS. The GDS Receiver module receives the CIN XML from the data pool. The further flow has two main branches that are traversed by a CIN depending on whether the pass through model is enabled or not.

If the pass through model is enabled, the pass through model scripts gets triggered that enable the automatic execution of the process flow on the CIN XML. Otherwise, the CIN XML is passed through the conventional workflow for processing. These scripts are prepackaged and can be modified only by the development team. If the conventional workflow, your interaction is required at every workflow step making it a potentially time-consuming process.

In the pass through model, you are only involved if an error occurs during CIN processing. During the execution of the pass through model script on a CIN, if no errors are encountered, the message item does not enter any workflow and it is ready for further processing. If an error is encountered, the message item is checked out into the appropriate step in the custom GDS workflow. You are notified to perform the appropriate action at this stage. Once you have finished your task, the rest of the script is run on the message item. The process is repeated for every error that occurs until the end of the script. After the script has completed execution, the message item is ready for further processing.

Another reason for a message item to get caught in a workflow step is if the category mapping settings are not set to automatic processing. To do so, set the following properties to True in the $TOP/etc/default/gds.properties file.
  • mandatory_gpc_validation
  • gpc_to_internal_hierarchy_mapping
Essentially, processing and final output of CIN XML messages in the pass through or conventional model are the same. The difference lies in your actions at different steps. The pass through model offers the following advantages over the conventional model:
  • Less user intervention: You are notified only if an error occurs while you process a CIN XML.
  • Better performance: The pass through model is tuned to perform better. More time is saved in processing a CIN XML as most of the processing is automatic.

The pass through model is the default model of CIN processing in GDS. Thus, there are no setup costs and no services engagement that is required in using this model. However, if you want to customize the features of the pass through model, you can write the necessary scripts for these customizations.

The settings that are required for the pass through model are:
  • Ensure that the publicationprocess.properties file is present in the $TOP/etc/processflow/wwre folder. (By default, this file exists.)