Share

Siebel EAI – Introduction

Introduction to Interface

Organizations need to integrate business processes across a large number of disparate applications in order to drive revenue growth, increase productivity, and gain visibility into business performance.

To integrate Siebel Business Applications into the Universal Application Network, Siebel Systems continues to enhance the integration tool set within Siebel applications—Siebel Enterprise Application Integration (Siebel EAI).

About Siebel EAI  Siebel EAI provides components for integrating Siebel Business Applications with external applications and technologies within your company and is designed to work with third-party solutions such as those from IBM, TIBCO, WebMethods, and others. 

 

Siebel EAI provides bidirectional real-time and batch solutions for integrating Siebel applications with other applications as well as the tools for cross application integration through UAN.  Siebel EAI is designed as a set of interfaces that interact with each other and with other components within Siebel application. These interfaces: 

  • Allow a flexible service-based architecture, built on top of configurable messages using XML and other formats. 
  • Are compatible with IBM MQSeries; Microsoft MSMQ, BizTalk, and OLE DB; Sun Microsystems Java and J2EE; XML, and HTTP, and many other standards. 
  • Expose internal Siebel Objects to external applications. 
  • Take advantage of prebuilt adapters and enterprise connectors, and are compatible with thirdparty adapters and connectors. 

 

  • Allow for data transformation. 
  • Integrate external data through Virtual Business Components (VBCs) and External Business Components (EBCs).
  • Provide a graphical business process designer, programmatic interfaces, and a high-volume batch interface.

We will discuss Siebel EAI in detail.

2 comments on “Siebel EAI – Introduction”

  1. Prasad Reply

    Fetching the Primary Contact from the Integration Object
    ********************************************************
    Hi Dears
    I have built an Integration Object with Account and Contact
    When ever i generate the Siebel Message, the Siebel Message should contain Only Primary Contact

    For this, One Alternative is we can create a Data Map and give the Source Search Specification at IC level as IsPrimaryMVG = “Y”
    But i don’t like to use the Data Mapper and would like to filter in the IO Level itself

    Under my Workflow I have created Process Property called SearchSpec and mentioned default string as: [Account_Contact.IsPrimaryMVG] =”Y”
    i.e Integration Component.Field Convention

    When I use the above SearchSpec in the Workflow Process and Simulating ,getting an error as mentioned below

    ******************************************************************
    Error invoking service ‘EAI Siebel Adapter’, method ‘Query’ at step ‘Fetch Primary Contact’.(SBL-BPR-00162)

    Method ‘Execute’ of business component ‘Contact’ (integration component ‘Account_Contact’) returned the following error:
    “No field matches identifier ‘IsPrimaryMVG’.
    Please ask your systems administrator to check your application configuration.(SBL-DAT-00416)”(SBL-EAI-04376)
    *******************************************************************
    Could you please let me know how can i resolve this and fetch the only Primary Contact and what are all the alternative methodologies to achieve the same?

    Thanks in Advance

    Prasad

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!