This topic describes how to install the JD Edwards agent in an existing Automation Engine system.
Steps to Install or Upgrade the JD Edwards Agent
To set-up the RA JD Edwards agent, you need to:
Make sure that this and other 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.
On the host, check the current version of your system's Java Virtual Machine (JVM) using the following command:
java -version
/etc/alternatives/jdk1.7.0_45/bin/java -Xmx2048m -jar ucxjcitx.jar disable_cache
For platform-specific Java requirements on your Automation Engine machine, see your Automation Engine release notes.
You can get the necessary files to install Java from Oracle.
License File Requirement
License files for RA agents need to have a EX.RA.<AGENT TYPE> line in them and be loaded into the database. For more information on loading keyfiles, see your Automation Engine documentation.
Putting Agent Core Files on the Host Machine
Install each RA agent in its own sub-directory on its host machine.
The agent core must be the same version as the Automation Engine. You can update the agent core by getting updated files for an Automation Engine release by downloading the image for that release from the Automic Download Center and putting the agent files in place following these instructions.
For UNIX
automic/agents/ra_ftp
automic/agents/ra_bo
automic/agents/ra_ws
gunzip ucxjcitx.tar.gz
tar -xvf ucxjcitx.tar
For Windows
C:\automic\agents\ra_ftp
C:\automic\agents\ra_bo
C:\automic\agents\ra_ws
Supplied Files
The Rapid Automation agent core includes the following notable files:
| File name | Description |
|---|---|
|
ucxjcitx.jar |
Agent core for Rapid Automation |
|
ucxjcitx.ini |
Rapid Automation configuration file |
| *.jar |
Libraries |
| uc.msl | Message library |
| setup.exe | The Windows installation executable for the RA agent core |
Editing the ucxjcitx.ini File
Edit the required parameters in the ucxjcitx.ini file for the RA agent described in the table below.
| Parameter | Description |
|---|---|
| name |
Name of the agent object. The agent name is limited to 32 of the following characters: "A-Z", "0-9", "_", ".", "$", "@", "-" and "#". Hyphens ("-") are only allowed in agent names. They must not be used in the names of any other objects. Although agent names are limited to 32 characters, you should keep them under 25 characters. The last seven characters are used for adding the suffix '.NEW.nn' when a new agent is created from its template. |
| system | Automation Engine system name. This entry must be identical to the entry in the .ini file of the Automation Engine server. |
| cache_directory | Directory to which the agent should store the RA solutions. This will be set to cache by default and does not need to be altered unless you want to change it. |
| lib_directory |
Directory that contains external libraries that are not part of the solution (such as ojdbc6.jar). Default: lib |
| ra | Used for additional trace. Before starting a newly installed or upgraded agent, it is a good idea to turn Rapid Automation trace on by adding ra=99 as shown below. This will give more troubleshooting information if something goes wrong during the install. After a successful agent start, you can set ra=0, and restart the agent to turn Rapid Automation trace off. |
| cp |
Address of the communication process in the Automation Engine system to which the agent should connect itself. The format is: <DNS name or TCP/IP address>:<port number> |
For information on the additional parameters in the ucxjcitx.ini file, see your Automation Engine documentation.
A sample ucxjcitx.ini file is shown below. The required parameters are shown in bold:
[GLOBAL]
name=RA01
system=AE
logcount=10
logging=../temp/RA_LOG_##.TXT
;LogMaxSize: 0...default, qualifiers k...Kilo, M...Mega, G...Giga
LogMaxSize = 0
language=E
helplib=uc.msl
[RA]
cache_directory=cache
ext_directory=external
shared_directory=shared
lib_directory=lib
[TCP/IP]
connect=20
cp=localhost:2217
[AUTHORIZATION]
KeyStore=
InitialPackage=
[VARIABLES]
uc_host_jcl_var=RA
uc_ex_path_bin=.
uc_ex_path_temp=..\temp\
uc_ex_path_jobreport=..\temp\
[TRACE]
file=..\temp\RA_TRACE_##.TXT
;TraceMaxSize: 0...default, qualifiers k...Kilo, M...Mega, G...Giga
TraceMaxSize=0
tcp/ip=0
ra=99
trccount=10
[CP_LIST]
2218=PC01
Loading the JD Edwards .jar File into the Database
On the host machine, start the utility AE.DB Load and select the RA JD Edwards agent's .jar file. The utility will then load it to the Automation Engine database. 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, keep in mind that each solution requires its own RA agent.
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.
Starting the JD Edwards Agent
The JD Edwards agent only starts if an agent object of the same name exists in system client 0000. A template for the agent objects is stored in the TEMPLATE folder.
You can use the following command to start the agent via the command line (UNIX and Windows):
java -jar -Xrs -Xmx256M ucxjcitx.jar disable_cache
You can also start the JD Edwards agent using the Service Manager program. For more information, see your Automation Engine documentation.
If you load the JD Edwards solution, then start the agent shortly afterward, you may get a cached agent rather than the one you just loaded. You can avoid this by adding disable_cache to the end of the start command. That way the loaded version is always started.