Implementing Metadata Parameters Using External Classes
A basic model specifying all adapter metadata parameters is described in
Metadata Model for Connection.
Integration Server derives a parameter's name and data type from the name of the accessor methods defined in the class in which the parameter is defined.
If a class contains a conforming accessor method that uses an object data type not existing in the listed data types, the adapter interprets that object as being an external container for the metadata parameters. For more information about the data types supported, see
paramType parameter in
Overview.
In this example, the WmAdapterService class contains an accessor method:
SetParameters(MyServiceParameters value);
Integration Server considers
MyServiceParameters, an external class that contains accessor methods.
Integration Server introspects the
MyServiceParameters class, and derives metadata parameter names from it.
Note:
MyServiceParameters must support a default (no argument) constructor.
This feature changes the name of the parameter string used in the descriptor methods as well as the resource bundle by prefixing it with the name derived from the method that implements the indirection.
If MyServiceParameters class includes a setFoo(String value) method, then
The string that referenced this parameter is
parameters.foo.
The
parameters value is derived from
setParameters method.
The
foo value is derived from
setFoo method.