Changes in SAP NetWeaver '04

Service Packs

Table of Contents
1 GENERAL....................................................................................................................................................................................3 1.1 SP 11 ..............................................................................................................................................................................3 1.2 SP 12...............................................................................................................................................................................3 1.3 SP 13...............................................................................................................................................................................4 1.4 SP 14...............................................................................................................................................................................5 1.5 SP 15...............................................................................................................................................................................6 1.6 SP 16...............................................................................................................................................................................7 2 RUNTIME WORKBENCH........................................................................................................................................................8 2.1 SP 11...............................................................................................................................................................................8 2.2 SP 12...............................................................................................................................................................................8 2.3 SP 13...............................................................................................................................................................................9 2.4 SP 14...............................................................................................................................................................................9 2.5 SP 15.............................................................................................................................................................................10 3 MAPPING LOOKUPS..............................................................................................................................................................10 3.1 SP 13.............................................................................................................................................................................10 4 MULTI-MAPPINGS.................................................................................................................................................................11 4.1 SP 16.............................................................................................................................................................................11 5 MAPPINGS.................................................................................................................................................................................11 5.1 SP 13.............................................................................................................................................................................11 5.2 SP 14.............................................................................................................................................................................11 6 MAPPING EDITOR..................................................................................................................................................................12 6.1 SP 11.............................................................................................................................................................................12 7 RECEIVER DETERMINATION............................................................................................................................................12 7.1 SP 15.............................................................................................................................................................................12 7.2 SP 16.............................................................................................................................................................................12 8 INTERFACE DETERMINATION..........................................................................................................................................12 8.1 SP 14.............................................................................................................................................................................12 9 INTEGRATION ENGINE........................................................................................................................................................13 9.1 SP 11.............................................................................................................................................................................13 9.2 SP 12.............................................................................................................................................................................13 9.3 SP 13.............................................................................................................................................................................13 9.4 SP 14.............................................................................................................................................................................14 10 PATTERNS FOR INTEGRATION PROCESSES..............................................................................................................14 10.1 SP 14...........................................................................................................................................................................14 11 TRANSPORTING USING THE CHANGE MANAGEMENT SERVICE......................................................................14 11.1 SP 11...........................................................................................................................................................................14 11.2 SP 14...........................................................................................................................................................................14 Page 1 / 22

Changes in SAP NetWeaver '04 Service Packs 12 ANALYZING INTEGRATION PROCESSES IN THE RUNTIME CACHE................................................................15 12.1 SP 11...........................................................................................................................................................................15 13 CONFIGURATION TEST.....................................................................................................................................................15 13.1 SP 12...........................................................................................................................................................................15 14 COLLABORATION AGREEMENT....................................................................................................................................15 14.1 SP 12...........................................................................................................................................................................15 14.2 SP 15...........................................................................................................................................................................15 15 DEMO EXAMPLES................................................................................................................................................................16 15.1 SP 12...........................................................................................................................................................................16 15.2 SP 13...........................................................................................................................................................................16 16 ADAPTERS..............................................................................................................................................................................16 16.1 SP 12...........................................................................................................................................................................16 16.2 SP 13...........................................................................................................................................................................17 16.3 SP 14...........................................................................................................................................................................18 16.4 SP 15...........................................................................................................................................................................18 16.5 SP 16...........................................................................................................................................................................19 17 RNIF ADAPTER 1.1................................................................................................................................................................19 17.1 SP 13...........................................................................................................................................................................19 17.2 SP 15...........................................................................................................................................................................19 17.3 SP 16...........................................................................................................................................................................19 18 CIDX ADAPTER.....................................................................................................................................................................20 18.1 SP 16...........................................................................................................................................................................20 19 LOCAL XI FOR ERP 2004....................................................................................................................................................20 19.1 SP 13...........................................................................................................................................................................20 20 SERVICE..................................................................................................................................................................................20 20.1 SP 13...........................................................................................................................................................................20 20.2 SP 14...........................................................................................................................................................................20 21 CONVERSION AGENT.........................................................................................................................................................20 21.1 SP 15...........................................................................................................................................................................20 21.2 SP 16...........................................................................................................................................................................21 22 MODULE PROCESSOR........................................................................................................................................................21 22.1 SP 15...........................................................................................................................................................................21 23 SEND STEP IN INTEGRATION PROCESSES.................................................................................................................21 23.1 SP 15...........................................................................................................................................................................21 24 EXTERNAL DEFINITIONS..................................................................................................................................................22 24.1 SP 16...........................................................................................................................................................................22

Page 2 / 22

Changes in SAP NetWeaver '04 Service Packs

1 General
1.1 SP 11
http://help.sap.com/saphelp_nw04/helpdata/en/90/c6be40ced9dd50e10000000a1550b0/RN_XI_EN_neu.pdf

