Adapters (Enhanced)
Use
● To make it easier for you to enter parameters, the parameters for adapters with many input parameters are grouped together on multiple tabs. The function of the adapter remains the same.
The following adapters are divided into tabs:
RFC, File/FTP, JDBC, JMS, Mail, SOAP, CIDX and RNIF (1.1 and 2.0).
There may be empty tabs for CIDX and RNIF adapter scenarios.
● The following functions are available for the IDoc adapter:
○ IDoc tracking is now available in IDoc adapter monitoring (IDX5). You can track IDocs and call the corresponding monitors in sender and receiver systems.
More
information:
Displaying XML
Messages.
○ On the Integration Server, you can use the IDoc Adapter: Acknowledgments function to define the acknowledgments you want to request for a sender port and client.
More
information:
Configuring
Acknowledgment Requests.
○ On the Integration Server, you can call a function to convert acknowledgment IDocs to XI request messages and send them.
More
information:
Sending Acknowledgment
IDocs as XI Request Messages.
○ A new parameter is available in the receiver IDoc adapter:
If you set the Restore Original Parties for Acknowledgments indicator, the original parties from the IDoc request message are used. This means you no longer have to maintain the alternative identifiers (for party conversion) in the Integration Directory.
More
information:
Configuring the IDoc Receiver Adapter.
● The following new parameters are available for the file/FTP adapter:
○ For sender adapters you can specify in Advanced Mode the Maximum File Size in Bytes that the adapter can process.
More information:
Configuring the FTP
Sender Adapter,
Configuring the File
Sender Adapter.
○ In the sender adapter, you can make specifications for an archive directory for archiving files if a permanent error occurred when they were processed.
In the MessageTransformBean module, you can set a parameter that defines whether errors of the executed module are to be evaluated as temporary or permanent.
More
information:
Configuring the Sender
FTP Adapter,
Configuring the Sender
File Adapter, under Processing Parameters,
Adding MessageTransformBean in the Module Processor.
○ New parameters are available for converting the file content in the sender adapter.
You can use these parameters to influence the behavior of the conversion routine if the structure at runtime is different from the configured structure.
More
information: Converting
Text Format into
File/FTP Sender Adapter in XML, parameters NameA.missingLastFields and NameA.additionalLastFields.
○ You can specify the Maximum Concurrency for receiver adapters.
This determines how many adapter messages are to be processed in parallel on a cluster node.
More
information:
Configuring the FTP
Sender Adapter,
Configuring the File
Sender Adapter under Processing Parameters.
○ The Create Target Directory parameter allows you to specify that the adapter is to create the target directory if it does not exist.
More
information:
Configuring the FTP
Sender Adapter,
Configuring the File
Sender Adapter under Defining File Access Parameters.
○ You can set how empty files (length 0 bytes) are to be handled in the sender adapter, and how XI messages with an empty main payload are to be handled in the receiver adapter.
More
information:
Configuring the
Receiver FTP Adapter,
Configuring the
Receiver File Adapter,
Configuring the Sender
FTP Adapter,
File /FTP Adapter
Overview, under Defining Processing Parameters.
● The following new parameter is available for the sender JDBC adapter:
○ To remove empty tags from the XML document, you can set the Remove Empty Tags indicator in the sender JDBC adapter.
This allows you to reduce the size of the XML document.
More
information:
Configuring the Sender
JDBC Adapter, under Defining Additional Parameters in Advanced
Mode
○ You can specify the Maximum Concurrency for JDBC receiver adapters. This determines how many adapter messages are to be processed in parallel on a cluster node.
More
information:
Configuring the
Receiver JDBC Adapter under Processing Parameters.
● The following new parameters are available for the JMS adapter:
○ The sender JMS adapter supports the failover of channels with quality of service Exactly Once in Order in a cluster environment.
More information: Configuring the Sender JMS Adapter, under Defining XI Settings, Quality of Service
○ The adapter-specific message attributes have been enhanced in the sender and receiver adapter. You can now use 10 additional attributes to set or use JMS properties in the message header of the XI message.
In the receiver adapter, you can also set the Java type of the respective attribute for the JMS message.
More
information: Configuring the Sender
JMS Adapter,
Configuring the
Receiver JMS Adapter, under Defining Adapter-Specific Message
Attributes
● The SOAP adapter and mail adapter now have additional adapter-specific message attributes in the message header:
More information:
Configuring the Sender
SOAP Adapter
Configuring the
Receiver SOAP Adapter
Configuring the Sender
Mail Adapter
Configuring the
Receiver Mail Adapter
● You can optionally use the Axis framework in the SOAP Adapter and can increase the functionality of the adapter by using Axis handlers.
More
information:
Configuring the Axis
SOAP Sender Adapter,
Configuring the Axis
SOAP Receiver Adapter.
● The following new parameters are available for the plain HTTP adapter:
You can set or use adapter-specific attributes in the sender and receiver adapter for synchronous responses.
More
information:
Configuring the Plain
HTTP Sender Adapter in the Integration Directory,
Configuring the Plain
HTTP Receiver Adapter in the Integration Directory.
Effects on Existing Data
The sender and receiver JMS adapter no longer have the adapter-specific message attributes DCJMSStringProperty1 and DCJMSStringProperty2.
Instead, they have the attributes DCJMSMessageProperty0, DCJMSMessageProperty1, ..., DCJMSMessageProperty9 (see above).
You must adapt the configuration of existing communication channels using these attributes.