Re: Enterprise Application Integration

Thanks for that response Sean!
The integration involves conversion of non-XML data to XML (using
Any2XML) and marshall into some uniform layout (thinking SOAP objects
here) and decode, convert from XML to whatever at the other end, in
order to connect the end points. I am assuming SOAP is synchronous like
XML::RPC, otherwise we could use a database (PostgreSQL) or if the
customer wants to spend $$$ then MQ Series / Tibco etc.

Thanks again for the input.

---Closing information gaps-----
Ranga Nathan, Reliance Technololgy
>>Live demo at http://any2xml.com/docs/timesheet_demo.shtml<<
>>Get free COBOLExplorer at http://goreliance.com/download-products <<

> -----Original Message-----
> From: Discussion of implementing SOAP applications today
> [mailto:SOAP@xxxxxxxxxxxxxxxxxxx] On Behalf Of Sean Meisner
> Sent: Thursday, September 19, 2002 1:09 PM
> To: SOAP@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [SOAP] Enterprise Application Integration
>
>
> Hi,
>
> By reading this I am not sure if what you want to do is a
> customized integration for a customer, or to provide a
> generic integration interface to go along with your toolkit.
>
> If you are going to provide a generic integration interface
> with your software, I would say use SOAP::Lite, for the very
> reasons you suggested.  Wider application and standards
> compliance.  From what I have seen and done, I don't think
> SOAP::Lite is substantially harder to use than XML::RPC.
>
> However if you are doing a custom project then I would
> suggest you need to base your decision on what technologies
> the applications you wish to integrate already use.  Do they
> have SOAP or XML::RPC interfaces?  If not, and if all you
> need to do is exchange XML documents, I would seriously be
> inclined to simply use email or standard CGI on a web server
> to pass the documents around.  Or a message system like
> MQSeries or Tibco.  This would probably be somewhat faster to
> implement.  If all you want to do is pass some XML data
> around, SOAP could be overkill.
>
> Again, it all depends on the nature of your project.
>
> Cheers,
>
> Sean
>
>
> > -----Original Message-----
> > From: Ranga Nathan [mailto:ranga.nathan@xxxxxxxxxxx]
> > Sent: Tuesday, September 17, 2002 2:11 PM
> > To: SOAP@xxxxxxxxxxxxxxxxxxx
> > Subject: [SOAP] Enterprise Application Integration
> >
> >
> > I am proposing an integration project using our software
> Any2XML (free
> > download at http://goreliance.com/devel) which is also
> available as an
> > ActiveX dll. While this will work as an agent between disparate
> > applications, I still need a transport mechanism to deliver the
> > messages. As we do almost all our work in Perl, I am not sure if I
> > should stick with XML::RPC or SOAP::Lite. It appears that
> XML::RPC is
> > certainly quicker to implement and less complex but SOAP holds a
> > bigger promise of wider application and standards
> compliance. But SOAP
> > is not 'Lite' anymore with the way the big companies are
> pushing it.We
> > are working with tight budgets and need to complete
> projects quickly
> > in order to see some money.
> >
> > I am trying to learn from others' experience before I committ to
> > anything. Thanks for your input
> >
> > ---Closing information gaps-----
> > Ranga Nathan, Reliance Technololgy
> > >>Live demo at http://any2xml.com/docs/timesheet_demo.shtml<<
> > >>Get free COBOLExplorer at
> http://goreliance.com/download-products <<
> >
> > You can read
> messages from the SOAP archive, unsubscribe from SOAP, or
> > subscribe to other DevelopMentor lists at
> http://discuss.develop.com.
> >
>
> You can read messages from the
> SOAP archive, unsubscribe from SOAP, or subscribe to other
> DevelopMentor lists at http://discuss.develop.com.
>

You can read messages from the SOAP archive, unsubscribe from SOAP, or 
subscribe to other
DevelopMentor lists at http://discuss.develop.com.