Siebel CRM Integration to Oracle FLEXCUBE Universal Banking Implementation Guide > Customizing the Integration >

Overview of Oracle AIA Direct Integration

To customize or extend the data that is synchronized online in the Integration generally involves importing Oracle AIA Enterprise Object Library artifacts into Siebel CRM to create or extend Web services. The Oracle AIA Enterprise Object Library artifacts that are used to achieve direct integrations of data between applications are:

• Enterprise Business Objects

  Enterprise Business Objects (EBOs) provide definitions of standard business data objects, such as a loan account or a sales order, and reusable data components. The collection of EBOs provided in the Enterprise Object Library constitutes a data model that facilitates the integration of data in applications and systems. Each application data schema is mapped only once to the EBO data model, thereby eliminating the requirement to map data directly from one application to another. The EBOs are provided as XML Schema Definition (XSD) files.

• Enterprise Business Services

  Enterprise Business Services (EBSs) represent standard Web service definitions for performing a business task, such as creating an account. These services provide message-driven interfaces (described in XML) for the purpose of exchanging data between applications, both synchronously (request-and-response) and asynchronously (fire-and-forget). These services can be implemented by applications that participate in the Integration.

  The interface definitions for the EBSs are defined in Web Service Definition Language (WSDL) files, which list the operations, message exchange pattern, and payload that are applicable for each operation of a service. This interface description is composed of all details required for a client application to call the service. An EBS takes an EBM as input and provides another EBM as output.

• Enterprise Business Messages

  Enterprise Business Messages (EBMs) are the messages that are exchanged between the participating applications in the Integration. The EBM represents the specific content of an EBO needed for performing a specific operation on a business object, such as creating a loan account or deleting a sales order. The metadata about the message is specified in the message header section.

The relationship between EBOs, EBMs, and EBSs in a direct integration is illustrated in Figure 12 for a Loan Account business entity. As shown in Figure 12, an EBM exists for each operation supported for the Loan Account EBO. WSDL files provide service definitions for each of the operations performed by the Loan Account EBS.

Figure 12. Relationship Between EBOs, EBMs, and EBSs for a Loan Account Business Entity

For additional information on the Oracle AIA framework, architecture, and concepts, see Oracle® Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack.