Sending Documents to Your Trading Networks from Another System
If a trading partner does not have its own Trading Networks, the partner must use an application that communicates with the host Integration Server to send documents to Trading Networks. This application is called an IS client. Clients can be Java, C/C++, or browser based.
If sending an XML document, the client must invoke the wm.tn:receive service. If sending a flat file document, the client must invoke a document gateway service, and the gateway service must invoke the wm.tn:receive service.
Business documents exchanged in
Trading Networks are stored in the database. If these documents contain personal information of users, you can remove those documents using the archival services. See
Archiving and Deleting Documents for instructions to archive and delete documents.
Clients can send documents to Trading Networks service using the methods listed in the following table:
Method | Client |
Post an XML or flat file document to the Integration Server through HTTP, HTTPS, FTP, SFTP, FTPS, or SMTP. | Any type except browser based |
Submit an XML document in the $xmldata variable. | Any type |
Send an XML or flat file document by invoking a Web service you publish. | Any type |
You can create a Web service using any Integration Server service. The service you use to create the Web service must internally invoke the wm.tn:receive service.
The following table lists the links for additional reading:
Subject | See |
Creating and publishing Web services | Web Services Developer’s Guide |
Creating clients | webMethods Service Development Help |
Passing XML data to services | webMethods Service Development Help |
Security for this type of document exchange | |