The configuration process described in the following steps configures
the adapter and creates business objects for different BAPI calls that are
associated with a customer.
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
- Switch to the Business Integration perspective in WebSphere® Integration
Developer.
- Right-click the frame of the Business Integration perspective
window and select 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.
- 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 will 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.
- When prompted to specify properties in the Configure
Settings for Discovery Agent window, specify the connection configuration
properties for connecting to SAP. Be sure to set the Select
Module property (under Metadata Properties)
to the value of BAPI. Properties marked with an asterisk
(*) are mandatory.

Specifying
properties
- At the bottom of the window, click the Show Advanced button.
- 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.
- Click Next.
- 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.

BAPI categories
- 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.
- 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 wild card character to indicate that you want
to discover all SAP application components that start with BAPI_CUSTOMER.
- Click OK.
- Select the following BAPIs:
- BAPI_CUSTOMERCRM_CREATE
- BAPI_CUSTOMERCRM_CHANGE
- BAPI_CUSTOMERCRM_DELETE
- BAPI_CUSTOMER_GETLIST
- In the Configuration
Parameters window, do the following to add the selected BAPIs to
the list of business objects to be imported:
- Select the Use Field Name to generate attribute(s) check
box.
- 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.
- Click OK.
The selected objects appear in the bottom window frame.

Business objects to be imported
- Repeat step 12 and step 13 for the following objects
and then click Next:
- BAPI_CUSTOMERCRM_CREATE
- BAPI_CUSTOMERCRM_CHANGE
- BAPI_CUSTOMERCRM_DELETE
- BAPI_CUSTOMER_GETLIST
The selected objects appear in the bottom window frame.
- If you want to remove an object from the list, select the object
name and click Remove.
- After you have added all the objects to be discovered, click Next to
proceed.
- In the Configure Objects window:
- 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.
- Specify the name space.
- Enter the name of the business object. For example, BapiCustomer.
- Do not select the Check this for creating
BAPI transaction object check box.

Configure
Objects window for multiple BAPI selection
If in Step
12 you selected a single BAPI, for example BAPI_CUSTOMERCRM_CREATE,
then instead of the previous screen, the following screen appears. Use the
following screen to specify the object location and business object name and
click Add to add the operation(s) you want to associate
to the single BAPI.

Configure Objects window for single BAPI selection
- Specify the appropriate JCo methods for each of the object’s operations. For example, specify the following methods:
- For the CREATE operation, specify BAPI_CUSTOMERCRM_CREATE.
- For the UPDATEWITHDELETE operation, specify BAPI_CUSTOMERCRM_CHANGE.
- For the RETRIEVE operation, specify BAPI_CUSTOMER_GETLIST.
- For the DELETE operation, specify BAPI_CUSTOMERCRM_DELETE.
- Click Next.
- In the Generate Artifacts window, click New to
create a new business integration module and then specify BapiCustomer for
the module name where the SCA artifacts (business objects, their properties,
import file, export file, and WSDL) should be saved.

Generate Artifacts window
- In the Generate Artifacts window, specify
the folder within the module where the service description should be saved.
- In the J2C Authentication Data Entry field,
enter SAP_Auth_Alias and select the Deploy
connector with module check box.
- 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).

Specifying properties
- 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.