New Functions and Changes in SAP NetWeaver 04 Including SPS 11 New Functions and Changes Release notes for SAP Exchange Infrastructure up to and including SAP XI 3.0 Feature Pack (SAP NetWeaver 04 SPS 04) There are now enhanced functions available for analyzing integration processes in the runtime cache. The functions for transporting design and configuration objects using the Change Management Service have been enhanced. The Integration Engine functions for monitoring and processing IDoc messages have been enhanced. The mapping editor functions for message mappings in the Integration Builder have been enhanced. The Runtime Workbench functions for message monitoring, end-to-end monitoring, and alerting have been enhanced. Release Notes German Version English Version Analyzing Integration Processes in the Runtime Cache (Enhanced) Transporting Using the Change Management Service (Enhanced) Integration Engine (Enhanced)

Mapping Editor (Enhanced)

Runtime Workbench (Enhanced)

Additional Changes in the Documentation in SAP NetWeaver 04 SPS 11 Changes The documentation for the monitoring functions for the Business Process Engine has been enhanced. The documentation for transporting design and configuration objects by using the Change Management Service (CMS) has been reworked. A new table with the string-constant key values which is required in some special cases - has been added to the documentation for the mapping-runtime runtime constants. Monitoring the Business Process Engine

Transporting Using the Change Management Service

Special Access to Mapping Runtime Constants

1.2

SP 12

New Functions and Changes in SAP NetWeaver 04 SPS 12 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. Adapters (Enhanced)

Page 3 / 22

Changes in SAP NetWeaver '04 Service Packs A new scenario variant has been added to the existing demo examples. The new variant enables you to show a simple usage case for communication with a Web service server. The Integration Engine functions for message queues and message packages have been enhanced. When using the mail adapter, you have the option of configuring security settings for encoding/decoding and signing/verifying messages. The Integration Directory has a new test tool for checking configurations. The Runtime Workbench functions for component monitoring and message monitoring have been enhanced. If you display the Workflow log from the Business Process Engine monitoring functions, you can now restrict the number of Workflow steps that are displayed by making an appropriate entry in your personal settings. By doing so, you can reduce the time required to display the log. Demo Examples (Enhanced)

Integration Engine (Enhanced)

Collaboration Agreement (Enhanced)

Configuration Test (New) Runtime Workbench (Enhanced)

Technical Workflow Log (Enhanced)

Additional Changes in the Documentation for SAP NetWeaver 04 SPS 12 Changes The documentation for integration processes now contains checklists to help you employ integration process correctly, as well as new examples and information about defining integration processes. The documentation for the module processor now contains a description of the modules shipped by SAP. The documentation for the IDoc adapter now contains a description of the structure of the IDoc control record. The documentation for the SOAP adapter now contains a description of how the quality of service Exactly Once is ensured for the sender SOAP adapter. Checklist: Making Correct Use of Integration Processes

Modules

Fields of the IDoc Control Record

Ensuring Exactly-Once Processing

1.3

SP 13

New Functions and Changes in SAP NetWeaver 04 SPS 13 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. Adapters (Enhanced)

Page 4 / 22

Changes in SAP NetWeaver '04 Service Packs The demo examples now contain simple application cases for routing and mapping. The application cases can be configured and executed as required. The archiving of messages can now be restricted to the inbound version of a message. ALE audits as acknowledgments from IDoc receivers - can now be processed as packages. It is now possible to install SAP Exchange Infrastructure together with an SAP ERP 2004 application on SAP Web Application Server 6.40. The structure overview of the data-flow editor and the test environment in the mapping editor have been enhanced. New standard functions and example message mappings are also now available. By using a new mapping lookup API, in message, Java, and XSLT mapping programs, you can now read data from an application system or execute mapping routines at runtime. The new RNIF 1.1 adapter enables you to exchange messages between the Integration Server and any RosettaNet-enabled system that supports RNIF 1.1. Input help is now available for the sender and receiver in message monitoring. It is now possible to save a selection filter in performance 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 for certain adapter types. Demo Examples (Enhanced)

Integration Engine (Enhanced)

Local XI (New)

Mapping Editor (Enhanced)

Mapping Lookups (New)

RNIF 1.1 Adapter (New)

Runtime Workbench (Enhanced)

Service (Enhanced)

Additional Changes in the Documentation for SAP NetWeaver 04 SPS 13 Changes An overview of the adapters shipped by SAP that contains information about transport and message protocols, acknowledgments, attachments, and quality of service, is now available. The description of configuration objects for testing your own adapter in the Partner Connectivity Kit has changed. You no longer need to define a mapping. Adapters

Configuration Objects for the Adapter Test

1.4

SP 14

New Functions and Changes in SAP NetWeaver 04 SPS 14 New Functions and Changes

Page 5 / 22

Changes in SAP NetWeaver '04 Service Packs 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 adapterspecific 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. Changes The documentation for adapter and module development now contains information about access control by using assigned users. The functions module processor and adapterspecific 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. Accessing Configuration Data in Sender Direction Adapters (Enhanced)

Transporting Using the Change Management Service (Enhanced) Integration Engine (Enhanced)

Interface Determination (Enhanced) Mapping (Enhanced)

Patterns for Integration Processes (Changed)

Runtime Workbench (Enhanced)

Service (Enhanced)

