7.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.
|
Functionality |
Collection of information about the application operating status in versions 09-00 and earlier |
Collection of information about the operating status of processes beginning with version 10-00 |
|---|---|---|
|
Acquisition of command line |
Yes |
Yes |
|
Maximum value for a command line that can be acquired |
119 bytes |
4,096 bytes |
|
Collection of performance information for specific processes |
No#1 |
Yes#2 |
|
Maximum value for monitoring conditions that can be specified |
127 bytes |
4,096 bytes |
|
Maximum value for monitoring conditions that can be displayed in PFM - Web Console |
31 bytes |
4,096 bytes |
|
Case sensitivity of monitoring targets |
No |
Yes#3 |
|
Identifying monitoring conditions by label |
No |
Yes#4 |
|
Grouping targets when setting process monitoring |
|
|
- 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 7.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 10. Commands.
- 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.