A.3 Changes in 10-00

• The following operating systems are no longer supported:

  • HP-UX 11i V2 (IPF)

  • Solaris 9 (SPARC)

  • Solaris 10 (x64)

  • Solaris 10 (x86)

  • AIX 5L V5.3

  • Red Hat Enterprise Linux(R) AS 4 (AMD64 & Intel EM64T)

  • Red Hat Enterprise Linux(R) AS 4 (IPF)

  • Red Hat Enterprise Linux(R) AS 4 (x86)

  • Red Hat Enterprise Linux(R) ES 4 (AMD64 & Intel EM64T)

  • Red Hat Enterprise Linux(R) ES 4 (x86)

  • Red Hat Enterprise Linux(R) 5 (AMD/Intel 64)

  • Red Hat Enterprise Linux(R) 5 (IPF)

  • Red Hat Enterprise Linux(R) 5 (x86)

  • Red Hat Enterprise Linux(R) 5 Advanced Platform (AMD/Intel 64)

  • Red Hat Enterprise Linux(R) 5 Advanced Platform (IPF)

  • Red Hat Enterprise Linux(R) 5 Advanced Platform (x86)

• The following operating systems are now supported:

  • Linux 6 (x64)

  • Linux 6 (x86)

  • Windows Server 2012

• JP1 Performance Management can now link with Job Management Partner 1/IT Service Level Management Description, User's Guide, Reference and Operator's Guide.

• Performance data can now be collected in IPv6 environments.

• Limits now apply to the process that refines on-screen information based on keywords.

• A point regarding the Agents window has been added.

• You can now specify filter conditions when searching from a window.

• Data group buttons have been added that you can use to navigate to the previous or next time band of a report.

• The description of backup and restoration has been revised.

• Information about the backup and restoration of the information set in definition templates for process monitoring has been added.

• Information about migrating definition information and operation monitoring data has been added.

• JP1 event settings have been added to the health check agent properties.

• Information about the output format of troubleshooting logs has been added.

• The start time and end time can now be hidden when displaying a report.

• An access control feature based on business groups has been added, allowing you to set the range of information individual users can monitor.

• Business group ordinary user has been added as a user permission for Performance Management.

• You can now use the following commands to create and edit business groups:

  • jpcconf bgdef check

    Verifies the contents of a business group definition file.

  • jpcconf bgdef delete

    Deletes definition information for a business group.

  • jpcconf bgdef display

    Displays definition information for a business group.

  • jpcconf bgdef export

    Exports definition information for a business group to a file.

  • jpcconf bgdef import

    Imports definition information for a business group from a file.

  • jpcconf bgdef list

    Displays a list of business group names.

• In the Edit Agents > New Agents window, you can now use keywords to refine the list of agents.

• The jpctool service sync command can now be used to synchronize the service information registered in PFM - Manager and PFM - Web Console.

• The autolabel feature can now display tooltips that show data values plotted on a graph.

• The default color for graph series has been changed. You can also now change the color used to display series in a graph.

• A cautionary note about pie graphs has been added.

• Information about how to plan report definitions to avoid a memory shortage when displaying reports that use graphs has been added.

• A cautionary note describing what to do when a report takes a long time to display has been added.

• Information about the temporary files created when a graph image is displayed or output has been added.

• The Show Grid graph option now only applies to the graph in the foreground.

• When a series group contains 3D clustered column/3D stacked column graphs or line graphs, any group can now be displayed in the foreground regardless of the order of the series groups.

• The sequence in which the Y axis scales are displayed in combination reports now conforms to the order in which the graphs are drawn.

• The following conditions regarding combination reports have been added or changed:

  • The conditions under which some or all of a graph or legend is invisible and the legend breaks over two or more lines

  • The conditions under which part of the legend is invisible due to an excessive number of characters

  • The conditions under which the series group name overlaps the legend

  • The conditions under which a line break appears in the graph title

• The user-created alarm table can now be displayed as a separate tree from the table of alarms defined by monitoring templates.

• The maximum number of alarms you can define in one alarm table has been increased from 50 to 250. Accordingly, the maximum number of alarms you can define in one alarm definition file has been increased from 50 to 250.

• The circumstances that cause an alarm event with the message text Alarm Cleared to be generated have been changed. Accordingly, a description of alarm evaluation when PFM - Agent or PFM - RM stops has been added.

• The following message text can now be output in an agent event relating to the operation status of a monitored system:

  • Monitored System Available

  • Monitored System Unavailable

• Depending on the confirmation status of an agent alarm, the following message text can now be output in an agent event:

  • State change(Unconfirmed)

  • State information

  • State information(Unconfirmed)

• The jpcprocdef command has been added.

• A cautionary note about the health check function has been added.

• Troubleshooting procedures have been added for the following circumstances:

  • When the Correlator service takes a long time to start after PFM - Manager restarts

  • When the Agent Collector service or Remote Monitor Collector service fails to start

• Windows firewall information is now part of the troubleshooting information collected when a problem occurs in a Windows environment.

• A list of command locations has been added.

• Information about the settings of the health check function when PFM - Manager version 09-00 or later is installed has been added.

• You can now limit the information available to users with general user permission in the Agents tree.

• Process monitoring in PFM - Agent for Platform and PFM - RM for Platform can now be configured in the Agents tree.

• Information about the number of user accounts has been added.

• The following commands can now be used to create and edit the Agents tree.

  • jpcconf agttree export

    Exports an Agents tree definition file.

  • jpcconf agttree import

    Imports an Agents tree definition file.

• Information about how to handle a situation in which performance data collection is skipped has been added.

• The OK button has been removed from the Service Properties window, and Close and Apply buttons have been added.

• Information about the retention period for records in the Store database has been added.

• Reports can now be displayed over several pages when there are too many graph legends.

• The information cached to memory when displaying reports can now be output to a file.

• The maximum number of lines of table data displayed in the Print window and in HTML reports can now be restricted.

• The maximum number of drilldown data items in a graph can now be restricted.

• When monitoring alarms using multi instance records, users can now be notified when the value of a field returns to a normal range.

• An example of alarm evaluation when a monitoring time range and damping condition are specified has been added.

• An example of specifying an abnormal condition and warning condition in an alarm condition has been added.

• The message sent when a JP1 event is issued can now be defined within a range from 0 to 1,023 bytes.

• Information about the limits that apply to the number of alarm tables you can define in one Agent product has been added.

• Information about the character encodings used during alarm evaluation has been added.

• The setup command can now be executed in non-interactive mode.

• Information about making changes to a logical host environment after starting operation has been added.

• You can now choose how the system determines which Action Handler service is selected by default in the New Alarm > Action Definition window and Edit > Action Definitions window of PFM -Web Console when issuing a JP1 event.

To Page Top