Additional Changes in the Documentation for SAP NetWeaver 04 SPS 14

Generic Adapter Functions

Adapter Engine

1.5

SP 15

New Functions and Changes in SAP NetWeaver 04 SPS 15 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. Adapters (Enhanced)

Page 6 / 22

Changes in SAP NetWeaver '04 Service Packs The conversion agent enables you to convert unstructured and semi-structured formats to XML. You can call the conversion agent from an adapter module in the module processor. In a receiver determination, you can now specify in more detail what should happen to a message when no receiver is found at runtime. When using the SOAP adapter, you can specify the following additional security settings in the collaboration agreement: Security settings for time stamp and expiry date of message signature Security settings based on the S/MIME Internet standard (Secure Multipurpose Internet Mail Extension) You no longer need to specify a module key in the module processor. Passwords can now be encoded and saved in the module configuration. In the RNIF adapter, you can now specify an alternative interface namespace. Improvements have been made in message archiving, message monitoring, and in cache monitoring. In an asynchronous send step, you can set a conversation ID and define the quality of service as EOIO (Exactly Once In Order). Conversion Agent (Enhanced)

Receiver Determination (Enhanced)

Collaboration Agreement (Enhanced)

Module Processor (Enhanced)

RNIF Adapter (Enhanced) Runtime Workbench (Enhanced)

Send Step in Integration Processes (Enhanced)

Additional Changes in the Documentation for SAP NetWeaver 04 SPS 15 Changes The adapter and module development documentation has been enhanced as follows: See: Components of the XI Message, Choose CorrelationID Methods for setting and determining the ConversationID. Choose Message Class Determining the message class Choose Adapter-Specific Message Attributes Add message attributes to the adapters.

See: Creating Acknowledgment Messages Methods for recognizing an acknowledgment message. See: Synchronous Messages New methods are available that enable you to read error information from the message in the form of an ErrorInfo object, or set it in a message. The integration process documentation has been enhanced with the following administration information: Error Notifications for Administrators Deleting Obsolete Process Data

1.6

SP 16
Page 7 / 22

New Functions and Changes in SAP NetWeaver 04 SPS 16

Changes in SAP NetWeaver '04 Service Packs New Functions and Changes Some of the adapters shipped by SAP have new parameters. The CIDX adapter and the RNIF adapter now support adapter-specific message attributes. The Conversion Agent provides additional functions. You use an enhanced receiver determination to have a mapping determine the receivers of the message at runtime. Using external definitions, you can now import WSDL documents in rpc-style format. It is now possible to specify multiple multimapping programs that are to be executed consecutively. Furthermore, a restriction in mapping has been removed. Adapters (Enhanced) CIDX Adapter (Enhanced) RNIF Adapter (Enhanced) Conversion Agent (Enhanced) Receiver Determination (Enhanced)

External Definitions (Enhanced) Multi-Mappings (Enhanced)

Additional Changes in the Documentation for SAP NetWeaver 04 SPS 16 Changes The documentation for the security settings has been enhanced. A new overview chapter lists all the security settings that you can make in the Integration Directory, and contains links to further information. The documentation for adapter and module development has been enhanced. It now contains a description of how to access the J2EE keystore in an adapter, and how to save security settings in the adapter metadata. Security Settings

Accessing the J2EE Keystore Attributes Example Adapter and Example Module

2 Runtime Workbench
2.1 SP 11
The Runtime Workbench has the following new functions: Message Monitoring: The selection and display of messages can now be restricted to a specified number of messages; this has a positive effect on system performance. End-to-End Monitoring Duplicate PMI events from the Adapter Engine no longer have any negative effects on the RNIF and CIDX adapters. Alerting Alerts triggered by the Runtime Workbench can now be forwarded to the CCMS Alert Monitor and displayed there. See also SAP Note 824039

2.2 SP 12 The Runtime Workbench has the following new functions:

Component Monitoring: Page 8 / 22

Changes in SAP NetWeaver '04 Service Packs

Cache-Connectivity Test In component monitoring, you now have the option of checking whether the cacheconnectivity is functioning correctly. This is useful when you are experiencing problems when updating the runtime cache, for example.

See also:

Testing Cache-Connectivity.

Detailed Results for Ping and Self-Test Detailed information about pings and self-tests is now available for certain components. See also: Status and Results. CCMS Alert Monitor You can now configure one new CCMS Alert Monitor per Adapter Engine for adapterspecific processing errors.

See also:

Current Adapter-Specific Processing Errors.

Message Monitoring: You can now select the central Integration Engine and central Adapter Engine together as component Integration Server. See also: Displaying and Managing Messages.

2.3

SP 13

The Runtime Workbench has the following new functions: Message Monitoring: Input help is now available for the filter criteria for the sender and receiver. See also: Filtering Messages Performance Monitoring: You can now save defined criteria as a selection filter when selecting messages. See also: Performance Monitoring

2.4

SP 14

