MC-CLI recording refers to the recording of Management Console actions. The recordings are saved in the form of MC-CLI functions. In this way, it is possible to record configuration and management jobs. You can adapt the recorded configuration steps for other proxies or lower-level objects and then perform the configuration of these objects in Jython scripts. The recordings can also simply be used to log the performed actions.
MC-CLI recording is always enabled during a Management Console session. The MC-CLI calls corresponding to all the actions performed in the Management Console are recorded in the following internal buffers:
a "Console" buffer for all cross-proxy actions
a separate buffer for each proxy or proxy cluster
You can view these buffers in the internal Management Console editor and write them to a file if required. You can configure how the recordings are written to file in the Management Console.
Only actions for which there are corresponding calls in MC-CLI are recorded. If changes made in a properties sheet relate only to properties that are not supported by MC-CLI recording then the system behaves as if nothing has been modified when you quit the dialog box. A comment is output informing you that no changes have been made and no modifyProperties call is recorded.
Manually controlling the output of recordings
You can view recordings relating to proxy actions, proxy cluster actions or console actions in the Management Console's text window, explicitly write these to a file or delete the accumulated recordings. You control the output of recordings as follows:
Proxy actions or proxy cluster actions: Command Mccli Recording of Proxy/Proxy Cluster (followed by Show/Save/Clear ...) in the context menu of the relevant proxy or proxy cluster.
Console actions: Extra menu, command Show/Save/Clear Mccli Recording of Console.
Configuring recording output to file
You can specify whether and, if required, when a recording is to be written to file: only when required (on demand), always at the end of the session (at end) or after every action (unbuffered). Proceed as follows:
In the Extra menu, choose the command Settings - Logging/Traces and activate the required mode under Mccli Recording.
Please note the following:
When a proxy of proxy cluster is deleted, the corresponding internal MC-CLI recording is also deleted. If on demand mode is set (default setting) and you want to back up the recordings, then you must explicitly write them to a file before deleting.
If you want to log very extensive sessions, you should choose unbuffered mode.
Reason: BeanConnect uses two temporary buffers (current buffer and backup buffer) with a capacity of approximately 1000 lines each. If the amount of data recorded exceeds the combined capacity of these two buffers then data may be lost if it is not backed up to file in the interim.
Name of recording file
A recording file is created in the directory <MC_home>/cli-rec and is named as follows:
<time>.Console.py
for the recording of console actions
<time>.<proxy_id>.py
for the recording of the actions of the proxy with the ID <proxy_id>
<time>.<cluster_id>.py
for the recording of the actions of the proxy cluster with the ID <cluster_id>
Here, <proxy_id> is the unique ID of the proxy, <cluster_id> is the unique ID of the cluster, and <time> is the current timestamp at the moment of creation of the recording file.
If a file with the name <time>.<id>.py already exists then this is renamed to <time>.<id>.py.old. Any existing file with the name <time>.<id>.py.old is overwritten without a warning.
For more information on the format of recording files, see Creating Jython scripts from MC-CLI recordings .
BeanConnect does not delete the recording files. You should therefore regularly check which files you still need. You must manually delete any recording files that you no longer need.