Note that modifications that have been made in the ServiceManager dialog program are automatically adjusted in this file. No manual adjustment is required.
The definition file (UC4.SMD by default) contains all start parameters for AE services. For each service there is a line that starts with the keyword DEFINE. The individual start parameters are separated by semicolons, and comment lines start with an exclamation mark.
Syntax
DEFINE Service; component INI file; Working directory [; -svc%port%] [; LOGON=(User name, Password, Domain )] [; Start1=() ; Start2=(); Start3=() etc.]
Syntax |
Description/Format |
---|---|
Service |
Service name. You can also use blanks. |
component |
Path and file name of the AE program that should start. You can use absolute or relative path specifications. "*OWN" means that the program must be listed in the directory of the calling ServiceManager.
Agents for SAP, JMX, databases and Rapid Automation require a Java call.
Java agents: Also specify the Java path because the ServiceManager under UNIX does not read all environment variables.
|
|
Insert a blank between the parameters component and INI file. |
INI file |
File name of the INI file that should be used. You can also specify an absolute or relative path (relative refers to the program that should be started). |
Working directory |
Working directory for the program that should start. If the program to be started is a Java-based agent (SAP, Databases, JMX, Rapid Automation), the working directory must be the path to the JAR file. |
-svc%port% |
Additional display option for server processes. With this start parameter being specified, the ServiceManager dialog program displays the name of the server process and the number of connections in addition to the name of the service. |
LOGON= |
LoginAnmeldedaten für Zielsysteme. Auch ein eigener Objekttyp in der Automation Engine. data for the AE program. This parameter only applies for the ServiceManager on Windows. |
Start1= |
Several start methods for a server process (WP).
Syntax:
Name = The name of the start mode that you can define using the ServiceManager start parameter -sm. To start the WP with a specific mode, you must append the following parameter: For example: 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) |
You can structure variables in order to increase
their readability because the individual lines can be very long.
For example:
VAR Name of the variable;value of the variable
The SMD file is divided in two parts. All VAR statements must be listed in the beginning, then the DEFINE statements are listed.
Within a DEFINE line, you can insert a variable by specifying a "*" followed by the variable name.
Example of an SMD File
! Variables
VAR SRV_PATH;*OWN\..\..\Server\bin\
VAR CP_STARTCMD;*OWN\..\..\Server\bin\UCsrvcp.exe *OWN\..\..\Server\bin\ucsrv.ini -svc%port%
VAR WP_STARTCMD;*OWN\..\..\Server\bin\UCsrvwp.exe *OWN\..\..\Server\bin\ucsrv.ini -svc%port%
VAR WP_START1;*WP_STARTCMD -parm"StartMode=COLD"
VAR WP_START2;*WP_STARTCMD -parm"SystemStop=YES"
VAR WP_START3;*WP_STARTCMD -parm"StartMode=COLD;SystemStop=YES"
! Server processes
DEFINE UC4 CP1;*CP_STARTCMD;*SRV_PATH
DEFINE UC4 WP1;*WP_STARTCMD;*SRV_PATH;START1=(Coldstart,*WP_START1);START2=(Systemstop,*WP_START2);START3=(Coldstart with Systemstop,*WP_START3)
! Windows agents
DEFINE WIN01;*OWN\..\..\AgentWin\bin\UCXJWI3.exe;*OWN\..\..\AgentWin\bin\
DEFINE UC4MAIL;C:\AUTOMIC\Agents\win\bin\UCXJWI3.exe UC4MAIL.ini;C:\AUTOMIC\Agents\win\bin;LOGON=(uc4mail,10D888EA16FE7D2C0FE,)
! SAP agent
DEFINE SAP01;java -jar -Xrs -Xmx256M ucxjr3x.jar;*OWN\..\..\Agents\SAP\bin