Web Configuration Interface for the Java EE/JMX Agent

A web configuration interface is available for adjusting the JMX agent to your system environment. It can be accessed with a web browser using the address http://Server name:Port/ucxjjmx.

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.

Note: When Tomcat is used, the configuration interface can be called directly by using the Web Application Manager.

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.

Note: The TLS/SSL implementation does not apply to the HP-UX Agent, as it is no longer supported in this version.

You can use the trustedCertFolder=, agentSecurityFolder=, and keyPassword= parameters in the respective INI file to point to the relevant certificates. If the trustedCertFolder= parameter is not set, the certificates should be installed in the respective store; that is the Java trust store for Java Agents, the Windows OS store for Windows Agents, or the TLS/SSL store for UNIX Agents. For more information, see Securing Connections to the AE (TLS/SSL).

For more information about the different certificate types and for detailed instructions on how to create and use them, see What Kind of Certificates Should I Use for Automic Automation v21.

TLS/SSL Agents (in containers or on-premises) and the TLS Gateway, when used for the Automic Automation Kubernetes Edition, establish a connection to an ingress / HTTPS load balancer and not the JCP directly. The ingress / HTTPS load balancer must be reachable and requires a certificate for authentication. The address of the load balancer must be defined on both sides: the Automation Engine and the Agent / TLS Gateway.

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.

Configuring the Java EE/JMX Agent

  • Status

    Indicates whether a JMX agent is currently running.

  • Start time

    The start date and time of the JMX agent.

  • Current time

    The current date and time.

  • Host

    The computer on which the application server is available.

  • Name

    The name of the agent. A maximum of 32 characters is allowed.

  • System

    The name of the AE system.

  • JCP host

    The name of the computer on which a Java communication process is available.

  • JCP port

    The port number of the Java communication process.

  • Language

    The language used for logging. The values allowed are E (English), D (German), and F (French).

  • Write agent log to disk

    The log file is stored as a text file.

  • Log count

    The number of log files that are stored.

  • Change logging every

    A new file is created if the log file reaches the size specified here.

  • Auto-run

    The JMX agent is started automatically.

  • TCP/IP Trace

    Activates the TCP/IP trace.

    Important! Set trace flags only in close cooperation with our support team.

  • Encrypted communication

    Activates encryption for transfers.

  • Application Sever

    The type of application server on which the JMX agent runs.

The log files can be accessed via a link of the same name.

See also: