Deploying and configuring for Scenario 2 (ALE inbound)

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:

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

  1. In the Business Integration Perspective of WebSphere® Integration Developer, right-click the frame and from the pop-up menu, select New > Enterprise Service Discovery.
  2. In the Import Configurations window, select IBM WebSphere Adapter for SAP Software.
  3. 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.
  4. At the bottom of the Discovery Agent Initialize Properties window, click the Show Advanced button.
  5. When prompted to specify logging options, set the Logging Level to FINEST to provide the highest level of logging and then click Next.
  6. In the Metadata Query window, click Run Query.
  7. Under Objects Discovered, drill down to the Discover By Name node, and then click the Filter button.
  8. In the Filter Properties for Discover by Name window, enter DEBMAS03 (the name of the IDoc in SAP) and click OK.
  9. Navigate to DEBMAS03 and click the Add button.
  10. 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.
  11. Click Next.
  12. 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,
  13. Click Add to specify the operations.
  14. From the list of available operations (Create, Delete, and UpdateWithDelete), double-click Create to add it to the list of operations.
  15. Click OK . This adds Create to the list of operations in the Configure Objects window.
  16. 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.
  17. In the Generate Artifacts window, when prompted, enter AleCustomerInbound as the module name, and click Finish.
  18. 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.
  19. Select Use discovered connection properties.
  20. In J2C Authentication Data Entry, enter SAP_Auth_Alias.
  21. 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
  22. Click Finish.
  23. 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.

Related tasks
Configuring properties
Adding external dependencies
Related reference
Configuration properties of WebSphere Adapter for SAP Software

Terms of use |

Last updated: Sun Mar 12 11:15:18 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)