6.2.2 Differences in functionality from previous versions

The following table shows the differences in functionality between how past versions collected information about the application operating status and how version 10-00 collects information about the operating status of processes.

Table 6-1 Differences from previous versions in the collection of information about the operating status of processes

FunctionalityCollection of information about the application operating status in versions 09-00 and earlierCollection of information about the operating status of processes beginning with version 10-00
Acquisition of command lineYesYes
Maximum value for a command line that can be acquired119 bytes4,096 bytes
Collection of performance information for specific processesNo#1Yes#2
Maximum value for monitoring conditions that can be specified127 bytes4,096 bytes
Maximum value for monitoring conditions that can be displayed in PFM - Web Console31 bytes4,096 bytes
Case sensitivity of monitoring targetsNoYes#3
Identifying monitoring conditions by labelNoYes#4
Grouping targets when setting process monitoring
  • Programs (Name)
  • Services (Argument List)
  • Programs (Program Name)
  • Command line (Command Line)
Legend:
Yes: Can be executed.
No: Cannot be executed.
#1
Always collects performance information for all processes.
#2
Collects performance information only for the processes for which process monitoring has been set.
#3
By default, letter case is distinguished. For details, see 6.2.7 Distinguishing the letter case of monitoring targets.
#4
Use the MonitoringXX Label field to identify a process.

You can use the jpcappcvt command to upgrade application definitions that were set in version 09-00 or earlier to application definitions for version 10-00. For details about the jpcappcvt command, see 9. Commands.

Reference note
There is no need to upgrade application definitions that were set in version 09-00 or earlier if they are not being extended into version 10-00.