The eG Installation Guide - eG Innovations

Installing and Configuring on Unix
Note:
By default, the eG agent package for Solaris (32-bit) is bundled with JRE 1.5. In environments
where the agent-manager communication is SSL-enabled, if for some reason you want the agent
to use JRE 1.3 instead, then follow the steps below to ensure SSL communication between the
agent on JRE 1.3 and the eG manager:
Open the /opt/egurkha/lib/jre1.3 directory on the agent host.
Copy the jsse, jnet, and jcert files from this directory to the /opt/egurkha/lib directory on the
agent host.
2.9.2 Deploying the eG Agent on Linux Environments
While the standard 32-bit Linux agent package can be deployed on a 64-bit Linux host too, there may
be a couple of caveats. On some variants of these operating systems, the 32-bit JRE may fail to run
because of incompatible shared libraries. To remedy such situations, after deploying the standard
Linux agent on a 64-bit operating system, follow the steps given below and change the JRE used by
the eG agent:
1. Stop the eG agent.
2. Login to the eG agent host as the eG install user. You will currently be working in the /opt/egurkha
directory.
3. Move the JRE directory that is used by the eG agent (by default) to another location, say /tmp.
mv jre /tmp
4. If a 64-bit-compatible version of the JRE is already available on the eG agent host, provide a soft
link to that directory using the following command:
ln -s jre
For instance, if the 64-bit version of JRE is available in the /opt/usr/JRE directory, then the
command will be:
ln -s /opt/usr/JRE jre
5. On the other hand, if a compatible JRE does not pre-exist on the agent system, then download
and install the 64-bit version of the JRE from the java.sun.com web site.
6. Then, provide a soft link to the JRE directory using the command indicated by step 4 above.
7. Finally, restart the eG agent.
61