The Runtime Workbench has the following new functions: Message archiving In message archiving in component monitoring, you can now define and schedule delete jobs. A standard delete job is scheduled automatically. The user interface for message archiving has been redesigned. See also: Message Archiving. End-to-end monitoring Input help is now available for the filter criteria for the sender and receiver. You can now save criteria you define as selection filters and reuse them as required. See also: End-to-End Monitoring. Alerting Alerting is no longer dependent on the configuration and activation of end-to-end monitoring. Consequently, the delay between when an error occurs in message processing and the creation of an alert is significantly reduced. Furthermore, you no longer need to schedule the report SXMSALERT_PROCESS_DATA_GET as a background job. See also: Alert Configuration. Cache monitoring Page 9 / 22

Changes in SAP NetWeaver '04 Service Packs The number of cache instances that can be monitored in cache monitoring has been increased. In addition to the Integration Server Java cache, you can now also monitor the Integration Server ABAP cache and the central and non-central Adapter Engine(s) cache. See also: Cache Monitoring.

2.5

SP 15

The Runtime Workbench has the following new functions: Message Archiving In addition to the existing delete jobs in the message archiving part of component monitoring, you can now also define jobs for restarting and rescheduling messages. For this reason, this function has been renamed Background Processing. See also: Background Processing. Message Monitoring In message monitoring, you now also have the option of searching for adapter-specific message attributes as well as terms in the message payload. However, to be able to do so, you must have already indexed your messages. Use the Search and Classification Engine TREX for this purpose. See also: Searching for Messages Using the Index. Index Administration Index administration is a new function that enables you to centrally control and monitor indexing for the index-based message search. See also: Index Administration. Cache Monitoring In cache monitoring, you can now call the notification table for cache updates. Here you can search for specific problems that arose during runtime cache updates. See also: Notification Table.

3 Mapping Lookups
3.1 SP 13
Some mapping programs require additional data from an application system to map messages to each other. Furthermore, you may want to reuse existing mapping routines from an application system. It was previously only possible to read values for/while executing message, Java, or XSLT mapping programs from a global value-mapping table. Also, If you wanted to execute calls to an application system during a mapping, you could use the Java Connector (JCo), for example. Calls of this kind are known as lookups, and were previously only visible in the program code of the mapping program. This Support Package Stack contains a new API for the mapping runtime that enables you to execute lookups for message mappings, Java mappings, and XSLT mappings (J2EE Engine). The lookup API contains methods for generically accessing application systems by using the RFC, JDBC, and SOAP adapters. Also included is a special API for the JDBC adapter, which simplifies the procedure for accessing application systems. You configure the access procedure by using a communication channel in the Integration Directory. When configuration is complete and the runtime is active, you can test lookups that are part of a mapping program by using the test environment of an interface mapping. See also: Mapping Lookups

Page 10 / 22

Changes in SAP NetWeaver '04 Service Packs

4 Multi-Mappings
4.1

SP 16
Previously, it was only possible to specify one step with a multi-mapping per direction in an interface mapping that can contain multiple source and target interfaces. It is now possible to execute multiple multimappings consecutively in an interface mapping.

See also: Interface Mappings Previously, when executing message mappings for multi-mappings in the Mapping Editor, you could only reference source and target messages if they were in the same software component version as the message mapping, or an underlying software component version. Now, provided that all the source messages are in one software component version, and all target messages are in another, the source and target messages do not have to be in the same software component version as the message mapping. If the software component version of the source or target message has underlying software component versions, you can also reference any source or target messages they contain from the message mapping. See also: Developing Multi-Mappings for Integration Processes Developing Multi-Mappings for Message-Splits

5 Mappings
5.1 SP 13
The following enhancements have been made in the mapping area: Previously, you could only develop multi-mappings for integration processes. It is now also possible to develop multi-mappings for 1:n transformations; you specify the relevant interface mapping directly in the interface determination (see: Developing Multi-Mappings for Message Splits). For more information, see the release note Interface Determination (Enhanced). A new message header for adapter-specific properties is available; you can access the message header from within Java mapping programs, message mappings, XSLT mappings programs, and ABAP mappings (see: Java Mapping of Adapter-Specific Properties). For more information, see the release note Adapters (Enhanced). The example message mappings have been renamed. Instead of the prefix MapPattern, all examples and their message types and data types now have the prefix MapExample. The example MapExampleFlatStructureToNestedTables has also been enhanced.

5.2

SP 14

The following enhancements have been made in the mapping area: Previously, you could only develop multi-mappings for integration processes. It is now also possible to develop multi-mappings for 1:n transformations; you specify the relevant interface mapping directly in the interface determination (see: Developing Multi-Mappings for Message Splits). For more information, see the release note Interface Determination (Enhanced). A new message header for adapter-specific properties is available; you can access the message header from within Java mapping programs, message mappings, XSLT mappings programs, and ABAP mappings (see: Java Mapping of Adapter-Specific Properties). For more information, see the release note Adapters (Enhanced). The example message mappings have been renamed. Instead of the prefix MapPattern, all examples and their message types and data types now have the prefix MapExample. The example MapExampleFlatStructureToNestedTables has also been enhanced.

Page 11 / 22

Changes in SAP NetWeaver '04 Service Packs

