Entering Names and Folders for Adapter Service Nodes
The other significant adapter interaction that occurs when creating adapter service nodes occurs after the user of the adapter has entered the name and folder of the new adapter service node.
The following figure describes the parameter interrogation during the creation of an adapter service node:
Before displaying the adapter service editor screens:
Integration Server invokes the connection's
adapterResourceDomainLookup method for each lookup registered with the service.
The values argument in these lookups reflect the dependent parameters' default values that are cached when the user of the adapter selects a connection node. If your default value for a dependent parameter is null, make sure your resource domain lookup code can handle a null value in the values argument.
After the lookups are complete,
Integration Server instantiates the adapter service template class (again), and each of the accessor methods are called.
Values passed to "set" methods come either from the parameter default, or from the result of a resource domain lookup. These accessor method calls merely validate their operation; the service class instance is not cached. This is the last interaction with the metadata parameter accessor methods during the process of creating an adapter service node. The "set" methods are not called with the final node settings until the service is executed.