• B2B ADAPTERS - PROCESSORS
• Transaction Attributes
• Key Encryption
• B2B Authentication
• Charset Conversion
• EBCDIC to ASCII
• Base64 Encoder
• Chained Transactions
• Data Attribute Swapper
• Zip / Unzip
• XLS to XML
• MD5 Hashing
• Java XML Binding
• MIME Decoder
• MIME Encoder
• MTOM
• TIFF to XML
• Remove Namespaces
• Regex Evaluation
• Add SOAP Header
• Symmetric Encryption
• XML Logging
• XML Validation Rules
• WS-Security
• XML to PDF
• XPath Evaluation

MTOM

The XCS eiConsole's MTOM Input Processor Parses an MTOM-Encoded (Message Transmission Optimization Mechanism) Message Into Text

The MTOM Input Processor allows you to parse an MTOM-encoded (Message Transmission Optimization Mechanism) message into text. As with all the components of the eiConsole the user is presented with a graphical interface with easy to configure panels. The user selects the MTOM Input Processor from the drop down menu of the Add Processor Panel.

Configuring the MTOM Input Processor requires first specifying a parameter handling method (XPath or Literal). The "XPath" and "Literal" configuration tabs are selected based on this parameter handling. Using the XPath-based method, the user supplies two XPath expressions to provide the external reference ID for attachments and the attachment filename. With the literal-based method, the user provides only a file folder and a path for the attachment.

MTOM Output Processor

The XCS eiConsole's MTOM Output Processor Converts a SOAP Request into an MTOM-Encoded (Message Transmission Optimization Mechanism) Message, Including Attachments

Similarly to the MTOM Input Processor configuring the MTOM Output Processor requires first specifying a parameter source, which is either XPath or Literal-based. Both the XPath and Literal configuration tabs provide fields for naming attachments and identifying them.