Configuring the service for a BAPI transaction

The configuration process described in the following steps configures the adapter and creates business objects for a BAPI transaction.

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 and click Next. If you have previously run the enterprise service discovery wizard, your connection properties have been saved and appear when you expand the adapter name node by clicking the plus symbol (+) next to the adapter name. You can select the saved connection properties if you plan to connect to the same SAP application as when you last ran the enterprise service discovery wizard,
  4. When prompted to specify properties in the Configure Settings for Discovery Agent window, specify the adapter configuration properties for connecting to SAP. Properties marked with an asterisk (*) are mandatory. Note that when you first created the project, if you imported a RAR file that supports transactions, the Select Module property (under Metadata Properties) is set to a value of BAPI and cannot be changed. Otherwise, set the value of this property to BAPI.
  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. In a test environment, choose FINEST, which provides the highest level of logging. In a production environment, choose a level lower than FINEST, so as to optimize the logging process.
  7. Click Next.
  8. In the Find and Discover Enterprise Services window, click Run Query. The objects discovered by the query are grouped into two BAPI categories: RFC and BOR.
    This image is described in the surrounding text.

    BAPI categories

  9. Under Objects Discovered by query, select RFC or BOR, drill down to the Discover By Name node, and click the Filter button. Or, you can drill down to Discover By Description.
  10. In the Filter Properties for Discover by Name window, enter the name of the BAPI you want to add to your transaction, plus an asterisk as a wild card character to indicate that you want to discover all SAP application components that start with BAPI_SALESORDER. For example, enter BAPI_SALESORDER*
  11. Click OK.
  12. Select the BAPIs to add to the transaction. For example, select BAPI_SALESORDER_CREATE and BAPI_SALESORDER_CHANGE.
  13. Repeat step 12 for the remaining BAPIs you want to add to your transaction, and then click Next.
  14. In the Configuration Parameters window, do the following to add the selected BAPIs to the list of business objects to be imported:
    1. Select the Use Field Name to generate attribute(s) check box.
    2. Select the Check if you want to select optional parameters for this interface check box and then select the optional parameters you want included in your business object definition. By default, enterprise service discovery generates the mandatory parameters for the selected BAPI interface, so select this check box to also include the optional parameters.
    3. Click OK.
    The selected objects appear in the bottom window frame.
    This image is described in the surrounding text.

    Selected BAPI objects

  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:
    This image is described in the surrounding text.
    1. Enter the directory name, for example BODEFS, for the object location. This specifies a directory that is relative to the project’s directory in the WebSphere Integration Developer workspace.
    2. Specify the name space.
    3. Enter the name of the business object.
    4. Select the Check this for creating BAPI transaction object check box.
  18. Click Add.
  19. Perform the following steps to specify the sequence of BAPIs in the transaction object:
    1. Select a BAPI.
    2. Click Add.
    3. Select COMMIT as needed for the transaction.
    4. Repeat these steps for each BAPI you want to include in the transaction. The list of BAPIs you create must be in the sequence in which they are to be performed within the transaction.

    This image is described in the surrounding text.

    Configure objects window

  20. Click Next.
  21. In the Generate Artifacts window, click New to create a new business integration module and then specify the module name (for example, BapiSalesOrder) where the SCA artifacts (business objects, their properties, import file, export file, and WSDL) should be saved.
    This image is described in the surrounding text.

    Generate Artifacts window

  22. In the Generate Artifacts window, specify the folder within the module where the service description should be saved.
  23. In the J2C Authentication Data Entry field, enter SAP_Auth_Alias and select the Deploy connector with module check box.
  24. In the Generate Artifacts window, click the Use discovered connection properties radio button to set properties at this time. (The Use connection properties specified on server button lets you configure properties later, using the WebSphere Process Server administrative console).
    This image is described in the surrounding text.

    Generate Artifacts window

  25. 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.
Related concepts
Learning about business objects for the BAPI interface
Related tasks
Generating reference bindings
Enabling logging

Terms of use |

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

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