This subsection describes the main files used when setting up a system that executes batch applications. For details on each file, see 3. Files Used on Batch Servers in the uCosminexus Application Server Definition Reference Guide.
- Note
- To change a file, stop the batch server. The operation will not be guaranteed if you change the contents of a file while the batch server is running.
- usrconf.properties (user property file for batch server)
This file specifies user properties of batch servers. The file specifies the Naming Service, connection, container, log, security, and the CTM usage that a batch 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 batch server)
This file specifies the JavaVM startup options of a batch 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 batch server)
This file specifies the security policy of a JavaVM on which the batch 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
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 F-1 Types of troubleshooting data and whether or not specifying the settings (for a system that executes batch applications)
Type of data | Possibility of specifying the settings |
---|
snapshot log | #1 |
Trace based performance analysis file | N#2 |
Batch server log | ![[Figure]](figure/zueng020.gif) |
Application user log | Y |
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 | ![[Figure]](figure/zueng020.gif) |
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 the 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 snapshot log collection target definition files. 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 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.