AMQP Integration Toolkit (AIT)
How does one make use of existing code, written in any language, from client code running on multiple platforms, written in different languages, preferably employing standards-based software wherever possible; and achieve isolation of the client code from the server code; and obtain scalability and reliability without modifying existing server or client code; and all of the above with little to no modification to the existing code and without writing excessive new code or interface definitions?
- Tried and proven routines
- HP WSIT "Object to XML" to expose the interfaces in the tried and proven routines
- AMQP Server (an integral part of the AIT)
- Some client code
- Compile the tried and proven routines
- Generate the interface definitions from the tried and proven routines using the HP WSIT obj2idl utility
- Generate an HP WSIT JavaBean and the stub for the C server. The C stub has the names of the tried and proven routines
- Build the OpenVMS shareable image with the C stub and the tried and proven routines. These will be loaded by the AMQP Server at run-time
- Build the generated client JavaBean using the generated build procedure
Note: a future version of the document and software will explain and
contain similar instructions for logic encapsulated by HP ACMS Tasks.
- Execute the generated procedure to run the server
- Compile the generated Java client
- Run the Java client
Run-time configuration of the AIT
Disclaimer: the information in this document is the sole responsibility of the
authors. The information contained herein is offered on a best-effort
basis. The authors and their respective employers offer no support or warranty on any of the content in this
document or the software described in it.