Java Connector for Siebel and Websphere App Server

I need to get xml information from siebel 7 to Websphere and send response back to Siebel. For this we are planning to use MQSeries for message MOM. Is there any way we can develop Java Connector(using JCA and JMS)for EAI in place of MQSeries or other available MOM. Thanks in advance. Regards, Manish

Developing you own personal JCA is no easy task- there is a lot to do. If you are using MQ and XML- that would do what you are wanting to do. But JCA is just an architecture framework- you certainly can implement it- once again using MQ etc. HTH Sanjay [ April 30, 2002: Message edited by: Sanjay Bahal ]

Hi, Here's what I would do in your situation. 1. Understand the end-to-end integration scenario. It seems like you want to integrate Siebel with a legacy system that is based on MQSeries. The first thing to do is document the interactions between Siebel and the legacy system without any implementation details. 2. If Siebel is hosted on a J2EE server, then you could develop a JCA resource adapter for MQSeries or JMS provided your version of MQSeries is JMS compliant. 3. The interaction between the Siebel application and legacy system which you document in step 1 should form the basis of your JCA adapters CCI based API. 4. You can definately use XML for the interface if you have the right tools and frameworks to support it. 5. Have a good test plan for testing the integration scenario. There are a number of other things that you will have to do when developing a JCA resource adapter. If you like send me an email and we can exchange some more thoughts on this. Bottom line, plan you integration from an end-to-end scenario perspective before getting into the JCA and other details. Sincerely, Atul

Hi Atul, Thanks for ur reply, 1./In my Application I am not integrating Siebel to any Legacy system.Siebel is interacting with J2EE application Server for some logical processing & the media for communication is MOM. 2./Siebel is hosted on Microsoft's IIS. 3./My Application Flow is: Siebel recieves user request and its EAI generates XML file. Middleware(MOM) monitors a directory on the Siebel's server where new XML file is placed. Middleware transports (and/or manipulates) XML data to adapter in the J2EE Application Server . The adapter passes the XML to message Driven Bean which in turn passes it to some session Beans & response is transfered back to another Message driven bean which in turn passes it to Adapter & so on. So, I need to develop a generic adapter ;which should work with all MOM and J2EE Application Server. Any suggestion.... Thanks in advance... Regards, Manish

Tiger Scott
Ranch Hand

Joined: Mar 01, 2001
Posts: 223

posted May 02, 2002 06:34:00

0

Manish, just out of curiosity- why does Seibel write a XML file and place it in a directory- and not directly send a message with the XML? Sanjay

Atul Apte
Author
Greenhorn

Joined: Feb 19, 2002
Posts: 29

posted May 02, 2002 09:01:00

0

Manish, The scenario as you described is one of the cases which are not ideal for JCA JCA works best when a J2EE application requires information from EIS not the otherway round. However in my book I have described a very similar scneario and how to potentially solve it. Your approach seems right although there are too many moving parts in between. Managing the scenario will be difficult at runtime as the volume of transactions go up. However, here's what I would suggest.. Choose a specific MOM if you haven't already done so. Preferably a JMS compliant MOM like MQSeries. This hopefully will eliminate the need for an adapter on the J2EE platform side.. a message driven bean may be enought (as you have stated). Also I would look into session management between the adapters (the message driven bean, and the IIS based directory monitor). This will be needed to ensure there is no data loss, and request/responses are coordinated properly. If you log on to our web site www.iconexio.com and send us an email with a little bit more detail on platforms, MOM, etc. we can send you our integration plaform/tool for evaluation. It may help you solidify your architecture and concepts. Atul

Yuvraj Singh
Greenhorn

Joined: Apr 30, 2002
Posts: 11

posted May 03, 2002 04:28:00

0

Hi Atul, Sanjay for your answer Siebel understands User request in its own language(siebel has a set of proprietory language ) & it is suffiecient for its own working but when we need to extract these information for EAI or any other; we have to configure its workflow to add EAI Siebel Adapter business service which converts it to XML using EAI XML Converter & puts into the directory specified. So, here Siebel's job ends & if we want to use these XML information there are two methos 1./EAI MQSeries transport 2./EAI HTTP TransportAtul, as with second method EAI HTTP TransportAtul;I am reconsidering my design: 1./I think I can place a servlet over ejb beans in the J2EE Application Server ; this Servlet(its URL I can specify in the EAI HTTP Transport) would take care of request and response ; Servlet could pass over the XML request( which it will get from Siebel HTTP Transport)to ejb session beans and can get response from these beans. There are methods in siebel for session management(synchronous request/response method). I am just thinking of this architecture(as this will remove MOM) ;but not sure of interoperability of IIS with J2EE App Server, Performance bottlenecks,Security etc. Could you shed some light over this Architecture. Thanks in Advance, Regards, Manish S

Yuvraj Singh
Greenhorn

Joined: Apr 30, 2002
Posts: 11

posted May 03, 2002 06:09:00

0

Hi Atul, Sorry ,I forgot to add that I am in the process of finding out which Messaging Service would be suitable for my Application; Asynchronous or Synchronous. After this I will decide over the final Architecture of using MOM or HTTP transfer for the Application. Any suggestion for this scenario... Thanks in advance, Manish S

Atul Apte
Author
Greenhorn

Joined: Feb 19, 2002
Posts: 29

posted May 03, 2002 11:24:00

0

Manish, I think your architecture and idea of using a servlet over HTTP will work. It will be better to get an idea of how many transactions or messages you expect to process thru this channel. If that volume is very high then it may be better to go with an async messaging platform as the middleware. The best strategy is to use a framework that will enable you to plug-and-play components as you scale the number of transactions between Siebel and other systems. The framework should also help simplify the management aspect of the integration components. Have you documented the integration scenarios? In my book I have also mentioned why integration scenario analysis is important to any integration project. Atul