Compiling and running the TwineBall JNI implementation
We use Make to build the shared library. Ensure you have a complete
build environment for the target platform. Each platform's makefile
contains the information about which compiler it is built for. If that
compiler and Make are installed, all you should have to do to compile the
library is to extract the files onto the target platform and type make
-f Makefile.Platform where Platform is the
desired target platform.
To run the TwineBall adapter with the JNI bridge:
- Install either WebSphere InterChange Server or the WebSphere Business
Integration Adapter Framework on the target platform.
- Put the compiled classes for the TwineBall server and the adapter in the
ProductDir/connectors/twineball directory.
- Put the message file from "dependencies" in the "messages"
folder.
- Put the shared library and the start_twineball.sh script
in the ProductDir/connectors/twineball directory.
You will not need to set up the TwineBall database or server because in this
example, the adapter will call the JNI bridge instead.
- Configure the adapter, using twineball.cfg as a template, and use
the special string JNIStub as the server URL.
- Start the adapter normally using its start script.
The JNI backend for the adapter implements both service call and event
delivery for "TwineBallCustomer" business objects. You will
find the TwineBallCustomer business object in the "sample business
objects" folder.
