Managing Engines with SQDAEMON |
Scroll |
Precisely recommends using a local Engine Controller Daemon for managing the execution of Engines. The local SQDAEMON, described in detail in the the SQDAEMON Utility Reference, provides enables a number of features including:
•The ability to display the SQDAEMON's inventory, the list of all agents managed by the local daemon and their current operating state.
•The ability to Start and Stop the Engine
•The ability to Display the detailed status of the Engine including source and target datastore record counts.
•The ability to launch other types of agents including shell and other scripts or even SQDUTIL operations that can perform any desired function such as initiating a Target table refresh.
•The ability to perform all of these activities remotely and securely.
•The local SQDAEMON performs the same NaCL Key validation procedure as the remote daemon does for Engine connection requests.
Notes:
1.The most important thing to remember when managing agents through a local SQDAEMON is that the Connect CDC SQData Version, build and Release or Diagnostic code that were in use when the SQDAEMON was launched will be used to launch any Engines or other agents Started using the daemon. Switching from Release to Diagnostic code or Version/Build will therefore require the SQDAEMON process itself to be recycled.
2.Modifications to the SQDAEMON's own configuration files, sqdagents.cfg, acl.cfg and it's nacl_auth_keys files also require the SQDAEMON to be Reloaded but not completely recycled using the SQDMON reload command.