Scenario 2 of the of the ALE inbound sample application requires
you to use the Enterprise Service Discovery to deploy the application package,
configure the adapter, and generate the SCA artifacts.
Before you begin
Before you begin to deploy and configure:
- Import the CWYAP_SAPAdapter.RAR file into the project.
- Add the external dependencies (SAP Java™ Connector (SAP JCo) interface) to the
project.
Why and when to perform this task
For this task,
you must run the Enterprise Service Discovery within WebSphere Integration
Developer to set adapter configuration properties. To change the property
values later, use the WebSphere Process Server Administrative Console.
Steps for this task
- In the Business Integration Perspective of WebSphere® Integration Developer, right-click
the frame and from the pop-up menu, select .
- In the Import Configurations window, select IBM
WebSphere Adapter for SAP Software.
- In the Discovery Agent Initialize Properties window,
specify the configuration properties to initialize the discovery agent. Be
sure to set the Select Module field to the value of ALE. Properties marked with an asterisk (*) are mandatory.
- At the bottom of the Discovery Agent Initialize Properties window,
click the Show Advanced button.
- When prompted to specify logging options, set the Logging
Level to FINEST to provide the highest
level of logging and then click Next.
- In the Metadata Query window, click Run
Query.
- Under Objects Discovered, drill down to
the Discover By Name node, and then click the Filter button.
- In the Filter Properties for Discover by Name window,
enter DEBMAS03 (the name of the IDoc in SAP) and click OK.
- Navigate to DEBMAS03 and click the Add button.
- In the Configuration Parameters window, select
the Use SAP Field Name to generate attribute(s) check
box, and click OK to add DEBMAS03 to the list of business
objects to be imported.
- Click Next.
- In the Configure Objects window, specify the
following properties to configure objects that will be imported:
- The object location. In this example, enter BoDefs to
indicate that all business object schemas will be placed in the BoDefs directory.
- A namespace for the business object.
- Inbound for the Service Type,
- Click Add to specify the operations.
- From the list of available operations (Create, Delete,
and UpdateWithDelete), double-click Create to
add it to the list of operations.
- Click OK . This adds Create to
the list of operations in the Configure Objects window.
- In the Generate Artifacts window, specify
the module name where the artifacts should be saved, and then click New to
create a new business integration module.
- In the Generate Artifacts window, when prompted,
enter AleCustomerInbound as the module name, and click Finish.
- In the Generate Artifacts window, specify
a folder name within the module where the Service Description should be saved
and select the Deploy connector with module check box.
- Select Use discovered connection properties.
- In J2C Authentication Data Entry, enter SAP_Auth_Alias.
- Scroll down to enter values that are appropriate for your installation
in the following inbound connection properties:
- GatewayHost
- GatewayService
- RfcProgramID
- Client
- NumberOfUsers
- UserName
- Password
- Language
- ApplicationServerHost
- SystemNumber
- EDTTableName
- EDTDriverName
- EDTDatabaseName
- EDTUserName
- EDTUserPassword
- EDTSchemaName
- Click Finish.
- Using Business Object Editor, manually edit the file SapDebmas03.xsd in
the Data Types folder as follows: replace the <sapasi:MsgType/> tag
with <sapasi:MsgType>DEBMAS</sapasi:MsgType>. For details about editing business objects using the Business Object
Editor, refer to the WebSphere Integration Developer documentation.
What to do next
The business integration module project with its SCA artifacts
and corresponding business objects has been created. The next task is to generate
reference bindings for the module.