Users may modify the metadata parameter values of an adapter service node using the adapter service editor at any time after the node is created.

When an adapter service node is opened (selected), the adapter service editor performs an adapterResourceDomainLookup call for any resource domain values that it has not already cached. This lookup interaction is shown in steps 1 and 2 of the above figure.

Resource domain values are cached in the adapter service editor based on the values of dependent parameters for the adapter service template/connection type combination (that is, for the class, not the node; thus cached values may be used across nodes that are based on the same template and connection type). Whenever the user of the adapter changes the value of a dependency parameter (a parameter upon which a resource domain lookup depends), the adapter service editor checks its cache for a set of resource domain values based on the new value. If an appropriate set of resource domain values is not found in the cache, then the adapter service editor calls the adapterResourceDomainLookup method again.

Adapter Check Values operate very much like resource domain lookups. When user of the adapter types a value into a parameter configured with an adapter check value, a call is made to the adapterCheckValue method of the corresponding connection class. If the validation succeeds, the adapter service editor caches the checked parameter value as well as the values of any dependent parameters for future use. If a parameter uses the adapter check value feature and is also a dependency parameter for the resource domain lookup of another parameter, the adapter check value validation is performed first. If the validation succeeds, the appropriate lookups are performed. For more information, see Adapter Check Value Callbacks.