Point-to-Point Direct Connection Design and Configuration in

Point-to-Point Direct Connection Design and Configuration in SAP using NetWeaver Processing Integration 7.1

Applies to: NetWeaver Process Integration 7.1 SP4

Summary Author: William Li

Company: SAP Labs LLC

Created on: 12 February 2008

Author Bio William Li is a member of the SAP NetWeaver Integration Team in SAP NetWeaver RIG Americas focusing on Process Integration. He has been with SAP since 1998 - originally as a consultant then as a developer. He joined SAP NetWeaver RIG Americas in January of 2003.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 1


Table of Contents Introduction .........................................................................................................................................................3 System Setup .....................................................................................................................................................4

Users & Authorizations....................................................................................................................................4 Connection parameters...................................................................................................................................4

Creating a new Business System ................................................................................................................................4 Adding the URL to an existing Business System: ........................................................................................................5

Business Scenario ..............................................................................................................................................6 Design and Configuration Steps.........................................................................................................................6

Design Inbound and Outbound Interfaces for Scenarios 1 and 2...................................................................6 Request data type:.......................................................................................................................................................7 Response data type: ....................................................................................................................................................7 Request message type: ...............................................................................................................................................8 Response message type:.............................................................................................................................................8 Inbound synchronous service interface:.......................................................................................................................9 Outbound synchronous service interface: ..................................................................................................................10

Generate Proxies on SAP Backend System for Scenarios 1 & 2.................................................................11 Inbound proxy: ...........................................................................................................................................................11 Outbound proxy: ........................................................................................................................................................12

Integration Directory Configurations for Scenario 1......................................................................................13 Create Receiver Communication Channel for Scenario 1..........................................................................................13 Create Direct Connection for Scenario 1 ...................................................................................................................15 Activate the Configuration Objects.............................................................................................................................16 Testing the Connection for Scenario 1.......................................................................................................................17

Integration Directory Configurations for Scenario 2......................................................................................18 Create Receiver Communication Channel for Scenario 2..........................................................................................18 Create Direct Connection for Scenario 2 ...................................................................................................................21 Activate the Configuration Objects.............................................................................................................................22 Testing the Connection for Scenario 2.......................................................................................................................23

Appendix...........................................................................................................................................................25 Checking the successful distribution of the configuration .............................................................................25 Enabling the distribution of the Configuration ...............................................................................................28 ABAP Report Used to Initiate the Outbound Proxy Interface for Scenario 1 and 2......................................30

Related Content................................................................................................................................................32 Copyright...........................................................................................................................................................33




Introduction Direct Connection is when one system calls another system directly without using the Integration Server as a central instance. Communication takes place using the Web services runtime.

When applications are coupled tightly they can exchange messages directly - without a redirection through a middleware (like the Integration Server) that offers services such as mapping. However, this peer-to-peer message exchange can still be configured (technical address of the Receiver System, authentication, security settings etc) in one central place.

Point-to-point connection allows a much greater message throughput performance, simply because a middleware is not involved in message processing. However, because of this, services such mappings, dynamic receiver determination, ccBPM (as provided by the middleware) are no longer available during the message exchange.

When an environment contains many point-to-point connections, the administration and maintenance of connections becomes quite cumbersome to support. This is where the benefit of SAP NetWeaver 7.1 Process Integration (PI) becomes obvious. PI provides a tool and infrastructure to centrally design, configure and support of the point-to-point connection. With PI, message types and interface can be designed in the Enterprise Services (ES) Repository, and connection configurations and communication channels can be done in the Integration Directory (ID). All the configuration objects are also propagated automatically to the perspective backend business systems.

To allow this to happen, the Service Runtime in PI is now also a component of all SAP NetWeaver 7.1 systems. Therefore, in order to use point-to-point direct connection, a 7.1 system is a prerequisite.

The peer-to-peer message exchange will use the Web Service Message Protocol and a new Web Service Runtime. Therefore, the Integration Builder Directory can be used to configure peer-to-peer between Business Systems using the WS Message Protocol.

This document describes how to configure point-to-point direct connection using SAP NetWeaver Process Integration 7.1.

