Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this document? Why not share!

Integration Within Several Projects

on

  • 1,942 views

 

Statistics

Views

Total Views
1,942
Views on SlideShare
1,936
Embed Views
6

Actions

Likes
0
Downloads
84
Comments
0

4 Embeds 6

http://supratech.co.il 3
http://localhost 1
http://www.supratech.co.il 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Integration Within Several Projects Integration Within Several Projects Document Transcript

    • 1. Project – A (Israel) The implementation of the project was by Siebel 2000 and based mostly on dedicated client. The case is classical thick windows client. The implemented system has been integrated within the company enterprise using two integration approaches: asynchron and synchronous. The following figure illustrates ous high level of integration framework. As wrote above the whole possible interfaces within the Siebel system were divided on two groups for asynchronous and synchronous integration using MQSeries transport/receiver and local COM object respective ly. The local COM object allowed encapsulation of synchronous integration using asynchronous messaging engine provided by MQSeries. The MQSeries transport and receiver are internal Siebel tools designed just for using against MQSeries suite. Inbound interface were handled just by MQSeries. 2. Project – B (Israel) The implementation of project was by Siebel 2000 and based mostly on dedicated client. The case is classical thick windows client. The implemented system has been integrated within the company enterprise using two integration approaches: asynchron and synchronous. The following figure illustrates ous high level of integration framework
    • As wrote above the whole possible interfaces within the Siebel system were divided on two groups for asynchronous and synchronous integration using MQSeries transport/receiver and HTTP transport/EAI object manager respectively. The HTTP transport has been used as ultimate tool for outbound interfaces, when inbound have been handles by EAI object manager using appropriate definitions within Siebel Enterprise Server and object manager's configuration file. The MQSeries transport and receiver are internal Siebel tools designed just for using against MQSeries suite. Inbound interface were handled respectively to their nature by MQSeries or EAI object manager. 3. Project – C Israel The implementation of project was by Siebel 7.8 and based completely on web client. The case is classical thin windows client. The implemented system has been integrated within the company enterprise using two integration approaches: asynchron and synchronous. The following figure illustrates ous high level of integration framework As wrote above the whole possible interfaces within the Siebel system were divided on two groups for asynchronous and synchronous integration using just by HTTP
    • transport/EAI object manager or wrapped Java adapter for the integration layer based TIBCO The wrapped Java adapter allowed synchronous integration as well as asynchronous when provided: Submit, GetResponse, and SubmitResponse methods.The approach allowed effective synchronous integration through the SubmitResponse method and asynchronous through Submit and GetResponse methods. The Java adapter has been wrapped by Siebel Java Service. The alternative path for integration was provided using standard HTTP transport as well as Service Web Service. The inbound interfaces were handled by EAI object manager using EAI dispatcher or Siebel Web Services