6 Mapping Editor
6.1 SP 11 The following enhancements have been made for message mappings in the Integration Builder mapping editor:
In the dataflow editor for target-field mappings, you can now call a menu that enables you to access the most frequently used standard functions quicker. To call the menu, double-click an empty screen area in the data-flow editor. In the user-defined functions, it was previously only possible to query runtime constants for the message mapping by using the container-object method getTransformationParameters(). You can now also use the GlobalContainer-object method getParameters() for this purpose. See also: GlobalContainer Object. The following enhancements have been made to the standard functions of the mapping editor:

Previously, the way the standard function ifWithoutElse() operated was predefined in the ELSE case. Now, if the value resulting from this function is to be transferred to another function in the target-field mapping, you have the option of setting the ELSE value in the function properties. See also: ifWithoutElse

The new standard function useOneAsMany()replicates the value of a field that only occurs once to enable it to be combined in pairs with the values of a field that occurs more than once (as records). See also: useOneAsMany

7 Receiver Determination
7.1 SP 15
You can configure a receiver determination in such a way that the receivers of the message are determined dynamically at runtime by a mapping. See also: Enhanced Receiver Determination

7.2

SP 16

You can configure a receiver determination in such a way that the receivers of the message are determined dynamically at runtime by a mapping. See also: Enhanced Receiver Determination

8 Interface Determination
8.1 SP 14
You use an interface determination to configure a mapping-based message split. This involves assigning the interface determination a multi mapping from the Integration Repository. The inbound interfaces are determined at runtime during the mapping step (see Interface Determination). For more information, see the release note Mapping Editor (Enhanced).

Page 12 / 22

Changes in SAP NetWeaver '04 Service Packs

9 Integration Engine
9.1 SP 11 The following improvements have been made in the Integration Engine:
Monitoring The selection and display of messages can now be restricted to a specified number of messages; this has a positive effect on system performance. IDoc Adapter

Using a special filter function, you can group IDoc messages in packages at runtime and instead of sending them to the relevant receiver individually, you can now send them in these packages. A special monitor is available for such message packages. See also:

Event-Driven Message Processing Monitor for Message Packages System acknowledgments are now only returned by the IDoc adapter on request, and not by default as was previously the case. This has a positive effect on system performance.

9.2

SP 12

The following improvements have been made in the Integration Engine: New Message Queue An additional outbound queue for the asynchronous processing of messages is now available. The new queue will process exceptionally large messages with the quality of service Exactly Once. You can specify the queue - which has the prefix XBTM - during queue prioritization. See also: Queues for Asynchronous Message Processing Message Selection Filter Monitor for Message Packages You can now call the monitor for message packages by choosing Integration Engine Monitoring or directly by calling transaction IDXP. See also: Monitor for Message Packages Activating Message Packages There is a new function available for IDoc messages that enables you to speed up the activation of message packages. You can call the function by choosing Integration Engine Administration or directly by calling transaction IDXPW. See also: Activating IDoc Message Packages

9.3

SP 13

The following improvements have been made in the Integration Engine: Message Archiving The default setting when archiving messages is to archive all existing message versions. This setting can now be restricted so that only inbound messages are archived. See also: Defining Interfaces and Retention Periods for Archiving Packaging ALE Audits ALE audits, which are returned to an IDoc system (sender) from a receiver of IDoc messages in the form of acknowledgments, can now also be processed as packages. Page 13 / 22

Changes in SAP NetWeaver '04 Service Packs See also: Message Selection Filter

9.4 SP 14 The following improvements have been made in the Integration Engine:
Multi-message bulking between the Integration Engine and the Adapter Engine By using the new multi-message bulking option in a 1:n split of the message payload, you can drastically reduce resource consumption and increase performance. The only prerequisite is that all individual messages are sent to the same Adapter Engine. In multi-message bulking, a mapping-based message split creates n individual messages. These messages are not persisted individually but instead are grouped together immediately in one bulk message. The bulk message is then sent to the Adapter Engine just like a normal XI message, thus simplifying message transfer. The Adapter Engine then splits the bulk message up into the individual messages and persists them. See also:

Enhanced (Mapping-Based) Interface Determination Developing Multi-Mappings for Message Splits

For more information, see the following release notes: Interface Determination (Enhanced) and Mappings (Enhanced). Monitor for messages from multi-message bulking The report SXMS_MMF_MONITOR can be used to display the bulk messages and the corresponding individual messages. You can either display all bulk messages for a particular time period, or enter a specific message ID and display the corresponding parent and child messages. You can navigate from the list of displayed messages to the monitor for processed messages.

10 Patterns for Integration Processes

10.1 SP 14
The use of correlations has been modified in the patterns that are shipped by SAP. Where required, the correlations were defined as local correlations. This avoids problems that can occur when the validity is not correctly defined. For more information about correlations, see Checklist: Making Correct Use of Correlations. You can find the example processes in the Integration Repository under SAP Basis SAP Basis 6.40, namespace http://sap.com/xi/XI/System/Patterns.

11 Transporting Using the Change Management Service