PI

ES Repository

ID

Sender

Business

System

Receiver

Business

System

Distribution of configuration

objects.

Service Runtime

Service Runtime


System Setup There are different settings needed, before you can start configuring a Web Service communication.

Users & Authorizations

The users that want to define WS communications in the Integration Directory need the role SAP_XI_CONFIGURATOR. These users have to be defined in the Integration Server.

The configuration maintained in the Integration Directory has to be distributed into the ABAP Backends (the sending & receiving Business Systems). The users for this distribution are defined in the Integration Directory (per Business System) and these users need to exist in the respective ABAP clients and they need the roles SAP_BC_WEBSERVICE_ADMIN & SAP_XI_ID_SERV_USER.

Connection Parameters

For the distribution of the configuration, we not only need users in the Backends (see above) we also need to know the URLs to reach these Backends. This URL is maintained in the SLD. There are two different use cases:

Creating a New Business System

Start the SLD, choose Business Systems and press the Button ‘New Business System…’. Follow the Wizard and in step 2 there is a field ‘URL’. You can either choose one of the already existing URLs or simply type in a new one in the field to the right.



© 2008 SAP AG 5

The “Configuration URL” is required for the distribution of the configuration objects to the business systems.

Adding the URL to an Existing Business System:

Start the SLD, choose Business Systems and select the desired Business System in the list. You will get the details of this Business System and on the Tab ‘Integration’ you will find a field ‘Configuration URL’ where you can enter the URL that shall be used. This URL is used for the distribution of the configuration objects to the perspective business systems.

The same configuration URL applies to SYS2.

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


Business Scenario Two scenarios will be described:

Point-to-point connection where the sender and receiver are of the same SAP business system. This scenario is for local calls in the same business system. A message containing a key-value pair will be sent to a receiver, where the key-value pair will be inserted into a custom table. The sender and receiver business systems are both SYS1.

Point-to-point connection where the sender and receiver are of different SAP business systems. A message containing a key-value pair will be sent to a receiver, where the key-value pair will be inserted into a custom table. This is identical to the first scenario, except the sender and receiver business systems are different. The send business system is SYS1 and the receiver business system is SYS2.

Design and Configuration Steps The basic steps required for the complete design and configuration process are as follow:

1. Design the inbound and outbound interfaces in the Enterprise Services (ES) Repository.

2. If any of the business systems is an SAP system, then ABAP proxies will have to be generated on the corresponding backend SAP system, using the interfaces in the previous step. The primary reason is that during the activation process in the Integration Directory (ID), the proxy objects of the interfaces will be checked. If the proxies do not exist, then the activation will not be completely successful.

3. Configure and activate the ID objects, specifically the receiver communication channel and the direct connection.

4. Test the connection using the ABAP proxies. (Sample proxies and programs are included in the appendix.)

The procedures described below will be based on manual configuration. Configuration Wizard can also be used, using the same entries as in the manual configurations.

Design Inbound and Outbound Interfaces for Scenarios 1 and 2

Scenarios 1 and 2 are identical, except the receiver of scenario 1 is the same as the sender, and the receiver of scenario 2 is of a different business system. Therefore, the interfaces for these 2 scenarios are the same.

The data type, message type and service interface are created in the same way as in SAP NetWeaver XI 3.0 or PI 7.0.



Request Data Type:

Response Data Type:



Request Message Type:

Response Message Type:



Inbound Synchronous Service Interface:



Outbound Synchronous Service Interface:



Generate Proxies on SAP Backend System for Scenarios 1 & 2

Inbound Proxy:

Source code of the inbound proxy:

METHOD zrkt_ii_p2preceiver~rec_update_request.

* Data types to get data of input message

DATA: lv_key TYPE char10,

lv_value TYPE char10,

lv_date LIKE sy-datum,

lv_time LIKE sy-uzeit,

ls_lookup TYPE zp2p_table,

lv_cnt TYPE i.

* MESSAGE X000(00).

lv_key = input-update_req_mt-key.

lv_value = input-update_req_mt-value.

lv_date = sy-datum.

