D.2 Limits when using the Central Console

The tables below describe the limits that apply to JP1/IM - Manager and JP1/IM - View when using the Central Console.

Organization of this subsection

(1) JP1/IM - Manager limits
(2) JP1/IM - View limits

(1) JP1/IM - Manager limits

The following table describes the limits that apply to JP1/IM - Manager.

Table D‒2: Limits for JP1/IM - Manager
Item	Limit
Number of logical hosts that use the IM database	9
Number of instances of JP1/IM - View	64^#5
Number of hosts that can be managed by one instance of JP1/IM - Manager (Considering the configuration of agents, this indicates the maximum number of hosts of JP1/IM - Manager and instances of JP1/Base that can be placed directly below JP1/IM - Manager.)	When `close` is specified as the communication type in the event server settings file (`conf`) of JP1/Base on the all agents IM Configuration Management database is set to L size: 2,500 IM Configuration Management database is set to S size or M size: 1,024 When the version of JP1/Base that is placed on the same host as JP1/IM - Manager is 11-10 or earlier, the maximum number of managed hosts is 1,024. If using the IM Configuration Management, you must set the IM Configuration Management database to L size. When there are one or more hosts where a value other than `close` is specified as the communication type in the event server settings file (`conf`) of JP1/Base on the agent In UNIX: 100 In Windows: 62 This value is for a maximum configuration. The number of managed hosts is restricted by the system configuration and network traffic.
Number of hosts that can execute commands from one instance of JP1/IM - Manager	2,500
Event buffer size (number of extracted events that can be buffered from the event database)	2,000
Maximum length of an event acquisition filter^#1 (total size of the event acquisition filters to be applied (total of pass conditions and exclusion-conditions) and the valid common exclusion-condition groups in basic mode)	60 KB When no exclusion-condition group or valid common exclusion-condition group in basic mode is set. 64 KB When an exclusion-condition group or a valid common exclusion-condition group in basic mode is set.
Maximum length of common exclusion conditions^#1	Basic mode: 64 kilobytes (total size of the event acquisition filters to be applied (total of pass conditions and exclusion-conditions) and common exclusion-conditions groups) Extended mode: 15 megabytes Note that the following limitations apply to the items that are specified in the common-exclusion-conditions extended definition parameters: Common exclusion-conditions group name: 1 to 50 bytes Comments: 1,024 bytes Number of event conditions: 256 Total size of event conditions: 64 KB
Maximum length of an event receiver filter^#1	1 MB (total size when more than one event receiver filter is set)
Maximum length of a severe events filter^#1	64 KB
Maximum length of a view filter^#1	1 MB per JP1 user (total size when more than one view filter is set)
Maximum length of an event search^#1	64 KB
Number of event receiver filters	128
Number of conditions that can be set in a filter (applies to passing conditions and exclusion-conditions)	Event acquisition filter: 30 per filter Event receiver filter: 30 per filter Severe events filter: 30 View filter: 5 per filter Event search: 5
Number of filters that can be defined in the list of event acquisition filters	50
Maximum length of a filter name specified in the list of event acquisition filters	50 bytes
Number of common exclusion-conditions that can be defined in the list of event acquisition filters	Basic mode: 30 Extended mode: 2,500
Maximum size of the file containing the list of event acquisition filters	1 MB
Number of queued commands executed by automated actions	65,535
Length of an action definition parameter for an automated action	No limits when using version 09-00 or later. However, the following items specified in an action definition parameter have limit values: Length of an action name: 1 to 50 bytes Length of a comment: 1,040 bytes Length of an event condition: 4,096 bytes Length of a user name: 31 bytes Length of `executing-host-name` `\|` `host-group-name`: 255 bytes Length of a `business-group-name` `\|` `monitoring-group-name`: 2,048 bytes Length of an action: 4,096 bytes Length of an environment variable file name: 255 bytes Size of an automated action definition file: 22 megabytes (23,068,672 bytes)
	When version 08-50 or earlier is used: 5,706 bytes However, the following items specified in an action definition parameter have limit values: Length of an event monitoring condition: 1,040 bytes Length of an action: 4,096 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes Length of a target host name: 255 bytes
