Integration Engine

Use

Feature	Type of Change	Description
Configuration Parameters	New	In Integration Engine configuration (transaction SXMB_ADM) are the following new RUNTIME parameters available: AE_EOIO_OPTIMIZE This parameter defines whether messages with quality of service EOIO sent from the Integration Engine to the Adapter Engine without principal propagation are set and sent in the HTTP stream of the JSESSIONID cookie corresponding to the queue. Messages that are sent to a queue are processed on the same J2EE server node if possible. SKIP_INBOUND_PERS Asynchronous messages sent by the Advanced Adapter Engine or the Business Process Engine (ccBPM) are persisted in the inbound channel of the Integration Engine. This step can be skipped and then messages run through the pipeline to the message split according to the interface determination and are persisted there. SYNC_ERROR_LOG This parameter controls which parts of a message (whole message, headers, no message) are displayed in an error message in synchronous communication (Quality of Service = Best Effort). AUTHORITY_ON_MSG_TYPE This parameter allows controling the access to services on interface and operation level in the receiver system. The access is based on authorization object S_SERVICE. The check is identical to the check performed in the ABAP Web Services runtime. In Integration Engine configuration (transaction SXMB_ADM) are the following new TUNING parameters available: EO_RETRY_AUT_COUNT This parameter dependent on and enhances the functionality of parameter EO_RETRY_AUTOMATIC. When the value of parameter EO_RETRY_AUTOMATIC is 0, it defines the number of messages above which an automatic restart is executed. This restricts the number of messages that receive an error status due to the duration of the error situation, since an automatic start results in queues being blocked. EO_QUEUE_BALANCING_READ and EO_QUEUE_BALANCING_SELECT These parameters support controling the distribution of EO messages across the queues.
Configuration Parameters	Changed	In Integration Engine configuration (transaction SXMB_ADM) the following RUNTIME parameter has been enhanced: IS_URL determines the URL or HTTP destination for the Integration Server belonging to the client. You can now use entries from Sender/Receiver ID to define sub parameters for IS_URL. This enables you to define URLs for the Advanced Adapter Engines and the Integration Server. To ensure monitoring all Engines have to belong to the same domaine.
Messaging System Monitor	New	The Messaging System Monitor allows administrators to perform tasks like displaying messages, searching for messages, filtering the displayed messages by different categories, for example. More information: Messaging System Monitor
PI Background Jobs	New	PI background have been added to the standards jobs. It is therefore no longer necessary to schedule PI background jobs individually.
New Report RSXMB_SWITCH_ARCHIVE_VERSIONS	New	For already processed messages you can subsequently determine whether all message versions or only one message version should be archived.
JMS receiver adapter's connection on demand support for IBM MQ series	New	You can create a connection and optimally reuse it for multiple messages. More information: Configuring the Receiver JMS Adapter
Service Variants	New	Service variants provide views on service interfaces. Instead of using all the parameters in a service interface, a service variant allows you to use only parameters that are needed for a particular business context. More information: Working with Service Variants
Subsequently Defining Interfaces for Archiving	New	You can use the new report RSXMB_DEL_TO_ARCH to subsequently define interfaces for archiving so that you can archive their messages. This can be required in the following situations: You have forgotten to consider certain interfaces for the archiving of their messages, or you have forgotten to configure message archiving at all. You want to archive selected messages, for example, only messages of interface xy that were processed the day before. More information: Defining Interfaces and Retention Periods for Archiving
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
IDoc Sender Adapter Available in Integration Directory	New	You can now configure an IDoc sender adapter in the Integration Directory for processing IDoc packages that reach the inbound channel of the Integration Server and to enter the segment release so that the IDocs are forwarded correctly. More information: Configuring the Sender IDoc Adapter
Comparing Metadata for the IDoc Adapter	New	You have the option of comparing metadata that has been loaded to the Integration Server with the current metadata from the SAP reference system that the metadata comes from. More information: Comparing Metadata with the Reference System
IDoc Adapter	Changed	You can now configure an IDoc sender adapter in the Integration Directory so that you are able to process IDoc packages that reach the inbound channel of the Integration Server using the Integration Engine also as packages and to enter the segment release so that the IDocs are forwarded correctly.
Communication with Web Service Applications	New	Web service applications can communicate with Integration Server using Java Proxy Runtime. More information: Using Java Proxy Runtime for Communication of Web Service Applications with PI
Message Packaging	New	You can now improve the performance of message processing in SAP NetWeaver Process Integration by grouping together asynchronous messages in packages and then processing each message package. More information: Message Packaging
Interface-/Operation-Specific Authorization Check in Local Integration Engine (Inbound)	Changed	If you like to configure interface operation-specific authorization checks for inbound messages processes by the local Integration Engine in a receiver system, you are affected by a change in the default setting of an authorization check. The parameter AUTHORITY_ON_MSG_TYPE is set default to 1 (activated) by default. This means that you need to maintain the authorization objects S_SERVICE as described in SAP note 1416725 . Note This change is only relevant for back-end systems based on AS ABAP 7.3.
Archiving	Changed	Integration Engine archiving now offers a function for migrating archive administration data. More information: Migrating Archive Administration Data
IDoc Adapter - New Parameter	Changed	The IDoc adapter now has a new parameter: If you set the Restore Original Parties for Acknowledgements 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 Receiver IDoc Adapter
Comparing Metadata for the IDoc Adapter	New	You have the option of comparing metadata that has been loaded to the Integration Server with the current metadata from the SAP reference system that the metadata comes from. More information: Comparing Metadata with Reference System
IDoc Adapter - IDoc Tracking	Changed	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
IDoc Adapter: Acknowledgments Function	Changed	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
IDoc Adapter - Converting Acknowledgment IDocs to XI Request Messages	Changed	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
Monitor for Message Packages	Changed	The message monitor of the Integration Engine now also displays message packages, from which you can navigate to the monitor for message package.