Cove XML Business Catcher and XML Dispatcher

advertisement
Application Note
Cove XML Business Catcher and XML Dispatcher
XML (Extensible Markup Language) allows data to be exchanged in a format that
is both computer and humanly readable, using an extension of the industry
standard HTML language. This flexibility allows the data exchanged to be
displayed in a humanly readable form using a standard Web Browser.
Additionally, this standard format allows the transfer of these documents via the
Internet.
Operational Flow Overview
When you have data to send, the originating system’s XML Dispatcher uses the
Internet, an Intranet, or a Private Virtual Circuit to connect to the recipient's web
server. This connection can either be by HTTP or HTTPS. Connections made
using HTTPS enjoy the benefit of a completely secure encrypted connection.
The originating party only needs to know the recipient's web server address and
XML interface name, for example https://www.clienturl.com/cgi-bin/covexml
When your XML Business Catcher receives the XML document, it is passed to
your XML Router, behind the firewall. Your XML Router, working directly with
your STREAM II ERP system, is able to respond to the request in real-time.
XML looks like it will be a replacement for classical EDI as it provides significant
benefits:
1. It eliminates the VAN (Value Added Network), as a standard now exists for
the transfer of documents via the Web.
2. Mapping is substantially easier as data tags are part of the document.
© 2000 Cove Systems, Inc.
D:\533578940.doc
Application Note
3. Implementation costs are lower as less third party software is required. It
is possible to expand the document formats unilaterally and still maintain
backward compatibility with existing trading partners.
The following diagram shows the elements of the Cove XML Interface in a
typical environment.
Trading
Partner 1
Trading
Partner 2
Web Server with
XML Business
Catcher and Java
Connection Server
Linux Host with
XML Dispatcher,
XML Router, XML
Uploader and
Firewall Java Data Server
Linux Host
with Stream II
Data
The
Internet
Public
Network
Private
Network
Internet
Accessible
Technical Operational Description
Using a price request as an example, the following operational flows detail the
processes of both outbound and inbound transactions.
© 2000 Cove Systems, Inc.
D:\533578940.doc
Application Note
Outbound
5. Trading Partner
returns result of P&A
request to XML
Uploader.
6. XML Uploader passes
data back to XML
Dispatcher which writes it to
REPORT file for user
process to pick up.
`
2. XML Dispatcher
processes request to
generate XML
request.
The
Internet
4. Trading Partner recieves
required data and processes it
as an Inbound XML request..
Public
Network
1. User initiates
P&A outbound
request.
Private
Network
3. XML Uploader uploads resulting data
to the XML Business Catcher on Trading
Partner's Web Server..
1) The user initiates a P&A request from within the application. To do this, the
application creates an XML request by creating a record in the REPORT file
containing the XML request. Using the REPORT file allows users on multiple
platforms to submit requests. For example, remote users on a mixed Unix
and Windows/NT system could not always share a directory.
2) The XML Dispatcher (fvxmlout) picks up the request from the REPORT file,
and generates a properly formatted and encoded request message that it
passes to the XML Uploader.
3) The XML Uploader reads the address from the first line of the XML document,
connects to the recipient's Web Server XML Business Catcher though the
Firewall, and posts the data to the remote Business Catcher.
4) The Trading Partner processes the request.
5) The Trading Partner returns the result of the request to the XML Uploader.
© 2000 Cove Systems, Inc.
D:\533578940.doc
Application Note
6) The XML Uploader passes the result to the XML Dispatcher, which writes the
response data to the same REPORT record that created for the XML request
and changes the Status to ‘R’.
7) The originating program picks the response up from the REPORT file and
continues processing.
© 2000 Cove Systems, Inc.
D:\533578940.doc
Application Note
Inbound
1. P&A Request sent
to the XML Business
Catcher by the
trading partner
2. XML Business
Catcher receives the
request, preprocesses it
and passes it to the XML
Router via JCS/JDS..
3. XML Router
receives request and
passes it to P&A
data formatter.
Firewall
The
Internet
6. Trading
Partner
recieves
required data.
5. XML Business
Catcher passes
result back to
Trading Partner.
Public
Network
Private
Network
4. XML Router uploads
resulting data to the XML
Business Catcher.
1) The originator initiates an XML request and posts it to the XML Business
Catcher (COVEXML) on your Web Server.
2) The XML Business Catcher receives XML documents and does any required
pre-processing, including removing any MIME wrappers, decompressing it,
etc.
3) Then the Business Catcher sends the document through the Firewall using
the JCS/JDS interface to the XML Router
4) The XML Router (fvxmlin) does the following:
a) Determines the source of the XML document.
b) Checks the document for structural completeness against available DTDs.
c) Formats the document for better readability. During this process it reads
the document from the clipboarf and writes the source document out as an
ASCII file (name: F248:#XMLIN.X1), then processes it and rewrites it with
the extension X3.
d) Forwards the XML document to the correct Master Processor.
5) The Master Processor (fvXxxxMP) the does the following:
© 2000 Cove Systems, Inc.
D:\533578940.doc
Application Note
a) Checks the document to confirm the correct version number
b) Determines what type of documents it is.
c) Passes the document to the appropriate Transaction Processor
6) The Transaction Processors do the following:
a) Parse the contents of the XML document into the required data items.
b) Authenticates the transaction.
c) Creates a file (extension XOT) containing the response in XML format, if
the transaction requires a response.
7) The XML Router reads the XOT file, then passes the document through the
firewall to the XML Business Catcher via the JCS/JDS interface, where the
Business Catcher sends it to originator.
© 2000 Cove Systems, Inc.
D:\533578940.doc
Application Note
Configuration and Testing Information
Address to post inbound XML documents to, from outside the Firewall.
Testing at Cove: http://oldboys.covesys.com/cgi-bin/covexml
Live Transactions at Cove: http://covesys.com/cgi-bin/covexml
Test XML document submissions: run xmltest.sh {document}must be in Mimi
wrapper for CommerceOne or normal file for non CommerceOne.
© 2000 Cove Systems, Inc.
D:\533578940.doc
Download