2.2.3 usrconf.properties (User property file for J2EE servers)
- Organization of this subsection
(1) Format
J2SE property file format.
Specify the key as follows:
key-name=value
- How to specify:
-
-
The string up to the linefeed is a value.
-
The line beginning with a hash mark (#) is a comment.
-
If you define a line without a value, the line is ignored.
-
You cannot add alphanumeric strings such as spaces and comments after the value. If you add such values, they will be considered as invalid.
(Example) key-name=value#comment
-
Use the ISO 8859-1 character encoding according to the Java specifications for the characters to be encoded.
-
If the format does not conform to Java specifications, the J2EE server might fail to start.
(Example) When the format contains an invalid Unicode escape sequence (the string after \u is not an appropriate Unicode hexadecimal value).
-
(2) File storage location
-
In Windows
Cosminexus-installation-directory\CC\server\usrconf\ejb\server-name\
-
In UNIX
/opt/Cosminexus/CC/server/usrconf/ejb/server-name/
(3) Functionality
Specify the system properties of the JavaVM that execute the J2EE servers.
If you specify the same key in the usrconf.properties file and in -D of add.jvm.arg of the usrconf.cfg file, the value specified in usrconf.properties is given priority.
If you change the contents of this file while the J2EE server is running, the changes become effective only when the J2EE server is started next.
(4) Keys reserved in a J2EE servers
A J2EE server internally uses the keys beginning with the following prefixes. As a result, the keys beginning with these prefixes must not be used in applications.
-
ejbserver.*
-
webserver.*
-
appclient.*
-
j2eeserver.*
-
manager.j2ee.*
(5) Keys for customization of J2EE servers
You can customize the operations of the J2EE servers by setting the values in the following system property keys.
The keys are classified and described as follows:
(a) Keys beginning with ejbserver.application
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- Note:
-
You can specify the following values in the respective character sets used in the property definitions of the user log functionality (other than the ejbserver.application.InitTermProcessClasses key):
-
Class character sets (character sets used in defining the class name)
Single-byte alphanumeric characters (a-z, A-Z, 0-9), periods (.), dollar signs ($) and underscores (_)
-
Single-byte character sets
Single-byte alphanumeric characters (a-z, A-Z, 0-9), periods (.), dollar signs ($), underscores (_), hyphens (-), vertical bars (|), colons (:), ampersands (&), at marks (@), hash marks (#), and percent signs (%)
If the specified value is invalid, such that it does not fulfill the conditions of the character sets that can be used or is not within the range of the values that can be specified, a warning message is output and a valid default value is used at that point. The valid default value at that point implies the value of the key when the handler-name=default, or the default value of the 'Default values' column.
-
- #1
-
Use the handler name to differentiate between the property values. Specify a class character set from 1 to 1024 bytes beginning with a single-byte alphanumeric character for the handler name. If you specify default, handler name indicates a property that is recognized as the common default value by all CJLogHandler.
- #2
-
Use the following rules for the source of the output destination:
ejb.server.log.directory-value\user or ejb.server.log.directory-value/user
For the value of ejb.server.log.directory, follow the specifications of ejb.server.log.directory. The default value of ejb.server.log.directory of J2EE servers is as follows:
-
In Windows
Cosminexus-working-directory\ejb\J2EE-server-name\user\user-specified-value
-
In UNIX
Cosminexus-working-directory/ejb/J2EE-server-name/user/user-specified-value
-
- #3
-
You specify the logger name when the instances of the logger are acquired with Logger.getLogger (logger-name). The logger name is appended with a dot (.) and must be declared beforehand in ejbserver.application.userlog.loggers property. For details on the logger name, follow the specifications of java.util.logging.Logger.
Specify a class character set from 1 to 1024 bytes beginning with a single-byte alphanumeric character for the logger name. If you specify default, logger name indicates a property that is recognized as the common default value by all CJLogHandler.
The properties identified by the logger names are used for initializing the logger class of the user log functionality.
If a logger name ends with .handlers, there may be confusion when the properties of ejbserver.application.userlog.Logger.logger-name.handlers are specified, and therefore, Hitachi recommends that you do not end a logger name with ".handlers".
(b) Keys beginning with ejbserver.bv
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the threshold value for issuing an alert for the string length during the message interpolation processing performed when constraint violation occurs. You can specify a value in the range from 1 to 2147483647. If you specify a value larger than the value of the system property, the system outputs the KDJE60110-W message and continues the processing. If you specify a non-numeric value or a numeric value outside the specifiable range, the system outputs the KDJE60111-W message and sets the default value. |
10000 |
09-85 |
(c) Keys beginning with ejbserver.client
The following table lists the specifiable key. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify an integer from 1 to 8 as the priority for extracting the requests accumulated in the queues within CTM. Smaller the value higher is the priority. If the specified value is wrong or omitted, 4 will be set. |
4 |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(d) Keys beginning with ejbserver.commonj
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify an integer from 1 to 65535 for the maximum pool size of the thread pool for executing a short-lived Work in WorkManager. |
10 |
08-50 |
(e) Keys beginning with ejbserver.compiler
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the maximum value of the heap size of the javac command that is invoked when a J2EE application is started. Specify the value in the format that is accepted by the -Xmx and -Xms options of the java command. If you specify the value in any other format, the operation may not produce the desired results. Specify as follows:
This property is valid for the Application Server version 09-00-01 or earlier. Even if this property is specified for the Application Server version 09-00-02 or later, the specification is ignored. |
256m |
-- |
|
Specify the initial value of the heap size of the javac command that is invoked when a J2EE application is started. Specify the value in the format that is accepted by the -Xmx and -Xms options of the java command. If you specify the value in any other format, the operation may not produce the desired results. Specify as follows:
This property is valid for the Application Server version 09-00-01 or earlier. Even if this property is specified for the Application Server version 09-00-02 or later, the specification is ignored. |
32m |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(f) Keys beginning with ejbserver.connectionpool
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
- Legend:
-
--: Indicates a version earlier than the version 08-00.
Blank cell: Related information does not exist.
(g) Keys beginning with ejbserver.connector
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify an integer from 1 to 16 for the number of log files of a resource adapter. |
4 |
-- |
|
Specify an integer from 4096 to 2147483647 (units: bytes) for the size of the log files of a resource adapter. |
2097152 |
-- |
|
Specify the contents for initializing the statements when the statements are reused in the statement pooling functionality.
|
true |
08-70 |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(h) Keys beginning with ejbserver.container
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specify whether to enable the database audit trail linkage functionality.
|
false |
-- |
||
Specify operation lock control of an Entity Bean (BMP).
To enable the changes in this property, once delete the J2EE application that is being started and then re-create or re-import it. |
false |
-- |
||
Specify whether to enable the reconnection of EJB home object functionality.
|
false |
-- |
||
Specify an integer from 0 to 2147483 (units: seconds) for the interval to invoke the thread for monitoring the timeout and pool status of an Enterprise Bean. When 0 is specified, monitoring is not performed. The thread for monitoring the timeout and pool status of an Enterprise Bean executes the following processing at the interval specified here:
|
0 |
-- |
2.11 Setting up timeout in the EJB container in EJB Container Functionality Guide |
|
Specify re-connection and re-sending of requests in the EJB client, in the case of a communication failure when invoking the EJB method.
|
VB_TRANSPARENT |
-- |
2.13 Invoking the EJB remote interface in EJB Container Functionality Guide |
|
Specify whether to enable the functionality for controlling the access of Enterprise Bean. For details about the functionality used for controlling the access of Enterprise Beans, see 2.10 Access control for Enterprise Bean in the manual uCosminexus Application Server EJB Container Functionality Guide. This property is not related to the security policy specified in server.policy (security policy file for J2EE servers).
|
false |
-- |
||
Specify an integer from 0 to 153722867280912 (units: minutes) for the interval to invoke the thread for monitoring the timeout of an activated Stateful Session Bean. When you specify either 0 or a value below 0, the timeout is not monitored. If you specify a value greater than 153722867280912, 153722867280912 is set. If you specify a non-numeric value, the default value will be set. |
5 |
-- |
2.11.2 Timeout of a Stateful Session Bean in the EJB Container Functionality Guide |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
Blank cell: Related information does not exist.
(i) Keys beginning with ejbserver.ctm
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
This property is necessary for using the CTM functionality. When you deploy a J2EE application that uses the CTM functionality, the J2EE server activates the schedule queue. At this point, specify a value from 0 to 2147483647 for the standby time (units: seconds). If you specify 0, the standby time continues infinitely and when if you do not specify a value, 180 (seconds) is set. |
180 |
-- |
||
This property is necessary for using the CTM functionality. Specify an alphanumeric character from 1 to 31 or an underscore (_) for the CTM domain name to which the J2EE server belongs. You cannot specify a CTM domain name beginning with 'CTM' or 'ctm'. If you do not specify a value, "CTMDOMAIN" is set. |
CTMDOMAIN |
-- |
3.3.5 CTM domains and CTM domain managers in the Expansion Guide |
|
This property is necessary for using the CTM functionality. Specify an alphanumeric character from 1 to 31, an underscore (_), or a period (.) for the CTM identifier of the CTM daemon that controls the J2EE server. You can, however, use a period (.) only when specifying the identifier as an IP address. You cannot specify a CTM identifier beginning with 'CTM' or 'ctm'. You also cannot specify a name that is same as the CTM domain name. If you do not specify a value, the IP address is set. |
IP-address |
-- |
||
This property is necessary for using the CTM functionality. Specify the host name or the IP address used by CTM in a node-switching environment, wherein multi-home or IP address is inherited. Specify a string of 1 to 64 characters for the host name or IP address. If you do not specify a value, the host name that can be acquired by the hostname command is set. If you specify this property without specifying the ejbserver.ctm.CTMID property, the IP address specified in this property becomes the default CTM identifier. |
host-name-acquired-by-hostname-command |
-- |
||
When un-deploying the J2EE applications that use the CTM functionality, the J2EE server passivates the schedule queue. Specify a value from 0 to 2147483647 (units: seconds) for the standby time (awaiting completion of the running requests) at that point. If you specify 0, the standby time continues infinitely and when if you do not specify a value, 180 (seconds) is set. If you attempt to stop an application via CTM when the application contains some running requests, it is not possible to perform forced termination, and therefore, do not specify 0. |
180 |
-- |
||
Specify whether to use the CTM functionality.
|
|
-- |
||
A J2EE server generates the CTM queue, when J2EE applications that use the CTM functionality are deployed. Specify a value from 1 to 32767 for the length of the CTM queue at this point. If you do not specify a value, the length during the generation of the CTM queue maintained in the CTM daemon (length specified by the -CTMMaxRequestCount option) becomes valid. When the CTM queue is shared, since the CTM queue is already created, the already created length becomes valid instead of the specified value. |
None |
-- |
||
Switches the default lookup name used when no optional name is specified for Enterprise Bean in a configuration using the CTM functionality.
|
false |
09-00 |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(j) Keys beginning with ejbserver.deploy
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specifies whether library JAR annotations will be read when a J2EE application is deployed.
This key is used to restrict the memory usage when you import applications containing a library JAR with a large number of classes and in which the library JAR annotations are not required.
|
true |
09-50 |
14.3 Classes to be loaded and the class path required for loading in Common Container Functionality Guide |
|
Specify whether to disable forced termination of a J2EE application.
|
false |
-- |
||
Specify whether to ignore the exceptions occurred when loading the classes for acquiring the annotation information.
|
false |
08-00 |
14.3 Classes to be loaded and the class path required for loading in Common Container Functionality Guide |
|
Specify an integer (units: seconds) from 0 to 2147483647 for the interval to detect an update in the application setup file. If you specify a numeric character other than 0 and 1 to 2147483647, automatic reloading is performed. Only command reload is accepted. |
0 |
-- |
15.8.6 Update detection interval for J2EE applications in the Common Container Functionality Guide |
|
|
app |
-- |
15.8.2 Scope of reloading in the Common Container Functionality Guide |
|
Specify an integer (units: seconds) from 0 to 2147483647 for the standby time for update of an application setup file. If you specify a numeric character other than 0 or 1 to 2147483647, it is assumed that there is no standby time. |
0 |
-- |
15.8.7 Interval for updating the J2EE application configuration file in the Common Container Functionality Guide |
|
Specify an integer (units: seconds) from 1 to 2147483647 for the maximum standby time until the receipt of the next response sent from a command after the completion of server processing. The commands affected by this property are those classified as update, reference and privilege, from among the commands used in a J2EE server. The commands classified into update, reference and privilege can be checked in the list of commands used in J2EE servers. For details on the commands used in a J2EE server, see 2. Commands Used with a J2EE Server in the uCosminexus Application Server Command Reference Guide. If you specify an invalid value, a warning message is output and the default value will be set. If there is no communication from the command side even after the specified time, the server assumes invalid termination of the command and forcibly cancels command exclusion. The standby time is the total of the time that a command requires to go to and return from the servers and the processing time of the command. |
60 |
-- |
||
Specify whether to scramble the DD files related to DataSource, JavaMail, and ResourceAdapter that are expanded below the working directory. Even if the value of this property is switched and the J2EE server is started, the status of the DD files of the resource that is already imported or deployed does not change, as long as the definition information is not updated.
|
false |
-- |
||
Output the session information file of a Web application in the directory present below the set ejbserver.deploy.session.work.directory-property-value\web\context-root-name. |
|
-- |
||
Specify the target range for generating the classes required for communication, such as stub. Specify ejb during new installation and app during upgradation.
|
ejb |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
Blank cell: Related information does not exist.
(k) Keys beginning with ejbserver.distributedtx
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
- Legend:
-
--: Indicates a version earlier than the version 08-00.
Blank cell: Related information does not exist.
- Note:
-
In the status file of in-process transaction service, a host name or an IP address is incorporated as the identification information of the J2EE server. As a result, you need to stop the J2EE server to change the host name or the IP address. Change the host name or IP address of the storage directory of status file, when customizing the operation settings of the J2EE server. For details about customization of the operation setup for J2EE servers, see 3.15.13 Settings in execution environment in the manual uCosminexus Application Server Common Container Functionality Guide.
(l) Keys beginning with ejbserver.DynamicStubLoading
The following table lists the specifiable key. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specify whether to use dynamic class loading.
|
false |
-- |
3.7.3 Dynamic class loading in the EJB Container Functionality Guide |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(m) Keys beginning with ejbserver.ejb
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
This option uses the existing CMR table during deployment. Generally, a CMR table is generated during deployment so there is no need to use the existing CMR table. However, when recovering from an error, specify this option temporarily.
|
false |
-- |
|
Specify an integer from 1 to 100 for the maximum number of threads that call back the timeout method in TimerService, in the entire J2EE server. |
1 |
-- |
|
Specify an integer from 0 to 2147483646 for the maximum frequency for retrying to call back the timeout method in TimerService. |
1 |
-- |
|
Specify an integer (units: seconds) from 1 to 604800 for the interval for retrying to call back the timeout method in TimerService. |
5 |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(n) Keys beginning with ejbserver.ext
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
If this property is set, it implies:
|
0 |
-- |
5. Operations of J2EE Applications in Operation, Monitoring, and Linkage Guide |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(o) Keys beginning with ejbserver.http
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the port number for the management server. You can specify an integer in the range from 1 to 65535. You cannot specify a port number that is already being used in or secured for another application. Furthermore, do not specify the same value in port numbers of the ports to be used to communicate with the Web server in multiple J2EE servers. The cjstartsv command cannot start up multiple J2EE servers in which identical port numbers are specified. |
28008 |
11-00 |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(p) Keys beginning with ejbserver.instrumentation
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify whether to integrate with the Management Server.
|
true |
-- |
- Legend:
-
--: Indicates a version earlier than 08-00.
(q) Keys beginning with ejbserver.javaee
The following table lists the specifiable key. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
(r) Keys beginning with ejbserver.jca
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the IP address or host name used for communication (receipt and dispatch) in the TP1 inbound integrated function. However, if you cannot resolve the address when the host name is specified, use the default value. |
Valid local address selected automatically by the system |
08-50 |
(s) Keys beginning with ejbserver.jndi
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
- Legend:
-
*: Indicates iteration of the part within brackets (()).
--: Indicates a version earlier than the version 08-00.
(t) Keys beginning with ejbserver.jta
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specify the default value (in seconds) for the timeout time of transactions started on J2EE servers. You can specify an integer in the range from 1 to 2147483647. |
180 |
-- |
3.15.8 Transaction timeout and statement collection in the Common Container Functionality Guide |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(u) Keys beginning with ejbserver.logger
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
- Legend:
-
--: Indicates a version earlier than the version 08-00.
Blank cell: Related information does not exist.
- #:
-
You can set the following names as channel name:
-
Channels for output of Cosminexus system log:
MessageLogFile, MaintenanceLogFile, ExceptionLogFile, ConsoleLogFile, EJBContainerLogFile, WebContainerLogFile, WebServletLogFile, UserOutLogFile, UserErrLogFile, JPAOperationLogFile, JPAMaintenanceLogFile
-
Channels for output of resource depletion monitoring log
MemoryWatchLogFile, FileDescriptorWatchLogFile, ThreadWatchLogFile, ThreaddumpWatchLogFile, RequestQueueWatchLogFile, HttpSessionWatchLogFile, ConnectionPoolWatchLogFile
For details about the acquisition of documents, see 2.3 Acquiring the Data in the manual uCosminexus Application Server Maintenance and Migration Guide.
(v) Keys beginning with ejbserver.management
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(w) Keys beginning with ejbserver.manager
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the settings required for integrating with the Management Server. The Management Server automatically sets these contents in a J2EE server. For details on the contents set up automatically by the Management Server in a J2EE server, see Appendix E.4 Contents set automatically by Management Server to the J2EE server in the uCosminexus Application Server System Setup and Operation Guide. |
None |
-- |
|
Specify the settings required for integrating with the Management Server. The Management Server automatically sets these contents in a J2EE server. For details on the contents set up automatically by the Management Server in a J2EE server, see Appendix E.4 Contents set automatically by Management Server to the J2EE server in the manual uCosminexus Application Server System Setup and Operation Guide. |
false |
-- |
|
Specify the path of the setup file for JP1 integration. |
None |
-- |
|
Specify whether to integrate with JP1. |
false |
-- |
|
Specify a value similar to the address of the ports parameter that is specified in the event server setup file (conf) of the event service of JP1/Base in use. If multiple addresses are specified in the ports parameter, specify any one of the specified addresses. If you use an event service, wherein "0.0.0.0" (default value) is specified in the address of the ports parameter, either omit this key or specify the host name of the local machine or localhost. |
localhost |
-- |
|
Specify an absolute path for the property file for issuing the Management event. If you do not specify the property file, or if the specified file does not exist, the Management event is not issued. For details on property file for issuing the Management event, see 8.2.11 Property file for issuing Management events. |
None |
-- |
|
Specify whether to enable the functionality for issuing the Management event.
If you specify an invalid value, the default value will be set. |
false |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(x) Keys beginning with ejbserver.naming
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the runtime option added in the CORBA Naming Service that is invoked when the CORBA Naming Service is used in the automatic invocation mode (ejbserver.naming.startupMode=automatic or inprocess). Generally, there is no need to set a value in this property. This property is used to determine, take action and avoid any failures in the CORBA Naming Service, when the CORBA Naming Service is used in the automatic invocation mode. For the runtime option, specify the string in the format that is specified in the command line argument of nameserv (specify by adding -J at the beginning of each property and demarcating with a space. It is actually specified in one line). (Example of specification) ejbserver.naming.exec.args=-J-Dvbroker.se.iiop_tp.scm.iiop_tp.listener.port=900 -J-Dvbroker.agent.enableLocator=false If, however, the CORBA Naming Service is used in the in-process mode, you cannot specify the following properties:
This property value is given priority over the values specified in ejbserver.naming.port and vbroker.agent.enableLocator property. If, however, the same property as that specified in ejbserver.naming.exec.args is set in the system properties when the CORBA Naming Service is invoked in the in-process mode, the information set in the system properties is given priority. For details about the properties that you can specify when executing the CORBA Naming Service, see the manual Borland(R) Enterprise Server VisiBroker(R) Developers Guide and the manual Borland(R) Enterprise Server VisiBroker(R) Programmers Reference. |
None |
-- |
|
Specify the host name or the IP address that invoke the CORBA Naming Service that the J2EE server uses. When using the name switching functionality, do not use "localhost" as the host name. Specify the host name or the IP address that the CORBA Naming Service invokes. If the CORBA Naming Service is used in the automatic invocation mode (ejbserver.naming.startupMode=automatic or in-process), specify either the default value ("localhost"), or the host name or IP address that starts the J2EE server. |
localhost |
-- |
|
Specify a name when the name is added to the CORBA Naming Service that is invoked, when the CORBA Naming Service is used in the automatic invocation mode (ejbserver.naming.startupMode=automatic or in-process). Specify the name with a string consisting of alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). This name is used in the parameters of the nsutil command of VisiBroker. If a name is not specified, the name "NameService" is automatically set in VisiBroker. For details about how to use the nsutil command, and also about its usage conditions, see the manual Borland(R) Enterprise Server VisiBroker(R) Developers Guide. |
None |
-- |
|
Specify an integer from 1 to 65535 for the port numbers of the CORBA Naming Service that the J2EE server uses. You cannot specify a port number that is already being used by another application. If the J2EE server is started by specifying a port number that is already being used by another application, the invocation process might not be finished. |
900 |
-- |
|
Specify the access protocol to the CORBA Naming Service that is used in the J2EE servers. Currently, this key supports only corbaname. You can, however, perform the operations even with the protocols (iioploc or iiopname) that were in use in the older versions. |
corbaname |
-- |
|
Specify the invocation mode of the CORBA Naming Service.
|
inprocess |
-- |
|
If the CORBA Naming Service still does not start after the lapse of invocation wait time of the CORBA Naming Service that is specified in ejbserver.naming.startupWaitTime, specify an integer from 0 to 2147483647 for the iteration frequency to await invocation only for the number of seconds specified in ejbserver.naming.startupWaitTime. If you specify 0, the process for checking invocation status of the CORBA Naming Service is not retried. If you specify 0 in ejbserver.naming.startupWaitTime, this property value is invalid. |
9 |
-- |
|
Specify an integer from 0 to 2147483647 for the standby time (units: seconds) until the CORBA Naming Service becomes available when a J2EE server is started. When you specify 0, invocation of the CORBA Naming Service is not awaited. If inprocess is set in ejbserver.naming.startupMode, do not specify 0. |
1 |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #
-
If the J2EE server is started by using the Management Server, do not specify automatic. If you specify automatic, the CORBA Naming Service process is no longer monitored by the operation support functionality of TPBroker and is not restarted even if the process is down.
(y) Keys beginning with ejbserver.rmi
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specify the scope of the functionality for optimizing local invocation.
|
app |
-- |
2.13 Invoking the remote interface of EJB in the EJB Container Functionality Guide |
|
Specify an integer from 2 to 16 for the number of RMI communication log files of a J2EE server. If you specify a non-numeric value, or a numeric value outside the range, or if you do not specify a string, a message is output and the default value will be set. |
4 |
-- |
||
Specify an integer from 8192 to 2147483647 (units: bytes) for the size of the RMI communication log files of a J2EE server. |
1048576 |
-- |
||
Specify the host name or the IP address of the RMI registry and MBean server that the J2EE server uses in a multi-homed host environment. The specified single-byte alphabets are not case-sensitive. |
None |
-- |
||
Specify an integer from 1 to 65535 for the port number of RMI registry used by the J2EE server. You cannot specify a port number that is already being used by another application. If the J2EE server is started by specifying a port number that is already being used by another application, the invocation process may not finish. |
23152 |
-- |
||
If you specify true, the arguments and the return value are not passed by value but are passed by reference, by invoking the EJB method that contains the remote interface. If, however, the range specified in ejbserver.rmi.localinvocation.scope is exceeded when invoking the EJB method, the pass-by-reference functionality becomes disabled. With the help of pass-by-reference, you can reduce the cost generated by copying the value, but, you need to be careful as the original value can be changed by using the reference that has been passed. |
false |
-- |
||
You can specify optional values to fix the request reception port for the statistics information acquisition by the JMX client (such as Administration Agent and JP1/Performance Management - Agent Option for uCosminexus Application Server). Specify an integer from 0 to 65535. You cannot specify a port number that is already being used by another application. If the J2EE server is started by specifying a port number that is already being used by another application, the invocation process may not finish. If you specify 0 for this property, a random value is specified. Therefore, the request reception port might change when the J2EE server is restarted. A JMX client might send a request to the port that was previously used as the request reception port, but the port might have already been used by another process. To avoid this problem, we recommend that you fix the request reception port for statistics acquisition. |
23550 |
-- |
||
Specify an integer from 0 to 86400 for the communication timeout period (unit: seconds) between the client and server. If you specify 0, or if this property is not specified, the timeout does not occur. Note that if a value exceeding 86400 is set, a warning message is output, and there is no timeout. |
0 (seconds) |
-- |
2.11.5 Timeout of RMI-IIOP communication in the EJB Container Functionality Guide |
|
Specify whether the invocation of the remove method of Stateless Session Bean is required.
|
false |
-- |
4.3.1 Notes on implementing the Stateless Session Beans in EJB Container Functionality Guide |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
Blank cell: Related information does not exist.
- #
-
Pass-by-reference can also be set in the EJB from the server management commands.
(z) Keys beginning with ejbserver.security
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the message digest algorithm that is used for authentication of the security management functionality. You can specify MD5, SHA-1, SHA-256, or another message digest algorithm supported by JDK. For details, see java.security.MessageDigest in the Java SE API reference. If you specify an invalid value, it will be changed to the default value. If you change the value that has already been set for this property, you must delete the user and then re-create it. This functionality treats different string values as different message digest algorithms. If you use an algorithm other than SHA-1 to implement security on the EJB client, the version of the EJB client must be 09-70 or later. If the version is earlier than 09-70, authentication fails. If you implement security on the EJB client whose version is earlier than 09-70, you must use SHA-1 as the digest algorithm on the J2EE server used as an authentication server. |
SHA-1 |
09-70 |
(aa) Keys beginning with ejbserver.server
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specify whether to deploy the objects, stored in the HTTP session, on the Explicit heap.
However, if JavaVM option HitachiUseExplicitMemory is disabled, this property is disabled (same as for the case when false is specified). |
true |
08-00 |
||
Specify an integer from 45 to 92233720368547758 for the exclusive timeout period (units: seconds) required to concurrently access the Entity Beans of the same primary key. Specify the timeout period above the default value (45 seconds) and below the java.lang.Long.MAX_VALUE/1000 (seconds). If you specify a value lesser than the default value, the timeout period is considered as 45 (seconds). If you specify a value greater than java.lang.Long.MAX_VALUE/1000 (seconds), the timeout period is considered as java.lang.Long.MAX_VALUE (milliseconds). Similarly, if you specify a value greater than java.lang.Long.MAX_VALUE, the default value is considered. |
45 |
-- |
||
Specify the PRF identifier. If you specify a PRF identifier when the PRF daemon is invoked, specify the same PRF identifier. If the PRF identifier is omitted when invoking the PRF daemon, do not specify the PRF identifier. If the PRF identifiers do not match, the performance analysis trace is not collected. |
PRF_ID |
-- |
||
Specify an integer from 1 to 2147483647 for the upper limit of the thread dump file count, when the J2EE server detects an error and voluntarily outputs the thread dump. If you specify a value outside the range, the default value will be set. If the environment variable JAVACOREDIR is specified, the current value is a total of the number of thread dump files in both the directory specified in the environment variable JAVACOREDIR and the default output destination directory (Windows: Cosminexus-working-directory\ejb\server-name, Unix: Cosminexus-working-directory/ejb/server-name). If there is an external request to output the thread dump, the files of thread dump are output, regardless of the setting of this option. The following are examples of external requests to output the thread dump.
|
256 |
-- |
4. Monitoring Resource Depletion in the Operation, Monitoring, and Linkage Guide |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
Blank cell: Related information does not exist.
(ab) Keys beginning with ejbserver.stateful
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify whether to use the functionality for passivating and activating the Stateful Session Bean.
|
false |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(ac) Keys beginning with ejbserver.stdoutlog
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify whether to enable the automatic flush functionality of the user output log and user error log. The automatic flush functionality is the automatic flush option of java.io.PrintStream used for the output of user output log (user_out[n]log) and user error log (user_err[n].log).
|
false |
08-00 |
(ad) Keys beginning with ejbserver.watch
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify whether to enable the alert output to monitor pending queues of HTTP requests, in the case of the default pending queue.
|
true |
-- |
|
Specify an integer from 1 to 2147483647 (units: seconds) for the interval to monitor the pending queues of HTTP requests, in the case of the default pending queue. |
30 |
-- |
|
Specify an integer from 1 to 100 (units: %) for the threshold value to output alert messages. If the storage ratio of the default pending queue for the requests to be monitored exceeds the value specified in this key, an alert message will be output. |
80 |
-- |
|
Specify whether to output the results to monitor pending queues of HTTP requests to a file, in the case of the default pending queue.
|
true |
-- |
|
Specify whether to enable the depletion monitoring of all the resources.
|
true |
-- |
|
Specify whether to enable the alert output for file descriptor monitoring. Note that file descriptor monitoring cannot be used in Windows and AIX.
|
true |
-- |
|
Specify an integer from 1 to 2147483647 (units: seconds) for the interval for monitoring file descriptor. Note that file descriptor monitoring cannot be used in Windows and AIX. |
60 |
-- |
|
Specify an integer from 1 to 2147483647 for the threshold value to monitor the usage of a file descriptor. When the number of in-use file descriptors exceeds the threshold value, an alert will be output. Set the threshold value in the following manner: The number of file descriptors that can be allocated in the OS processes# > Value acquired from the file descriptor estimation formula > File descriptor threshold value # On some platforms, the system may not have any upper limit. Note that file descriptor monitoring cannot be used in Windows and AIX. |
2147483647 |
-- |
|
Specify whether to output the results of file descriptor monitoring in a file. Note that file descriptor monitoring cannot be used in Windows and AIX.
|
true |
-- |
|
Specify whether to enable alert output of memory monitoring.
If you specify true, make sure that the same value is set for the following Java VM options:
If different values are set, the system might perform Full GC without generating an alert. |
true |
-- |
|
Specify an integer from 1 to 2147483647 (units: seconds) for the memory-monitoring interval. |
60 |
-- |
|
Specify an integer from 1 to 100 (units: %) for the threshold value to monitor the memory usage status. The system generates an alert if it detects a symptom that can trigger Full GC under any of the following conditions: If serial GC is enabled:
If G1 GC is enabled:
|
80 |
-- |
|
Specify whether to output the results of memory monitoring in a file.
|
true |
-- |
|
Specify whether to enable alert output of thread monitoring. Note that you cannot monitor the number of threads in Linux.
|
true |
-- |
|
Specify an integer from 1 to 2147483647 (units: seconds) for the thread monitoring interval. Note that you cannot monitor the number of threads in Linux. |
60 |
-- |
|
Specify an integer from 1 to 2147483647 for the threshold value for monitoring the usage of threads. When the number of generated threads is greater than the threshold value, alert will be output. Set the threshold value in the following manner: The number of threads that can be allocated in the OS processes#>Value acquired from the thread estimation formula>Thread threshold value # On some platforms, the system may not have any upper limit. Note that you cannot monitor the number of threads in Linux. |
2147483647 |
-- |
|
Specify whether to output the results of thread monitoring to a file. Note that you cannot monitor the number of threads in Linux.
|
true |
-- |
|
Specify whether to enable alert output of thread dump monitoring.
|
true |
-- |
|
Specify an integer from 1 to 2147483647 (units: seconds) for the intervals in the thread dump monitoring period. |
30 |
-- |
|
Specify an integer from 1 to 100 (units: %) for the ratio of the threshold value for thread dump monitoring with respect to the maximum value. When the ratio of the current value with respect to the maximum value of number of files of thread dump is greater than the threshold value, alert will be output. If the environment variable JAVACOREDIR is specified, the current value is a total of the number of thread dump files in both the directory specified in the environment variable JAVACOREDIR and the default output destination directory. |
80 |
-- |
|
Specify whether to output the results of thread dump monitoring to a file.
|
true |
-- |
|
Specify whether to enable alert generation for Rate2 in the memory depletion monitoring information that is output by the resource depletion monitoring functionality.
|
true |
Cosminexus Component Container 09-70-12 or later and 09-80-02 or later |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(ae) Keys beginning with ejbserver.webj2ee
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify whether to use the automatic close functionality.
If you specify an invalid value, the default value will be set. |
true |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(af) Keys beginning with https
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the recommended coding suite to be used in HttpsURLConnection.# |
# |
09-00 |
|
Specify the protocol to be used in HttpsURLConnection.# |
# |
09-00 |
- #
-
For details about keys, see the JDC documentation.
(ag) Keys beginning with java
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the factory class for the implementation class of the context delegated by InitialContext of JNDI. The operation for each set value is as follows:
|
com.hitachi.software.ejb.jndi.InsContextFactory |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(ah) Keys beginning with vbj
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the maximum heap size of the java2iiop command that is invoked when a J2EE application is started. Specify the value in the format that is accepted by the -Xmx and -Xms options of the java command. If you specify the value in any other format, the operation may not produce the desired results. Specify as follows:
|
128m |
-- |
|
Specify the initial heap size of the java2iiop command that is invoked when a J2EE application is started. Specify the value in the format that is accepted by the -Xmx and -Xms options of the java command. If you specify the value in any other format, the operation may not produce the desired results. Specify as follows:
|
16m |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(ai) Keys beginning with vbroker
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
- Important note
-
You cannot specify the Cosminexus TPBroker properties that are not described in the following table (if specified, the operations cannot be guaranteed).
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specify whether to use the Smart Agent. Normally, this property need not be set. You use the default settings for this key. When the CTM linkage functionality is valid (true is specified to the ejbserver.ctm.enabled key) true is automatically set up when you start the J2EE server. If the Smart Agent is required for any other purpose than above, set true. Before you specify true for this property, make sure that the Smart Agent has been started and vbroker.orb.htc.oadNoUse=true has been specified. For details about the Smart Agent, see the manual Borland(R) Enterprise Server VisiBroker(R) Programmers Reference. |
false |
-- |
||
Specify the port number of Smart Agent. For details, see the manual Borland(R) Enterprise Server VisiBroker(R) Programmers Reference. |
14000 |
-- |
||
Specify whether the closing of the connection will be controlled when a timeout occurs during the invocation of the EJB method defined as the remote interface.
|
false |
09-50 |
||
Specify whether to invoke the thread for managing the reply receiving threads. To set up vbroker.ce.iiop.ccm.htc.readerPerConnection=true, specify true. |
false |
09-50 |
||
Specify a value from 100 to 30000000 for the upper-limit of the entry count in one communication trace file of Cosminexus TPBroker. |
120000 |
-- |
||
Specify a value from 1 to 256 for the upper-limit of the communication trace file count for Cosminexus TPBroker. |
3 |
-- |
||
Specify a range of 1 to 210 bytes for the path of the output destination of Cosminexus TPBroker trace files. You need to create comtrc and mdltrc as the subdirectories of the specified path beforehand. In the case of default output destination, the subdirectories comtrc and mdltrc are automatically created when the server is started for the first time. Use a forward slash (/) as the delimiter in the directory path. For example, in Windows, if C\temp\work is to be set as the work directory, specify as follows: (Example of specification) vbroker.orb.htc.tracePath=c:/temp/work |
|
-- |
||
Set the IP address of the EJB container for each J2EE server by specifying any optional value. |
None |
-- |
2.14 Fixing the communication port and IP address of the EJB container (TPBroker options) in the EJB Container Functionality Guide |
|
Specify the name of the host where the J2EE server and CORBA Naming Service are allocated. Set up the host name such that the name is resolved as a NAT IP address with the EJB client. Also, if the EJB client does not use NAT, specify settings such that the name is resolved as a J2EE server IP address with the host. |
None |
09-50 |
||
You can set a communication port for each J2EE server, by specifying any optional value. Make sure that the port number is not the same as that of any other program. If this property is not set, Cosminexus TPBroker sets a random value. Moreover, if you specify true in ejbserver.container.ejbhome.sessionbean.reconnect.enabled, make sure to specify the value and then fix the port number. |
0 |
-- |
||
Specify the name of the host where the J2EE server and CORBA Naming Service are allocated. Set up the host name such that the name is resolved as a NAT IP address with the EJB client. Also, if the EJB client does not use NAT, specify settings such that the name is resolved as a J2EE server IP address with the host. |
None |
09-50 |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #
-
These keys are set up for the J2EE server and CORBA Naming Service, if NAT is set up between an EJB client and J2EE server. How you set up the keys depends on the invocation mode of the CORBA Naming Service.
If the invocation mode of the CORBA Naming Service is an in-process and auto-invocation mode, specify these keys in the user property file for J2EE servers. The following is an example of settings where the host name of the computer on which the J2EE server is allocated is MyJ2EEHost:
# CORBA Naming Service invocation mode settings ejbserver.naming.startupMode=inprocess # Settings for communication between the EJB client and J2EE server in a NAT configuration vbroker.se.iiop_ts.proxyHost=MyJ2EEHost vbroker.se.iiop_tp.proxyHost=MyJ2EEHost
If the CORBA Naming Service is invoked automatically as an out-process, specify these keys in both; the user property file for J2EE servers and the user property for J2EE servers ejbserver.naming.exec.args. The following is an example of settings where the host name of the computer on which the J2EE server is allocated is MyJ2EEHost. Specify the settings for ejbserver.naming.exec.args on one line, delimited with spaces for each -J. Also, if a value is set up for ejbserver.naming.exec.args in the existing system, specify that value for the command additionally.
# CORBA Naming Service invocation mode settings ejbserver.naming.startupMode=automatic # Settings for communication between the EJB client and J2EE server in a NAT configuration vbroker.se.iiop_ts.proxyHost=MyJ2EEHost vbroker.se.iiop_tp.proxyHost=MyJ2EEHost ejbserver.naming.exec.args=-J-Dvbroker.se.iiop_ts.proxyHost=MyJ2EEHost -J-Dvbroker.se.iiop_tp.proxyHost=MyJ2EEHost
If the CORBA Naming Service is invoked manually as an out-process, specify these keys in both, the user property file for J2EE servers and the invocation option of the nameserv command. The following is an example of settings where the host name of the computer on which the J2EE server is allocated is MyJ2EEHost:
# CORBA Naming Service invocation mode settings ejbserver.naming.startupMode=manual # Settings for communication between the EJB client and J2EE server in a NAT configuration vbroker.se.iiop_ts.proxyHost=MyJ2EEHost vbroker.se.iiop_tp.proxyHost=MyJ2EEHost
An example of executing the nameserv command is as follows. Note that to execute the nameserv command, specify the settings on one line, delimited with spaces for each -J. Also, if the nameserv command is being executed in the existing system, add a postscript to that command.
nameserv -J-Dvbroker.agent.enableLocator=false -J-Djava.security.policy=="Application-Server-installation-directory\CC\server\sysconf\cli.policy" -J-Dvbroker.se.iiop_tp.scm.iiop_tp.listener.port=port-number -J-Dvbroker.se.iiop_ts.proxyHost=MyJ2EEHost -J-Dvbroker.se.iiop_tp.proxyHost=MyJ2EEHost
(aj) Keys beginning with webserver.application
The following table lists the specifiable key. Note that Default value is the value that is assumed when the key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the version of the Web application that you want to set with the version setup functionality of the Web application. When you specify 2.4, Web applications of version 2.4 or earlier as defined in web.xml are executed as Web applications of version 2.4. When you specify 2.5, Web applications of version 2.5 or earlier as defined in web.xml are executed as Web applications of version 2.5. |
None |
08-20 |
(ak) Keys beginning with webserver.connector
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specify the local IP address that is used by the management server or a local host name that can resolve to the local IP address. The single-byte space before and after the IP address or the host name will be ignored. If you do not specify a value, the wild card address is used. |
None |
-- |
||
Specify the IP address (in decimal notation) or host name of the host to be permitted to access the management server. Note that the local host (the host whose address is associated with localhost#3) can always access the management server implicitly. If this key is omitted, the local host (the host whose address is associated with localhost#3) is the only host that can access the management server. When specifying multiple hosts, demarcate the IP addresses or the host names with a comma (,). If there are no access restrictions, specify only an asterisk (*). The single-byte space before and after the IP address or the host name is ignored. |
None |
-- |
||
Specify an integer from -1 to 2147483647 as the maximum number of request parameters. The valid range of maximum number of request parameters is a total of the request query strings and number of parameters of the form data with the Content-Type header value as application/x-www-form-urlencoded or multipart/form-data. If you do not want to set up the maximum number of request parameters, specify -1. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. If the number of request parameters exceeds the specified value, the following operations are performed depending on the APIs and the KDJE39341-W or the KDJE39342-E message is displayed:
|
10000 |
09-00 |
||
Specify an integer from -1 to 2147483639 (unit: bytes) for the maximum size of form data of a POST request. If the maximum size is not set, specify -1. If the following numeric values or strings are specified, a message is output and the default value is applied:
|
2097152 |
08-50 |
||
Specify the length (in bytes) of the TCP listen queue that stores connection requests from the Web client. You can specify an integer in the range from 1 to 2147483647. The maximum valid specified value or the length of the TCP listen queue that is actually set, is different for every OS. |
511 |
11-00 |
||
Specify the IP address or host name that is used by the NIO HTTP server. Halfwidth spaces before and after the IP address or host name are ignored. If no value is specified, the wildcard address is used.
|
None |
11-00 |
||
Specify whether to perform reverse lookup for conversion of the client's IP address into a host name in response to a request received on the NIO HTTP server. If reverse lookup of a host name is performed, the throughput is degraded. If the IP address cannot resolve to a host name, an IP address in a dot-separated format will be output by the getRemoteHost() method of the javax.servlet.ServletRequest interface or to log files.
|
false |
11-00 |
||
Specify the maximum length of time (in seconds) for which the threads in the thread pool on the NIO HTTP server can continue to be idle. You can specify an integer in the range from 1 to 2147483647. |
60 |
11-00 |
||
Specify the maximum number of successive connections that can be continued without closing a TCP connection. You can specify an integer in the range from 0 to 2147483647. If you do not want to set the upper limit, specify 0. |
0 |
11-00 |
||
Specify the time (in seconds) for which to wait for a request without closing a TCP connection. You can specify an integer in the range from 0 to 3600. If you specify 0, no timeout occurs. |
0 |
11-00 |
||
Specify an integer from 0 to 32767 for the upper limit of the number of HTTP headers included in the HTTP requests. Specifying the value 0 indicates that no headers can be included. Even if the number of included HTTP headers is less than the value of this property, an error occurs if the total header size exceeds the value specified for the webserver.connector.nio_http.limit.max_request_header property. |
100 |
11-00 |
||
Specify (in bytes) the maximum request body size of an HTTP request. You can specify an integer in the range from -1 to 9223372036854775807. If you do not want to set the upper limit, specify -1. If a request body is sent in chunk format, the size of the chunk header must be included in the specified size. |
-1 |
11-00 |
||
Specify (in bytes) the maximum request header size of an HTTP request. You can specify an integer in the range from 7 to 65536. Even if the actual request header size is less than the maximum set for this property, an error occurs if the number of HTTP headers exceeds the value specified for the webserver.connector.nio_http.limit.max_headers property. The two-byte line break code (CR(0x0d)+LF(0x0A)) that indicates the end of the HTTP header must be included in the specified size. |
16384 |
11-00 |
||
Specify the maximum number of the Web client connections that can be established. You can specify an integer in the range from 1 to 2147483647. Note that the actually effective maximum value differs depending on the platform. |
1024 |
11-00 |
||
Specify the maximum number of concurrently executable threads within the web container when the web container executes synchronous servlets via the NIO HTTP server. You can specify an integer in the range from 1 to 2147483647. The value you specify must be equal to or less than the maximum number of threads that can be processed on the NIO HTTP server (value specified for the webserver.connector.nio_http.max_threads parameter). If you specify a value larger than the maximum number of threads that can be processed on the NIO HTTP server, the system outputs the KDJE39010-W message and changes the specified value to the number of concurrent executions for which the web container processes the request. The maximum number of concurrently executable threads that can be controlled by using this parameter includes only the number of threads for synchronous servlets and does not include the number of other threads, such as those for executing asynchronous servlets and for calling back by asynchronous I/O API functions. The total maximum number of threads that can be processed including those that are not used for executing synchronous servlets is specified by using the webserver.connector.nio_http.max_threads parameter. |
100 |
11-00 |
||
Specify the maximum number of threads that can be processed on the NIO HTTP server. You can specify an integer in the range from 1 to 2147483647. |
100 |
11-00 |
||
Specify the minimum number of threads that can be processed on the NIO HTTP server. You can specify an integer in the range from 1 to 2147483647. The value you specify must be equal to or less than the maximum number of threads (the value specified for the webserver.connector.nio_http.max_threads parameter). If you specify a value larger than the maximum number of threads, the system outputs the KDJE39010-W message and changes the specified value to the maximum number of threads. Note that the actually effective maximum value differs depending on the platform. |
10 |
11-00 |
||
Specify the IP address (in decimal notation) or host name of the host to be permitted to access the NIO HTTP server. To specify multiple IP addresses or host names, specify them as a comma-separated list. If there are no access restrictions, specify only an asterisk (*). Note that the local host can always be accessed even if it is not specified. If you specify a null character string or whitespaces, the system outputs the KDJE39009-W message and changes the specified value to the default value. If the host names you specify are unresolvable, the system outputs the KDJE39563-W message and permits only the local host to access the server. Halfwidth spaces before and after each IP address or host name are ignored. |
* |
11-00 |
||
Specify the port number used by the NIO HTTP server. You can specify an integer in the range from 1 to 65535. Do not specify a port number that has already been used by another application or a port number that has not been secured. If you do so, the KDJE39566-E message is output and the J2EE server does not start. |
8008 |
11-00 |
||
Specify an integer from 0 to 3600 for the period until timeout (units: seconds), when requests are received from the Web client. If you specify 0, no timeout occurs. |
300 |
11-00 |
||
Specify the value of the Server header that is automatically added to the response. |
CosminexusComponentContainer |
11-00 |
||
Specify an integer from 0 to 3600 for the period until timeout (units: seconds) when a response is sent to the Web client. When you specify 0, the timeout is not enabled. |
300 |
11-00 |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #1
-
-
The valid maximum value depends on the operating platform.
-
Some of the requests arriving in the Web server are passed to the Web container, therefore, the maximum number of concurrent connections of the Web server to be set up must be greater than the total size of the default pending queue and the pending queue of each URL group and Web application + maximum number of concurrently executing threads in each Web container.
In a servlet or JSP performing the database operations, since it is not possible to obtain greater multiplicity than the number of database connections, you need to increase the number of usable database connections, when increasing the concurrently executing number of Web containers.
When tuning the performance, always consider the following relation and adjust the value of each parameter:
Maximum-number-of-concurrent-connections-of-Web-server > Total-size-of-the-pending-queues-of-each-URL-group-and-Web-application-and-the-default-pending-queue + Maximum-number-of-concurrently-executing-threads-in-each-Web-container
Maximum-number-of-concurrently-executing-threads-in-each-Web-container ≥ Number-of-database-connections
For details on controlling the number of concurrently executed threads in Web containers, see 2.14 Controlling the number of concurrently executed threads in Web containers in the manual uCosminexus Application Server Web Container Functionality Guide.
For details about the number of concurrent connections used for processing in the Web server, reference the manual of the Web server.
-
- #2
-
Whitespace imply single-byte spaces, tabs, LF (0x0a), CR (0x0d) or FF (0x0c).
- #3
-
This is the address that is associated with localhost when the J2EE server starts.
(al) Keys beginning with webserver.container
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
When SOAP request messages arrive from the client of the Web Service, specify whether to receive the SOAP request messages and distribute them to the Web Service implementation class if the Web Service implementation class or Provider implementation class developed using Cosminexus JAX-WS is included even when web.xml is not included in the WAR file either completely or partially.
To avoid the occurrence of situations such as those where an unexpected class is associated with the URL by mistake, or where a user is allowed access from outside, the default value is set to none (false). |
none |
08-00 |
||
When SOAP request messages arrive from the client of the Web Service, specify whether to receive the SOAP request messages and distribute them to the Web Service implementation class if the Web Service implementation class or Provider implementation class developed using Cosminexus JAX-WS is included even when web.xml is not included in the WAR file either completely or partially.
|
lax |
08-70 |
||
Specify the path name of the WAR file for setup, for the Web service implementation class included in the EJB-JAR files#1. The WAR file for setup might be created by the user and auto-generated during deployment. When the WAR file for setup is auto-generated during deployment, this property need not be set up. |
CosminexusWSEE.war |
08-70 |
||
Specify whether to add the HTTP cookie that indicates the server ID to the HTTP response.
If you specify a string other than true or false or if you specify a null character string or a whitespace#2, a message is output and the default value will be set. |
false |
-- |
||
If you choose to add the HTTP cookie that indicates the server ID to the HTTP response, use this key to specify the name of the HTTP cookie. Specify the value as a string from 1 to 64 characters. You can use single-byte alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). The following name is used by the Web container and is case sensitive:
If you specify an invalid value, a warning message is output and the default value will be set. |
ServerID |
-- |
||
If you choose to add the HTTP cookie that indicates the server ID to the HTTP response, use this key to specify the value of the HTTP cookie. Specify the value as a string from 1 to 64 characters. You can use single-byte alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). If you specify true in webserver.container.server_id.enabled, and this property is omitted, or if you specify an invalid value, a null character string, or a whitespace#2, a message is output and the default value will be set. |
String generated using the hash function from the host name and J2EE server name/Web container server name (compatibility functionality). The generated value is a 64-character hexadecimal number. |
-- |
||
Specify whether to enable the default servlet mapping.
|
false |
08-00 |
||
Specify an integer from 0 to 2147483647 for the default size of the pending queues, when the functionality for controlling the number of concurrently executing threads in each Web application is to be used. This functionality is enabled only in the J2EE server mode. |
8192 |
-- |
2.17 Controlling the number of concurrently executing threads in the Web application in the Web Container Functionality Guide |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #1
-
When a user creates the WAR file for setup, the WAR file for setup must be created in such a way that the file matches the relative path within the EAR file specified in this property. Note that the WAR file for setup includes the web.xml that is used for distributing the SOAP request messages to the Web Services included in an EJB-JAR file.
To deploy the exploded-archive-format applications in which the Web service implementation class is included in an EJB-JAR file and the WAR file for setup does not exist, specify the path name from 1 to 255 bytes. Note that the path length is a total of the following A + B + C:
A: Path length of the directory for an exploded-archive-format application
B: Path delimiter (1 byte)
C: Length of the path specified in this property
To change the value of this property, stop the Web applications that include the EJB Web Services. If you change the property value while the Web application is running, the operations cannot be guaranteed. The other applications might become invalid and an unexpected exception might occur.
- #2
-
Whitespace implies single-byte spaces, tabs, LF (0x0a), CR (0x0d) or FF (0x0c).
(am) Keys beginning with webserver.context
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name |
Contents |
Default value |
VR |
Related information |
---|---|---|---|---|
Specify an integer from 0 to 2147483647 (units: seconds) for the interval to detect the update of a Web application. If you specify 0, the update will not be automatically detected. If the reload functionality of a J2EE application is disabled, you cannot set this property. If you set this property, it is ignored. If you specify a non-numeric value, a numeric value outside the range, or a null character string, a message is output and the default value will be set. |
Value set in ejbserver.deploy.context.check_interval (default value: 0) |
-- |
15.8 Detecting updates and reloading the J2EE applications in the Common Container Functionality Guide |
|
Specify a negative integer or a value from 0 to 2147483647 (units: seconds) for the maximum delay time of the delay execution functionality for reloading the Web application. If you specify 0, the delay execution functionality for reloading is not used. If the reload functionality of a J2EE application is disabled, you cannot set this property. If you set this property, it is ignored. If you specify a negative integer, the delay execution functionality for reloading is used without specifying the maximum delay time. |
0 |
-- |
||
Specify the maximum time (in seconds) for which to wait for completion of asynchronous processing before stopping the application. You can specify an integer in the range from 0 to 2147483647. If you specify 0, the system waits for 0 seconds, which means that the system does not wait for completion of asynchronous processing. When the specified time elapses, the system stops the application even if there is asynchronous processing that has not yet been completed. The behavior of asynchronous processing that remains after the application stops depends on the implementation of the application. If all asynchronous processing for the application to be stopped is completed before the specified time elapses, the system immediately stops the application. |
30 |
11-00 |
||
Specify an integer from 0 to 2147483647 (units: seconds) for the time interval required for copying the file that you will update. Specify extra time for the interval. The monitoring of a request that is being processed starts after the lapse of the specified interval from the detection of resource update. If the JSP reload functionality is disabled, you cannot set this property. If you set this property, it is ignored. If you specify a non-numeric value, a numeric value outside the range, or a null character string, a message is output and the default value will be set. |
ejbserver.deploy.context.update.interval (default value: 0) |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(an) Keys beginning with webserver.dbsfo
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the maximum size of the HTTP session attribute information that can be included in the global session information in bytes. |
1024 |
08-00 |
|
Specify whether to enable the size estimation functionality (database session failover functionality) for the HTTP session attribute information.
|
off |
08-00 |
|
Specify the optional name of the DB Connector to be used by the database session failover functionality. |
COSMINEXUS_SFO_DBCONNECTOR |
08-00 |
|
Specify whether to enable the database session failover functionality.
|
false |
08-00 |
|
Specify the compatibility option of the exception that occurs when the HttpServletRequest#getSession method is executed in the error page of the request for which the database session failover functionality is to be controlled.
|
false |
08-70 |
|
Specify the extension for controlling the database session failover functionality. If the extension matches with the extension specified in the URL path, the database session failover functionality will be disabled in the applicable request. The comparison between the specified extension and the URL is not case sensitive. Also, if the extension for controlling the database session failover functionality is not specified, specify a null character string or a comma (,). |
txt,htm,html,jpg,gif,js |
08-00 |
|
Specify a URI for inhibiting the database session failover functionality. If the path of the request URI matches the specified URI, the database session failover functionality is disabled for that request. The comparison of the specified URI with the request URI is case sensitive. If the URI for inhibiting the database session failover functionality is not set, a null character string will be set. |
None |
08-50 |
|
Specify whether to enable the integrity guarantee mode of the database session failover functionality.
|
false |
08-70 |
|
Specify whether to continue or cancel the Web application start processing when the negotiation implemented during the startup of a Web application fails while the database session failover functionality is being used.
|
false |
08-70 |
|
Specify the URI to be used as the reference request of the database session failover functionality. The values that can be specified are as follows:
To specify multiple URIs, demarcate them with a semicolon (;). If you do not want to set up a reference request, specify a null character string. If the specified URI matches with the request URI, this request becomes a reference request. When the specified URI is compared with the request URI, uppercase and lowercase characters are distinguished. |
None |
08-70 |
|
Specify the operations to be performed when the pending queue space is insufficient, and if the database session failover functionality is used while the functionality for controlling the number of concurrently executing threads for Web applications is enabled.
|
false |
08-70 |
(ao) Keys beginning with webserver.errorpage
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify whether to output stack trace in the default error page, when an exception occurs.
If you specify a string other than true or false, or if you specify a null character string or a whitespace#, a message is output and the default value will be set. |
false |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #
-
Whitespace imply single-byte spaces, tabs, LF (0x0a), CR (0x0d) or FF (0x0c).
(ap) Keys beginning with webserver.http
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the character encoding to be used in the request body and query decoding. The characters that can be specified as the default character encoding are the character encoding supported in the JavaVM. For details about the character encoding supported in JavaVM, see the explanation related to the supported encoding in JDK documentation. The strings that can be specified are the character encoding described in the canonical name for the java.nio API and canonical name for the java.lang API and their optional names. |
None |
-- |
|
Specify whether to decode the servlet path and additional path information.
|
false |
08-00 |
|
Specify the character encoding to be used in the encoding of the response body. The characters that can be specified as the default character encoding are the character encoding supported in the JavaVM. For details about the character encoding supported in JavaVM, see the explanation related to the supported encoding in JDK documentation. The strings that can be specified are the character encoding described in the canonical name for the java.nio API and canonical name for the java.lang API and their optional names. |
None |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(aq) Keys beginning with webserver.jsp
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #
-
Whitespace imply single-byte spaces, tabs, LF (0x0a), CR (0x0d) or FF (0x0c).
(ar) Keys beginning with webserver.prf
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify (as a string value) the HTTP header name that is to be output as the operation name in the performance analysis trace event with the ID 0x8236. If you specify nothing, a null character string, or the name of a non-existing header, nothing will be output as the operation name in the event 0x8236. |
None |
11-00 |
(as) Keys beginning with webserver.servlet
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
(at) Keys beginning with webserver.ServletContainerInitializer_jar
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the path of the JAR file that includes the ServletContainerInitializer implementation class as an absolute path. When specifying multiple methods, demarcate them with a comma (,). Use a forward slash (/) as the directory delimiter. The specified path of the JAR file must also be specified for add.class.path in the usrconf.cfg file (option definition file for J2EE servers). |
None |
09-00 |
(au) Keys beginning with webserver.session
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #
-
Whitespace imply single-byte spaces, tabs, LF (0x0a), CR (0x0d) or FF (0x0c).
(av) Keys beginning with webserver.static
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify enable/disable/forcibly disable the functionality for caching static contents.
When this property is false and forceoff, the setting of webserver.static_content.cache.size and webserver.static_content.cache.filesize.threshold becomes disabled. In a Web application, wherein the functionality for caching the static contents is not specified as either enable or disable in the DD file (web.xml) or the HITACHI Application Property file, the value specified in this property becomes valid. In a Web application, wherein the functionality for caching the static contents is set as either enable or disable, the value specified in this property becomes invalid. If, however, you specify forceoff, the value specified in this property becomes valid, irrespective of the settings of the DD file (web.xml) or the HITACHI Application Property file. If a string other than true, false, forceoff, or a null character string or whitespace# are specified, a message is output and the default value will be set. |
false |
-- |
|
Specify an integer from 0 to 2147483647 for the upper limit of the size (units: bytes) that can be cached in the memory when the functionality for caching static contents is enabled. If the value specifying the total cache size in each Web application is exceeded, deletion will begin from the cache with the longest no access time and the deletion of cache repeats until the total size of the cache becomes lesser than the set value. If you specify 0, no upper limit is set for the cacheable size. In a Web application, wherein the cacheable memory size is not set in DD (web.xml) or the HITACHI Application Property file, the value specified in this property becomes valid. In a Web application, wherein the cacheable memory size is set, the value specified in this property becomes invalid. If you specify an invalid value, a value lesser than that specified in webserver.static_content.cache.filesize.threshold, a null character string, or a whitespace#, a message is output and the default value will be set. |
10485760 |
-- |
|
Specify an integer from 0 to 2147483647 for the file size (units: bytes) that can be cached, when the functionality for caching static contents is enabled. A file of a size exceeding the specified value does not get cached. If you specify 0, no upper limit is set for the file size that can be cached. In a Web application, wherein the file size that can be cached is not set in DD (web.xml) or the HITACHI Application Property file, the value specified in this property becomes valid. In a Web application, wherein the file size that can be cached is set, the value specified in this property becomes invalid. If you specify an invalid value, a value greater than that specified in webserver.static_content.cache.size, a null character, or a whitespace#, a message is output and the default value will be set. |
524288 |
-- |
|
Specify an extension to be applied to the character encoding used for static contents. This key is enabled when the webserver.http.response.encoding key is specified. If the value is not specified for the key, this key is disabled. |
None |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #
-
Whitespace imply single-byte spaces, tabs, LF (0x0a), CR (0x0d) or FF (0x0c).
(aw) Keys beginning with webserver.work
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify whether to delete the directory created below the temporary directory for JSP, when starting and shutting down the server.
|
false |
-- |
|
Specify an absolute path for the temporary directory for JSP. Specify the directory name.# Use a forward slash (/) as the delimiter in the directory path. For example, in Windows, if C\temp\work is to be set as the work directory, specify as follows: (Example of specification) webserver.work.directory=c:/temp/work |
|
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
- #
-
The length of the file name is restricted based on the OS to be used. For example, in Windows, the file name is restricted to around 250 bytes. As a result, the servlets and JSPs cannot be executed at a location wherein the directory hierarchy is deep. Particularly, a file name generated from a JSP file becomes longer in proportion to the depth of the directory hierarchy deployed in a Web application and it may not be possible to generate a Java file for a JSP file. To avoid this, make a shallow hierarchy of the directories deployed in a Web application and specify a shallow directory hierarchy by an absolute path in the property webserver.work.directory. For details on the Cosminexus work directory, see Appendix C.1 Work directory of the J2EE server in the manual uCosminexus Application Server System Setup and Operation Guide.
(ax) Keys beginning with webserver.xml
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify whether to check if the tag library descriptor (TLD file) in the Web application of Servlet 2.3 has been written as per the schema coded in DTD. The specification of this property is disabled in web.xml invoked in the J2EE server mode and in the TLD files of the Web applications of Servlet 2.4 and later versions. All the TLD files included in the Web applications of Servlet 2.4 and later versions are checked, irrespective of the version of TLD. You specify the following values:
|
true |
-- |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(ay) Keys beginning with mail.mime
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specify the default character code set to be used in JavaMail. If this property is omitted, the file.encoding property of J2SE is used. This property allows you to change the default character code set applied to files that are used when messages are sent. |
None |
-- |
|
Specify whether to convert the line break code to CR-LF if the data meets all of the following conditions. If you set false for this property, the line break code is converted.
|
false |
-- |
|
Specify whether to decode an invalid email header that violates RFC 2047 (a delimiter is not included at the start of encoded text). Examples of invalid encoding that violates RFC 2047 are as follows:
|
true |
-- |
|
See the standard specifications. |
false |
09-50 |
|
See the standard specifications. |
false |
09-50 |
|
See the standard specifications. |
true |
09-50 |
|
See the standard specifications. |
true |
09-50 |
|
See the standard specifications. |
false |
09-50 |
|
See the standard specifications. |
false |
09-50 |
- Legend:
-
--: Indicates a version earlier than the version 08-00.
(az) Keys beginning with manager.j2ee
The Management Server automatically sets this content in a J2EE server. Note that Default value is the value that is assumed when a key is not specified.
Because this key is used internally, do not specify or change the settings if nothing is specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name |
Contents |
Default value |
VR |
---|---|---|---|
Specifies information required to link with the Management Server. Because the Management Server automatically specifies this information, you cannot edit this key manually. For details about the information that the Management Server specifies automatically, see Appendix E.4 Contents set automatically by Management Server to the J2EE server in the manual uCosminexus Application Server System Setup and Operation Guide. |
none |
11-00 |
(6) Examples of coding
ejbserver.deploy.stub.generation.scope=ejb ejbserver.compiler.jvm.maxHeapSize=256m ejbserver.compiler.jvm.minHeapSize=32m ejbserver.naming.host=localhost ejbserver.naming.port=900 ejbserver.naming.protocol=corbaname ejbserver.naming.startupMode=inprocess ejbserver.naming.startupWaitTime=1 ejbserver.naming.startupRetryCount=9 ejbserver.logger.enabled.*=Error,Warning,Information,Debug ejbserver.logger.channels.define.MessageLogFile.filenum=2 ejbserver.logger.channels.define.MessageLogFile.filesize=1048576 ejbserver.application.InitTermProcessClasses=InitTermClass1,InitTermClass2 webserver.connector.http.permitted.hosts=host1,host2 webserver.work.directory=c:/work