. server_env.sh. uc4_env.sh. uc4_functions.sh
smcl is a wrapper function for the Service Manager Command Line program ucybsmcl. It is specifically adapted for use with the Service Managers that control the Automation Engine (UC4). Because it automatically reads some information from configuration files, it is simpler to use than ucybsmcl. When using smcl, you do not need to specify three ucybsmcl options:
The smcl function automatically fills in these details based on context - mostly based on the server where you run it.
If a password is required, you will be prompted for it.
This is a shortened syntax adapted to make commonly-used functions quicker to type.
smcl start service
smcl stop service
smcl shutdown service
If no action is specified, the default is list.
This is the classic syntax used by ucybsmcl.
smcl -c GET_PROCESS_LIST
smcl -c START_PROCESS -s service
smcl -c STOP_PROCESS -s service [-m stop mode]
smcl -c SET_DATA -s service -d property value
The smcl function is defined in uc4_functions.sh, a script containing shared functions that are also used in other scripts like ae_server.sh. The uc4_functions.sh script is sourced by the .bashrc of all UC4 technical users so, smcl should be available to all of these users.
smcl works only with the AE server Service Manager running on the same node where you run it. It cannot be used to interact with the Agent Service Manager, or with Service Managers running on other nodes. The script was developed primarily for one AE implementation. It may need to be customized for your environment.
The script is implemented as a Bash function in uc4_functions.sh. It relies on many other functions in that script.
ae is a function that can be used to quickly start or stop the Automation Engine (UC4), or to display Service Manager information for the AE.Here's a bit more detail about how these actions work:
STOP_PROCESS -m C
STOP_PROCESS -m S
The script performs lots of error-checking and prompts for confirmation before performing potentially destructive actions. It also prompts for the Service Manager password, if required.
To start the Automation Engine normally, just run ae start by itself or run ae start normal.
ae start normal
Run ae by itself or run ae status. This will list details of the AE server Service Manager process and display the number of child processes.
Run ae list to list all of the running AE server processes.
This lists only the AE server processes that the Service Manager knows about. If the AE is experiencing problems, there may be a breakdown in the communication between the AE and the Service Manager. In this case, the list of processes displayed may be incomplete or not up-to-date. In this situation, you should use the ps command to make sure you identify running all AE server processes, including those that have lost communication with the Service Manager.
Run ae stop and type 1 to confirm.
The stop action does not stop the Service Manager. You will need to run ae kill before trying to start it again. (See the following example.)
Just run ae kill and type 1 to confirm.
If any child processes of the Service Manager are still running, a kill signal will be sent to them when the Service Manager process ends. Usually this will cause the child processes to end too. However, the Automation Engine is experiencing problems, some AE server processes may refuse to die. In this situation, it may be necessary to list hung AE server processes using the ps command, and then kill them one by one, or all at once using a command like killall.
Run ae shutdown and type 1 to confirm.
This will completely shut down the AE server on all nodes. This is done by sending STOP_PROCESS with stop mode S (shutdown) via the SMgr to the WP with the highest CPU usage. (This is often the PWP.) This WP will in turn instruct all other running AE server processes to stop.
For troubleshooting, it can use useful to start the AE Server gradually, initially starting just a few processes. This makes it much simpler to find errors in the AE server logs, because there are fewer active logs to search through.
Run ae start with start mode mini.
The start modes rely on a particular naming convention for Service Manager Command (SMC) files. Take a look at the uc4_functions.sh script to learn more or to customize this for your needs.
ae was developed primarily for one particular AE implementation. It may need to be customized for your environment.
The script is implemented as a Bash function in uc4_functions.sh. It relies on many other functions in that script, including the smcl function described above.