You can monitor AEM forms deployments from both a system level and an internal level. You can use specialist management tools such as HP OpenView, IBM Tivoli, and CA UniCenter and a third-party JMX monitor called JConsole to specifically monitor Java activity. Implementation of a monitoring strategy improves availability, reliability, and performance of your AEM forms deployments.
For more information about monitoring AEM forms deployments, see A technical guide for monitoring AEM forms deployments.
AEM forms provides two registered MBeans that provide navigation and statistic information. These are the only MBeans that are supported for integration and inspection:
ServiceStatistic: This MBean provides information about Service name and its version.
OperationStatistic: This MBean provides the statistic of every forms server’s service. This is where administrators can get information about a particular service such as invocation time, number of errors, and so on.
public String getServiceId(); public int getMajorVersion(); public int getMinorVersion();
// InvocationCount: The number of times the method is invoked. public long getInvocationCount(); // InvocationStartTime: The time at which the method started to execute. public long getInvocationStartTime(); // InvocationEndTime: The time at which the method finished execution. public long getInvocationEndTime(); // InvocationTime: The time taken for the execution of the method. public long getInvocationTime(); // LastSamplingDateTime: Convert InvocationStartTime to a formatted string public String getLastSamplingDateTime(); // MaxInvocationTime: The maximum time taken for the execution of the method. public long getMaxInvocationTime(); // MinInvocationTime: The minimum time taken for the execution of the method. public long getMinInvocationTime(); // AverageInvocationTime: the averege execution time taken for the execution of the method. public double getAverageInvocationTime(); // ExceptionCount: The number of times the method has thrown an Exception. public long getExceptionCount(); // ExceptionMessage: The message of the last exception occurred. public String getExeptionMessage(); public void setExceptionMessage(String errorMessage);
Using a JMX console (JConsole), statistics from OperationStatistic MBean are available. These statistics are MBean's attributes, and can be navigated under the following hierarchy tree:
Adobe Domain Name:
Depends on Application Server. If the Application Server does not define the domain, the default is adobe.com.
Time taken for the execution of the method. This does not include the time the request is serialized, transferred from client to server, and deserialized.
Average invocation time:
Average time of all invocations that have executed since the server was started.
Max invocation time:
The duration of the longest invocation that has executed since the server was started.
Min invocation time:
The duration of the shortest invocation that has executed since the server was started.
Default is millisecond.
To enable JMX monitoring, the application servers typically need some configuration. See your application server documentation for the specifics.
To view MBeans from JConsole, configure the JBoss application server’s JVM startup parameters. Ensure JBoss is started from the run.bat/sh file.
For WebLogic, you can access the MBean using either remote or IIOP.
Add or uncomment the following three lines in the /opt/IBM/WebSphere/AppServer/java/jre/lib/management/management.properties file (or <Your Websphere JRE>/ lib/management/management.properties):
com.sun.management.jmxremote.port=9999 //any port you like, but make sure you use this port when you connect com.sun.management.jmxremote.authenticate=false com.sun.management.jmxremote.ssl=false