Saturday, February 06, 2016

Fusion Middleware 12c Inbound - SAP Integration using SAP Adapter

Inbound to Fusion Middleware 12c from SAP

Before we Start to Design and Deploy, We need to Configure SAP JCo library at Jdevloper and at Server level.
For the Steps of Download and configuration, Refer my Previous Blog post at :

Fusion Middleware 12c – SAP Adapter Configuration

http://soa11g-12c.blogspot.in/2016/02/fusion-middleware-12c-sap-adapter.html



Once you have completed these steps, Now we can move forward with Developement and Deployment.

Now Using JDevloper 12c IDE, we will create an Inbound integration service. This integration can either be a SOA project or OSB project. For demonstration, we are taking an OSB Project.

 Design Time

The steps to create Service Bus Inbound integration service are :
a. Open JDevloper 12c (SOA Extensions should have been installed.)
b. Since we have already created a Service Bus Application, same can be used.
c. Create a Service Bus Project
d. Drag & Drop SAP adapter from Components palette to Proxy Services Pane, shown Below in image


e. Adapter configuration screen will appear, Enter the Name of the Adapter, Click Next



f. In this step, Enter JNDI Name then Click on the ‘+’ button to add a new SAP Connection, This will Open new Connection window



g. Provide the below required details for connection. These details are given by SAP system
UserName , Password, Client, Language, Application Server, System Number, Gateway Host, Gateway Service, Program ID and Connection Count





h. Click on the Test Connection. If all the provided details are correct, Connection should be successful.



i. Once connection is successful, click on OK button to close connection wizard, then on Next button. The below screen will be shown



j. Expand ‘ALE/EDI’ section and select the IDOC, which you want to use for integration, Then click on Next button.



k. Next is the JCA summary Screen, Click on Next Button.



l. Next is Finish Screen, Click on the Finish Button. The adapter wizard will create one xsd, two wsdl, one jca and one Proxy Service file. As shown below



m. Save all Changes. This integration can not be deployed at this point, because while deploying, it will look for the SAP Adapter JNDI, which we have given at previous Step f. Hence to deploy and run the integration, we need to complete below run time configurations.



Continue with the further steps of configuration in my Next post at:

Fusion Middleware 12c Inbound - SAP Integration using SAP Adapter - Part 2

http://osb-dheeraj.blogspot.in/2016/02/fusion-middleware-12c-inbound-sap_17.html

No comments:

Post a Comment