Scenario 2 of the BAPI outbound sample application requires you
to use the enterprise service discovery wizard 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 IBM 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 BAPI. 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 BAPI_CUSTOMER*, the name of the BAPI in SAP plus
an asterisk as a wild card character to indicate that you want a list of all
SAP application components that start with the phrase BAPI_CUSTOMER*.
- Click OK.
- Navigate to BAPI_CUSTOMER_CREATFROMDATA
and click the Add button.
- 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.
- Repeat steps 10 and 11 for BAPI_CUSTOMER_CHANGEFROMDATA. The selected objects appear in the bottom frame, under Objects
to be imported. Objects can be removed from the list by selecting
the object and clicking the Remove button.
- Click Next.
- In the Selection Properties window, enter BapiCustomerCreate as
the name of the business object and 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.
- Click Next.
- In the Generate Artifacts window, specify
the module name were the artifacts should be saved and then click New to
create a new business integration module.
- When prompted, enter BapiCustomer as the
module name and click OK.
- Specify ScaArtifacts as the folder name
within the module where the Service Description should be saved.
- In J2C Authentication Data Entry, enter SAP_Auth_Alias and
select the Deploy connector with module check box.
- Select the Use discovered connection properties radio
button, enter values for the connections properties, and click Finish. The new BapiCustomer module is added to the Business Integration
Perspective, along with all its artifacts.
- Export the project to the .EAR file (note that the .EAR file does
not yet exist; this step defines it):
- Right-click the BapiCustomer module and select Export.
- Select EAR file from the Export window.
- Click Next.
- In the EAR Export window, select BapiCustomerApp for
the .EAR project and specify its destination directory. Then click Finish.
- In the EAR Export window, export the EAR file
of the adapter:
- Select the EAR file in the EAR project field.
- Specify its destination directory in the Destination field.
- Click Finish.
- Deploy the .EAR file.
What to do next
The adapter application package, including all its SCA artifacts,
is now configured and deployed. You can now run the sample application.