Configuring the service for an outbound ALE IDoc wrapper

The configuration process described in the following steps configures the adapter and creates business objects for an outbound ALE IDoc wrapper.

Why and when to perform this task

For information about configuring other business objects, refer to the appropriate service configuration topics.

Steps for this task

  1. Switch to the Business Integration perspective in WebSphere Integration Developer.
  2. Right-click the frame of the Business Integration perspective window and select New > Enterprise Service Discovery from the pop-up menu. If Enterprise Service Discovery is not visible, select Other from the bottom of the pop-up menu. Then, in the window that appears, expand the Business Integration folder and select Enterprise Service Discovery and click Next.
  3. When prompted to select an adapter to use for discovering the service, select IBM WebSphere Adapter for SAP Software. You make this selection in the Import Configurations window.
  4. When prompted to specify properties in the Configure Settings for Discovery Agent window, specify the adapter configuration properties for connecting to SAP. Be sure to set the Select Module field (under Metadata Properties) to the value of BAPI. Properties marked with an asterisk (*) are mandatory.
  5. At the bottom of the window, click the Show Advanced button.
  6. When prompted to specify logging options, specify a log file location and set the Logging Level to FINEST to provide the highest level of logging.
  7. Click Next.
  8. In the Find and Discover Enterprise Services window, click Run Query.
  9. Under Objects Discovered by query, drill down to the Discover By Name node, and then click the Filter button.
  10. In the Filter Properties for Discover by Name window, enter BAPI_CUSTOMER*, which is the name of the BAPI in SAP plus an asterisk as a wildcard character to indicate that you want to discover all SAP application components that start with BAPI_CUSTOMER.
  11. Click OK.
  12. Navigate to BAPI_CUSTOMER_CREATFROMDATA and click the Add button.
  13. In the Configuration Parameters window, select the Use Field Name to generate attribute(s) check box, and click OK to add BAPI_CUSTOMER_CREATFROMDATA to the list of business objects to be imported.
  14. Repeat step 11 and step 12 for the following objects and then click Next:
    • BAPI_CUSTOMER_CHANGEFROMDATA
    • BAPI_CUSTOMER_DELETE
    • BAPI_CUSTOMER_GETDETAIL
    The selected objects appear in the bottom window frame.
  15. If you want to remove an object from the list, select the object name and click Remove.
  16. Click Next to proceed.
  17. In the Configure Objects window, enter BODEFS for the object location and BapiCustomerCreate for the name of the business object.This image is described in the surrounding text.
  18. Specify the appropriate JCo methods for each of the object’s operations. For example, specify the following methods:
    • For the CREATE operation, specify BAPI_CUSTOMER_CREATEFROMDATA.
    • For the UPDATEWITHDELETE operation, specify BAPI_CUSTOMER_CHANGEFROMDATA.
    • For the RETRIEVE operation, specify BAPI_CUSTOMER_GETDETAIL.
    • For the DELETE operation, specify BAPI_CUSTOMER_DELETE.
  19. Click Next.
  20. In the Generate Artifacts window, specify BapiCustomer for the module name where the SCA artifacts (business objects, their properties, import file, export file, and WSDL) should be saved, and then click New to create a new business integration module.This image is described in the surrounding
text.
  21. In the Generate Artifacts window, specify the folder within the module where the service description should be saved.
  22. In the J2C Authentication Data Entry field, enter Sca_Auth_Alias and select the Deploy connector with module check box.
  23. Click the Use discovered connection properties radio button.This image is described in the surrounding
text.
  24. Specify the connection properties and then click Finish. Properties marked with an asterisk (*) are required.

Result

The new BapiCustomer module is added to the Business Integration perspective, along with all its artifacts.

What to do next

After you configure the service, the next step is to generate reference bindings. The purpose of reference bindings is to link the adapter to other server processes.

Parent topic: Configuring the service

Related concepts
Learning about business objects for the ALE interface

Related tasks
Generating reference bindings


Copyright IBM Corp. 2003, 2005