B2B Integration 10.4 | Administering and Monitoring B2B Transactions | webMethods Module for EDIINT | Before You Can Transport Documents Using EDIINT | Configuring Whether Trading Networks Is to Process Payloads
 
Configuring Whether Trading Networks Is to Process Payloads
In addition to having Module for EDIINT perform transport-level processing for an entire inbound EDIINT document, you can perform further processing on the payload of the document by having the module send the payload to Trading Networks for separate processing. As installed, the module is configured to submit the payload to Trading Networks.
When Module for EDIINT is configured to send the payload to Trading Networks, the module submits the payload after it completes transport-level processing.
Use the Module for EDI to process payloads that have one of the following content types:
*application/edi-x12
*application/edifact
*application/xml
*application/edi-consent (which you can use to submit TRADACOMS payloads)
If you want to have Module for EDIINT submit payloads that have a different content type, you must provide your own service to process the payload and submit it to Trading Networks.
* To enable or disable Trading Networks payload processing
1. Open Integration Server Administrator.
2. In the Solutions menu of the navigation panel, click EDIINT.
Integration Server Administrator opens a new browser window to display the Module for EDIINT home page.
3. In the navigation panel of the Module for EDIINT home page, click Configuration.
4. Enable or disable Module for EDIINT to or from submitting payloads to Trading Networks by doing one of the following:
* To enable, select the Submit payload to TN check box.
*To disable, clear the Submit payload to TN check box.
Note: You can also set this option in My webMethods by configuring the submitPayload EDIINT property. For more information, see Configuring EDIINT Properties.
5. In the User Process Payload Service field, specify a service that you created to process payloads and submit them to Trading Networks. You only need to specify a service if:
*You selected the Submit payload to TN check box.
-AND-
*The content types of the inbound payloads are not application/edi-X12, application/EDIFACT, application/XML, or application/edi-consent.
The service you specify in the User Process Payload Service field must accept the following input variables:
Input Variable
Description
stream
InputStream The payload.
contentType
String The content type of the payload.
EDIINTbizdoc
Document The bizdoc that contains the original EDIINT message. For the structure of EDIINTbizdoc, see the wm.tn.rec:BizDocEnvelope service in the webMethods Trading Networks Built-In Services Reference for your release.
attachmentsPartName
Document List Collection of attachments from the original EDIINT message.
Variable
Description
attachmentPartName
String Internal name assigned to the attachment for unique identification.
attachmentPartStream
InputStream The attachment stream attached to the original message.
Note: You can also specify this service in My webMethods by configuring the userProcessPayloadService EDIINT property. For more information, see Configuring EDIINT Properties.
6. Module for EDIINT ignores your settings in the following situations:
Conditions
Behavior of Module for EDIINT
*You select the Submit payload to TN check box -AND-
*You specify a service in the User Process Payload Service field -AND-
*The inbound payload has a content type that is one of:
*application/edi-X12
*application/EDIFACT
*application/XML
*application/edi-Consent
Module for EDI ignores the service you specify in the User Process Payload Service field.
When you select the Submit payload to TN check box, Module for EDIINT always uses the Module for EDI to process payloads that have one of the following content types:
*application/edi-X12
*application/EDIFACT
*application/XML
*application/edi-Consent
*You select the Submit payload to TN check box -AND-
*You do not specify a service in the User Process Payload Service field -AND-
*The content type of the inbound payload is not one of:
*application/edi-X12
*application/EDIFACT
*application/XML
*application/edi-consent
Module for EDIINT ignores the check in the Submit payload to TN check box.
The module cannot submit a payload with an unsupported content type to Trading Networks. You must provide a service that submits payloads with unsupported content types.
*You clear the Submit payload to TN check box -AND-
*You specify a service in the User Process Payload Service field.
Module for EDIINT ignores the service you specify in the User Process Payload Service field.
The module only invokes a service you specify to submit payloads to Trading Networks when you select the Submit payload to TN check box.
7. Click Save Changes.
Note: For information about how to set up Module for EDI and Trading Networks to process EDI documents, see the webMethods Module for EDI Installation and User’s Guide .
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release