This document lists and describes the start parameters of the Automic ServiceManagerA program that facilitates the starts and stops of Automation Engine components..
UNIX:
Starting the ServiceManagers: nohup ./ucybsmgr [-ipath and name of the INI file] phrase&
Windows:
Installing the service: UCYBSMGR[.EXE]
-install phrase [-ipath
and name of the INI file]
De-installing the service: UCYBSMGR[.EXE]
-remove phrase
With the command line program UCYBSMCL, the ServiceManager can be managed through batch processing. Services can be started and ended with this program. A listShows entities in a grid view of all services of a computer belonging to a ServiceManager environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. can also be called up. The command line program is available for Windows and for UNIX.
Please mind the correct spelling as upper and lower case are distinguished.
Windows:
UCYBSMCL[.EXE] -c GET_PROCESS_LIST -h computer name -n phrase
UCYBSMCL[.EXE]
-c START_PROCESS -h computer
name -n phrase -s name
of the service [-p passwordA secret combination of characters for a Automation Engine user.]
UCYBSMCL[.EXE]
-c STOP_PROCESS -h computer
name -n phrase -s name
of the service [-m stop mode] [-p password]
Unix:
ucybsmcl -c GET_PROCESS_LIST -h computer
name:port number -n phrase
ucybsmcl -c START_PROCESS -h computer name:port
number -n phrase -s name
of the service [-p password]
ucybsmcl -c STOP_PROCESS -h computer name:port
number -n phrase -s name
of the service [-m password] [-p password]
Start Parameter |
Assignment |
Description |
---|---|---|
-c |
|
Command that is to be processed. |
|
GET_PROCESS_LIST |
Requests a list of all services belonging to a ServiceManager environment on a computer together with the available information. |
|
START_PROCESS |
Starts a service |
|
STOP_PROCESS |
Stops a service |
-h |
|
Computer |
|
Computer name |
Name of the computer on which the ServiceManager is to be handled. A remote computer can also be used. This computer must be available from the computer which is calling it. The userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. must be authorized to access services on this remote computer. |
|
Port number |
In UNIX, the port number of the ServiceManager must additionally be indicated. |
-n |
|
ServiceManager environment. |
|
Phrase |
Name of the ServiceManager environment which summarizes/outlines the various AE services on a computer. In the dialog program of the ServiceManager, this is designated as a phrase. |
-s |
|
Service. |
|
Name of the service |
Specification of the name of a service Available in the following places:
Since a service name can also contain spaces, it should always be entered within quotation marks. |
-m |
|
End mode. |
|
Stop mode |
Way in which a service should be ended Allowed values: "C" (default value),
"S", "A" |
-p |
|
Password. |
|
Password |
Password for service start and stop authorization. |
-sm |
The start mode of server work processes (WPs) The values that are allowed for the parameter -sm depend on the service definition in the ServiceManager's SMD configuration file. |
|
Start mode |
For example, the definition of a WP service in an SMD file (including variables): VAR SRV_STARTPATH;*OWN\..\..\Server\bin DEFINE UC4 WP2;*WP_STARTCMD;*SRV_STARTPATH;START1=(Coldstart,*WP_STARTCMD_COLD);START2=(Systemstop,*WP_STARTCMD_STOP);START3=(Coldstart with Systemstop,*WP_STARTCMD_COLDSTOP) For this WP service, the following values can be used for the parameter -sm "Coldstart" = Cold start mode |
When you call the command line program using incorrect or missing parameters, a short help text will be displayed that shows correct parameters and return codes.
When you call the command line program with the GET_PROCESS_LIST command, the requested information will be displayed line by line. It corresponds to the view of the ServiceManager Dialog program.
Output format
"Service" "Status" ["ProcID" "Start time" "Runtime" "CPU Time"]
Column/Field |
Description |
---|---|
Service |
The name of the service. |
Status |
Service statusThis represents the condition of a task (such as active, blocked, generating).. |
ProcID |
Process number of a service |
Starttime |
The start date and time of a service. |
Runtime |
The runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start). of a service. |
CPU Time |
The CPU time that a service requires. |
Return code |
Description |
---|---|
0 |
A command has been processed without an error. |
1 |
An incorrect command has been entered. |
2 |
No active ServiceManager has been located on the specified computer. Possible reason: |
3 |
The ServiceManager reacts to a command in an unexpected way. Possible reason: |
4 |
Errors occurred with the ServiceManager connection. |
5 |
The specified ServiceManager environment is not present on the corresponding computer. Possible reason: |
The first example retrieves all services that belong to the computer "WINW2K01" and the ServiceManager environment "UC4P".
UCYBSMCL.EXE -c GET_PROCESS_LIST -h WINW2K01 -n UC4P
Output:
"UC4 CP1" "R" "1588" "2004-04-05 21:39" "0/01:11" "0/00:00:22.69"
"UC4 WP1" "R" "3388" "2004-04-05 21:39" "0/01:11" "0/00:00:22.69"
"UC4 WP2" "R" "1576" "2004-04-05 21:39" "0/01:11" "0/00:00:22.69"
"Win32-Agent WIN01" "R" "2708" "2004-04-05 21:40" "0/01:11" "0/00:00:01.31"
"Win32-Agent WIN21" "R" "2392" "2004-04-05 21:40" "0/01:10" "0/00:00:01.30"
"Win32-Agent UC4MAIL" "R" "2932" "2004-04-05 21:40" "0/01:10" "0/00:00:01.31"
"SAP Agent C46" "S"
"PeopleSoft-Agent PS01" "S"
The second example terminates a UNIX agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host normally.
./ucybsmcl -c STOP_PROCESS -h unixw2k01:8871 -n uc4p -s unix01 -m Close
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |