This subsection describes the main files used when setting up a system that executes J2EE applications. For details on each file, see 2. Files Used on J2EE Servers in the uCosminexus Application Server Definition Reference Guide.
- Note
- To change a file, stop the J2EE server. The operation will not be guaranteed if you change the contents of a file while the J2EE server is running.
- usrconf.properties (user property file for J2EE server)
This file specifies the user properties of a J2EE server. It specifies the Naming Service, transaction, connection, container, log, and security that the J2EE server uses.
The file storage destination is as follows:
- In Windows
Cosminexus-installation-directory\CC\server\usrconf\ejb\server-name\usrconf.properties
- In UNIX
/opt/Cosminexus/CC/server/usrconf/ejb/server-name/usrconf.properties
- usrconf.cfg (option definition file for J2EE server)
This file specifies the JavaVM startup options of a J2EE server.
The file storage destination is as follows:
- In Windows
Cosminexus-installation-directory\CC\server\usrconf\ejb\server-name\usrconf.cfg
- In UNIX
/opt/Cosminexus/CC/server/usrconf/ejb/server-name/usrconf.cfg
- server.policy (security policy file for J2EE server)
This file specifies the security policy of a JavaVM on which the J2EE server is running.
The file storage destination is as follows:
- In Windows
Cosminexus-installation-directory\CC\server\usrconf\ejb\server-name\server.policy
- In UNIX
/opt/Cosminexus/CC/server/usrconf/ejb/server-name/server.policy
- hitachi_web.properties (Web application property file for J2EE server)
This file specifies the properties of each Web application. Note that the setup of the properties of the entire J2EE server is specified in usrconf.properties.
The file storage destination is as follows:
- In Windows
WEB-INF-directory-of-Web-application\hitachi_web.properties
- In UNIX
WEB-INF-directory-of-Web-application/hitachi_web.properties
When you change hitachi_web.properties, create a WAR file, and re-import.
The following table describes data required for troubleshooting, and whether or not specifying the settings for troubleshooting is required. For details on specifying the settings, see 3. Preparation for Troubleshooting in the uCosminexus Application Server Maintenance and Migration Guide.
Table C-1 Types of troubleshooting data and whether or not specifying the settings (for a system that executes J2EE applications)
Type of data | Possibility of specifying the settings |
---|
snapshot log | #1 |
Trace based performance analysis file | N#2 |
J2EE server log | ![[Figure]](figure/zueng020.gif) |
SFO server log | ![[Figure]](figure/zueng020.gif) |
Web server log | ![[Figure]](figure/zueng020.gif) |
Redirector log | ![[Figure]](figure/zueng020.gif) |
J2EE application user log | Y |
In-process HTTP server log | ![[Figure]](figure/zueng020.gif) |
Statistics file | ![[Figure]](figure/zueng020.gif) |
Resource adapter log | ![[Figure]](figure/zueng020.gif) |
Trace file of Cosminexus TPBroker | ![[Figure]](figure/zueng020.gif) |
Log of Cosminexus DABroker Library | N |
Statistical information of the OS | Y |
User dump | Y |
core dump | Y |
JavaVM data | Y |
Log of server management commands | ![[Figure]](figure/zueng020.gif) |
- Legend:
- Y: Settings must be specified when collecting data.
: Settings must be specified only when changing the default settings for collecting data.- N: Settings need not be specified.
- #1
- Collect the snapshot logs using the snapshotlog command. In such a case, during the execution of the command, specify the already set up list files as arguments. For details on the snapshotlog command, and the snapshot logs that can be collected with the default settings, see snapshotlog (collect snapshot logs)of 11.2 Details of commands used in log operations. To change the snapshot log collection destination, edit the definition files for which the snapshot logs are to be collected. For the snapshot log collection target definition files, see 12.2 Definition file for collecting snapshot log in the uCosminexus Application Server Definition Reference Guide.
- #2
- During daily system operations, when you start the performance tracer by executing the cprfstart command, you can specify the PRF trace collection level and the number of files. For collecting the trace based performance analysis file, see 7.3.1 How to collect the trace based performance analysis files in the uCosminexus Application Server Maintenance and Migration Guide.
The logs described in the Table C-1 can be collected in a batch as the snapshot log. However, some trace files of Cosminexus TPBroker can be collected, while some cannot be collected. Besides this, you must specify the settings for collecting the log that cannot be collected with the default settings of the snapshot log, and add them to the snapshot log collection destination.
Note that you cannot change the log output destination of the following logs:
- install.log created during setup, and log files of the migration commands
- Java thread dump files that are output to the following directory:
In Windows
work-directory\ejb\server-name
In UNIX
work-directory/ejb/server-name
For the types and default values of logs, channel names, details of the logs that can be collected and collection methods, see 2.4 Types of data that must be collected in the uCosminexus Application Server Maintenance and Migration Guide.