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

Overview

In this exercise we will implement a simple asynchronous link between a file sender and Microsoft SQL Server database. The same vendor data that was used in exercise (1) will be sent to database.

As a result of this exercise, you will understand the JDBC adapter, its configuration and data format. In addition, we will introduce the concept of routing to multiple receivers for XI messages. Finally we introduce the concept of usage dependency between software components.

Prerequisites

•  Good understanding of basic XI features.

•  Basic knowledge of RDBMS.

Description

A custom XML document containing vendor information (same as exercise 1) is picked up from the file system by the file adapter. The message is mapped to the layout of the SQL table VendorMaster (this corresponds to the XML canonical format for the receiver JDBC adapter). This is sent to the JDBC adapter and the data in the SQL table is realized.

Exercise steps

Step 1 – SLD

•  Business systems

We will reuse the sender business system from Exercise 1 (XIWS_legacy_BS_[XX]). The appropriate objects have already been created in the SLD.

•  Software Components

You will keep working in your own software component, “XI RIG US workshop [XX]”. For this exercise, there is an additional requirement to reuse some objects which are maintained centrally, in a separate software component called “XI RIG US workshop base comp”, which we will refer to as the base component.

In the SLD you will now define a usage dependency between software components, and specify that your SWC “XI RIG US workshop [00..30]” will be based on SWC “XI RIG US workshop base comp”.

•  From the SLD homepage, select “Software Catalog”.

•  As software type, select “Software Components”

•  Locate your own software component “XI RIG US workshop [XX] of SAP XI RIG US ” and click on the SWC version.

•  Click on “Usage Dependencies” and select “Define Dependencies”.

•  Important: from the screen “Define Dependencies”, select “Installation Time”

•  Now select the SWC “XI RIG US workshop base comp” from the list, and click “create”. You have now created a usage dependency.

Step 2 – Integration Repository

•  Because we just defined a usage dependency in the SLD, it is necessary to re-import your SWC into the Integration Repository. After doing so, you will notice a new node “Basis objects”, under which there is a namespace “urn:xiworkshop:xirig”. Please compare this with the contents of SWC “XI RIG US workshop base comp”. When an object is updated in the base component, the change will be propagated to the basis object under your own SWC. If you have modified the object yourself under your own SWC and the basis object is updated in the mean time, the Integration Repository will offer conflict resolution before overwriting the object.

•  For this exercise we will reuse the data type VendorMaster_insert_DT and the message type VendorMaster_insert type from the base component. Please examine these objects. The data type represents the canonical XML format for the inbound JDBC adapter. The instructor will provide more explanations, if needed.

•  Create a message interface in your own namespace:

•  Message interface name: “VendorMaster_in” (inbound, asynchronous)

•  Reference to message type: VendorMaster_insert (from base comp)

•  Create a message mapping “Vendor__VendorMaster_insert” in your namespace as below. We are mapping to the XML canonical format which will be used by JDBC adapter to insert/update the data in the SQL server:

•  Source message: Vendor (urn:xiworkshop:group[XX]:legacy)

•  Target message: VendorMaster_insert (urn:xiworkshop:group[XX]:legacy)

Next

 Back to SAP XI Tutorials