System monitoring with Java Management Extensions (JMX)
By default, nodes are enabled to use Java™ Management Extensions (JMX) technology. This technology is useful for monitoring AS4 Microservice and updating system settings at run time.
You can use JMX technology to view the same information that you display when you run the member list command (member name, member type, member status, and other information).
To view information by using JMX, you must have a tool like JConsole.
When you install AS4 Microservice, you specify JMX ports for each type of member. You can disable and re-enable the JMX settings for some or all of the member types in your cluster.
Using JMX with AS4 Microservice requires the following items:
- User name and password to connect to the JMX server. The user
name and password are applied to all members on a host. You can change
the password. The default values are
jmxuserandjmxpassword. Use the jmx config command to set the password. - A certificate that can be used for Transport Layer Security (TLS). This
certificate is used for all member types on a host. The TLS connection is secured by default with a
self-signed certificate that is created during the installation of AS4 Microservice. You can upload another
certificate to replace the default certificate. Use the system_certificate
config command to upload another certificate.Important:
- Although you can use either the Transport Layer Security (TLS) or Secure Sockets Layers (SSL) protocol with AS4 Microservice, IBM recommends that you use SSL only for backward compatibility due to security vulnerabilities. For more information, see the IBM Product Security Incident Response Blog.
- TLS is supported only for server identification. You cannot configure client authentication certificates.
- A custom client connector JAR file in your class path. This JAR file (restConnector.jar) is included in your installation at install_dir\resources\clients. You must use the restConnector.jar file that is provided in the installation.