Interchange 5.12 Administrator Guide Save PDF Selected topic Selected topic and subtopics All content Message protocols for staged HTTP The staged HTTP transport is supported for the AS2, ebXML, RosettaNet 1.1, RosettaNet 2.0 and secure file message protocols. The following topics provide notes about using each protocol with staged HTTP. Extra configuration steps are required only with the secure file message protocol. AS2 Using staged HTTP to trade AS2 messages does not require any special configuration of the staged HTTP servlet. The servlet, in conjunction with Interchange, knows how to handle asynchronous and synchronous receipts correctly. ebXML Using staged HTTP to trade ebXML messages does not require any special configuration of the staged HTTP servlet. The servlet, in conjunction with Interchange, knows how to handle asynchronous and synchronous acknowledgments correctly. RosettaNet 1.1 and 2.0 Using staged HTTP to trade RosettaNet 1.1 and 2.0 messages does not require any special configuration of the staged HTTP servlet. However, Interchange does not support synchronous RosettaNet 2.0 responses of any type (single or dual action). Consequently, synchronous RosettaNet 2.0 responses over staged HTTP are not supported. Secure file Supporting the secure file message protocol requires special configuration of the staged HTTP servlet. The configuration requires editing two files in the staged HTTP servlet’s conf directory on the application server: configurationrules.xml and webmailboxconfig.xml. After editing the files, restart the servlet. Support for the secure file protocol by the staged HTTP servlet is on a mailbox-by-mailbox basis. To have all mailboxes added from this point forward support the secure file protocol, open the configurationrules.xml file and add or change the DefaultPostMode element to the Mailbox element inside the MailboxTemplate element. See the following figure configurationrules.xml file. <Rules> ... <MailboxTemplate id="default"> <Mailbox> ... <DefaultPostMode>async</DefaultPostMode> ... </Mailbox> </MailboxTemplate> ... </Rules> To add support for the secure file protocol to specific existing mailboxes, open the webmailboxconfig.xml file and add or change the DefaultPostMode element in each desired Mailbox element in the Mailboxes element see the following figure: webmailboxconfig.xml file. <WebMailboxConfiguration> ... <Mailboxes> ... <Mailbox ...> ... <DefaultPostMode>async</DefaultPostMode> ... </Mailbox> ... </Mailboxes> ... </WebMailboxConfiguration> Related topics Overview of staged HTTP Staged HTTP configuration outline Staged HTTP files to deploy Log on to servlet UI Manage mailboxes Staged HTTP UI fields File forwarding to bypass polling High availability staged HTTP Deploy the web servlet Related Links
Message protocols for staged HTTP The staged HTTP transport is supported for the AS2, ebXML, RosettaNet 1.1, RosettaNet 2.0 and secure file message protocols. The following topics provide notes about using each protocol with staged HTTP. Extra configuration steps are required only with the secure file message protocol. AS2 Using staged HTTP to trade AS2 messages does not require any special configuration of the staged HTTP servlet. The servlet, in conjunction with Interchange, knows how to handle asynchronous and synchronous receipts correctly. ebXML Using staged HTTP to trade ebXML messages does not require any special configuration of the staged HTTP servlet. The servlet, in conjunction with Interchange, knows how to handle asynchronous and synchronous acknowledgments correctly. RosettaNet 1.1 and 2.0 Using staged HTTP to trade RosettaNet 1.1 and 2.0 messages does not require any special configuration of the staged HTTP servlet. However, Interchange does not support synchronous RosettaNet 2.0 responses of any type (single or dual action). Consequently, synchronous RosettaNet 2.0 responses over staged HTTP are not supported. Secure file Supporting the secure file message protocol requires special configuration of the staged HTTP servlet. The configuration requires editing two files in the staged HTTP servlet’s conf directory on the application server: configurationrules.xml and webmailboxconfig.xml. After editing the files, restart the servlet. Support for the secure file protocol by the staged HTTP servlet is on a mailbox-by-mailbox basis. To have all mailboxes added from this point forward support the secure file protocol, open the configurationrules.xml file and add or change the DefaultPostMode element to the Mailbox element inside the MailboxTemplate element. See the following figure configurationrules.xml file. <Rules> ... <MailboxTemplate id="default"> <Mailbox> ... <DefaultPostMode>async</DefaultPostMode> ... </Mailbox> </MailboxTemplate> ... </Rules> To add support for the secure file protocol to specific existing mailboxes, open the webmailboxconfig.xml file and add or change the DefaultPostMode element in each desired Mailbox element in the Mailboxes element see the following figure: webmailboxconfig.xml file. <WebMailboxConfiguration> ... <Mailboxes> ... <Mailbox ...> ... <DefaultPostMode>async</DefaultPostMode> ... </Mailbox> ... </Mailboxes> ... </WebMailboxConfiguration> Related topics Overview of staged HTTP Staged HTTP configuration outline Staged HTTP files to deploy Log on to servlet UI Manage mailboxes Staged HTTP UI fields File forwarding to bypass polling High availability staged HTTP Deploy the web servlet