Administration Guide > Installation > New Installation > Installing the Agent for Database Variables

Installing the Agent for Database Variables

The following guide describes the installation process of the databaseA database is an organized collection of data including relevant data structures. 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 for Variable objects with the source SQL. This agent is also referred to as the DB Service Agent.

This installation guide can be used for Windows and for Unix.

The agent for SQL variables (DB Service Agent) can access each supported database type. This type must be determined in a DB-type Connection object that can be assigned to Variable objects with the source SQL. In doing so, only one DB Service Agent is required for all SQL variables.
In this Connection objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task, you can also determine the database name and the connection parameters (such as Server name and port number). The agent is configured in the AutomationEngine's INI file and not in its own INI file.
The agent is only required for Variable objects with the source SQL. SQLI variables do not require an agent because they access the AE database directly via the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes..

The DB Service Agent must be installed on the same computer as the Automation Engine.
This includes that you can only log on to MS SQL Server databases via Windows authentication when the Automation Engine does not run on UNIX. The reason for this is that the library "sqljdbc_auth.dll" cannot be loaded under UNIX.

A DB Service Agent may always be used throughout the whole system, regardless of the authorization settings (Agent object > Authorizations tab).

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.

Supplied Files

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.



Procedure

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

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