Re: Enterprise Application Integration

Thanks again Souman. Any2XML converts to any target XML structure using
templates and that is what I have in mind. If the input conforms to
something like CFD (COBOL File Definition)  which  is a 'struct' definition,
then Any2XML would know the data types too. We intend to use the XSLT at the
delivery end if an application needs text input. However Any2XML also
includes XML::Ximple which creates a Perl data structure from XML that we
can programmatically access and print out.


----- Original Message -----
From: "Soumen Sarkar" <SoumenS@xxxxxxxxx>
To: <SOAP@xxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, September 25, 2002 12:09 AM
Subject: Re: [SOAP] Enterprise Application Integration


> Ranga,
>
> If you DO want to use SOAP messaging, then you need to
> convert An2XML output to SOAP messages. Assuming An2XML output
> is not SOAP messages, you need to go through a XML to XML
> conversion step.
>
> Just wanted to point out that there is a W3C standard and
> free tools for XML to XML conversion and that is XSLT.
>
> Soumen Sarkar.
>
> -----Original Message-----
> From: Ranga Nathan
> To: SOAP@xxxxxxxxxxxxxxxxxxx
> Sent: 9/24/2002 8:19 PM
> Subject: Re: [SOAP] Enterprise Application Integration
>
> Souman you have a valid point. I was thinking along the lines you so
> well articulated.
> Though the use case does not demand SOAP implementation, it is good for
> Any2XML to be SOAP compliant. As Sean pointed out, I am persuaded to
> look at SOAP::Lite. Yes there are cases when just the XML document is
> all that is required at some end. But then one needs to add receipting,
> logging and messaging which will be easy to hang on top of a SOAP
> server.
>
> ---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 Soumen Sarkar
> > Sent: Friday, September 20, 2002 1:13 PM
> > To: SOAP@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [SOAP] Enterprise Application Integration
> >
> >
> > I do not understand, why you would go for SOAP RPC. No need! Do the
> > following:
> >
> > 1. Convert any data to XML using Any2XML
> > 2. Transfer the XML document as an attachment. Why take pain
> > converting
> >    the XML document to SOAP RPC format!
> > 3. Receive the XML attahment doc.
> > 4. Convert to any from XML using An2XML.
> >
> > Why are you thinking of "SOAP Objects"? Why extra encoding
> > and decoding -- just transfer the XML doc as it is.
> >
> > On a philosophical note:
> >
> > Every software architecture decision point needs to backed by
> > use case. So if you are thinking of "SOAP Objects" as an
> > software architectural decision point, where is your use case?
> >
> > Substantiate your need to use SOAP by use case.
> >
> > Soumen Sarkar.
> >
> > -----Original Message-----
> > From: Ranga Nathan [mailto:ranga.nathan@xxxxxxxxxxx]
> > Sent: Friday, September 20, 2002 8:36 AM
> > To: SOAP@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [SOAP] 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.
>
> 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.

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