Specifying Adapter Service Signature Data
After implementing the configuration logic for the adapter service template, implement the logic that defines the runtime signature of a configured adapter service node. To do so, create the following additional metadata parameters:
sigIn and
sigOut.
The reserved signature resource domains uses these parameters.
fieldNames and
fieldTypes These parameters are the dependency parameters in which you build the signature data. Because the example update service has the same input and output signature, only one set of name and type parameters is necessary. The relationship between these parameters is established in the
WmTemplateDescriptor. The mechanics of signature construction is discussed in
Adapter Service Node Signatures.
These parameters do not accept input from the users of the adapter; from the user's perspective, they are largely redundant with information provided elsewhere in the adapter service editor. In most implementations, these parameters are included in the same group with the configuration parameters, but are hidden from the users of the adapter. For demonstration purposes, these parameters remain visible in the example, but they are located in a separate group. Except for that, the metadata constructs for these parameters follow the same basic rules for specifying a signature for any service.