D. List of Limits
This appendix describes the limits of JP1/Base.
|
Item |
Limits |
|---|---|
|
Maximum length of a line in the event service environment settings (event server settings file, forwarding settings file, and distribution definition file) |
1,023 bytes |
|
Maximum length of a filter for a forwarding settings file |
64 kilobytes |
|
Maximum length of an event server name |
255 bytes (However, you can specify no more than 240 bytes for a Windows jevregsvc command.) |
|
JP1 user name |
1 to 31 bytes |
|
JP1 user password |
6 to 32 bytes |
|
OS-user-name |
1 to 64 bytes (including a domain name. However, the maximum length varies depending on the OS.) |
|
OS user password |
1 to 64 bytes |
|
Information-search-user-name |
8 to 64 bytes (including aduser/) |
|
Maximum length of a server host name |
255 bytes |
|
Maximum length of a logical host name |
196 bytes (63 bytes recommended) for Windows# 255 bytes (63 bytes recommended) for UNIX# |
|
Maximum length of a line in a user-permission level file |
4,096 bytes |
|
Maximum length of a line in a user mapping definition file |
4,096 bytes |
|
Number of JP1 users that can log into the authentication server simultaneously |
10,000 users |
|
Number of JP1 users that can be registered |
3,000 users |
|
Number of OS users that can be registered |
2,048 users |
|
Number of JP1 users that can be registered in the user permission level file |
3,000 users |
|
Maximum length of a line in a health check definition file |
1,023 bytes |
#: The limits above are those for JP1/Base. Some of these limits do not apply to the items for the cluster software. When specifying a logical host name with JP1/Base, note that the name must not exceed the limit for the cluster software. We recommend 63 bytes or less for actual operation.