Installing the Agent for Databases

Installing the Agent for Databases

Installing the Agent for Database Variables

---

Installing the Agent for Database Jobs and Events

The following guide describes the installation process for the agent 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 object. 

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.

Additionally, two empty folders (Temp and JDBC) are supplied. The Temp folder 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.

• Admin computer and/or user computer
• The Version of the current Java Virtual Machine (VM) of the system can be checked with the following command:

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 list of directories is used.

• Download the required Java Runtime Environment from http://java.sun.com and install it. The installation process includes the automatic installation of the Java Plug-in for Web browsers. You can deactivate it in the system control. The Automation Engine does not need it.

	2.	Installing the Agent

• Host
• Create a separate directory for the agent (such as C:\AUTOMIC\AGENTS\SQL\BIN or UC4/AGENTS/SQL/BIN).
• Copy the content of IMAGE:AGENTS\SQL to the directory you just created. Under Windows, you can also use the program SETUP.EXE for the installation. It is available in the directory IMAGE:AGENTS\SQL\WINDOWS.

	3.	Installing the JDBC driver

• Host
• A suitable JDBC driver must be installed for all databases that the agent will use. Refer to the particular vendor's installation guide.
• Create the folder JDBC in the database agent's BIN folder. Copy the JDBC driver files to this folder after successful installation.

• Microsoft SQL Server
• Install the Microsoft JDBC Driver for SQL Server or Microsoft JDBC Driver 4.0 for SQL Server
• Copy the file sqljdbc4.jar to the folder's JDBC directory after you have installed the driver.
• 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 list of directories is used.
• When you start the agent under Windows, you can use the corresponding OS user for logging on to the MS SQL database (Windows authentication). When you install the JDBC driver, you must also copy the file "sqljdbc_auth.dll" to the database agent's BIN directory. Make sure that this file's architecture complies with the architecture of the JVM that is used (x64, for example).

• Oracle
• Install the driver.
• Copy the file ojdbc5.jar or ojdbc6.jar to the folder's JDBC directory after you have installed the driver.
• The JDBC driver of version 9.0.1 or earlier cannot be used with this agent due to a program error in the driver.
• The agent searches the relevant jar-file classes in the JDBC folder. The file name is irrelevant. It is important to use the most current jar file. Automic recommends storing only one jar file in the JDBC folder.

• MySQL
• Install the driver.
• Copy the file mysql-connector-java-5.0.3-bin.jar to the folder's JDBC directory after you have installed the driver.

• DB2
• The JDBC driver is part of the DB2 installation. It is available in the directory SQLLIB/java (under Windows: C:\Program Files\IBM\SQLLIB\java).
• Copy the following two files to the agent's JDBC directory:
• db2jcc.jar (JDBC Type 4 Driver)
• db2jcc_license_cu.jar (Server license)
• The JDBC driver can be downloaded from IBM's homepage.
  Click on the entry "DB2 Personal Developers Edition: Re-distributable JDBC Type 4 Driver."

• Sybase
• Install the driver (jConnect 5.5/6.05).
• Copy the file jconn2.jar or jconn3.jar to the folder's JDBC directory after you have installed the driver.

• Informix
• Install the driver (V3.5).
• When the driver is installed, copy the files ifxjdbc.jar and ifxlang.jar to the agent's jdbc directory.
• Note that the agent requires Informix databases with transaction support.
•  Due to an Informix error, it is necessary to specify the value for the environment variable DB_LOCALE in particular versions. The error "Database locale information mismatch" occurs if DB_LOCALE has not been correctly set.
  In this case, set the corresponding value in the agent's INI file, section [INFORMIX], using the parameter db_locale= (use lower case).
  For example: [INFORMIX] db_locale=EN_US.CP1252 

• Ingres
• Install the jdbc driver.
• When the driver is installed, copy the file iijdbc.jar to the agent's JDBC directory.

• SAP HANA
• Copy the file ngdbc.jar from the HANA client's installation directory to the agent's jdbc directory.

	4.	Additional important notes

• Oracle RAC
• The agent can also be configured so that it can connect to an Oracle database in RAC.

	5.	Setting up the system environment

• Host
• Adjust the INI file UCXJSQLX.INI to the system environment.
• If the agent starts under Windows and accesses an MS SQL database, you can use the relevant Windows user in order to log on to the database. The following measures are required:
• Install the JDBC driver as described above.
• Agent's INI file: WindowsAuthentication=1
• UC_HOSTCHAR_DEFAULT: ANONYMOUS_JOB = Y
• In database jobs, you must still specify a Login object that includes a suitable entry for the particular agent even if you use the Windows authentication. The Login object's user and passwordA secret combination of characters for a Automation Engine user. are neither used nor checked.

• Admin computer or Server computer
• Adjust HEADER.WINDOWS, TRAILER.WINDOWS and RESTART.WINDOWS if necessary. See: Job - Execution.

	6.	Starting the Agent

• Server computer
• The AE system must be running.
• Host
• Start the agent with the following command:
  java -jar -Xrs -Xmx256M ucxjsqlx.jar
  
  An Agent object is automatically created in system client 0000 and stored in the folder HOST.
  
  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..
  
• Admin computer or Server computer
• Verify that the agent is logged on to the AE system.
  • Start the UserInterface for client 0000. Call the information about agents in the System Overview. Newly logged-on agents have not yet been assigned to a client; they can only be viewed in client 0000. The newly installed agent can now be assigned to clients with the required rights via the Agent object.

Use the ServiceManager to start or end the agent as a service.