The Client Commands section serves to create, test, distribute, manage and monitor Client Commands. Client Commands are modular scripts which can be run on the console or on a client. |
||
By the time it runs on the console/client, a Client Command has undergone four phases. Each phase is listed as a separate sub-item in the navigation. With the matching buttons, a Client Command can be transferred from one phase to the next or returned to an earlier one.
In the phase Creation Client Commands can be created, edited, versioned and managed. Furthermore, the scripts of a Client Command and its version history can be viewed as well.
In the phase Testing Client Commands can be tested on selected clients. In doing so, the test clients must be directly connected to the ACMP server.
In the phase Synchronization any additional files of a Client Command are distributed across the various file repositories (see Distributed File Repositories).
In the phase Release any additional files of a Client Command are distributed across all file repositories (or at least part thereof) The Client Command can now be released for use and is then available to the clients.
In addition there is the item Run. A log file can here be viewed for each execution of a Client Command. This makes it possible to analyze any problems which have occurred.
Since Client Commands have to be adjusted every now and then, they can be versioned. This means that there may be different versions of a Client Command. This means that a new version of a currently used Client Command (4th phase) can be created. This new version now has to run again through the first three phases. Only with the 4th phase the new version replaces the old version.
Note: |
Different rights can be assigned for working with Client Commands. |
In the phase Execute all Client Commands which are ready for execution are shown. You will also receive information about previously executed Client Commands.
Last change on 10.12.2014