lv_time = sy-uzeit.



SELECT MAX( id ) FROM zp2p_table INTO lv_cnt.

ADD 1 TO lv_cnt.

ls_lookup-id = lv_cnt.

ls_lookup-keyname = lv_key.

ls_lookup-value = lv_value.

ls_lookup-change_date = lv_date.

ls_lookup-change_time = lv_time.

INSERT zp2p_table FROM ls_lookup.

output-update_resp_mt-count = lv_cnt.

output-update_resp_mt-record-key = lv_key.

output-update_resp_mt-record-value = lv_value.

output-update_resp_mt-record-change_date = lv_date.

output-update_resp_mt-record-change_time = lv_time.

ENDMETHOD.

Outbound Proxy:

The ABAP report using this proxy is included in Appendix 4.3.



Integration Directory Configurations for Scenario 1

Create Receiver Communication Channel for Scenario 1 a. Right-click on “Communication Channel” “New”:

-OR- b. Click on “Create Object” on the top menu and select “Communication Channel”



c. Configure the adapter, using the following info.

Adapter type: WS

Check “Local Call in Business System” to indicate the receiver is the same as the sender business system.



Create Direct Connection for Scenario 1 a. Right-click on “Direct Connection” “New”:

-OR- b. Click on “Create Object” on the top menu and select “Direct Connection”



c. Configure “Direct Connection” using the following info.

Activate the Configuration Objects

After activation, verify the successful status of object distribution to the backend system. Please see the appendix for details.



Testing the Connection for Scenario 1

Using the ABAP report, ZRKT_P2P_UPDATE_SYNC1:



The custom table, ZP2P_TABLE, is updated. Using TR: SE16, we can examine the content:

Integration Directory Configurations for Scenario 2

Create Receiver Communication Channel for Scenario 2 d. Right-click on “Communication Channel” “New”:

-OR-



e. Click on “Create Object” on the top menu and select “Communication Channel”



f. Configure the adapter, using the following info.

Adapter type: WS

Check “SAP System (ABAP Stack)” and the corresponding technical settings for the receiver business system.



Create Direct Connection for Scenario 2 d. Right-click on “Direct Connection” “New”:

-OR- e. Click on “Create Object” on the top menu and select “Direct Connection”



f. Configure “Direct Connection” using the following info.

Activate the Configuration Objects

After activation, verify the successful status of object distribution to the backend system. Please see Appendix 4.1 for details.



Testing the Connection for Scenario 2

Using the ABAP report, ZRKT_P2P_UPDATE_SYNC1:



On the receiver system, the custom table, ZBL_Lookup, is updated. Using TR: SE16, we can examine the content:



Appendix

Checking the Successful Distribution of the Configuration

To verify, that all your configurations are successfully distributed to the Backends (otherwise the communication can obviously not work) you should check the ‘Cache Notifications’:

In the menu, choose Environment Cache Notifications to see an overview of all notifications which are sent to the Backends (and also to the Integration Server and to Adapter Engines – but this is not relevant now). You can filter for the Cache-Instance (choose the Business System you are interested in) and also for the user (that activated the changelist) or the time.

Successful Cache Refresh is indicated by green lights in both columns!

The yellow light means that you have to be patient, while a red light indicates a general error (most for technical reasons) that prevented the update of ALL objects of the changelist.

A half green/yellow light indicates that there are problems with specific objects of the changelist. This can happen when the proxy has not been generated for one of the interfaces.



In any case except for two green lights, something went wrong and you should switch to the ‘Problems’-Tab!!!

When selecting a line you will see, what object (channel or direct connection) could not be distributed and the problem description in the bottom gives further hints what went wrong. If you can not solve the problem by changing configuration or system settings (e.g. it’s simply a bug) – please add this problem description to your Customer Message to SAP support.

Also, verify the activation in the SAP backend system using the TR: SXI_CACHE

After activation, 3 categories in the RunTime Cache should be updated: Profile, Assignment and Direct Connection.





Enabling the Distribution of the Configuration

