| Oracle® Fusion Middleware Application Adapter for SAP R/3 User's Guide for Oracle WebLogic Server 11g Release 1 (11.1.1) E17057-01 |
|
 Previous |
 Next |
| Oracle® Fusion Middleware Application Adapter for SAP R/3 User's Guide for Oracle WebLogic Server 11g Release 1 (11.1.1) E17057-01 |
|
Previous |
Next |
This chapter contains the following examples:
The scenarios shown in this chapter require the following prerequisites.
Prerequisites
The following are installation and configuration requirements:
Oracle Application Adapter for SAP R/3 must be installed on Oracle WebLogic Server.
SAP must be configured for inbound and outbound processing. See Appendix A, "Configuring SAP R/3 for Inbound and Outbound Processing" for more information.
The examples in this chapter present the configuration steps necessary for demonstrating service and event integration with SAP. Prior to using this material, you must be familiar with the following:
How to configure Oracle Application Adapter for SAP R/3 for services and events. For more information, see Chapter 3, "Configuring Oracle Application Adapter for SAP R/3".
How to configure Oracle JDeveloper. For more information, see Chapter 5, "Integration With BPEL Service Components in the Oracle SOA Suite".
Overview of Mediator Integration
Mediator provides a comprehensive application integration framework. Oracle Application Adapter for SAP R/3 used with Mediator enables you to seamlessly integrate enterprise software, eliminating custom code. Functional modeling, as opposed to custom coding solutions, allows for software reuse and reduces the complexity and management challenges that arise over the software lifecycle. This integration model consists of two components--high-level integration logic and low-level platform services.
Adapter integration with Oracle Mediator is a two-step process:
Design Time: Oracle Application Adapter for SAP R/3 is configured in Application Explorer for services and events, as described in Chapter 3, "Configuring Oracle Application Adapter for SAP R/3". Integration logic is modeled in Mediator.
Runtime: The underlying platform treats this metadata as run-time instructions to enable the communication between participating applications.
To configure a new Application Server connection in Oracle JDeveloper:
Open Oracle JDeveloper on your system.
From the menu bar, click View and select Application Server Navigator.
The Application Server tab is displayed.
Right-click Application Servers and select New Application Server from the context menu.
The Create Application Server Connection Wizard is displayed.
Accept the default selection (Standalone Server) and click Next.
The Name and Type page is displayed.
Specify a new name for the Application Server connection and click Next.
The Authentication page is displayed.
Specify a valid user name (for example, weblogic) and a password (for example, welcome1) for your new connection.
Click Next.
The Configuration page is displayed.
Specify the Oracle WebLogic host name (for example, localhost), which is the system IP where the process must deploy and Oracle WebLogic domain (for example, base_domain).
Click Next.
The Test page is displayed.
Click Test Connection.
Make sure that the test status is successful.
Click Next.
The Finish page is displayed.
Click Finish.
The new Application Server connection is listed in the left pane (Application Server tab), as shown in the following image.
The following example describes how to configure a Mediator outbound process to your SAP system, using a Mediator project in Oracle JDeveloper.
Prerequisites
Before you design a Mediator outbound process, you must generate the respective WSDL file using Application Explorer. See "Generating WSDL for Request/Response Service" for more information.
Perform the following steps to create an empty composite for SOA:
Create a new SOA application.
Enter name for the new SOA Application and click Next.
The Name your project page is displayed.
Enter a project name (for example, sampleTest) and click Next.
The Configure SOA settings page is displayed.
From the Composite Template list, select Empty Composite and click Finish.
This section describes how to define a Mediator outbound process, which consists of the following stages:
Configuring a Third Party Adapter Service Component
Configuring an Outbound Mediator Process Component
Configuring the Routing Rules
Configuring a Third Party Adapter Service Component
Perform the following steps to create a third party adapter service component:
Drag and drop the Third Party Adapter component from the Service Adapters pane to the External References pane.
The Create Third Party Adapter Service dialog is displayed.
Enter a name for the third party adapter service.
Ensure that Reference is selected from the Type drop-down list (default).
Click the Find existing WSDLs icon, which is located to the right of the WSDL URL field.
The SOA Resource Browser dialog is displayed.
Browse and select an outbound WSDL file from the following directory:
C:\oracle\Middleware\home_GA\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\wsdls
Click OK.
The Localize Files dialog is displayed.
Click OK.
The outbound WSDL file and associated request and response XML schema files (.xsd) are imported to the project folder that has been created.
You are returned to the Create Third Party Adapter Service dialog.
Click the Find JCA file icon, which is located to the right of the JCA File field.
The SOA Resource Browser dialog is displayed.
Browse and select the JCA properties file from the following directory:
C:\oracle\Middleware\home_GA\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\wsdls
Click OK.
The following message is displayed.
Click Yes.
A copy of the JCA properties file is made in the project folder.
You are returned to the Create Third Party Adapter Service dialog.
Click OK.
The third party adapter service component (GetDetail) is created in the External References pane, as shown in the following image.
You are now ready to configure an outbound Mediator process component.
Configuring an Outbound Mediator Process Component
Perform the following steps to configure an outbound Mediator process component:
Drag and drop the Mediator Process component from the Service Components pane to the Components pane.
The Create Mediator dialog is displayed.
In the Name field, enter a name to identify the new outbound Mediator process component (for example, CompanyCode_GetDetail).
From the Template drop-down list, select Synchronous Interface.
Click the Browse icon, which is located to the right of the Input field to select the associated XML request schema file.
The Type Chooser dialog is displayed.
Expand Project WSDL Files, CC_GetDetail_invoke_Nov18.wsdl, Inline Schemas, and select CompanyCode.GetDetail.
Click OK.
You are returned to the Create Mediator dialog.
Click the Browse icon, which is located to the right of the Output field to select the associated XML response schema file.
The Type Chooser dialog is displayed.
Expand Project WSDL Files, CC_GetDetail_invoke_Nov18.wsdl, Inline Schemas, schema, and select CompanyCode.GetDetailResponse.
Click OK.
You are returned to the Create Mediator dialog.
Click OK.
Create a connection between the outbound Mediator process component (CompanyCode_ GetDetail) and the third party adapter service component (GetDetail).
You are now ready to configure the routing rules.
Configuring the Routing Rules
Perform the following steps to configure routing rules for the Mediator outbound process component:
Double-click the outbound Mediator process component (CompanyCode_ GetDetail) in the Components pane.
The Routing Rules dialog is displayed.
In the <<Filter Expression>> area, click the icon to the right of the Transform Using field.
The Request Transformation Map dialog is displayed.
Select the Create New Mapper File option and click OK.
The following mapping page is displayed.
Map the iWayRequest:CompanyCode.GetDetail source element to the iWayRequest:CompanyCode.GetDetail target element.
The Auto Map Preferences dialog is displayed.
Retain the default values and click OK.
You are returned to the Routing Rules dialog.
In the Synchronous Reply area, click the icon to the right of the Transform Using field.
The Reply Transformation Map dialog is displayed.
Select the Create New Mapper File option and click OK.
The following mapping page is displayed.
Map the iWayResponse:CompanyCode.GetDetail.Response source element to the iWayResponse:CompanyCode.GetDetail.Response target element.
The Auto Map Preferences dialog is displayed.
Retain the default values and click OK.
The mapping is complete, as shown in the following image.
Click the Save All icon in the menu bar to save the new outbound Mediator process component that was configured.
You are now ready to deploy the Mediator outbound process.
Perform the following steps to deploy the Mediator outbound process.
Right-click the project name in the left pane (for example, sampleTest), select Deploy from the context menu, and click sampleTest.
The Deployment Action page is displayed.
Ensure that Deploy to Application Server is selected.
Click Next.
The Deploy Configuration page is displayed.
Leave the default values selected and click Next.
The Select Server page is displayed.
Select an available application server that was configured and click Next.
The SOA Servers page is displayed.
Select a target SOA server and click Next.
The Summary page is displayed.
Review and verify all the available deployment information for your project and click Finish.
The process is deployed successfully.
If an Authorization Request dialog is displayed during the deployment process, provide the required user name and password and click OK.
Perform the following steps to invoke the input XML document in the Oracle Enterprise Manager console.
Logon to the Oracle Enterprise Manager console.
Expand your domain in the left pane followed by the SOA folder.
Select an available project in the left pane.
Click Test.
Click the Request tab.
Provide an appropriate input value in the Input Arguments area and click Test Web Service.
The output response is received in the Oracle Enterprise Manager console, as shown in the following image.
The following example describes how to configure a Mediator inbound process to your SAP system, using a Mediator project in Oracle JDeveloper.
Prerequisites
Before you design a Mediator inbound process, you must generate the respective WSDL file using Application Explorer. See "Generating WSDL for Event Integration" for more information.
Perform the following steps to create an empty composite for SOA:
Create a new SOA application.
Enter name for the new SOA Application and click Next.
The Name your project page is displayed.
Enter a project name and click Next.
The Configure SOA settings page is displayed.
From the Composite Template list, select Empty Composite and click Finish.
This section describes how to define a Mediator inbound process, which consists of the following stages:
Configuring a Third Party Adapter Service Component
Configuring an Inbound Mediator Process Component With a File Adapter
Configuring the Routing Rules
Configuring a Third Party Adapter Service Component
Perform the following steps to create a third party adapter service component:
Drag and drop the Third Party Adapter component from the Service Adapters pane to the Exposed Services pane.
The Create Third Party Adapter Service dialog is displayed.
Enter a name for the third party adapter service (for example, CC_GetDetail_Mediator_IB).
Ensure that Service is selected from the Type drop-down list (default).
Click the Find existing WSDLs icon, which is located to the right of the WSDL URL field.
The SOA Resource Browser dialog is displayed.
Browse and select an inbound WSDL file from the following directory:
C:\oracle\Middleware\home_GA\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\wsdls
Click OK.
The Localize Files dialog is displayed.
Click OK.
The inbound WSDL file and associated receive/request schema file (.xsd) are imported to the project folder that has been created.
You are returned to the Create Third Party Adapter Service dialog.
Click the Find JCA file icon, which is located to the right of the JCA File field.
The SOA Resource Browser dialog is displayed.
Browse and select the JCA properties file from the following directory:
C:\oracle\Middleware\home_GA\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\wsdls
Click OK.
The following message is displayed.
Click Yes.
A copy of the JCA properties file is made in the project folder.
You are returned to the Create Third Party Adapter Service dialog.
Click OK.
The third party adapter service component (CC_GetDetail_Mediator_IB) is created in the Exposed Services pane, as shown in the following image.
You are now ready to configure an inbound Mediator process component.
Configuring an Inbound Mediator Process Component With a File Adapter
Perform the following steps to configure an inbound Mediator process component with a File adapter.
Drag and drop the Mediator Process component from the Service Components pane to the Components pane.
The Create Mediator dialog is displayed.
In the Name field, enter a name to identify the new inbound Mediator process component (for example, CC_GetDetail_Mediator_IB).
From the Template drop-down list, select Define Interface Later.
Click the OK.
The new Mediator process component is added to the Components pane, as shown in the following image.
Drag and drop the File Adapter component from the Service Adapters pane to the External References pane.
The Adapter Configuration Wizard is displayed, showing the Service Name page.
Type a name for the new File adapter in the Service Name field and click Next.
The Adapter Interface page is displayed.
Ensure that the Define from operation and schema (specified later) option is selected.
Click Next.
The Operation page is displayed.
Select Write File from the list of Operation Type options and specify an Operation Name (for example, Write).
Click Next.
The File Configuration page is displayed.
Specify a location on your file system where the output file is written.
In the File Naming Convention field, specify a name for the output file.
Click Next.
The Messages page is displayed.
Click Browse, which is located to the right of the URL field.
The Type Chooser dialog is displayed.
Expand Project WSDL Files, BAPI_COMPANYCODE_GETDETAIL_receive.wsdl, Inline Schemas, and schema.
Select the available schema (for example, BAPI.CompanyCode.GetDetail)
Click OK.
You are returned to the Messages page.
Click Next.
The Finish page is displayed.
Click Finish.
Create a connection between the inbound Mediator process component and the third party adapter service component.
Create a connection between the inbound Mediator process component and the File adapter component.
You are now ready to configure the routing rules.
Configuring the Routing Rules
Perform the following steps to configure routing rules for the Mediator inbound process component:
Double-click the inbound Mediator process component in the Components page.
The Routing Rules dialog is displayed.
In the <<Filter Expression>> area, click the icon to the right of the Transform Using field.
The Request Transformation Map dialog is displayed.
Select the Create New Mapper File option and click OK.
The following mapping page is displayed.
Map the iWayEvent:BAPI_COMPANYCODE_GETDETAIL source element to the iWayEvent:BAPI_COMPANYCODE_GETDETAIL target element.
The Auto Map Preferences dialog is displayed.
Retain the default values and click OK.
You are returned to the Routing Rules dialog. The mapping is now complete.
Click the Save All icon in the menu bar to save the new inbound Mediator process component that was configured.
You are now ready to deploy the Mediator inbound process. You can follow the same procedure in "Deploying the BPEL Inbound Process".
Once event messages are triggered through SAP GUI, output XML is received in the location that was specified for the File adapter component. For more information on triggering events in SAP R/3, see "Triggering an Event in SAP R/3".
|
 Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|