This Scenario explains about the retrieval of records from Oracle DB and transfers them to SAP R/3 via SAP XI. Query has to be triggered daily at a particular time (e.g.: daily at 14.00 hours).So Scheduling is done in JDBC Sender Adapter. XI Receiver Adapter is used to connect SAP R/3.
Prerequisites: * SLD should be configured. Topics covered in this Scenario are: 1. IR development 2. ID configuration 3. Scheduling a Channel Following are steps of the Scenario. I. _Integration Repository:_ 1) Import the Software Component Version created in SLD.
2) Specify the Namespace in the Software Component Version imported 3) Not Permitted option is checked for the Interface Import as we are not importing anything from R/3.
4) Create a Source Data type with the same field structure that is going to be retrieved from DB. 5) Here I have created a Target data type similar to the Source data type.
6) We create the corresponding Message types for both the Source and Target Structures. 7) Right-Click on Message type in Interface Objects to create a new Message Type MT_Source. 😎 Using F4, select DT_Source (Source Data type) in Source Message type MT_Source. 9) Similarly, create Target message type where DT_Target is included in MT_Target.
10) Now we have to create the Outbound & Inbound interfaces. 11) Right-click on the Message Interfaces to create the corresponding interfaces. 12) MI_oa_Source is a Outbound Asynchronous interface. Select the corresponding Message type MT_Source.
13) Similarly create MI_ia_Target which is a Inbound Asynchronous interface. Select MT_Target message type.
14) Create a Message mapping object MM_Source_to_Target. Select source as MT_Source and target as MT_Target. 15) Here for simplicity in mapping, we do a One-to-One mapping.
16) Interface mapping Object IM_Source_to_Target is created. 17) Select Source interface as MI_oa_Source and Target interface as MI_ia_Target. Save & Click on Read Interfaces. The corresponding Message types are displayed. 18) Select the Message mapping object MM_Source_to_Target created previously.
19) *Save* & III. *Steps to Schedule a Communication Channel:* 1) Go to Communication Channel Monitoring in Runtime Work Bench.
2) Go to the corresponding Communication Channel i.e., CC_211G_JDBC_Server
3) Click on "Availability Time Planning"
4) Create a Daily Schedule for the Communication Channel "CC_211G_JDBC_Server"
5) Schedule at 14:00 CET for a duration of 2 hour. 0.1. Click on "Details" tab 0.2. Select the "Active" checkbox 0.3. In "Time" field , enter "14:00 CET" for 2 hours
6) Click on "Communication Channels" tab Select "CC_211G_JDBC_Server" channel.
Then "*SAVE*" the settings done. 7) In Communication Channel monitoring Screen "Automatic Control" should be active for the scheduler to run. Check the following to see whether Scheduler is active. 0.1. Start & Stop button are both active and Automatic Control button is disabled. 0.2. "Availability Times" tab is displayed.
😎 "Availability Times" is displayed as seen in the Screenshot.
9) After the Successful trigger at the Scheduled time, the Channel starts.
Prerequisites: * SLD should be configured. Topics covered in this Scenario are: 1. IR development 2. ID configuration 3. Scheduling a Channel Following are steps of the Scenario. I. _Integration Repository:_ 1) Import the Software Component Version created in SLD.2) Specify the Namespace in the Software Component Version imported 3) Not Permitted option is checked for the Interface Import as we are not importing anything from R/3. 4) Create a Source Data type with the same field structure that is going to be retrieved from DB. 5) Here I have created a Target data type similar to the Source data type. 6) We create the corresponding Message types for both the Source and Target Structures. 7) Right-Click on Message type in Interface Objects to create a new Message Type MT_Source. 😎 Using F4, select DT_Source (Source Data type) in Source Message type MT_Source. 9) Similarly, create Target message type where DT_Target is included in MT_Target. 10) Now we have to create the Outbound & Inbound interfaces. 11) Right-click on the Message Interfaces to create the corresponding interfaces. 12) MI_oa_Source is a Outbound Asynchronous interface. Select the corresponding Message type MT_Source. 13) Similarly create MI_ia_Target which is a Inbound Asynchronous interface. Select MT_Target message type. 14) Create a Message mapping object MM_Source_to_Target. Select source as MT_Source and target as MT_Target. 15) Here for simplicity in mapping, we do a One-to-One mapping. 16) Interface mapping Object IM_Source_to_Target is created. 17) Select Source interface as MI_oa_Source and Target interface as MI_ia_Target. Save & Click on Read Interfaces. The corresponding Message types are displayed. 18) Select the Message mapping object MM_Source_to_Target created previously. 19) *Save* & III. *Steps to Schedule a Communication Channel:* 1) Go to Communication Channel Monitoring in Runtime Work Bench.2) Go to the corresponding Communication Channel i.e., CC_211G_JDBC_Server3) Click on "Availability Time Planning" 4) Create a Daily Schedule for the Communication Channel "CC_211G_JDBC_Server"5) Schedule at 14:00 CET for a duration of 2 hour. 0.1. Click on "Details" tab 0.2. Select the "Active" checkbox 0.3. In "Time" field , enter "14:00 CET" for 2 hours6) Click on "Communication Channels" tab Select "CC_211G_JDBC_Server" channel. Then "*SAVE*" the settings done. 7) In Communication Channel monitoring Screen "Automatic Control" should be active for the scheduler to run. Check the following to see whether Scheduler is active. 0.1. Start & Stop button are both active and Automatic Control button is disabled. 0.2. "Availability Times" tab is displayed. 😎 "Availability Times" is displayed as seen in the Screenshot.9) After the Successful trigger at the Scheduled time, the Channel starts.
6 Comments
