Siebel Master Data Applications Reference for Industry Applications > Architecture and Framework > About Siebel Master Data Applications Architecture >

Siebel Connector and Integration of Siebel Master Data Applications

Siebel Connector for Master Data Applications describes a set of configurable components for integration among enterprise applications and Siebel Master Data Applications.

The Siebel Connector for Master Data Applications comprises the following prebuilt business services:

• UCM Account Source Data and History Service
• UCM Batch Manager
• UCM Contact Source Data and History Service
• UCM Converter
• UCM Data Quality Manager
• UCM Dispatcher
• UCM FINCORP Account Source Data and History Service
• UCM Household Source Data and History Service
• UCM Publish/Subscribe Service
• UCM Security Manager
• UCM Survivorship Engine
• UCM Transaction Manager
• UCM UI Interaction Service

Use Siebel Tools to review specific details on business services, including user properties, methods, and method arguments. For information on using Siebel Tools, see Using Siebel Tools. See also About Siebel Master Data Applications Integration Services.

UCM Account Source Data and History Service

UCM Account Source Data and History service synchronizes the Account record with the UCM Account Source Data and History record.

UCM Batch Manager

UCM Batch Manager processes insert requests queued in the source data history table in batch mode. It also processes batch data during initial load through EIM.

UCM Contact Source Data and History Service

UCM Contact Source Data and History service synchronizes the Contact record with the UCM Contact Source Data and History record.

UCM Converter

The UCM Converter converts Siebel Master Data Applications messages received to a property set for inbound communication. The converter iterates through the requests and responses in the message to construct error information (if any), and also constructs the envelope and header section of the message.

UCM Data Quality Manager

UCM Data Quality Manager is responsible for cleansing and matching records before processing a transaction.

UCM Dispatcher

The UCM Dispatcher is responsible for receiving and dispatching inbound messages. It receives the inbound message and scans the message for any operations specified in its rule sets dispatcher map, and associates the integration objects for the connector components. It then parses the envelope of the message, converts it to the header property set, and passes the integration objects for the specified action, the envelope layer property set, and the XML message to the connector components for further processing.

UCM FINCORP Account Source Data and History Service

UCM FINCORP Account Source Data and History service synchronizes the FINCORP Account record with the UCM FINCORP Account Source Data and History record.

UCM Household Source Data and History Service

UCM Household Source Data and History service synchronizes the Household record with the UCM Household Source Data and History record.

UCM Publish/Subscribe Service

The UCM Publish/Subscribe Service supports both near real-time and daily-batch publish types.

The near real-time publish module takes the Siebel Connector for Master Data Applications output message, which could include heterogeneous body segments with different business object types, as an input message. It dynamically constructs a unique output message for each system based on the Business Object type that the system registered in the Publish/Subscribe administration view. The near real-time publish module sends the constructed messages to the registered systems through a registered protocol type.

Similarly, the daily-batch publish module publishes the synchronization information of registered Business Object types. The module constructs messages according to Siebel Master Data Applications message specification and sends them to the registered system through registered protocol types.

Both publish modules then update the Last Publish time to the system in the Publish/Subscribe table.

The UCM Publish/Subscribe Service has the following default UserProperties:

• EnableCrossReference[FALSE]
• ReloadSystemsCounter[10]
• WorkflowName[UCM Async Realtime Publish Workflow]

UCM Security Manager

The UCM Security Manager acts as the gatekeeper of the Siebel Universal Customer Master Application. It verifies the System ID in the message header against the System Registrations in the Siebel Universal Customer Master Application before the system can perform its desired operations. After a system passes the registration verification process, the UCM Security Manager cycles through the heterogeneous commands in the body. The UCM Security Manager checks the privilege of the individual operations in the body sections against the privileges in the Universal Customer Master for the particular object and operation. Any fail operation instances in the body are removed from the XMLHierarchy and attached to the FailSecurityHierarchy.

UCM Survivorship Engine

UCM Survivorship Engine is a prebuilt business service to execute survivorship logic defined by data administrators. For background information on administering survivorship, see About UCM Survivorship Rules.

UCM Transaction Manager

The UCM Transaction Manager executes operations specified in Universal Customer Master Application message instances as Siebel database transactions. The UCM Transaction Manager also:

• Evaluates heterogeneous commands and executes the transactions.
• Invokes business services, including Siebel EAI, that are configured in its user properties. These business services can be invoked multiple times.
• Translates Universal Customer Master Application command elements to Siebel Adapter actions and combines return results as a single property set.

UCM UI Interaction Service

UCM UI Interaction Service creates a UUID during insert process. It captures attribute group data for survivorship during the user interface insert or upsert. It also captures the source data history records during the update or delete process.

Transport Adapter

Transport Adapter is a prebuilt business service providing an interface between Siebel Business Applications and external applications. Transports allow Siebel Master Data Applications to exchange data with external applications using standard technologies for both synchronous and asynchronous communication protocols. Transports provide connectivity to virtually any communication protocol that can represent data as text or binary messages, including MQSeries from IBM, and HTTP.

For details on transport adapters, see Transports and Interfaces: Siebel Enterprise Application Integration.

Siebel EIM and Integration of Siebel Master Data Applications

Siebel EIM is an important component of Siebel Master Data Applications. It bulk imports and exports data residing in other back-office systems into Siebel Master Data Applications and consolidates and replicates information from these sources. Unlike Siebel EAI, Siebel EIM does not go through a application object manager, but the data moves from the EIM_UCM_ORG interface table directly into the SDH (S_UCM_ORG) tables. Siebel EIM also provides a schema abstraction and has high throughput. Some features of Siebel EIM include:

• Denormalized interface tables
• Declarative mapping defined in Siebel Tools
• Automated SQL generation
• Support for parallelized import

For batch integration with external applications, Siebel UCM provides the following UCM-specific EIM tables to facilitate the loading of selected master objects into UCM's Source Data and History tables. These records can then be processed by UCM data management tasks at a later date:

• EIM_PTYUCM_DTL
• EIM_UCM_ADRPER
• EIM_UCM_ASSET
• EIM_UCM_ASTCON
• EIM_UCM_CON
• EIM_UCM_CONCHLD
• EIM_UCM_OGPCHD
• EIM_UCM_ORG
• EIM_UCM_ORGCHLD
• EIM_UCM_ORGGRP
• EIM_UCM_PRIVCY

For further information about Siebel EIM, see Siebel Enterprise Integration Manager Administration Guide.

Generation of Party_UID

Siebel EIM and Siebel Master Data Applications workflow processes generate the Party_UID field based on the value in the UCM_EXT_ID field. The process for generating this field occurs by either of the following means:

• Loading data to UCM SDH table using UCM Customer Profile Integration Process. In this scenario, the user must populate the <ID> integration object component field value in the CRMML message, which maps to UCM_EXT_ID field in the UCM SDH table. Additionally, the <PartyUId> field, which maps to PARTY_UID, must be empty or not sent with the CRMML message. The UCM Customer Profile Integration Process then generates the PARTY_UID based on UCM_EXT_ID.
• Loading data to UCM SDH table using Siebel EIM. In this scenario, users must populate the UCM_EXT_ID column value in the EIM interface table and the UCM_PARTY_UID field value must remain empty. The EIM interface table value populates the UCM_EXT_ID field in the SDH table. The UCM Batch Data Management workflow then generates the PARTY_UID based on the UCM_EXT_ID.

For further information on the Party_UID, see Siebel Enterprise Integration Manager Administration Guide.