IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Adapter Toolkit > Validating the code

Testing Enterprise Metadata Discovery for an adapter

Testing the EMD implementation means testing if the adapter can connect to EIS and discover services from an existing metadata repository or is able to build the appropriate interactions with the EIS by generating the required artifacts.

To test the enterprise metadata discovery (EMD) implementation for the developed resource adapter, copy the following three dependent JAR files into the connectorModule connector project from the IBM WebSphere Adapters Foundation Classes library.

• commonj.connector.jar
• CWYBS_AdapterFoundation.jar
• DESPI.jar

Procedure

1. Right-click connectorModule > import > File System and browse <WID>\eclipse\plugins\com.ibm.j2ca.wat.afc_7.5.0\runtime and select the required JAR files and click Finish.

   

   Displaying the dependent JAR import

2. Right-click on connector project (for example: HelloWorld) > properties > Java™ Build Path add the three JAR files to the build path by clicking Add JARs in the Libraries tab and click OK.

   

   Displaying the dependent JAR selection

3. On importing the dependent JAR files, the files are added to the connector project as below:

   

   Displaying the dependent JAR files

4. In theIBM Integration Designer window, click Go to the Business Integration perspective.
5. Right-click inside the Business Integration section of theIBM Integration Designer window.
6. Type in a new Module Name in the New Module window. Click Finish.
7. Open the external service by clicking the File > New > External Service.

8. In the External service window, expand Adapters and select Unlisted Adapters and click Next. Select the adapter name entered in the ra.xml file.

   You can enter the adapter name in the ra.xml file using the Resource Adapter Deployment Descriptor editor.

9. Click through Next to open the last External service window. Click Browse and select the module created in Step 4 to generate the required artifacts.

   If you do not add the dependency JAR files to the connectorModule, the following error might display during the deployment: java.lang.NoClassDefFoundError: com.ibm.j2ca.base.WBIResourceAdapter

Validating the code