Installing the Agent for PeopleSoft (Windows)

Installing the Agents

Installing the Agent for SAP

---

Setting Up the Agent for Rapid Automation 

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 (such as UC4/Agent/rapidautomation or C:\AUTOMIC\Agent\rapidautomation).

Supplied Files

The files that belong to the RA agent are stored in the directory IMAGE:AGENTS\RAPIDAUTOMATION.

Procedure

	1.	Installing Java Standard Edition

This installation step can be omitted if the required version of Java Standard Edition is already available.

• Admin computer and/or user computer
• Check the current version of your system's Java Virtual Machine (VM) using the following command:

java -version

Note that the order of the indicated directories is relevant when specifying %PATH% or $PATH if several versions of JRE or Java SDK are installed on your computer. The Java Runtime Environment listed first is used.

• Download the required Java Runtime Environment from http://java.sun.com and install it.

	2.	Setting up the Agent

• Host
• Create a separate folder for the RA agent and copy the supplied files to it. Under Windows, you can also use the program SETUP.EXE for the installation. It is available in the directory IMAGE:AGENTS\RAPIDAUTOMATION\WINDOWS.
• The RA Solution that should be used by the agent is stored in the folder named "cache." Create this folder in the installation directory.
• Several settings are available for adjusting the RA agent to your system environment. Of note are the agent and computer name, and the port of the communication process to which the agent should connect. Adjust the INI file.

	3.	Loading the RA Solution

• Host 

• Start the utility AE.DB Load and select the RA Solution's JAR file. The utility will then load it to the AE databaseA database is an organized collection of data including relevant data structures.. The JAR file can be loaded via the graphical interface or the Java batch mode (ucybdbld.jar) of the utility AE DB Load. Loading with the AE DB Load in batch mode (ucybdbld.exe) under Windows is not possible.
• The RA agent can only connect to one RA Solution. If you intend to use several RA Solutions, each solution requires its own RA agent.
• Note that you cannot load the same JAR file of an RA Solution to several systems at a time. Any attempt to do so can cause the utility AE DB Load to abort.

	4.	Creating Connection objects

• Host
• Log on to system client 0000.
• Depending on the RA Solution, one or more templates are generated for the required Connection objects and stored in the folder named "TEMPLATE." Create the required Connection object(s) and complete the tab fields that are subsequently required for the RA agent.

	5.	Starting the Agent

• Host
• The RA agent can only start when the system client 0000 contains an Agent object of the same name. The authentication method is irrelevant in this case.
• A template for the Agent objects to be used is created when the RA Solution loads. It is available in the folder named "TEMPLATE." Create an Agent object in the folder HOST and complete its tab fields (enter Connection objects, etc.).
• Use the following command to start the agent via the command line (UNIX and Windows):
  
  java -jar -Xrs -Xmx256M ucxjcitx.jar
  
   The agent can also be started via the ServiceManager.
  
  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.
  

	6.	Important notes for creating jobs

• Host
• When the RA Solution loads, one or more Job object templates are stored in the folder named "TEMPLATE." These templates can be used to create jobs for the RA Solution.
• RA jobs do not contain Login objects. During the installation process, login data is stored in one or several Connection objects which can be selected in the Agent object.