11.1 SP 11
The following changes have been made to the procedure for transporting design or configuration objects by using the Change Management Service (CMS): If you use the transport wizard to export design or configuration objects in CMS mode, the Integration Builder groups together all the objects in a transport list and then displays the latter on the Change Lists tab page. This tab page also displays the export status of all transport lists and change lists. See also: Change and Transport Lists for CMS Transports. In the CMS Transport Studio, it was previously only possible to transport either whole software component versions from the consolidation repository, or all consolidation directory content to the productive system. Now, by using the Subset Assembly option, you can create sub-transports from the selection of transport lists and change lists. See also: Transporting Design Objects and Transporting Configuration Objects

11.2 SP 14
It was previously only possible to deactivate the transport of change lists for Integration Repository change lists. You can now also deactivate the transport of Integration Directory change lists. Page 14 / 22

Changes in SAP NetWeaver '04 Service Packs See also: Deactivating Change List Transport

12 Analyzing Integration Processes in the Runtime Cache

12.1 SP 11
You can now display an activation log in the runtime cache; the log displays detailed messages about the last time an integration process was activated. Furthermore, you also have the option of navigating from the runtime version of an integration process to the corresponding XML objects and correlations. See also: Analyzing an Integration Process in the XI Runtime Cache

13 Configuration Test
13.1 SP 12
You now have the option of testing your configuration by simulating the processing of a message based on this configuration. You can enter the header and payload of the message as the input parameters. In the configuration test you can display and analyze the status of the message after each step in message processing. See also: Configuration Test

14 Collaboration Agreement
14.1 SP 12
When using the SOAP adapter, you can now specify additional security settings in the collaboration agreement both for the time stamp and for the expiry date of the message signature. For the signature of an outbound message in a receiver agreement, you can specify that a time stamp be set and an expiry date be specified. You can define in a sender agreement that inbound messages are then checked to see whether they are delivered within the specified expiry date for the signature. If this is not the case, the message is not processed further. Furthermore, when using the SOAP adapter, you can specify additional security settings that are based on the Internet standard S/MIME (Secure Multipurpose Internet Mail Extension). The new security settings are identical in both the Integration Directory and Partner Connectivity Kit (PCK). See also: Security Settings for Receiver SOAP Adapters Security Settings for Sender SOAP Adapters

14.2 SP 15
When using the SOAP adapter, you can now specify additional security settings in the collaboration agreement both for the time stamp and for the expiry date of the message signature. For the signature of an outbound message in a receiver agreement, you can specify that a time stamp be set and an expiry date be specified. You can define in a sender agreement that inbound messages are then checked to see whether they are delivered within the specified expiry date for the signature. If this is not the case, the message is not processed further. Furthermore, when using the SOAP adapter, you can specify additional security settings that are based on the Internet standard S/MIME (Secure Multipurpose Internet Mail Extension). The new security settings are identical in both the Integration Directory and Partner Connectivity Kit (PCK). See also: Page 15 / 22

Changes in SAP NetWeaver '04 Service Packs Security Settings for Receiver SOAP Adapters Security Settings for Sender SOAP Adapters

15 Demo Examples
15.1 SP 12
You can now use the demo examples to show a simple usage case for communication with a Web service server. For this purpose, the example integration scenario CheckFlightSeatAvailability (short text: Flight Availability Check) has an additional variant that enables the flight availability check in an airline system to be called using a Web service. The outbound processing of the messages is then performed by the SOAP adapter. See also: Checking Flight Seat Availability (Proxy-to-RFC)

15.2 SP 13
The demo examples have been enhanced as follows: Simple application cases now enable you to represent specific parts of the process integration. A simple integration scenario (containing a single cross-component communication step) is now available that enables you to effortlessly configure and execute simple application cases for routing and mapping. A complete set of configuration guidelines are provided. See also: Simple Application Cases

16 Adapters
16.1 SP 12 The following adapters now have additional parameters:
Sender RFC Adapter The parameter maximum connection delay defines how long the adapter is to wait before re-registering with the Gateway server.

See also: Configuring the Sender RFC Adapter Receiver File/FTP Adapter When you specify the target directory and file name schema, you now have the option of setting variables and defining them in a table. At runtime, the variables are replaced by elements from the XML structure and attributes from the XI message header. See also: Configuring the Receiver File/FTP Adapters Receiver JDBC Adapter

You can set the mode to Batch to group SQL statements together. You can set the formats for DATE, TIME, and TIMESTAMP when calling Stored Procedures. See also: Configuring the Receiver JDBC Adapter

The parameter types BLOB (Binary Large Object) and CLOB (Character Large Object) are supported as input and output parameters for the action EXECUTE when calling Stored Procedures. See also: Document Formats for the Receiver JDBC Adapter

JMS Adapter You can enter details about correlations in the sender and receiver adapter. These determine which algorithm is to be used to set the message ID of a new message. Page 16 / 22

Changes in SAP NetWeaver '04 Service Packs For information about sync/async communication, see SAP Note 838894.

Sender JMS Adapter You use the JMS message selector to specify conditions that a JMS message in the specified JMS queue must meet in order to be processed by the sender adapter.

