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
Validate your adapter implementation by unit testing it outside of a JCA container (unmanaged testing mode). You can then deploy to the target runtime server and test instances of the adapter (managed testing mode).
Unmanaged and managed testing modes are not mutually exclusive. A thorough testing regime typically involves unit testing to debug and refine adapter components before managed testing in the target environment.
- 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.- Testing the adapter in unmanaged mode
Testing in unmanaged mode means unit testing the adapter implementation in your development environment. You can unit test your adapter with JUnit, a widely used and reliable open source framework for regression testing.- Testing the adapter in managed mode
Testing the adapter in managed mode means testing adapter instances on IBM BPM. This type of testing, in contrast to testing in unmanaged mode, more closely reflects the production environment that customers encounter.- Validating code with Rational Application Developer and WebSphere Application Server
To test the adapter in the WebSphere Application Server environment, use the JavaBeans generation capability of EMD to generate records and a Java™ proxy interface to the adapter. Then generate a session bean that will call this interface, and use the WebSphere universal test client (UTC) to send data to the adapter.