3.2.3 Overview of data acquisition settings (Systems executing batch applications)
For changing the default settings (output destination or log size) of data or acquiring the data that is not acquired by default, edit the Easy Setup definition file or the user-defined file. This subsection describes whether you must specify the settings for the systems executing batch applications to acquire the data (log) in advance. This subsection also provides an overview of the setting methods.
For each data type, the following tables separately describe the data items for which the data collection settings must be specified and the data items for which settings must only be specified when changing the default data collection settings.
-
Data items that require data collection settings
Table 3‒5: Data acquisition settings (Systems executing batch applications) Type of material
Settings for collecting the material
Reference manual
Reference point
Application user log
Set up the logger or handler settings, output level of a log, size and number of files in the <configuration> tag of logical J2EE server (j2ee-server), in the Easy Setup definition file.
Use server.policy to specify the security policy.
uCosminexus Application Server Expansion Guide
Chapter 8
Statistical information of OS
In Windows, specify the performance data collection settings of system resources on the Windows system monitor.
This manual
User dump
In Windows, specify the settings for collecting user dumps by using the Windows debug tool.
This manual
core dump
In Unix, specify the settings for collecting core file using the simple setup definition file and shell commands.
This manual
JavaVM material
Set up the thread dump of JavaVM, output methods or output contents of the JavaVM logs (JavaVM log files) in the Easy Setup definition file. You can also set up file names to the output event log or output level of logs of the Explicit Memory Management functionality.
This manual
- #
-
The setting method is same as that of the J2EE server. Substitute J2EE server in the description of reference sections to batch server, and read.
-
Data items that must be set up only when changing the default data collection settings
Table 3‒6: Data acquisition settings (Systems executing batch applications) Type of material
Settings for collecting the material
Reference manual
Reference point
snapshot log
To change the collection destination, collection method, and collection timing of the snapshot log, edit the user definition file
This manual
Management Server log
Use mserver.properties (environment settings file of the Management Server) to set up the output level of a log and number of log files.
This manual
Trace based performance analysis file
Use mserver.properties (environment settings file of Management Server) to specify the number of trace based performance analysis files.
Specify the trace acquisition level of performance tracer or number of PFR trace files in the <configuration> tag of logical performance tracer (performance-tracer) in the Easy Setup definition file.
This manual
7.5#
Batch server log
Set up the output level of a log, size, and number of files in the <configuration> tag of logical J2EE server (j2ee-server), in the Easy Setup definition file.
When the settings of system log output are enabled by ejbserver.logger.systemlog.enabled in the <configuration> tag of logical J2EE server (j2ee-server), the start and stop of batch server and abnormal termination messages are output in an event log (in UNIX, syslog).
This manual
Operation information file
Set up the output destination of an operation information file or number of files in the <configuration> tag of logical J2EE server (j2ee-server), in the Easy Setup definition file.
uCosminexus Application Server Operation, Monitoring, and Linkage Guide
3.3.3
Cosminexus Manager log
Use manager.cfg to specify the number and size of the files of the integrated log.
This manual
Console log
Use adminagent.properties to specify the application of output, the number, and the size of the console log files.
uCosminexus Application Server Operation, Monitoring, and Linkage Guide
11.3#
Resource adapter log
Specify the application of log output for each resource adapter using Server management commands.
Set up the output level of a log, size, and number of files in the <configuration> tag of logical J2EE server (j2ee-server), in the Easy Setup definition file.
This manual
Cosminexus TPBroker trace file
Set up the output destination of trace files or number of files in the Easy Setup definition file (in the <configuration> tag of logical J2EE server (j2ee-server)) and the usrconf.bat (in UNIX, usrconf) and usrconf.properties for the server management commands.
This manual
Server management command log
You can use usrconf.bat (in UNIX, usrconf) and usrconf.properties for server management commands to specify the log output level.
uCosminexus Application Server Application Setup Guide
3.4
- #
-
The setting method is same as that of the J2EE server. Substitute J2EE server in the description of reference sections to batch server, and read.
The snapshot log can collects the logs described in table, in batches. In the trace file of Cosminexus TPBroker, the material that can be collected and the material that cannot be collected are mixed. In addition to this, you need to make the settings for collection and add the collection destination of the snapshot log for those logs that cannot be acquired with default settings. Collect user dumps (in Windows) or core dumps (in UNIX) for specific file names. To collect the material when an error occurs, you need to use the user created command at error detection time.
Note that you cannot change the log output destination for the following logs:
-
The install.log created during setup or log files of migration commands
-
The Java thread dump files output to the following directories:
-
In Windows
working-directory\ejb\server-name
-
In UNIX
working-directory/ejb/server-name
-
For details about the log types or default values, channel names, details of logs that can be acquired or acquisition methods, see 2.4 Types of Required Data.