This subsection describes the items that can be set up for acquiring the in-process HTTP server log.

In the in-process HTTP server, the access log, trace based performance analysis, thread trace, and the communication trace are output for supporting the application development, for performance analysis at operation time, and for troubleshooting at failure detection time. For these files, you can change the number of files and the file size in the Easy Setup definition file.

The following table describes the settings that you can change for acquiring the in-process HTTP server log and parameters of the Easy Setup definition file corresponding to the items.

Table 3-18 Settings for acquiring the in-process HTTP server log

Log or trace	Items	Corresponding parameters of the Easy Setup definition file
Access log	Availability access log output	webserver.logger.access_log.inprocess_http.enabled in the <configuration> tag on a logical J2EE server (j2ee-server) (By default access log is output)
	Access log file name	webserver.logger.access_log.inprocess_http.filename in the <configuration> tag on a logical J2EE server (j2ee-server)
	File size of the access log	webserver.logger.access_log.inprocess_http.filesize in the <configuration> tag on a logical J2EE server (j2ee-server)
	Number of files of access log	webserver.logger.access_log.inprocess_http.filenum in the <configuration> tag on a logical J2EE server (j2ee-server)
	Format name of the access log	webserver.logger.access_log.format_list in the <configuration> tag on a logical J2EE server (j2ee-server)#
	Output format of access log	webserver.logger.access_log.format-name in the <configuration> tag on a logical J2EE server (j2ee-server)#
	Format when the access log is output	webserver.logger.access_log.inprocess_http.usage_format in the <configuration> tag on a logical J2EE server (j2ee-server)#
Trace based performance analysis	--	Specify acquisition condition, when you want to execute the cprfed command for performing a daily system operation same as for other trace based performance analysis. For details about acquiring the trace based performance analysis files, see 7. Performance Analysis by using Trace Based Performance Analysis.
Thread trace	Number of files of thread trace	webserver.logger.thread_trace.inprocess_http.filenum in the <configuration> tag on a logical J2EE server (j2ee-server)
	File size of thread trace	File size of the thread trace =(((A+B) 32,786)+ 32,914) byte A= Value of webserver.connector.inprocess_http.max_connections parameter in the <configuration> tag on a logical J2EE server (j2ee-server) B=For 0, the value of the webserver.connector.inprocess_http.send_timeout parameter is 0, and when other than 0, the value is 1 in the <configuration> tag on a logical J2EE server (j2ee-server)
Communication trace	Number of files of the communication trace	webserver.logger.communication_trace.inprocess_http.filenum in the <configuration> tag on a logical J2EE server (j2ee-server).
	File size of the communication trace	File size of the communication trace=(((A+B) 172,050)+128) byte A=Value of webserver.connector.inprocess_http.max_connections parameter in the <configuration> tag on a logical J2EE server (j2ee-server) B=For 0, the value of the webserver.connector.inprocess_http.send_timeout parameter is 0, and when other than 0, the value is 1 in the <configuration> tag on a logical J2EE server (j2ee-server).

Legend:

--: Not applicable

#

In the access log, you can customize the log output format by defining the format with the above-mentioned keys. For customization of the access log of the in-process HTTP server, see 5.17.2 Customizing the access log of the in-process HTTP server in the uCosminexus Application Server Web Container Functionality Guide.