1. Service interface generation for WSDL import into ESR
The import of externally defined WSDL files into the ESR and the creation of service interface objects are supported via a wizard. The service interface definitions can be modified once they are imported into the ESR. The external services can be directly used for proxy generation. Multiple WSDL files can be imported.
2. Classification support in ESR
Classifications, which provide an option to add a semantic meaning, can be directly assigned in the ESR to one service interface or to a group of service interfaces. The ESR also allows searching for services by their classifications.
3. Security profile settings for service interfaces
Security levels can be directly assigned to the service interfaces in the ESR. The security level value is sent to the provider system during proxy generation and defines the minimum security configuration of the service definition.
4. Where-used list in Services Registry
The Services Registry allows searching for Service Groups. A Service Group bundles all services that are provided by the same logical service provider. If a service definition is assigned to a Service Group, it indicates that the service is used by a consumer. Service Groups can be published in SR and enable configuration of multiple services in one go.
5. Add information to services published in the Services Registry
The publication wizard of the Services Registry supports to classify the published service, add provider system information and a link to the documentation of the service, and add user name and password if the service requires authentication.
6. User defined usage profiles in the ESR & Service Registry
The ESR allows creating customized usage profiles to define sets of object types, software component versions and business modeling filters that are of interest to different user groups. The usage profiles can be assigned to specific users, roles, or groups, and are personalized filters that provide a fine granular control of who can view and edit SOA artifacts; with this a simplified UI is offered since all the other SOA artifacts are hidden. The Services Registry supports an elaborate authorization concept for its users and provides user-specific views on the content of the Services Registry. Security permissions can be defined that assign User Management Engine (UME) roles to classifications.
7. Cleanup of Services Registry
In the SAP NetWeaver Administrator tasks can be defined that provide information about invalid URLs and URLs that cannot be reached. The jobs can be either scheduled to run on a periodic basis or triggered as an event when required. Based on the information about the unavailable entities it can be decided to either correct a service endpoint or to remove the service definition from the Services Registry.
8. Generation of outbound interfaces based on inbound interfaces
The ESR provides a wizard to automatically create an outbound service interface for a given inbound service interface and assign a link between the service interfaces to indicate that the two interfaces match. The outbound service interface and the inbound service interface can reside in the same or in different software component versions.
9. Content Based Routing (CBR), Receiver Split+(RS) & Operation-dependent receiver determination in Advanced Adapter Engine (AAE)+
The integrated configuration, that determines the routing condition for the local processing on the AAE, supports the configuration of different receivers for different message payload values; i. e. a message that is processed locally on the AAE can be sent to different receivers depending on values of the message payload. The integrated configuration supports configuration of multiple receivers; i.e. a message that is processed locally on the AAE can be sent to multiple receivers. The receiver determination, that determines the routing condition on the Integration Server, supports definition of different receivers for different operations of same outbound SI.
11. Integration Directory API supports new objects types
The Integration Directory API, that provides a web services based API to access, edit, and activate objects in the Integration Directory, supports new object types and attributes that have been introduced with SAP NetWeaver PI 7.1, such as direct connections.
12. Enhanced search for communication channels
The Integration Directory allows searching for communication channels with adapter type specific attribute values; e. g. to search for communication channels with adapter type File/FTP who has configured a specific file name.
13. Scenario view in Integration Directory
The scenario view in the Integration Directory allows grouping assigned objects according to configuration scenarios.
14. Enhancements of Adapter Engine Java SE
Remote configuration: The remote configuration allows to add, start, and change remote adapter instances of the Adapter Engine Java SE; a message containing the configuration information is sent from the central Integration Server to local Adapter Engine Java SE.
Empty file handling: The empty file handling controls how the File/FTP sender adapter of the Adapter Engine Java SE handles empty files: The messages with empty files can be either processed or stopped with the creation of an error message.
Prevent overwriting files: The File/FTP receiver adapter of Adapter Engine Java SE allows to control whether files with names that already exist in target directory are to be overwritten.
15. Configuration based on Process Component Interaction Models
The model configurator, that creates the relevant configuration objects in the Integration Directory and groups them in a configuration scenario, allows to use one or multiple Process Component Interaction Models from the Enterprise Services Repository as a template for configuration; i. e. the Model Configurator creates the configuration objects in the Integration Directory based on the SOA artifacts saved in the Process Component Interaction Models together with additional assignments.
16. XI message protocol is supported in the AAEThe XI message protocol is supported via the SOAP adapter. With this messages that are sent to or received from ABAP proxies, other AAE's or Partner Connectivity Kits can be processed locally on AAE. The SOAP adapter is enhanced to accept XI message protocol.
17. End to end IDoc packaging
IDoc sender adapter allows optionally processing an IDoc package that reaches inbound channel of Integration Server from sender to receiver as IDoc package, i.e. IDoc package is not split into single messages that might have to be collected in integration process.
18. IDoc conversion adapter module
The IDoc conversion adapter module allows to convert an IDoc Xml message payload to an IDoc flat file format and vice versa. This IDoc conversion adapter module can be used together with a Java based sender and receiver adapter, optionally with local processing on the AAE, in order to connect to systems with IDoc entry points.
19. WS-Secure Conversation 1.3
This standard defines how to establish and maintain a persistent context for a secure session over which multiple web service invocations might be sent without requiring authentication each time. Currently supported is WS-Secure Conversation for SCT over SSL bootstrap.
20. User-defined message search for business criteria
A new, user-defined message search is available in the message monitoring that allows to search for business relevant information criteria contained in the message payload, such as sales order number or customer ID, as well as adapter-specific message attributes, such as file name for the File/FTP adapter. This new, user-defined message search does not require TREX. The previously introduced index-based message payload search using TREX is still available as well.
21. Cross domain message status overview
The SAP NetWeaver Administrator for PI offers a message overview for all domains that are connected to the SAP NetWeaver Administrator for PI. This enables an overview of the message processing at many levels, from the entire system landscape over domains to individual components, such as Integration Engines, Advanced Adapter Engines, Business Process Engines; therefore this is one further step towards monitoring the overall landscape of SAP NetWeaver PI systems.
22. PI monitoring and configuration capabilities available through SAP Solution Manager
The SAP Solution Manager, which is the central, IT role-based administration and monitoring infrastructure across the whole SAP landscape, provides direct access to main configuration and monitoring capabilities of SAP NetWeaver PI, such as SAP NetWeaver Administrator for PI or SOA Manager.
23. SOA configuration for connectivity of WS & consumers based on SOA Manager
The configuration for connectivity enables the configuration of groups of web services and web service clients in one go; i. e. multiple web services and web service clients do not have to be configured individually, but can be assigned to a configuration setting. The configuration is based on reusable objects, such as Service Groups; as mentioned above, Service Groups bundle all services that are provided by the same logical service provider.
24. Enhancement in migration controller for smooth upgrades of Java proxies to PI 7.1
