You must download and run the connectivity agent installer to install the agent in your local environment.
Satisfy the following system requirements before installing the on-premises connectivity agent.
The agent is only certified with Oracle JDK Version 8. The JDK installation can be shared with other products installed on the same host. However, ensure that the JDK installation is not modified for use with these other products.
The Oracle JDK used solely for running the connectivity agent is covered by the Oracle product use license. See Oracle Java SE Licensing FAQ.
The agent is certified on the following operating systems:
Oracle Enterprise Linux 6.x
Oracle Enterprise Linux 7.2
Oracle Enterprise Linux 7.5
Oracle Enterprise Linux 7.8
RedHat Enterprise Linux 6.6
RedHat Enterprise Linux 7.2
RedHat Enterprise Linux 7.5
RedHat Enterprise Linux 7.6
RedHat Enterprise Linux 7.8
Suse Linux Enterprise Edition 12 SP2
Windows Standard Edition 2016
Note:IBM or Open JDK are not supported.
Provide a minimum of 8 GB memory with 4 GB of heap size dedicated for the agent JVM. If you want to include any other processes on that host besides the on-premises agent, it is strongly recommended that you increase physical memory to a value greater than 8 GB.
Connectivity Agent Restrictions
Note the following connectivity agent restrictions.
When installed on a Windows host, the connectivity agent does not work with a proxy using NT LAN Manager (NTLM) authentication.
Restart the Agent
You can restart the on-premises connectivity agent if required.
Stop the agent in either of the following ways:
ctrl+con the host on which the agent is running.
Search for the connectivity agent process and kill it.
- Wait at least 45 seconds before restarting the agent. This is because the agent
monitoring framework waits for 45 seconds before marking the agent status as
being down. If you start the agent before 45 seconds have completed, agent
restart fails with the following error
Agent is already running for this particular instance
Restart the agent based on your environment and production load size.
Environment Enter the Following Command Production environments It is recommended that you restart the agent with the
java -XX:+HeapDumpOnOutOfMemoryError -jar connectivityagent.jar
If the connectivity agent runs out of memory, this parameter by default ensures that the heap dump is stored in a
java_pidpid.hproffile in the directory where the agent application is run.Based on production loads, it may sometimes be necessary to allocate a larger amount of heap size for the agent process. If you determine that the process must be allocated a larger heap size, tune the
For example, assume you want to assign a minimum of 2 GB and a maximum of 8 GB to the agent JVM.
-Xms2G -Xmx8GStart the agent with the following parameters.
java -Xms2G -Xmx8G -jar connectivityagent.jar
-Xmxparameters can all be specified at the same time, if needed.
java –jar connectivityagent.jar
You can restart the agent as a background process. See Run the Connectivity Agent Installer as a Background Process on Linux Systems.