Installing the Agent for Java EE/JMX (Oracle WebLogic)

The page guides you through the installation of 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. For more information, see Agent Authentication.

Tip! This page refers only to the manual installation process. If you want instructions on how to install a containerized Java agent, see Installing Containerized Java Agents.

Tip: It is best to install the agent in a separate directory (such as UC4/Agent/jmx or C:\AUTOMIC\Agent\jmx).

This page includes the following:

Connecting to the Automation Engine

The Automation Engine and the Windows, UNIX, and Java Agents communicate using TLS/SSL. These agents establish a connection with the Java communication process (JCP), which uses trusted certificates to prove their identity to other communication partners.

Important! Make sure you are familiar with the TLS/SSL and certificate implementation before installing and/or upgrading the respective component. For more information, see:

When you used certificates signed by a CA, the certificates are stored in the respective Java or OS store by default; that is the Java trust store for Java components and Java Agents, the Windows OS store for Windows Agents, or the TLS/SSL store for UNIX Agents. In this case, you only have to check that the root certificates already are in the respective store.

If the relevant certificates are not there and you want to import them, you can use OS or Java specific tools for that purpose, such as Keytool, cert-manager, OpenSSL and such. For more information on how to use those tools, please refer to the respective product documentation.

If you do not want to use the default locations for the components and Agents listed above, make sure you use the trustedCertFolder=, agentSecurityFolder=, and keyPassword= parameters (if applicable) in the respective configuration (INI) file to define the path to the folder where the trusted certificates are stored.

Important! TLS/SSL Agents (in containers and on-premises) as well as the TLS Gateway, when used for the Automic Automation Kubernetes Edition, establish a connection to an ingress / HTTPS load balancer, which requires a certificate for authentication.

Make sure that address of the load balancer is defined on both sides: the Automation Engine and the Agent / TLS Gateway and that your HTTPS load balancer has the required certificates in place. For more information, see Connecting to AWI, the JCP and REST Processes Using an Ingress.

Important! When you install or upgrade Agents manually for an Automic Automation Kubernetes Edition system, you have to make sure that you configure your Agents and/or TLS Gateway to reach the TCP or HTTPS load balancer and not the CP or JCP directly. Also, make sure that your HTTPS load balancer has the required certificates in place. For more information, see Connecting to the AAKE Cluster.

Installing the Agent for Java EE/JMX (Oracle WebLogic)

In the admin and/or user computer, install Java Standard Edition.

You can skip this step if the required version of Java Standard Edition is already available.
- Use the following command to check the current version of your system's Java Virtual Machine (VM):
  
  java -version
  
  Note: 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.
- A separate Java 11 installation is required if the agent runs on the same computer as the WebLogic Server (recommended). The JMX Agent cannot run with Java 8 that is part of the WebLogic Server.
On the host, set up the Agent.
- Create a separate folder for the JMX agent (bin) and copy the supplied files.
- In the INI file of the JMX Agent, set the Agent name, computer name, and port of the JCP to which the Agent should connect. For more information, see Agent JMX.
- When you used certificates signed by a CA, the certificates are stored in the respective Java or OS store by default. In this case, you only have to check that the root certificates already are in the respective store.
  
  If you do not want to use the default location for this component, make sure you use the trustedCertFolder=, agentSecurityFolder=, and keyPassword= parameters (if applicable) in the respective configuration (INI) file to define the path to the folder where the trusted certificates are stored.
  
  For more information, see Securing Connections to the AE (TLS/SSL).
- Copy wlthint3client.jar from the WebLogic Server directory to the agent's installation folder.
- Start the agent using the following command:
  
  java -jar ucxjjmx.jar
You can also start the agent using the ServiceManager. For more information, see ServiceManager.
On the host, before creating jobs, consider the following issues:
- Select Remote Java VM in the Job object's JMX tab
- Enter the term weblogic in the field Initial Context Factory
- Specify the WebLogic Server for the server URL using the Protocol and Name of the WebLogic Server:port of the WebLogic Server format. Example:
  
  t3://127.0.0.1:7001
You can also run the agent without a connection to the Oracle WebLogic Server. In this case, select the option Local Java VM and Use existing MBean Servers in the Job objects.

The WebLogic Server's default port is 7001.