Default values have been specified for the most parameters. They can be changed if required. Parameters that must be adjusted to your system 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. at any case are written in red letters.
Section/Parameter | Description |
---|---|
[GLOBAL] | |
system= |
Name of the AE system. * |
language= |
Language in which the logging is executed. Entries for primary and secondary language. Allowed values: "E", "D", "F" If there is no message in the primary language, a message in the secondary language is searched for. |
logging= | Path and file name of the log file.
The number signs serve as place holders for a series in numerical order. When starting the AE Connector, the log files are renamed so that the most current log file is always the one with the number "00". |
logcount= | Number of stored log files. |
helplib= | Name of the message file. |
helpcache= | Availability of the messages and language-dependent strings.
Allowed values: "ALL", "NONE",
"CONTROLS" |
loglevel= |
Level of message output in the log file. Allowed values: "0" - "2" |
MaxJobs= | Maximal number of requests which can be run simultaneously.
Allowed values: n |
ExecTimeOut= | Boundary of maximum 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). in seconds for processing a scriptA particular Automation Engine object type.
through the Automation Engine. If runtime is exceeded, a timeout error is sent
to the reply queueA particular Automation Engine (AE) object type. In AE, a queue determines the maximum number of concurrent tasks, their priorities and the order in which tasks should be executed. In ARA, queues are containers for workflow executions that should be executed at a certain time one after another..
Allowed values: n |
[TCP/IP] | |
CP= | Connection specifications: Name or TCP/IP address of the computer and port number of the listener on which the Automation Engine is running. |
connect= | Time interval in seconds in which the AE Connector attempts to establish connection to the Automation Engines. Effects the connection setup for a restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. or after a lost connection. |
[TRACE] |
|
file= | Path and file name of the trace file.
The number signs serve as place holders for a series in numerical order. When starting a trace, the trace files will be renamed so that the most current trace file is always the one with the number "00". |
trccount= | Number of stored trace files. |
trclevel= | Amount of messages output in the trace file.
Allowed values: "0" - "2" |
[MQSERIES] |
|
ConnName= | Connection name and port number of the WebSphere MQ Queue
Manager Server. The contents are equivalent to setup values when the MQSC
DEFINE CHANNEL command is used.
Allowed values: <mqsrv>:<port> |
SvrconnChannelName= | Server connection name of WebSphere MQ Queue Manager. The
parameter is only analyzed when the ConnName= Parameter is also used.
Allowed values: <srvchannel> |
QMgrName= | Name of the queue manager.
Allowed values: <mqmanager> |
QueueName=
|
Name of the request queue (SIQ). Allowed values: <siq> |
UseLibrary= |
Type of connection to MQSeries Allowed values: "C" (default) and "S" "C" - Client |
[GLOBAL]
system=UC4
language=(D,E)
logging=..\temp\UCXBMQCS_log##.txt
Helplib=uc.msl
HELPCache=ALL
logcount=3
loglevel=2
MaxJobs=10
ExecTimeOut=300
[TCP/IP]
CP=UC4SRV01:2104
connect=300
[TRACE]
file=..\temp\UCXBMQCS_trc##.txt
trccount=3
trclevel=0
[MQSERIES]
ConnName=MQSRV:1414
; SvrconnChannelName = system.admin.svrconn
QMgrName=queue.manager1
QueueName=UC4CInputQueue
See also:
Notes for Configuration-File Adjustments
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |