Interface Objects

Feature

Type of Change

Description

Automatic Migration of Message Interfaces

New

Until SAP NetWeaver 2004s there were message interfaces in the Integration Repository. Each message interface consists implicitly of an operation, which is not named in the message interface editor.

As of this release, you can no longer create message interfaces. You can only create service interfaces, which allow the definition of multiple operations. During an upgrade to the new release or a transport of message interfaces to the Enterprise Services Repository, all message interfaces are automatically converted to equivalent service interfaces with one operation. For example, a message interface called MI becomes a service interface called MI with one operation MI . You do not need to do anything to convert message interfaces to service interfaces.

For more information, see Service Interface .

Interface Pattern

New

Depending on the use of a service interface, there can be different types of operations for the respective use. To enable the selection of possible operations to be restricted at design time, each service interface has an interface pattern, which you use to decide implicitly on a communication and thus programming model.

For more information, see Interface Pattern .

Idempotency

New

In the service interface, for inbound category with mode as synchronous and any interface pattern except TU&C/C, a new option called Idempotent is available.

For more information about the Idempotent flag, see Service Interface .

Security Profile

New

You can assign security levels to the service interfaces in the ES Repository.

For more information about security profile, see Service Interface .

Assigning Service Interfaces

• To simplify the configuration of point-to-point connections, you can assign related service interfaces to one another in the Enterprise Services Repository (outbound service interface and inbound service interface).

  For more information, see Developing Point-to-Point-Services Outside-In .

• For a given inbound service interface, a wizard automatically creates an outbound service interface and assigns a link to match the two interfaces. This is applicable only for point-to point communication.

  For more information, see Matching Service Interfaces for Point-to-Point Communication .

Classifying service interfaces in the ES Repository

New

You can assign classifications to service interfaces in the ES Repository.

For more information: Classifying Services in the Enterprise Services Repository .

Publishing service interfaces

New

• Mass Publication

  You can publish multiple service interfaces at once to the Services Registry.

  For more information about publishing multiple service interfaces at once, see Publishing Service Interfaces .

• Auto-publication

  You can configure the ES Builder to automatically publish service interfaces to the Services Registry after activation.

  For more information, see Enabling Automatic Publication of Service Interfaces .

Creating service interfaces from WSDL files

New

A wizard enables you to import WSDL files into the ES Repository and create service interface objects.

For more information, see Creating Service Interfaces from WSDL Files .

Developing Data Types

Enhanced

Core data types and aggregated data types are developed according to ISO 15000-5 (ebXML Core Components Technical Specification (ebCCTS, shortened to CCTS)). This UN/CEFACT committee methodology defines semantic modules without syntax (core component types) that take into account the latest requirements for describing business data generically. Applying this methodology simplifies the implementation of cross-company processes, in particular.

SAP applies the CCTS methodology in an unification and standardization process to develop data types in XML schema in the ES Repository. For this purpose, the data type editor for core data types contains attributes that enable developers to reference the semantic modules of CCTS. Compared with free-style data types, core data types also contain additional information about the semantics of a particular data type. This information makes it easier to develop interface elements such as input and value help later on, for example. Free-style data types support the range of commands in XML schema only.

For more information, see Developing Data Types According to CCTS .

Help Type for Complex Types with SimpleContent

New

Previously, to define a complex type with simpleContent you had to manually create a help type. The data-type editor now creates this help type automatically in the background.

For more information, see Complex Types with SimpleContent .

Mass import of data types

New

The ES Builder enables you to import multiple data types at a time.

For more information, see Mass Import of Data Types .

Deletion Indicator

New

A consumer can explicitly communicate to a provider at runtime that the elements of a particular data type can be deleted.

Mass import of external definitions

New

Until now, you could only upload individual files to the Integration Repository one after the other. As of the new release, you can upload multiple files to the Enterprise Services Re pository at once and create an external definition for each file. For more information, see Mass Import for External Definitions .

Automatic Migration of Imported RFCs and IDocs

New

The internal data storage format for imported RFCs and IDocs has changed. The new data format is simpler and less performance-intensive. All RFCs and IDocs are automatically put in the new data storage format when you upgrade to the new release or transport RFCs or IDocs to the Enterprise Services Repository. There are no other effects

Defining interface texts

New

You use UI text objects to define interface texts at design time. You assign these texts to objects in the Enterprise Services Repository so that they are immediately accessible for later use in UI development.

For more information, see UI Text Objects .

General

Enhanced

• Parameterized Mapping Programs

  You can now work with parameters - whose values are not defined until configuration time - in message mappings, Java mapping programs, and XSLT mapping programs. In mapping lookups, to define the communication channel to be used in the Integration Directory, you can now use the new parameter type Channel . For more information, see Parameterized Mapping Programs .

• Test Environment

  In lower releases, you were able to test mapping programs if you had the authorization to display mapping objects in the Enterprise Services Repository. This authorization is now no longer sufficient. For more information, see Test Environment for Operation Mappings and Test Environment .

Message Mappings

Enhanced

• Function Libraries

  In lower releases, you were able to save and manage user-defined functions as part of one message mapping. You can now create function libraries independently of specific message mappings, and can use the functions you define in them in multiple message mappings. For more information, see Function Libraries .

• Standard Functions for Mapping Lookups

  In lower releases, you could only use mapping lookups in message mappings if you used the mapping-lookup-API in Java within a user-defined function. The mapping editor now has the standard functions JDBC Lookup and RFC Lookup for lookups involving the JDBC or RFC adapter. For more information, see Defining JDBC Lookups Graphically and Defining RFC Lookups Graphically .

• Variables

  In the target structure in the mapping editor, you can now define a graphical variable that you assign a value to at runtime by using a normal target-field mapping. You can then use this value in the scope of the variable when you apply the variable in other target-field mappings; doing so helps to simplify the target-field mappings concerned. For more information, see Variables in the Target Structure .

• Filter (Usability)

  A filter is now available in both the structure overview and the test environment in the mapping editor. The filter enables you to display only those fields in the respective structure that you require for your work on the message mapping. For more information, see Structure Overview .

• Precision of Standard Functions

  The arithmetic standard functions of a message mapping perform calculations with the precision of the Java data type float. The Java runtime converts values of type float to dyadic format before the calculation, calculates the result, and converts this result back to decimal format. The conversion may result in decimal places in the dyadic format that are periodically repeated and then automatically cut off. In the decimal system, this can result in inaccurate results (example: 2.11 + 22.11 = 24.220001).

  Until now you could not change the precision of the calculations. To prevent the above-mentioned inaccuracies in the calculations, you can now perform the calculation for a selection of standard functions in the decimal system. For more information, see Standard Functions or SAP Note 958486.

XSLT Mappings

New

SAP supports the SAP XML Toolkit for SAP NetWeaver Process Integration 7.1 and the next release of SAP NetWeaver. In SAP NetWeaver Process Integration 7.1 and higher you can work with the Java Development Kit (JDK) 5, which is a functionally superior tool to the SAP XML Toolkit. Both runtimes are available during the transition phase.

For more information, see XSLT Mapping .

Java Mappings

Enhanced

A new API is available for Java mappings. The previous mapping API still exists but no further development will take place (parameterized Java mapping programs are only possible with the new mapping API, for example). For more information, see JAVA Mapping .

Testing Mapping Programs

Changed

It was previously possible for users who had authorization to display mapping objects in the Integration Repository to test mapping programs. This authorization is now no longer sufficient.