Siebel Master Data Applications Reference for Industry Applications > Architecture and Framework > About Siebel Master Data Applications Architecture >
Siebel Universal Customer Master Business Objects Layer
The business logic layer for Siebel Master Data Applications contains object abstractions of entities and represents internal and external data. The logic layer also allows for complex entity relationships. For further information about the business objects layer and how to customize it, see Configuring Siebel Business Applications.
The business object manager consists of the Object Manager, Data Manager, and Siebel Master Data Applications Integration.
Object Manager and Data Manager
The object manager and data manager layer use:
- Business Objects
- Business Components
- Virtual Business Components
- External Business Components
These business objects are customizable. For further information about the business objects and data objects layer, see Configuring Siebel Business Applications.
Siebel Industry EAI Architecture
Siebel Industry EAI architecture is built to work with the Siebel Enterprise Application Integration (EAI) architecture and to support XML-based messaging communication infrastructure. Different applications require integration using messaging mechanisms. Connectors must be built to support various industry standards.
Siebel Business Applications allow you to build and deploy multiple connectors. For example, the Siebel Financial Services Application has built three connectors—Siebel Connector for Master Data Applications, Siebel Connector for ACORD XML, and Siebel Connector for IFX XML—based on the Siebel Industry EAI framework.
Figure 5 illustrates the high-level architecture of the Siebel Industry EAI and the standard connectors.
Figure 5. High-Level Architecture of Siebel Industry EAI and Standard Connectors
Siebel Connector for Master Data Applications is based on Siebel XML standards in addition to a predefined Universal Customer Master Application envelope, headers for identifying the sending system, and associated privileges information. It is designed to address the real-time requirement by defining business processes that include both a request and a response message. The Siebel Connector for Master Data Applications provides functions such as:
- Handling message header
- Handling heterogeneous objects in the body section of an XML message
- Security checking for system registration
- Privilege checking for customer business process management
- Publishing customer information changes in both real and batch time processing
The Siebel Connector for Master Data Applications includes several business services. For further information on these services, see Siebel Connector and Integration of Siebel Master Data Applications.
Business Process Flow
Each standard integration or custom integration is based on the creation of business process flows. A business process flow controls the entire business transaction instance. Figure 6 illustrates inbound (Receive-Send) business process flow. Some of the business flows might constitute messages published by Siebel Master Data Applications such as <InsertContactProduct>, <DeleteAccountAddress>, <UpdateContactProduct>, <UpdateHousehold>, <DeleteAccountAddressResponse>, <LookUpAccount>, <LookUpPersonalAddressByState>, and so on. These messages are included in Siebel Master Data Applications for Industry Applications.
The processing flow for each of these business process flows is largely contained within a Siebel workflow process. The workflow process is instantiated by the Business Integration Manager after receiving the inbound request from enterprise applications.
Figure 6. Business Process Flow
Inbound Data Flow
An inbound business process flow starts with a Receiver Server Component, such as the MQSeries or HTTP Receiver. The Receiver runs in the background, continuously waiting for messages to arrive from external applications. After receiving a CRMML message, the receiver then invokes the workflow process configured to handle and process the data.
The workflow dictates the business logic behind the Siebel Connector for Master Data Applications as follows:
- The raw XML text string passes through XML Hierarchy Converter and is converted into an XML integration object instance.
- The UCM Dispatcher traverses the XML instance and identifies the messages received according to the rule sets of the UCM Dispatcher Map. It then identifies the envelope, header, and body sections among the hierarchy nodes and sends it to the UCM Security Manager.
NOTE: The Dispatcher Map is shipped as a part of Siebel UCM Applications. For details, see UCM Dispatcher Map Integration Objects.
- The UCM Security Manager takes the XML instance, verifies the System for registration with Siebel Master Data Applications, checks the operation identified in each body section for privileges, and attaches any fail privilege bodies to the FailSecurityHierarchy before sending it to the UCM Converter.
- The UCM Converter takes the XML instance, and processes individual sections of the instance while converting each sub-tree into external integration object instances before sending it to the UCM Transaction Manager.
- The UCM Transaction Manager performs operations specified in the instance by invoking the services configured in its user properties. Source data is captured for insert, update, and delete operations, and history data is captured for update and delete operations.
- If the EnableRealtimeInsert user property is set to false, insert requests are queued in the Source Data History table.
- Update operations invoke UCM Survivorship Engine or UCM Data Quality Manager, if enabled.
- If UCM Publish/Subscribe Service is configured for real-time publishing, then messages are sent to systems registered for the particular business objects executed.
Siebel Business Process Designer is the center of the business data flow. Workflow processes control the flow and transformation of data into and out of the Siebel Business Applications. You create the workflow processes using a graphical user interface provided within Siebel Business Applications, called the Siebel Business Process Designer.
For details on workflow and the Siebel Business Process Designer, see Siebel Business Process Framework: Workflow Guide.
Integration objects are data containers used within the workflow environment. They represent the data structure of a Siebel Business Object or an external application's data object. You create integration objects with the Integration Object Builder provided in Siebel Tools. The Integration Object Builder creates Siebel Integration Objects from Siebel Business Objects, which are then used by components within the Siebel Master Data Applications Integration. Supporting integration objects for Siebel Master Data Applications business processes are shipped as part of the Siebel Master Data Applications.
For more information on Integration Objects, see Overview: Siebel Enterprise Application Integration.
Business services execute predefined or custom actions in a workflow process. Examples of business services include the UCM Transaction Manager, the EAI Siebel Adapter, the UCM Converter, and so on. These business services act on property sets passed to them. They perform business logic operations such as interfacing with the database, interfacing to external systems, or transforming one integration object into another. Many business services are provided, but you can create your own. Although you can use business services to perform many different functions, they all have a standard interface. Business services have object-like qualities, such as methods, method arguments, and user properties. These elements define how a business service can be used. Business services are defined in Siebel Tools. This guide describes those business services used to interface to external systems within an organization's application network.
For more information on business services in general, Integration Platform Technologies: Siebel Enterprise Application Integration.
Customer Relationship Management Markup Language (CRMML) is a Siebel messaging system targeted for CRM data exchange and remote business process invocation. CRMML allows different applications with different data models to share information, or replicate data through document exchange and cross reference objects. It also allows multiple applications to share business logic and business processes through remote procedure calls.
CRMML is an extensible XML vocabulary. CRMML specification defines a set of syntax and rules to describe how to interpret messages and how to extend the messages beyond the current offer. CRMML messages contain a simple envelope, a header section, and a body section.
For further information on CRMML, see About CRMML Messages.