The following guide describes the installation process for the 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 that is used to execute databaseA database is an organized collection of data including relevant data structures. jobs and events.
This installation guide can be used for Windows and for Unix.
The database agent for jobs and events is only available for a particular database type (such as MS SQL) and can be set in the agent's INI file. A separate agent must be installed for each database type that can be accessed by jobs or events. Database and server names must be defined in the particular Job or Event objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task.
The following guide describes how to install an agent in an AE system in which authentication is not used. Additional installation steps are required before the agent can be started and used if you intend to use one of the available authentication methods. More detailed information is provided in the document Advanced Security.
Automic strongly recommends installing the agent in a separate directory.
Before you start the installation, ensure that the Java agents can only connect to CP port numbers that are lower than 65536. If they use a higher port number, the agent cannot start and aborts with an error message. This limitation is caused by Java and affects the agents for JMX, databases, SAP and RA.
The files that belong to the Database agent are stored in the directory IMAGE:AGENTS\SQL.
File name | Description |
---|---|
UCXJSQLX.JAR |
Database agent |
UCXJSQLX.INI | Initialization file for the database agent |
UC.MSL | Message library |
SETUP.EXE | Installation program (Windows) |
Additionally, two empty folders (Temp and JDBC) are supplied. The Temp folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. stores log files, and the JDBC driver must be installed in the JDBC folder.
![]() |
1. | Installing the Java Runtime Environment (JRE) |
---|
If JRE is already available in the required version, this step of the installation process can be ignored.
java -version
If several JRE or Java SDK Versions are installed on the computer, make sure that the order of the directories is correct in the settings of %PATH% or $PATH. The particular Java Runtime Environment that is found first in the listShows entities in a grid view of directories is used.
![]() |
2. | Installing the Agent |
---|
![]() |
3. | Installing the JDBC driver |
---|
![]() |
4. |
Additional important notes |
---|
![]() |
5. | Setting up the system environment |
---|
![]() |
6. | Starting the Agent |
---|
Note that the storage limit should be set to at least 256MB (or 512MB) for starting Java agents (Databases, RA, JMX, SAP). You can specify a value for the storage limitation of Java applications by using the start parameter -XmX. Specifying a value that is too low can cause the agent to crash. The default value depends on the Java version that is used.
The Java parameter -Xrs ensures that the agent ends properly when a normal end is initiated. Automic recommends using this parameter. More detailed information is provided in the Java documentation.
.Use the ServiceManager to start or end the agent as a service.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |