WSID : THIS IS AN ARCHIVE SITE

The current integration is being done for Boston at http://www.xmethods.net/wsid-08-2002

This page hosts documents for the upcoming web services interoperability demo being produced by XMethods and SIGS101 for the XML WebServices One conference,  August 26-30, Boston.

If you are interested in participating, please contact Jim Turner

PLEASE NOTE:  This interoperability demo is a trade show event currently being produced by the XML WebServices One conference.  This event has no official relationship to SOAPBuilders!

======= Customer to Bank

Viewer for Test Log service
Viewer for Test Status service

>>>>>>> 1.21

Documents  Tables 

Demo Detailed Description

Abstract WSDL  for:

Supplier Interfaces
Warehouse Interfaces
Bank Interfaces
Logging Interface

<<<<<<< index.html

Integration Status Table

Roles Table
=======

Integration Status Table

Roles Table
>>>>>>> 1.21 Supplier to Warehouse Mapping
<<<<<<< index.html Customer to Credit Bureau

Viewer for Test Log service
Viewer for Test Status service

 

UDDI v1/v2 Inquiry Endpoint   :   http://www.xmethods.net/idemo/inquire

XMethods Log Viewer:  http://www.xmethods.net/wsid-08-2002/tools/XViewer.msi

 

 

Timeline

July 5 - Updated specification finalized. 

July 8 - August 2 - Development

August 5 - Integration testing begins.  We'll have a conference call to synchronize at the beginining of this week.

August 26 - Setup at show; final onsite integration testing.

 

Selecting a Role

The first task for participants is to select a role or set of roles to implement for the demonstration.  The following guidelines should be used to aid in your decision.  Once you have made your decision, please email me at thong@xmethods.net and I willl perform the appropriate setup activities and add the information to this page.

There are currently four roles defined:

The supplier is the most complex role, but it is also the most central and visible role.  Suppliers interact with all other role types.  Suppliers must be able to handle being an RPC/encoded server, a RPC/encoded client, and a doc/literal client.

The warehouse acts as both a RPC/encoded client and server.  Partiipants must be able to handle SOAP structures and arrays used in the RPC interactions.

The bank acts as a document/literal server.  As such, it must be able to handle the processing of literal XML payloads in document-style SOAP envelopes.

The customer role is a client-only role.  Participants must be able to execute RPC calls and handle SOAP structures and arrays.