Specifying Adapter Service Signature Data
After you have implemented the configuration logic for the adapter service template, you implement logic that defines the run-time signature of a configured adapter service node. To begin doing this, you create the following additional metadata parameters:
sigIn and sigOut
These parameters are for use with the reserved signature resource domains.
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 on lines 84-87 of
Code Example 1: WmAdapterService
Implementation Class. The mechanics of signature construction was discussed in
Adapter Service Node Signatures.
These parameters will not accept adapter user input; from the adapter user's perspective, they are largely redundant with information provided elsewhere in the Adapter Service Editor. In most implementations, they would be included in the same group with the configuration parameters, but would be hidden from the adapter user. 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.