IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

How the Invoker works

BTT invoker provides an XML-based invocation framework.

The following diagram shows the BTT invoker working mechanism:

Invoker mechanism

InvokerFactory is an instance factory, which have a lot of instances and copies in memory. Each InvokerFactory represents one XML definition. You can query Invoker Instance from factory by the ID defined in the XML.

An invoker instance is created by an InvokerFactory.createInvoker(String) method. The invoker instance has all the parameters, structures and necessary properties inside it’s’ instance.

You can define default parameter values inside the definitions or you can specify it at runtime. For POJO, EJB and WS invokers, these parameters might be the real parameter of the method; for user extended invoker or asynchronized invoker, these parameters might be some useful informations .

The typical invocation step is as follows:
  1. Get invoker instance from InvokerFactory using invokerId
  2. Construct an object array as the invoker parameter. You can build an object array directly or you can use the invoker utility class to construct the object array.
  3. Call the invoker.execute method to invoke an invoker. The object array is input as parameter.
The invoker has the following enhancements:
BTT Invoker has the following features:
  1. Speeds up development:
    1. You do not need to write invocation for each request.
    2. You are not required to learn the technologies to invoke other services.
    3. You can only change the definition's type if you want to test different targets.
    4. No centralized management is required.
  2. Speeds up deployment: You can change the invoker to different target only by changing the XML definition.


Feedback