Single User

Clear (default)

Select for direct connection to the Automation Device from Design Studio or when using the RDP connection.

"singleUser"

false (default)

true

Set to false to automatically register the Device Automation Service with the specified Management Console.

For direct connection to the Automation Device, set to true and specify a token.*

Host name

"hostName"

Name or IP address of the computer running the Device Automation Service.

If a computer has multiple names or IP addresses, specify the one that RoboServers and Design Studio contact this Automation Device Agent with. That is, the host name or IP address must be reachable from RoboServers and Design Studio.

Command port

"commandPort"

49998 (default)

Reassign this port for the Automation Device if necessary.

Stream port

"streamPort"

49999 (default)

This port is used to send data between Design Studio and Device Automation Service. If streamPort is set to "0", the Device Automation Service selects a random port number.

You might need to reassign the streamPort if there is a firewall between Design Studio and the Automation Device.

CA file

"caFile"

empty (default)

You can communicate with the Management Console using SSL. If the default certificate in node.js is not used, you can specify a path to another certificate file using this parameter.

Timeout

"commandTimeout"

This option specifies the timeout for command execution in seconds. A command is an instruction sent to Automation Device, such as click mouse button, open application, add a location found guard, and so forth. If a command cannot be completed in a specified time, the service sends a notification and execution of the robot stops.

Note that in case of a Location Found guard, this setting applies to invoking the guard in the workflow, but waiting for the guard to be satisfied is not bound to this timeout and can wait forever. Similar situation occurs when using the Move Mouse and Extract steps. The commands must be invoked on the device withing the timeout specified in this field, but the robot waits for up to 240 seconds for the commands to complete.

The command timeout for automating terminals or browsing websites in Device Automation Workflow is set either on the Device Automation tab of the Design Studio Settings window for executing the workflow in Design Studio, or in the Device Automation section on the Security tab of the RoboServer Settings window for roboserver execution.

Token on Single User tab

"token"

empty (default)

If the "singleUser" option is set to false, leave this option empty. If you use the direct connection to the Automation Device ("singleUser": true), specify a token. It can be any token you define.

List of drivers to load at startup, such as Windows, TN3270, TN5250, VT100

Windows (default)

"drivers"

["automationnative"] (default)

You can select drivers to load at startup.

Windows is the default driver for automating native Windows and Java applications. Leave this parameter as is.

To access a terminal from the Automation Device, select the corresponding driver.

Certificates tab

"tlsServerConfig"

Kapow provides TLS communication between Automation Device and RoboServer or Design Studio. The communication uses certificates for encrypting the communication. The following is a cerver.conf file code extract. For more information see Use TLS Communication.

  "tlsServerConfig": {
    "key": "kapow.remote.das.pem",
    "cert": "kapow.remote.das.cert.pem",
    "ca": "./serverCa"
  },

Windows tab

"automationnative"

"useLegacy": In some situations the Java Access Bridge does not work and it can help to switch to legacy mode. Default is false.

Log tab

This tab helps you open the log file to examine for any errors and shows the version and location of the service file.

OCR tab

"ocrConfig"

"defaultLanguage": "eng"

Specifies a language to perform an OCR operation. By default, Kapow installs the English language. See Change Default OCR Language for language installation instructions.

MC Path

Connection protocol, name or IP address, port number, and path of the Management Console the device must register with. The format is as follows:

http://10.10.0.136:50080.

"hostName"

Name or IP address of the Management Console the device must register with.

"port"

Connection port of the specified Management Console.

"schema"

Connection protocol of the specified Management Console.

"path"

empty (default)

The part of the path to the standalone Management Console after the port number. For example, if your Management Console is deployed on Tomcat at http://computer.domain.com:8080/ManagementConsole/, specify "/ManagementConsole/" in this parameter. Leave this parameter empty for the embedded Management Console installation.

User name

"user"

empty (default)

User name to authenticate on the specified Management Console.

Password

"password"

empty (default)

Password to authenticate on the specified Management Console.

"pingInterval"

5000 (default)

Time interval for the Device Automation Service to ping the Management Console.

Cluster

"cluster"

Production (default)

Cluster name on the specified Management Console.

Labels

"labels"

"label1,label2" (default)

Labels to distinguish the Automation Devices.

Use proxy to connect to Management Console

"useProxy"

Select this option for the Device Automation Service to use proxy when connecting to Management Console. All necessary parameters are specified in the following fields.

Under Linux, you can set up proxy parameters in the managementConsole section of the server.conf file.

    "useProxy": true,
    "proxyHostName": "proxyhost.com",
    "proxyPort": 9000,
    "proxyUserName": "username",
    "proxyPassword": "pwd"