Siebel Wire: 3 Nov 2011

Thursday 3 November 2011

Want to Learn Siebel EAI ???..Part2

Here comes the Part2....
Previous posting had identified the Areas to be concentrated while implementing an EAI solution.This Post would take through each of the identified areas.

1.What kind of Integration Architecure ?
Identifying the Integration Architecture plays major role in EAI. Siebel Provides various built in functions or Vanilla functions to support Integration.

Standard Siebel EAI Architecture

This Architecture covers various Vanilla Components/Subsytems defined by Siebel Appplication to support Data transport mechanisms.
Lets have few Examples..
1.To Integrate with a Mainframe Application the solution would be to go for MQ series.Siebel has various Subsytems defined to support the MQ middleware.
2.In case of transactions happening over the web we have HTTP transport Subsytem Defined to Support.

Here the Subsytem means Collection Of Parameters to Support Driver-Eg. MQ/HTTP.
Message Queue Parameters-Target System IP/Queue Name/URL/PortName need to be provided while configuring the Transport

Want to Learn Siebel EAI ??? Part1

I have seen many of my friends who want to learn Siebel EAI but not sure of where to begin with??
Lets start with few simple Qs,
           -What is EAI-Enterprse Application Integration ?
           -Why EAI ?
           -What are the benefits/Advantages of EAI ?

EAI is essential to Share the Data between 2 or more Applications. Data may be centralized or may have spread across various Applications but data sharing is essential in achieving efficienct,Cost Effective implemenation .The data share may happen in various ways either Synchronous(Online) or Asynchronous(Offline) or batch load.
Any EAI Implementaion basically concentrates on...
1.What kind of Integration Architecure ?
2.What kind of Data Shared?
3.Which Type of Target Application- Portal/Java/Mainframe??
4.Data Flow Across Applications
5.Primary Data Source.
6.Available Integration Techniques
Continued.....