SAP AG.co in Will Give information of SAP related meterials Like SAP Platform and Operation,,SAP Security , SAP Enterprise Portal (EP), ,SAP Knowledge Management (KW), SAP Business Intelligence (BI), Exchange Infrastructure (XI),Application Server, Mobile (MI), Master Data Management MDM, Composit Appications Frame work,Web Dynpros,OOPABAP,Blog,Intergration Bulder, Integration Repository (IB),Integration Directory (ID).System Landscape Directory (SLD), And Adopter Configuration like File to File,File to JDBC, File to IDoc, File Content Convertion, RFC, HTTP,SOAP,XI Interview Questions,Xi Sertification Questions, and many more about SAP Netweaver Platform XI Training And Tutorial and XI interview Questions ..

SAP Exchange Infrastructure Tutorials

SAP XI Exercises File to RDBMS

Exercise 2 – File sender to RDBMS receiver

(need to include mapping table in appendix).

•  Create an interface mapping “Vendor_out__VendorMaster_in” in your namespace:

•  Source interface: Vendor_out (urn:xiworkshop:groupXX:legacy)

•  Target interface: VendorMaster_in (urn:xiworkshop:groupXX:legacy)

•  Mapping program: “Vendor__VendorMaster_insert”

•  Activate your changes

  Step 3 – Integration Directory

You will reuse the scenario container created for your group (xiworkshop_group[XX]).

•  In the tab ‘objects', under ‘service without party', locate the business system XIWS_SQLSERVER_BS. Right-click and assign it to your scenario.

•  Check in the service XIWS_SQLSERVER_BS that your inbound interface appears in the list under the tab “receiver”.

•  Create a Communication channel for the business system XIWS_SQLSERVER_BS as shown below. The instructor will provide the relevant connection information for the database:

•  Communication channel name: “JDBC_Receiver_XX”

•  Adapter type: JDBC (receiver)

•  Transport protocol: JDBC 2.0

•  Message protocol: XML SQL Format

•  Adapter Engine: Integration Server

•  JDBC driver: com.microsoft.jdbc.sqlserver.SQLServerDriver

•  Connection string: jdbc:microsoft:sqlserver://<host>:<port>;DatabaseName=<DBName>

•  User name / password: check with instructor.

•   

By selecting XML SQL Format as message protocol, table values can be inserted, updated, or deleted in one or more tables. In the database, stored procedures can be called using transfer parameters. In the case of synchronous queries, results from database queries or return values of stored procedures can also be transferred

•  Open your existing receiver determination object. Add the service XIWS_SQLSERVER_BS as a receiver.

•  Create an interface determination object for your receiver:

•  Inbound interface: VendorMaster_in (urn:xiworkshop:groupXX:legacy)

•  Interface mapping: Vendor_out__VendorMaster_in

•  Create a Receiver Agreement which points to your receiver communication channel:

•  Activate your changes

Step 4 – Testing

The procedure to send the XML file to XI is the same as in exercise 1.

•  Use the file Vendor[XX].xml which you had previously saved. Copy the file to your shared folder under \\<hostname>\workshop\group[XX ].

*Note regarding the contents of the file: although the vendor number may have already been created in R/3 system, there is no need to change it for the purpose of this exercise. We are only concerned that the IDoc must be received at the technical level, and that the XML message must routed to the second receiver. Check with the instructor regarding the vendor number.

•  In order to reset the polling cycle of the inbound file adapter, you must go back to the Integration Directory and reactivate your communication channel ‘File_sender' under your business system ‘XIWS_legacy_BS_XX'. As soon as the file sender communication channel is activated and is replicated in the adapter engine cache, the polling cycle will start (this could take a few seconds).

•  Monitor your directory. The file should disappear after a few seconds. This means that it was processed and then deleted by the adapter engine.

•  Log on to the XI Integration Server, choose monitoring à Integration Engine monitoring (or execute transaction SXMB_MONI).

•  Choose “monitor for processed XML messages”. You can filter using different criteria, for example by date and also by sender service (find your own business service name in the drop-down list). In the monitor, your message should appear with status (message split executed). Notice that the message processing stops, and 2 children messages are created. When you scroll to the right, you can clearly view this in the column ‘Parent Message ID'. One of the children messages will be delivered to the IDoc adapter (as per exercise 1), and the other is the JDBC message. Inspect this message and look for any errors.

• In the Runtime workbench, under ‘Message monitoring', select messages from component ‘af.<SID>.nspad271' (this represents the central adapter engine.) Using the filter configuration, find your message ID in the list. Select your message, and click ‘Details'. From the details screen you can select ‘Audit Protocol' for more information regarding the status of your message and the JDBC post.

Previous Next

 Back to SAP XI Tutorials