Back End of an Adapter
The back end of an adapter represents a
Domain Manager
. Object manipulations (for example, setting an attribute) within an ASL rule set are translated into Remote API requests. TheDomain Manager
to which the API transmits the request is determined by the back end. Two back ends are available:- RemoteDomain Manager—Specifies a remoteDomain Manager.
- Restart-enabledDomain Manager— Specifies a remoteDomain Manager, but the adapter handles automatic reconnects if the connection to theDomain Manageris broken.The --server option to the sm_adapter command creates a remoteDomain Managerback end.% sm_adapter --server=myServer rules.aslThe restart-enabledDomain Managerback end is a specialization of the remoteDomain Managerthat adds automatic reconnect capabilities. When using a normal remote Domain Manager back end, the adapter terminates if one of the following occurs:
- Domain Manageris unavailable when the adapter starts.
- Domain Managerdisconnects while the adapater is running.The restart-enabledDomain Managershould be used in cases where you want the adapter to remain active when theDomain Manageris unavailable. The back end of a restart-enabledDomain Managerperiodically attempts to reconnect to theDomain Manager. Once it succeeds, the connection is restored and the adapter continues to function.The restart-enabled back end is most useful in conjunction with the subscriber front end. The section “Subscriber front end with a restartable Domain Manager” on page 134 provides additional information about using the restart-enabledDomain Managerwith the subscriber front end.