Advanced Adapter Engine

Use

Feature

Type of Change

Description

Advanced Adapter Engine Extended

New

The Advanced Adapter Engine Extended (AEX) is a new installation option of SAP NetWeaver Process Integration.

It provides the connectivity capabilities of the Advanced Adapter Engine (AAE) as well as design and configuration tools (ES Repository and the Integration Directory) to set up integration scenarios that are based on the AAE.

The AEX is based on AS Java alone. Therefore, it is easier to install and maintain as well as it needs less memory and data storage.

More information: Advanced Adapter Engine Extended

Feature	Type of Change	Description
Channel Specific Timeout	New	Channel specific timeout decouples each channel from the messaging system and enables the channels to have their own timeout. More information: Setting a Channel-Specific Timeout
Message Versioning on the Advanced Adapter Engine	New	Configure where message versions are stored on the Advanced Adapter Engine. More information: Saving Message Versions in the Advanced Adapter Engine
IDoc adapter on the Advanced Adapter Engine	New	You use the IDoc adapter (AAE) to have IDocs (intermediate documents) processed by the Advanced Adapter Engine. You can also use the IDoc adapter (AAE) to connect and process requests from non-SAP business systems by the Advanced Adapter Engine. More information: Configuring the IDoc Adapter (Advanced Adapter Engine)
HTTP adapter on the Advanced Adapter Engine	New	You can leverage the high performance capabilities of the Advanced Adapter Engine for the HTTP message traffic. More information: Configuring the Java HTTP Adapter
Topic support (publish/subscribe) in the JMS adapter	Changed	The JMS Adapter now supports both JMS publish/subscribe and point-to-point communication. More information: JMS Publish/Subscribe and Point-to-Point Communication
Configure the maximum message size and row size fetched from data base in JDBC adapter	Changed	More information: Configuring the Sender JDBC Adapter Defining Additional Parameters in Advanced Mode , additional parameters for large message size.
File splitting (EOIO processing of large binary files) in the File/FTP sender adapter	Changed	You can select this settings for larger files (for example, larger than 1 gigabyte). The file is first divided up into smaller file parts. These file parts are then processed individually at runtime. More information: Configuring the Sender File Adapter Configuring the Sender FTP Adapter
Configuring a mapping-based message split for local message processing on Advanced Adapter Engine	Changed	For a mapping-based message split, an outbound message is divided into multiple target messages using a multi-mapping. You can now also configure this option for local message processing on Advanced Adapter Engine (in the integrated configuration object in Integration Directory). More information: Configuring Mapping-Based Message Splits
CPA Cache	Changed	Minimal use is now made of cluster communication. This makes the CPA Cache more robust and ensures that the same CPA objects are on all the server nodes. The following properties can be configured: `communication.type` More information: Properties for XPI Service: CPA Cache `updateCPACacheJobInterval` More information: Properties for XPI Service: CPA Cache
SOAP sender adapter handles XI bulk messages	New	The SOAP sender adapter can split the incoming bulk message into individual messages.
Exactly Once In Order Messages	New	Handling of Exactly Once In Order (EOIO) messages is more robust. Exactly Once In Order (EOIO) messages with the same serialization context can be processed on the same J2EE server node. This reduces communication between the nodes, thus improving system performance.. This feature is controlled by parameter AE_EOIO_OPTIMIZE. AE_EOIO_OPTIMIZE determines whether the JSESSIONID cookie is sent for messages with a Quality of Service EOIO that are sent by the Integration Engine to the Adapter Engine without a user ID (Principal Propagation). By default, parameter AE_EOIO_OPTIMIZE is active. If you need to disallow JSESSION cookies, you can deactivate this feature.
Out Of Memory Handling	New	Out Of Memory (OOM) Handling has been improved. Errors due to memory leaks and incorrect sizing can be resolved by restarting the process. Errors caused by a single very large request or a few very large requests can be resolved without restarting the process.
MS Job Framework lock handling	New	Improved (auto-)recovery features for resolving lock conflicts.
Safe Restart	New	The restart behavior has been improved as follows: Loading of held EOIO messages into the sequencer Server startup is decoupled from backlog loading in order to prevent startup failures or timeouts. Asynchronous processing is used. Loading of EO backlog messages at connection registration time Server startup is decoupled from backlog loading in order to prevent startup failures or timeouts. Asynchronous processing is used. Synchronize Messaging System connection registration with JEE startup Message processing is started in synchronization with service and applications startup. Synchronize polling Adapter startup with JEE startup Message processing is started in synchronization with service and applications startup.
New Properties of XPI Service AF Core	New	XPI service AF Core uses new properties for aggregating data of the message payload for license auditing. More information: Properties for XPI Service: AF Core
Message Protocol XI 3.0 in SOAP Adapter	New	If you want to send an XI message via the XI message protocol to or from an Advanced Adapter Engine through the SOAP Adapter, then select the Message Protocol as XI 3.0. More information: Configuring the Sender SOAP Adapter and Configuring the Receiver SOAP Adapter
Additional Parameters in Mail Adapter	New	You can configure additional parameters when IMAP4 is selected as Transport Protocol. More information: Configuring the Sender Mail Adapter
Enhanced Routing Capabilities	Changed	When configuring local message processing by the Advanced Adapter Engine, you can now define routing conditions. More information: Defining the Integrated Configuration
Module to Add Attribute Values in Dynamic Configuration in Sender Mail Adapter	New	You can use the MultipartHeaderBean module to add the attribute values in dynamic configuration. More information: Adding MultipartHeaderBean in the Module Processor
Module to Convert IDoc XML to Flat File and Vice Versa	New	You can use the IDOCXmlToFlatConverter module to convert IDoc Xml to IDoc flat format and IDOCFlatToXmlConverter module to convert the data in IDoc flat format to Xml format. More information: Adding IDOCXmlToFlatConverter in the Module Processor and Adding IDOCFlatToXmlConverter in the Module Processor
Blacklisting	New	Blacklisting can prevent situations in which individual messages cause servers to become overloaded and even to fail. Blacklisting works by identifying and isolating messages that appear likely to cause a problem, or that were being processed when a server failure occurred. More information: Blacklisting
Local Message Processing on the Advanced Adapter Engine	New	Using Integrated Configuration you can define a local Message Processing on the Advanced Adapter Engine. The Advanced Adapter Engine provides mapping and routing for this locally. Message Processing is only executed on the Advanced Adapter Engine from one adapter to another without the involvement of the Integration Engine. You can gain a great improvement in performance. You can implement all adapters on the Adapter Engine for a local Message Processing on the Advanced Adapter Engine, apart from the RNIF adapters and the CIDX adapters. If you do not use the integrated configuration, message processing will continue to be performed using the Integration Engine.
Adapter Development	Changed	You must adapt adapters and modules that you have developed for SAP Exchange Infrastructure 2.0, SAP NetWeaver 2004 (SAP XI 3.0), and SAP NetWeaver 7.0 (2004s) to use them in SAP NetWeaver Process Integration 7.1. The changes to the Adapter Framework API are only syntactic, not semantic. SAP provides a help for converting partner adapters and modules. If you cannot convert adapters straight away, you can reconfigure them for a non-central Adapter Engine. This Adapter Engine is based on SAP NetWeaver 2004 and SAP NetWeaver 7.0 (2004s). It is connected to the SAP NetWeaver Process Integration 7.1 Integration Server by the XI adapter. SAP is only providing this solution for a transition period. Upgrade your adapters to SAP NetWeaver Process Integration 7.1 and have them certified as soon as possible. For more information about API cross references, see the appendix of SAP Note 1004000 .
File/FTP Adapter	Changed	The following new parameters are available for the File/FTP adapter: In advanced mode, you can specify the maximum file size in bytes to be processed by sender adapters. New parameters are available for the conversion of 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 in the Sender File/FTP Adapter to XML , (NameA.missingLastfields and NameA.additionalLastFields parameters) You can specify the maximum concurrency for receiver adapters. This defines the number of messages an adapter can process in parallel on a cluster node.
File/FTP Adapter	Changed	The following new parameters are available for the file/FTP adapter: 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 File/FTP Adapter in Integration Directory/PCK , section Configuring the (Sender/Receiver) File Adapter , under Defining Processing Parameters 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.
File/FTP Adapter	Changed	The sender file/FTP adapter now has a new parameter: The Create Target Directory parameter allows you to specify that the adapter is to create the target directory if it does not exist.
Adapter and Module Development	Changed	A monitor is provided for your adapter and module development, you can use it to measure the performance of your adapter or module. More information: Measuring Adapter and Module Performance
CIDX Adapter	Changed	Now, the CIDX adapters supports MD5 algorithm as part of the security services. You can specify this under the Security Settings of the sender or receiver agreement. More information: Configuring the CIDX Adapter
RNIF Adapter	Changed	Now, the RNIF Adapter 1.1 supports MD5 algorithm as part of the security services. You can specify this under the Security Settings of the sender or receiver agreement. More information: Configuring Security in the RNIF 1.1 Adapter
JDBC Adapter	Changed	You can specify the maximum concurrency for JDBC receiver adapters. This defines the number of messages an adapter can process in parallel on a cluster node. More information: Configuring the Receiver JDBC Adapter
JDBC Adapter	Changed	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 Additional Parameters .
JMS Adapter	Changed	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 XI Settings , Quality of Service
JMS Adapter	Changed	The sender and receiver JMS adapters 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 that use these attributes.
JMS Adapter	Changed	The following new parameters are available for the JMS adapter: 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 and Configuring the Receiver JMS Adapter under Adapter-Specific Message Attributes
HTTP Adapter	Changed	The following new parameters are available for the HTTP adapter: You can set or use adapter-specific attributes for synchronous response in sender and receiver adapters. More information: Configuring the HTTP Adapter
SOAP Adapter	Changed	You can choose to use the Axis Framework in the SOAP adapter and can enhance the functions of the adapter by using Axis handlers. More information: Using the Axis Framework in an SOAP Adapter
SOAP Adapter	Changed	The SOAP adapter and mail adapter now have additional adapter-specific message attributes in the message header: More information: Configuring the SOAP Adapter in the Integration Directory/PCK , Configuring the Mail Adapter in the Integration Directory/PCK
Adapters - Usability	Changed	To make entering parameters easier, the parameters for adapters with a large number of parameters are now grouped on tab pages. The functions of the adapters remain the same. The following adapters have tab pages for grouping parameters: RFC, File/FTP, JDBC, JMS, Mail, SOAP, CIDX, and RNIF (1.1 and 2.0) In CDIX and RNIF adapter scenarios, there can be empty tab pages.
Enabling Async/Sync and Sync/Async Communication With JMS Adapter	New	Modules are provided for the JMS adapter that enable async/sync and sync/async communication. You add the modules to the JMS adapter modules in the module processor. If you do not have any particular demand for monitoring or for troubleshooting in async/sync or synch/async communication, SAP recommends that you use the bridge in the JMS adapter instead of sync/async communication in the Business Process Engine. The advantage of using the bridge over the Business Process Engine is a fivefold to tenfold increase in system performance. More information: Configuring Async/Sync and Sync/Async Bridge in the JMS Adapter
EOIO Processing	Changed	Until now, the queue ID was used for serialization in the Advanced Adapter Engine. You can now perform receiver-specific serialization.
Queues	Changed	In the Advanced Adapter Engine there is now a queue for each adapter type in the receiver direction. This means that messages can be received in parallel. You can enter the default settings for these queues by using the corresponding properties. More information: Java Service Properties that May Require Changes
Non-central Adapter Engine in Java Proxy Mode	Changed	You can now configure the non-central Adapter Engine as a Java-only proxy application. In Java proxy mode, you cannot register any adapters in the System Landscape Directory.
Resending Messages to Receiver Systems	Changed	You can make settings for each receiver channel defining how many attempts are to be made to resend messages to a receiver, and the retry interval.
XML to Text Conversion Module	New	You use this module to convert an XML document contained in the mail payload of the XI message to simple text format. You can convert data records either to text with a fixed column width or a separate list. You can define the separator. During conversion, the structure of the XML document is checked using your specifications. More information: Adding StrictXml2PlainBean (XML to Text) in the Module Processor
Module Processor	Changed	You can specify a module key in the processing sequence, or use the proposed key. In Module Configuration, you can select the module key using an input help. More information: Adding Modules to the Module Processor