Preview on New Features of the Integration Directory in SAP Netweaver Process Integration 7.1

Preview on New Features of the Integration Directory in SAP NetWeaver Process Integration 7.1

Applies to: SAP NetWeaver Process Integration 7.1

Summary

The Integration Directory is the central tool for the configuration of cross-component processes that are based on the exchange of XML messages. In the Integration Directory you define which systems of your system landscape and which external communication partners are involved in the process, you define routing rules that govern the message flow between these entities, as well as security settings for the communication. At the core of the Integration Directory are the different adapters that enable you to configure the communication with a variety of SAP - as well as non-SAP - applications.

This article outlines in short the most important new features of the Integration Directory that will be made available with SAP NetWeaver Process Integration 7.1 (SAP NetWeaver PI 7.1).

Author(s): Peter Gutsche Company: SAP AG Created on: 01. November 2007

Author Bio Peter Gutsche joined SAP in 1999 with a university degree in physics. He is a member of the SOA product management team. As an expert in the topic area of SAP NetWeaver Process Integration, he is responsible for writing product documentation as well as for general information rollout.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Preview on New Features of the Integration Directory in SAP NetWeaver Process Integration 7.1

Table of Contents SAP NetWeaver PI 7.1 Opens the Door to the World of Web Services Reliable Messaging ..... 3 Publish WSDL description of Sender Agreements to Services Registry ...... 3 Quickly Configure Elementary Scenarios with Integrated Configuration ...... 3 Configure Principal Propagation on the Basis of Security Assertion Markup Language (SAML) 3 Define Reusable Receiver Rules for Logical Routing...... 3 Display Cache Status per Object ...... 4 Related Content ...... 4

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Preview on New Features of the Integration Directory in SAP NetWeaver Process Integration 7.1

SAP NetWeaver PI 7.1 Opens the Door to the World of Web Services Reliable Messaging Web Services Reliable Messaging (WS-RM) is an open standard for asynchronous messaging that guarantees a considerable level of reliability and security. As of SAP NetWeaver PI 7.1, the Integration Directory enables you to easily configure scenarios where the Integration Server acts as a message hub between WS-RM-enabled applications and any other application or technical system. To do this, you use a communication channel (choosing the new adapter type WS). Thus, you can configure scenarios where either a Web Service client calls the Integration Server and the message is then routed to any other application, or the other way around where any application calls a Web Service provider via the Integration Server. In the Integration Directory you can do the complete configuration of the Integration Server inbound or outbound processing. Customers who are already familiar with SAP NetWeaver Process Integration, will find this easy to do since the configuration is done with communication channels. So to configure the inbound processing where a Web Service client calls the Integration Server, you simply create a suitable sender agreement and assign a communication channel (adapter type WS) to the sender agreement. The complete configuration settings - including the WS-RM -specific security settings - can then be defined in the sender agreement and the communication channel. As an additional feature, the Integration Directory enables you to also centrally configure direct (point-to- point) communication between a Web Service client and a Web Service provider as long as the involved backends run on SAP NetWeaver Application Server 7.10. In this case, the configuration data you specified in the Integration Directory, will be propagated to the involved backend systems by the cache refresh mechanism.

Publish WSDL description of Sender Agreements to Services Registry But what about the configuration of third-party WS clients or WS providers connected to the Integration Server? Ok, as in any business-to-business process, there's no magic that automates this task. However, a further feature supported with SAP NetWeaver PI 7.1 might help your business partner to easily find the information required to call the Integration Server. A new feature implemented with SAP NetWeaver PI 7.1 enables you to publish a sender agreement in the Services Registry. The WSDL description of the sender agreement then contains all configuration data that is necessary for a Web Service client to call your Integration Server (e.g. the URL of your Integration Server). Since the Services Registry is typically located in front of the firewall of your company, your business partner can easily access the WSDL description.

Quickly Configure Elementary Scenarios with Integrated Configuration A new configuration object enables you to configure the complete message flow from a sender to a receiver quickly and in a clearly arranged way. In releases lower that SAP NetWeaver PI 7.1, you needed several configuration objects even for a simple communication scenario: a receiver determination, an interface determination and serveral communication agreements. With the integrated configuration object (the name of the new object type) you can configure elementary scenarios where the receiver of the message is already known at configuration time and merely a simple mapping as needed (multiplicity 1:1). The integrated configuration object allows you to configure scenarios where the message is transmitted from a sender adapter to a receiver adapter via one Advanced Adapter Engine. This local message processing on the Advanced Adapter Engine provides a considerable increase in performance.

Configure Principal Propagation on the Basis of Security Assertion Markup Language (SAML) As of SAP NetWeaver PI 7.1, you can configure principal propagation based on SAML 1.1. Principal propagation means that a user is securely propagated from a sender to a receiver system and even across multiple communication paths. This feature is supported for Web Service clients calling the Integration Server (WS adapter).

Define Reusable Receiver Rules for Logical Routing As of SAP NetWeaver PI 7.1, you can define routing rules within a separate, reusable object, the receiver rule. Key benefit is that you can reuse a receiver rule in different receiver determinations. The receiver rule

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Preview on New Features of the Integration Directory in SAP NetWeaver Process Integration 7.1

then applies to all messages whose address header matches the object keys of the receiver determinations in which the receiver rule is used. Since you can activate and transport receiver rules separately, they are particularly suitable for use in projects in which the routing configuration cannot be transported as a single entity. Conversely, you still have the option to define routing conditions for a specific receiver determination as in SAP NetWeaver 7.0. This is then called a local rule. A local rule only applies to those messages whose address header matches the object key of this receiver determination.

Display Cache Status per Object As of SAP NetWeaver PI 7.1, the cache notification function is enhanced by an object-specific display of the cache status. You can display which cache instances the changes to a particular object were propagated to, and analyze possible errors for each object individually.

Related Content Please include at least three references to SDN documents or web pages. • Preview of Web Services Reliable Messaging in SAP NetWeaver Process Integration 7.1 • Principal Propagation with SAP NetWeaver Process Integration 7.1 • Using Folders in PI 7.1

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Preview on New Features of the Integration Directory in SAP NetWeaver Process Integration 7.1

Copyright © Copyright 2007 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com