Adapter Development Kit 9.12 | webMethods Adapter Development Kit Documentation | webMethods Adapter Development Kit Installation and User’s Documentation | Adapter Services | Metadata Model for Adapter Services | Adapter Service Node Signatures | Implementing Resource Domain Lookups for Signature Names and Data Types
 
Implementing Resource Domain Lookups for Signature Names and Data Types
You can load a signature's name and data type parameters using resource domain lookups. You implement lookups by including an adapterResourceDomainLookup method in your WmManagedConnection implementation class.
These parameters are implemented as string arrays, with the corresponding index in each array used to associate a name with a data type. The following subsections describe the values you supply in your resource domains for the name and data type parameters.
Field Name String Values
A field name string can contain a simple value, such as itemNumber, or a more complex value such as customer.orders[].lineItems[].itemNumber. The complex field name string demonstrates the ability of a signature to specify hierarchy (using a dot ".") and multiplicity (using a pair a square brackets "[]"). Thus, this example shows an aggregate of customer fields containing multiple orders that may contain multiple line items that contain one itemNumber.
Follow these rules when creating resource domain values for containing signature names:
*A name can be used as a field (containing data) or an aggregate (containing fields), but not both.
*Each entry must contain a field with any containing aggregates. Do not specify aggregates alone.
*Both fields and aggregates can be arrays, indicated by square brackets. For example: customer.orders[].lineItems[].itemNumber.
*Use name restrictions.
For more information, see the webMethods Service Development Help for your release.
Data Type String Values
A data type string must contain the data type corresponding to the field name string at the same index in the field name's resource domain list of values. Data types for the adapter services are similar to the data types for Java services. If the signature item is made accessible from an Integration Server flow, its data type must be java.lang.String, java.util.Date, or one of the "big-letter-primitive" classes (e.g., java.lang.Integer). If the data is made to not be accessible from a flow, then any class type is acceptable.
Multiplicity in the data type string uses a pair of square brackets [] appended to the class name. Data type multiplicity represents the multiplicity across the entire signature hierarchy by adding a set of brackets for each set of brackets in the corresponding name string.
Even though there is only one item number in the lineItems aggregate, there are many in the signature. In this case, the data type would be java.lang.Integer[][] if itemNumber is an integer.
For examples, see Example 1: WmAdapterService Implementation Class. For more information, webMethods Service Development Help for your release and Interacting with the Pipeline.