MainView for JAVA Environments V3.1 is now available (GA 6/21/2018) and in this new release are many features requested by you, the active users, including the following capabilities:
Discover and monitor Traditional WAS environments
Automatic target Profiles can be created using JMX Port 0
See data from the IBM Health Center with MainView for Java Environments:
If MainView for Java Environments is monitoring a JVM that is instrumented for IBM Health Center, these views become available:
System properties information
Detailed garbage-collection data
Class histogram data
Object Allocation data
Identify whether product setup is complete by using the EZJE menu
Update product initialization and environmental parameters on the PARMEDT view
Automatic definition of NGL structures
Convert version 2.1 targets to version 3.1 targets
Enhanced capture of diagnostic data either when the monitor is stopped by using STDOUT, STDERR and SYSOUT stopped or while it’s still running using print commands from the DBUGINFO view.
View the task number and transaction ID for threads on CICS targets and quickly navigate into MainView for CICS if it is available.
New views displaying thread CPU data for SMF records on JZOS targets
Enhanced logging of product data
New metric views from the MainView Data Dictionary
For more information about the release follow this link.
Watch this short video demonstration including these new features here.
MainView for Java Environments provides a comprehensive solution for managing Java running on the mainframe, including auto discovery of JVMs and extensive data on JVM performance, memory usage and thread activity. Although no other MainView monitors are required for implementing MVJE, existing MainView users will also see all the MainView unique benefits of centralized architecture, smart alarms and alerts, guided navigation for root cause identification, and analysis. For more information about MVJE, visit the website.