Length of a target group name	30 bytes
File size of an event guide information file	1 MB
File size of an event-guide message file	1 MB
Total number of items that can be defined in an event guide information file	1,000
Length of an event-guide message after processing of placeholders (variables) and HTML encoding	196,608 characters^#2
Length of an event guide-message file name that can be specified in an event guide information file	1,024 characters^#2
Number of comparison conditions that can be defined in event guide information	100
Number of correlation event generation conditions that can be defined in a correlation event generation definition file	1,000
Number of filtering conditions for the correlation target range that can be defined in one correlation event generation condition	1
Number of event conditions that can be defined in one correlation event generation condition	10
Timeout period for a correlation event generation condition	1 second to 86,400 seconds (24 hours)
Maximum value that can be specified in the threshold event correlation type	100 events
Number of duplicate attribute value conditions that can be defined in one correlation event generation condition	3
Number of maximum correlation numbers that can be defined in one correlation event generation condition	1
Maximum length of the attribute value used in defining a correlation approval event	2,048 bytes
Number of sets of JP1 events that can be correlated simultaneously by one correlation event generation condition	1,024 sets
Number of sets of JP1 events that can be correlated simultaneously by all correlation event generation conditions	20,000 sets
Health check timeout period	216,000 seconds (60 hours)
Number of characters that can be specified for a URL in IE	2,046 characters
Number of conditions that can be defined in the List of Repeated Event Conditions window	2,500
Total size of the definitions of repeated event conditions	15 megabytes (15,728,640 bytes)
Length of a definition of repeated event condition	No limit However, there are limits for the following items that are related to specifying a repeated event condition: Repeated event condition name: 1 to 50 bytes Comment: 0 to 1,024 bytes Event conditions: 0 to 256 conditions Operand of event condition: 65,536 bytes^#3 Conditions for same attribute values: 0 to 3 conditions Number of seconds as threshold: 1 to 60 Number of events as threshold: 1 to 200 End monitoring period: 1 to 86,400 seconds Time for Checks for suppression to continue: 1 to 86,400 seconds Number of events for Checks for suppression to continue: 1 to 1,000,000
Maximum number of email destinations that can be specified at a time by the email notification function of JP1/IM - Manager	20 Multiple destinations cannot be specified over the maximum length of the command line.
Maximum lengths of items with which mail can be sent by the email notification function of JP1/IM - Manager	Mail address: 256 bytes Mail subject: 512 bytes Mail text: 4,096 bytes One line of mail text: 512 bytes
Number of days that can be specified as the range of events to be collected at login	1 to 31 days
Base time that can be specified for the range of events to be collected at login	0:00 to 23:59
Time that can be specified as the range of events to be collected at login	1 to 744 hours (corresponding to 31 days)
File size of a severity changing definition file	17 MB (17,825,792 bytes)
Number of definitions that can be defined by the severity changing definition function	1,000
Length of one severity changing definition	No limit However, there are limit values for the following items that are related to specifying event conditions for changing severity: Severity change definition name: 1 to 50 bytes Comment: 0 to 1,024 bytes Event conditions: 0 to 256 conditions Operand of event condition: 0 to 4,096 bytes
Number of definitions that can be defined by the display message change function	3,000
Length of one display message change definition	No limit However, there are limits for the following items that are related to specifying event conditions for changing display messages: Display message change definition name: 1 to 50 bytes Maximum length of a message after change: 1,023 bytes^#4 Comment: 0 to 1,024 bytes Event conditions: 0 to 256 conditions Operand of event condition: 0 to 4,096 bytes Maximum size of a display message change definition file: 22 megabytes (23,068,672 bytes)

#1: Because the character string data is stored in Shift-JIS code, the specifiable length of the character string is the same even if JP1/IM - Manager is running in Japanese UTF-8 code.

#2: Both 1-byte and 2-byte characters are counted as one character. For example, AAA is counted as three characters.

#3: For details about the limits other than the size of the operand of the event condition, see 4.4.3(2) Event comparison attributes that can be specified in repeated event conditions.

#4: The message length is based on the encoding settings for JP1/IM - Manager.

#5: If you perform a search in the integrated monitoring database and the search exceeds a limit value, a dialog box containing an error message (KAVB1661-E or KAVB1671-W) will appear in the instance of JP1/IM - View that was used to perform the search.

To Page Top

(2) JP1/IM - View limits

The following table describes the limits that apply to JP1/IM - View.

