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
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
Nice Posting...Thank you
ReplyDelete