See also: Configuring the Receiver JMS Adapter Configuring the Sender JMS Adapter Sender SOAP Adapter If you set the relevant indicator, the adapter expects a message without a SOAP envelope. See also: Configuring the Sender SOAP Adapter Mail Adapter If an e-mail server is communicating with the mail adapter, you can configure security settings to encrypt/decrypt and sign/verify messages. Here, message security is based on the S/MIME internet standard (Secure Multipurpose Internet Mail Extension). For this purpose, set the indicator S/MIME in the sender and receiver adapter.

You can set an indicator in the sender mail adapter to generate a report for every adapter poll-procedure. See also: Configuring the Sender Mail Adapter

You can set an indicator in the receiver mail adapter to send a delivery service notification to a defined e-mail address. See also: Configuring the Receiver Mail Adapter

16.2 SP 13 The following adapters now have additional parameters:

File/FTP Adapter

In SP13 and higher, the file/FTP adapter supports encrypted FTP connections. You have the option of encrypting the FTP control connection and the data connection. Setting the parameter Timeout enables the connection between the client and the FTP server to be terminated after the specified duration. You now have the option of canceling a particular operating system command after a specified duration.

See also: Configuring the Sender File/FTP Adapter, Configuring the Receiver File/FTP Adapter JDBC Adapter You now have the option of canceling a particular operating system command after a specified duration. See also: Configuring the Sender JDBC Adapter and Configuring the Receiver JDBC Adapter Sender Mail Adapter In Advanced Mode, you can set a parameter in the table that enables XML to be copied to the payload unchanged. See also: Configuring the Sender Mail Adapter Receiver SOAP Adapter You can now configure a certificate authentication for the HTTPS and SMTPS transport protocols. See also: Configuring the Receiver SOAP Adapter

Page 17 / 22

Changes in SAP NetWeaver '04 Service Packs

16.3 SP 14 Adapter-Specific Message Properties in the Message Header Some adapters support specific message properties, which contain additional information about messages. This information is contained in additional message header fields. The properties can be used in mapping and routing. You can display them in monitoring. See also: Adapter-Specific Message Properties in the Message Header and Mappings (Enhanced). Further Adapter Parameters The following adapters now have additional parameters:
IDoc Adapter It is now possible to get the sender and receiver of a message from the payload. See also: Configuring the Receiver IDoc Adapter RFC Adapter The RFC adapter supports Secure Network Communications (SNC). In the receiver adapter you can specify the commit control for individual BAPI calls. See also: RFC Adapter, Configuring the Receiver RFC Adapter SAP Business Connector Adapter The sender SAP Business Connector adapter gives you the option of extracting data from an external message protocol and using it to assemble the header of the XI message. See also: Normalization in the Sender Adapter. The message protocol IDoc-XML is also available. See also: Configuring the Receiver SAP Business Connector Adapter and Configuring the Sender SAP Business Connector Adapter. File/FTP Adapter In the sender file/FTP adapter, you have the option of using an additional placeholder to specify the source file. An advanced source-file-selection option is also available. See also: Configuring the Sender File/FTP Adapters. In the receiver file/FTP adapter, it is now also possible to initially write to a temporary file for the transport protocol file system. You can specify a name schema here, if required. See also: Configuring the Receiver File/FTP Adapters.

16.4 SP 15 Security Check for Inbound Messages You now have the option of defining the HTTP security level for sender and XI adapters. You can chose from the following:
HTTP HTTPS without client authentication HTTPS with client authentication

SOAP,

HTTP

To configure the security check in the Plain HTTP adapter, you can now also create a Plain HTTP sender adapter in the Integration Directory. For the security check to be performed, you must create a sender agreement that contains this communication channel.

The file/FTP adapter now has additional parameters:

You can now enter an operating system command in the file/FTP adapter prior to message processing. You can now chose between a passive and active data connection mode for the transport protocol FTP.

Page 18 / 22

Changes in SAP NetWeaver '04 Service Packs

See also: Configuring the Sender File/FTP Adapter, Configuring the Receiver File/FTP Adapter, and choose FTP Connection Parameter and Execute Operating System Command Before/After Message Processing. The SOAP adapter now has the following additional parameters: In the SOAP adapter, you now have the option of choosing either Web services security or S/MIME as the security profile. See also: Configuring the Receiver SOAP Adapter and Configuring the Sender SOAP Adapter. 16.5 SP 16

The plain HTTP adapter supports adapter-specific attributes in the message header:

See also: Adapter-Specific Attributes in Message Header, Configuring the Plain Sender HTTP Adapter, Configuring the Plain Receiver HTTP Adapter The JMS adapter now has the following new parameters: You now have the option of saving the JMS correlation ID of the request in the receiver JMS adapter. In the sender adapter, you can then set the XI conversation ID to the saved JMS correlation ID of the request. This makes the additional parameters that were required in previous Support Packages obsolete. However, the configuration settings that were made prior to SP 16 are still valid. See also: Configuring the Receiver JMS Adapter and Configuring the Sender JMS Adapter under Correlation Settings. Thereceiver JDBC adapter now has the following new parameters: For the purpose of calling stored procedures, for the action EXECUTE, the parameter type CURSOR is now supported as the output parameter in connection with the Oracle-JDBC driver. See also: Document Formats for the Receiver JDBC Adapter