As already mentioned in the System Setup, the configuration has to be distributed to both Backends – more precisely, the Backends will be notified that their Configuration is no longer up-to-date. For this, we need the URL to the Backends which is maintained in the SLD (see Connection parameters), but we also need a user and password. These users and passwords are maintained in the Integration Directory per Business System:

Open the sending or receiving Business System and select the tab ‘Other Attributes’. Select the flag ‘send Cache Notifications to backend’ and enter a valid user and password. This user should exist in the Business System and needs the roles SAP_BC_WEBSERVICE_ADMIN & SAP_XI_ID_SERV_USER (see Users & Authorizations).

Moreover, in the Backend we need a sm59 destination ‘INTEGRATION_DIRECTORY_HMI’ of type ‘H’ so the Backend can read the new Configuration from the Integration Server. The user to connect to the Integration Server needs the role ‘SAP_XI_IS_SERV_USER’.





ABAP Report Used to Initiate the Outbound Proxy Interface for Scenario 1 and 2 *&---------------------------------------------------------------------*

*& Report ZRKT_P2P_UPDATE_SYNC1

*&

*&---------------------------------------------------------------------*

*&

*&

*&---------------------------------------------------------------------*

REPORT ZRKT_P2P_UPDATE_SYNC1.

parameters:

key type char20 default 'sync1',

value type char20 default 'bbb'.

selection-SCREEN SKIP.

parameters:

t_party type sxi_to_party DEFAULT '',

t_srvc type sxi_to_service default 'SYS1'.

DATA: lr_paf_request_out TYPE REF TO ZRKT_CO_P2PSENDER,

lv_input TYPE ZRKT_UPDATE_RESP_MT,

lv_output TYPE ZRKT_UPDATE_REQ_MT,

l_cx TYPE REF TO cx_root,

lp TYPE prx_logical_port_name,

from_service TYPE sxi_from_service.

lv_output-UPDATE_REQ_MT-KEY = key.

lv_output-UPDATE_REQ_MT-VALUE = value.

*break liwi.

CALL FUNCTION 'LCR_GET_OWN_BUSINESS_SYSTEM'

IMPORTING

bs_key_name = from_service

EXCEPTIONS

OTHERS = 8

.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

TRY.

lp = cl_cpa_cache=>get_logical_port(

from_party = ''

from_service = from_service

to_party = t_party

to_service = t_srvc

actionns = 'urn:sap-com:p2p:test1' "# EC_NOTEXT

actionname = 'P2PSender'

).

CATCH cx_srv_binding_error INTO l_cx.

ENDTRY.



TRY.

CREATE OBJECT lr_paf_request_out

EXPORTING

logical_port_name = lp.

CATCH cx_ai_system_fault INTO l_cx.

ENDTRY.

TRY.

* lr_paf_request_out->SEND_UPDATE_REQUEST( output = output ).

CALL METHOD lr_paf_request_out->SEND_UPDATE_REQUEST

EXPORTING

output = lv_output

IMPORTING

input = lv_input.

CATCH cx_ai_system_fault INTO l_cx.

ENDTRY.

WRITE: / 'Call Successful!'.

WRITE: /,

/, 'Record ID = ', lv_input-UPDATE_RESP_MT-COUNT,

/ ' key = ', lv_input-UPDATE_RESP_MT-RECORD-KEY,

/ ' value = ', lv_input-UPDATE_RESP_MT-RECORD-VALUE,

/ ' date = ', lv_input-UPDATE_RESP_MT-RECORD-CHANGE_DATE,

/ ' time = ', lv_input-UPDATE_RESP_MT-RECORD-CHANGE_TIME.



Related Content • Demo for Design and Configuration of Direct Connection in SAP NetWeaver PI 7.1

• SAP NetWeaver Process Integration 7.1 - Overview

• SAP NetWeaver Process Integration 7.1 - Overview of New Capabilities


https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0b9885b-5ca9-2a10-6b8e-abe9ef432a23

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0ed3b8c-698c-2a10-fbaf-b1df0c82fc8a

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/706005a3-3bd6-2910-91ae-a2016239bdcf



Copyright © 2008 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.

Documents

Point-to-Point Direct Connection Design and Configuration in