Table D‒3: Limits for JP1/IM - View
Item	Limit
Number of instances of JP1/IM - View that can be started within a single session (per process^#1)	3^#2
Scroll buffer size (number of events that can be displayed in a window)	2,000
Number of events that can be acquired when a window is refreshed	200
Number of events that can be acquired in a search	2,000
Maximum length of a filter^#3	View filter: 1 MB per JP1 user (total size when more than one view filter is set) Event search: 64 KB
Number of view filters	50
Maximum length of a name of a view filter	50 bytes
Number of condition groups that can be set in a filter (applies to passing conditions and exclusion-conditions)	Event acquisition filter: 30 per filter Event receiver filter: 30 per filter Severe events filter: 30 View filter: 5 per filter Event search: 5
Maximum length that can be entered in the input field of each item in the filter window^#4	Filter name: 50 bytes (Event Acquisition Settings window, Settings for View Filter) 30,000 bytes (Detailed Settings for Event Receiver Filter window) Condition group name, Common exclusion-conditions group name: 50 bytes Items for which multiple attribute values other than the above cannot be specified: 30,000 bytes Items for which multiple attribute values can be specified: - Event ID - User name (Items that specify the names of the users to which the restrictions imposed by the event receiver filter apply) 30,000 bytes (Number of attribute values that can be specified: No restriction) - Other items 30,000 bytes (Number of attribute values that can be specified: Maximum of 100)
Number of instances of the `\|` special character that can be specified when regular expressions are used to specify conditions	1,000 per input field
Number of filters that can be defined in the list of event acquisition filters	50 (when connected to Central Console)
Number of common exclusion-condition groups that can be defined in the list of event acquisition filters	Basic mode: 30 Extended mode: 2,500
Longest environment variable file name that can be specified in the Execute Command window	255 bytes
Longest target host name that can be specified in the Execute Command window	2,048 bytes
Longest action definition parameter for an automated action definition	When connected to JP1/IM - Manager 09-00 or later: No limits when using version 09-00 or later. However, the following items specified in an action definition parameter have limit values: Length of an action name: 1 to 50 bytes Length of a comment: 1,040 bytes Length of an event condition: 4,096 bytes Length of a user name: 31 bytes Length of `executing-host-name` `\|` `host-group-name`: 255 bytes Length of a `business-group-name` `\|` `monitoring-group-name`: 2,048 bytes Length of an action: 4,096 bytes Length of an environment variable file name: 255 bytes When version 08-50 or earlier is used: 5,706 bytes The following limits apply to the individual items specified in the action definition parameter: Length of an event monitoring condition: 1,040 bytes Length of an action: 4,096 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes Length of a target host name: 255 bytes
	When connecting to JP1/IM - Manager version 08-00 to 08-50: 5,706 bytes The following limits apply to the individual items specified in the action definition parameter: Length of an event monitoring condition: 1,040 bytes Length of an action: 4,096 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes
Number of lines of execution results to display in the Execute Command window that can be specified in the Preferences window	100 to 10,000 lines
Size of text data that can be copied to the clipboard	6 MB
Number of conditions that can be defined in the List of Repeated Event Conditions window	2,500
Total size of the definitions of repeated event conditions	15 megabytes (15,728,640 bytes)
Length of a definition of repeated event condition	No limit However, there are limits for the following items that are related to specifying a repeated event condition: Repeated event condition name: 1 to 50 bytes Comment: 0 to 1,024 bytes Event conditions: 0 to 256 conditions Operand of event condition: 65,536 bytes^#5 Conditions for same attribute values: 0 to 3 conditions Number of seconds as threshold: 1 to 60 Number of events as threshold: 1 to 200 End monitoring period: 1 to 86,400 seconds
Number of days that can be specified as the range of events to be collected at login	1 to 31
Base time that can be specified for the range of events to be collected at login	0:00 to 23:59
Time that can be specified as the range of events to be collected at login	1 to 744 hours (corresponding to 31 days)
Number of definitions that can be defined by the severity changing definition function	1,000
Number of definitions that can be specified for a manager host in the non-encryption communication host configuration file for encrypted communication	1,024
Maximum length (in characters) of a manager host name in the non-encryption communication host configuration file for encrypted communication	255 characters
Number of definitions that can be defined by the display message change function	3,000
Length of one display message change definition	No limit However, there are limits for the following items that are related to specifying event conditions for changing a display message: Display message change definition name: 1 to 50 bytes Maximum length of a message after change: 1,023 bytes^#6 Comment: 0 to 1,024 bytes Event conditions: 0 to 256 conditions Operand of event condition: 0 to 4,096 bytes Maximum size of a display message change definition file: 22 megabytes (23,068,672 bytes)
Maximum length that can be entered in the input field in the Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window	Attribute name 32 bytes Attribute value 30,000 bytes

#1: The following viewers and windows are started for each process:

Central Console viewer and Central Scope viewer
IM Configuration Management viewer
Monitoring Tree (Editing) window

#2: The larger the number of active instances of JP1/IM - View, the greater the memory and disk space requirements.

#3: Because character string data is stored in Shift-JIS code, the specifiable length of a character string is the same even if JP1/IM - Manager is running in Japanese UTF-8 code.

#4: Filter windows are the Severe Event Definitions window, Event Search Conditions window, Event Acquisition Settings window , Common Exclusion-Conditions Settings window, Settings for View Filter window, and Detailed Settings for Event Receiver Filter window.

#5: For details about the limits other than the size of the operand of the event condition, see 4.4.3(2) Event comparison attributes that can be specified in repeated event conditions.

#6: The message length is based on the encoding settings for JP1/IM - Manager.

To Page Top