17 RNIF Adapter 1.1

17.1 SP 13
You can now use the new RNIF 1.1 adapter to exchange messages between the Integration Server and a RosettaNet-compliant system that supports RNIF version 1.1. The adapter transforms the Exchange Infrastructure (XI) message format to the RosettaNet PIP message format. See also: RNIF Adapters

17.2 SP 15
Now, the RNIF Adapter 1.1 supports Alternate Interface Namespaces for naming of messages. See Also Message Representation in SAP XI Message Interface Naming in RNIF Adapter 1.1 Message Interface Naming in RNIF Adapter 2.0

17.3 SP 16
Now, the RNIF Adapter 1.1, and RNIF Adapter 2.0 support Adapter-Specific Message Attributes. You can choose the attributes while configuring a communication channel. See also: Adapter-Specific Message Attributes in the Message Header Page 19 / 22

Changes in SAP NetWeaver '04 Service Packs

18 CIDX Adapter
18.1 SP 16
Now, the CIDX Adapter 1.1 supports Adapter-Specific Message Attributes. You can choose the attributes while configuring a communication channel. See also: Adapter-Specific Message Attributes in the Message Header

19 Local XI for ERP 2004

19.1 SP 13
It is now possible to install and run SAP Exchange Infrastructure together with an SAP ERP 2004 application on SAP Web Application Server 6.40. The following requirements must be fulfilled: The local Integration Server must be installed in a separate client. Only one SAP Exchange Infrastructure instance must be installed on each application server. Systems must be Unicode-enabled (the local Integration Server only supports Unicode systems). The local Integration Server is intended for installation in smaller system landscapes that have a lower throughput of data.

20 Service
20.1 SP 13
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. You can specify that messages that arrive from sender services may only be executed by the specified users in the Integration Server or Adapter Engine. This function is available when using the following sender adapters: XI Adapter Plain HTTP Adapter IDoc Adapter SOAP Adapter SAP Business Connector adapter Marketplace Adapter See also: Service

20.2 SP 14
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. You can specify that messages that arrive from sender services may only be executed by the specified users in the Integration Server or Adapter Engine. This function is now also available when using the RFC adapter. See also: Service (Enhanced) SPS 13

21 Conversion Agent
21.1 SP 15
Using the conversion agent, you can convert structured, semi-structured, and unstructured data to XML format. The conversion agent has a graphical development environment that enables you to define a conversion simply and quickly by using an example. Page 20 / 22

Changes in SAP NetWeaver '04 Service Packs The conversion agent is integrated in SAP Exchange Infrastructure and the PCK by means of an adapter module. This enables you to call the conversion agent from the adapters of the Adapter Engine. For current information and FAQs for the Conversion Agent, see SAP Note 894815. The conversion agent supports the following 32-bit platforms: Microsoft Windows 2003 (IA, 32 bit) Linux Red Hat, RedHat EL3 (IA32) Linux Suse SLES9 (IA-32) Solaris 9, 10 (64 bit) The conversion agent will soon also support further 64-bit platforms (UNIX, AIX, and so on). See also: Conversion Agent

21.2 SP 16
The Conversion Agent has the following additional functions: Improved Conversion Agent Studio environment with new project assistants, embedded help, and a guided mode. New data-transformation components Improved schema support features See also: What's New in Conversion Agent

22 Module Processor
22.1 SP 15
It is not longer possible to specify a module key in the Processing Sequence and in the Module Configuration for assigning parameter names and values to a particular module. The assignment is carried out automatically. You can display, create, change or delete the parameter names and values for the module in the processing sequence on which you are positioned. You can encode a password plus confirmation and enter it in the Module Configuration for parameter names that begin with pwd. See also: Module Processor

23 Send Step in Integration Processes

23.1 SP 15 In an asynchronous send step, you can set a conversation ID and define the Quality-ofService as EOIO (Exactly Once In Order). Conversation ID You can use the conversation ID to flag messages that belong together semantically. All messages with the same conversation ID in the message header semantically belong to the same business process. You can use this mechanism to represent more complex communication models that extend beyond basic request/response relationships. EOIO In EOIO, messages are delivered in exactly the same sequence that they are sent in by the integration process. See also: Sending Messages from Integration Processes Asynchronously

Page 21 / 22

Changes in SAP NetWeaver '04 Service Packs

24 External Definitions
24.1 SP 16
External definitions enable you to import WSDL, XSD, and DTD documents to the Integration Repository so that you can access the message definitions they contain as external messages. It was previously not possible to extract message definitions from parameter-oriented WSDL documents (rpcstyle). In the latest version, the Integration Builder converts such WSDL documents into a document-oriented WSDL document during import (document-style). See also: Import for WSDL-Documents in rpc-style

Page 22 / 22