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.

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.

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: