!--a11y-->
New Functions and Changes in SAP NetWeaver ’04 SPS 14
New Functions and Changes |
|
Some of the adapters shipped by SAP have new parameters. You can find these adapters in the Integration Directory and PCK. The specific properties are written in the message header for adapters. |
|
When transporting using CMS, you can now also deactivate the transport of Integration Directory changelists. |
|
The Integration Engine has a multi-message bulking option for messages sent to the Adapter Engine from the mapping-based message split. A monitor is available for monitoring these messages. |
|
You can use an interface determination to configure a mapping-based message split. |
|
In the mapping area, enhancements have been made in multi-mapping, access to adapter-specific properties in the message header, and in the message mapping examples. |
|
In the patterns for integration processes shipped by SAP, the validity of the correlations used have been checked and corrected where applicable. |
|
Modifications have been made in message archiving, alert configuration, cache monitoring, and in end-to-end monitoring. |
|
In the case of sender services of type Business Service or Business System, you can now restrict access to the runtime environment to particular users when using the RFC adapter. |
Additional Changes in the Documentation for SAP NetWeaver 04’ SPS 14
Changes |
|
The documentation for adapter and module development now contains information about access control by using assigned users. |
|
The functions module processor and adapter-specific properties in the message header are now grouped together in the documentation under Generic Adapter Functions. |
|
The documentation for the Adapter Engine adapters now contains links to SAP Notes that contain FAQs for the various adapters. |
