Client Adapter Lifecycle
Being Streams module, client adapters and other provcautil modules are described in the Fulfillment Provisioning flow and instantiated when the matching flow is loaded.
provadmin help streams
A client adapter instance is not enabled and ready to work until you invoke the unlock()and enable() operations on that instance. You should not invoke these operations on the client adapter instance until after the rest of the stream is instantiated, linked, and ready.
Locking/Unlocking: A locked client adapter instance refuses to process new requests and suspends current request processing.
Enabling/Disabling: Enabling and disabling refer to a connection with a northbound interface (a disabled TCP driver should be disconnected, a directory scanner should stop scanning. A disabled driver refuses to process new requests).
It is generally a good idea to perform client adapter operations in the following order:
To perform these administration operations, a plugin for the provadmin command line interface called ca is provided.
To get a complete list of commands accepted by the ca plugin, type the following on the command line:
provadmin help ca
As long as they do not encounter a fatal error, client adapters must stay enabled. Modules must use the event dictionary to log events at the warning severity for all non-fatal errors.