A Step-by-Step Guide on Asynchronous RFC - to - JDBC Scenario Using SAP PI 7.0

...Previous

B.2) Maintain ID (Integration Directory)  

B.2.1 Create Configuration Scenario

Open Integration Directory

Create a new Configuration Scenario or use an existing one. In our example scenario “rfc2jdbc” will contain all our scenario objects.

B.2.2 Add Sender and Receiver Business System.

Add sender and receiver business System in your Configuration scenario

The business Systems used in this scenario is as follows.

  1. CX1_Business_System
  2. TBIT40_SQLSERVER_BS  

B.2.3 Create Sender Communication Channel.  

Go to your Sender Business System, right click on communication channel and select “new”.

Create a new receiver communication channel “RFC_Test1”

Select the Sender Radio button to identify the channel as sender.

Adapter type: RFC

Transport Protocol: RFC

Message Protocol: RFC (RFC XML)

Adapter Engine: Integration Server.

Program ID: RFC2JDBC (should be same as used in RFC Destination)

Save & activate.

Enter the RFC Metadata Repository Parameter as follows. i.e the Sender system details.

B.2.4 Create Receiver Communication Channel.  

Go to your Receiver Business System, right click on communication channel and select “new”.

Create a new receiver communication channel “MSAccess_RECV_DS2”.

Select the Receiver Radio button to identify the channel as receiver.

Adapter type: JDBC      

Transport Protocol: JDBC 2.0

Message Protocol: XML SQL Format

Adapter Engine: Integration Server.

JDBC Driver: sun.jdbc.odbc.JdbcOdbcDriver

Save & activate.

B.2.5 Create Receiver Determination.  

Create a new Receiver Determination.

Sender service: CX1_Business_System

Interface: ZTEST_TIPS_DOI

Namespace: urn:sap-com:document:sap:rfc:functions

Enter your receiver business system “TBIT40_SQLSERVER_BS”.  Save.

B.2.6 Create Interface Determination.  

Create a new Interface Determination.

Sender service: CX1_Business_System

Interface: ZTEST_TIPS_DOI

Namespace: urn:sap-com:document:sap:rfc:functions

Inbound Interface: “masterData_MI”

Namespace: “urn:sap-com:Tipsinterface”

Interface mapping: “test_DS_IM”

Save & activate

B.2.7 Create Receiver Agreement.  

Sender service: “CX1_Business_System

Receiver service: “TBIT40_SQLSERVER_BS

Inbound Interface: “masterData_MI”

Namespace: “urn:sap-com:Tipsinterface”

Select the Receiver Communication Channel “MSAccess_RECV_DS2” created above.

Save & activate.  

B.2.8 Create Sender Agreement.  

Sender service: “CX1_Business_System

Interface: “ZTEST_TIPS_DOI

Namespace: urn:sap-com:document:sap:rfc:functions

Select the sender Communication channel “RFC_Test1” created above.  

Testing the Scenario

Go to transaction SE 38 and execute the Report “ZTEST_WEBSERVICE”.

A test message will be displayed on screen.

Go to transaction SXMB_MONI in XI server to view the status of the messages. Messages should have successful Status.

Open the database table to see if the records have been inserted into tables or not.

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image