Note: ORACLE_HOME is the Management Agent's instance home. The JKS Agent truststore is located at the following location: $ORACLE_HOME/sysman/config/montrust/AgentTrust.jks However, if self-signed certificates or the default (out-of-box) demo certificate are being used on the WebLogic servers, then the following step is needed to explicitly import the Root CA certificate for these server certificates to the Agent's truststore. A few popular Root CA certificates are available out-of-box in the Agent's JKS-based truststore and does not require any action by the customer.

It is recommended that customers using WebLogic t3s in a production environment use certificates signed by a well-known Certification Authority (CA), such as VeriSign or Thawte, on their WebLogic servers. The Agent comes with nine well-known CA certificates. The Agent maintains a Java Keystore ( JKS) truststore containing certificates of Certification Authorities (CAs) that it can trust when establishing a secure connection. When using Enterprise Manager version 12.1 and a Secure Socket Layer (SSL) protocol or Transport Layer Security (TLS) protocol to discover and monitor WebLogic servers, the Management Agent must be able to trust the server before it can establish a secure communication link.

This section describes how to monitor WebLogic domains.

Apache ant monitoring