Managing System Logs

• install_dir or install-dir refers to the name of the installation directory.
• logs refers to the primary log directory.
• directory refers to the subdirectory created when you start Sterling B2B Integrator.

  All the old log files are moved to this subdirectory for archiving. The naming convention to be used for the old log directory is logs_mmddyy_hhmmss.

• name identifies the type of the log file.
• log refers to the file name extension, which indicates the file type.
• Dyyyymmdd refers to the date in the year, month, and day format. The D at the beginning refers to Date.
• Thhmmss refers to the time in hours, minutes, and seconds format. The T at the beginning refers to Time.
• _# is the increment of the log file. If you attempt to write a log file that already exists, _# is appended to the log file name, allowing you to write a new file and save the integrity of the existing file.

  For example, if mylog.D20041101.T092022 exists, and you try to save a new log file with the same name, the new file becomes mylog.D20041101.T092022_2, where _2 indicates that it is the second log in a sequence using the same file name.

1. From the Administration menu, select Operations > System > Logs.
2. Click the appropriate log file.

1. In the install_dir/logs/log directory, locate the old log file that you want to view.
2. Open the log file in read-only mode using a text editor.

[2008-04-22 09:02:43.404] ERROR 000310160001 UTIL.FRAME_POOL.ERR_Pool [Pool] Could not create the initial objects for the pool gentranTPPool
[2008-04-22 09:02:43.405] ERROR 000000000000 GLOBAL_SCOPE [1208869363405] The driver manager could not obtain a database connection.

• YYYY-MM-DD refers to the date in year, month, day format.
• HH:MM:SS.ss refers to the time in hour, minutes, seconds, and hundredths of a second format.
• loglevel indicates how much information is logged and the relative importance of the message. A subsystem may log only a subset of these messages (as defined in the subsystem.loglevel property of log.properties), discarding those that have a severity that is lower (less severe) than the current log level set for that subsystem.

  Log Level	Description
  FATAL	Collects fatal and critical error information.
  ERRORDTL	Collects only error conditions, with a detailed description of the error.
  ERROR	Collects only error conditions such as exceptions and error messages (including errors from the user interface).
  WARN	Collects non-fatal configuration messages.
  SQLDEBUG	Collects SQL statements that are being executed.
  INFO	Collects basic operational information.
  TIMER	Collects timing information.
  COMMTRACE	Collects communication trace information.
  DEBUG	Collects basic debugging statements including system state and code paths.
  VERBOSE	Collects extra debugging statements (like XML information) that describe and explain what is happening in the system.
  ALL	Collects information about all the conditions.

• message code describes the activity or problem, using the following format:
  • The first four digits specify the scope (like Workflow, Ops, Util).
  • The next digit specifies the log severity level (default conventions use 1 for error or exception, 2 for debug messages, 3 for warnings, and 4 for information or all messages.
  • The next three digits specify the subsystem (like Workflow Queue or Workflow Engine).
  • The last four digits specify the error number.
• Scope.Subsystem.Name is a text description of the affected part of Sterling B2B Integrator (such as WORKFLOW, OPS, or UTIL), the Sterling B2B Integrator subsystem (such as FRAME_POOL, NOAPP, or SERVER), and what occurred (such as ERR_Pool or INFO_NamingException1).
• information string is a brief description of the activity that occurred.

[2006-05-30 11:06:55.661] ALL 000440020297
SERVICES.SERVICES_CONTROLLER.INFO_sdi_getName startup: loading HTTP_SEND_ADAPTER

• Scope (Services)
• The affected part of Sterling B2B Integrator (Services Controller)
• What occurred (INFO_sdi_getName)
• Error code (0297)

1. In the install_dir/properties directory, either create or locate the customer_overrides.properties file.
2. Open the customer_overrides.properties file using a text editor.
3. Specify the settings for the global log properties described in the following table. These properties are displayed in the following format:
   logService.Property=Value

   • logService identifies the log.properties file in the customer_overrides.properties file.
   • Property is the global property of the log.properties file that you want to set. See the following table for a list of properties.
   • Value is the property setting of the log.properties file.

   Property	Description
   newloggers	Specifies whether to allow new log files to be created when the maximum log file size setting has been exceeded. Valid values: true – Allow new logs to be created (Default) false – Do not allow new logs to be created Example: logService.newloggers=true
   defaultlog	Specifies the name of the default log. Default is systemlogger. Example: logService.defaultlog=logtype
   logtype.maxnumlogs	Specifies the maximum number of logs to retain before deleting the old logs. Default is 10. Examples: logService.defaultlog.maxnumlogs=15 sets the maximum number of a log type specified as the default log (systemlogger, by default) to 15. logService.uilogger.maxnumlogs=20 sets the maximum number of UI type logs to 20.

   The following table provides the log type name for each log file name defined by default in the log.properties file and extension files. If you have changed the file name, use the original file name to find the log type name.

   File Name of Log (As Shown on the System Logs Screen)	Log Type (For the customer_overrides.properties file)
   alerterlogger.log	alerterlogger
   archive.log	archivelogger
   Authentication.log	AuthenticationLogger
   cdinterop.log	cdinteroplogger
   cdinterop_cdjava.log	cdinteropcdjavalogger
   ceuinterop.log	ceulogger
   common3splogger.log	common3splogger
   delete.log	deletelogger
   ebXML.log	ebXMLlogger
   EDIINT.log	EDIINTLogger
   event.log	event
   ftp.log	ftplogger
   ftpclient.log	psftpclientlogger
   http.log	httplogger
   httpclient.log	httpclientlogger
   jetty.log	jettylogger
   lifecycle.log	lifecycleLogger
   mailbox.log	mailboxlogger
   mgmtdash.log	neo
   noapp.log	noapplogger
   ocsp.log	ocsplogger
   oftp.log	oftplogger
   ops_exe.log	opslogger
   Perimeter.log	PSLogger
   pipeline.log	pipelinelogger
   report.log	reportlogger
   resourcemonitor.log	resourcemonitorlogger
   mif.log	rnlogger
   sap.log	saplogger
   schedule.log	schedulelogger
   Security.log	SecurityLogger
   servicesctl.log	sclogger
   sftpclient.log	sftpclientlogger
   sftpserver.log	sftpserverlogger
   si_exe.log	silogger
   sql.log	sqllogger
   system.log	systemlogger
   system.log	purgelogger
   test.log	testlogger
   tracking.log	tracking
   txtrace.log	txtracelogger
   ui.log	uilogger
   ui_performance.log	ui_perf_logger
   webdav.log	webdavlogger
   WebSphereMQSuite.log	wsmqSuiteLogger
   webx.log	webxlogger
   wf.log	wflogger
   wfexception.log	wfexception_logger
   wfstatistics.log	wfstatistics

4. Save and close the customer_overrides.properties file.
5. Stop the Sterling B2B Integrator and restart it to use the new values.

• Location of the log file
• The number of lines pertaining to the log file to be saved
• The amount of details to log

1. From the Administration menu, select Operations > System > Logs.
2. Click the icon next to the log type whose log settings you want to change.
3. In the Log Settings page, specify the settings for the options described in the following table:

   Option	Description
   Location	Specifies the absolute path for the log file.
   Rollover Interval	If newloggers is set to false, the rollover interval specifies the point at which the oldest lines in the log file are deleted as new lines are created. If newloggers is set to true (default), the rollover interval is the maximum number of lines allowed in the log file before a new file is created. Select one of the following rollover interval values: 50000 lines 100000 lines 150000 lines 200000 lines Note: Here, the term “lines” refers to logical lines (entries) and not physical lines. For example, following is a “line”: [2005-07-11 08:12:07.679] ALL 000440020297 SERVICES.SERVICES_CONTROLLER.INFO_sdi_getName startup: loading HTTP_SEND_ADAPTER FtpConfig.logConfiguration() client configuration: ftpListenPort=[10021] localDataPortCollection=[null] localControlPortCollection=[null] minThreadPoolSize=[3] maxThreadPoolSize=[6] systemCertificateId=[null] caCertificatesIds=[null] passphrase=[******] cipher=[Strong] sslOption=[SSL_NONE] sslAllowed=[false] sslRequired=[false] sslImplicit=[false] cccAllowed=[false] cccRequired=[false] clusterNodeName=[Node1] perimeterServerName=[local] nonTerminationCharsToTotalCharsRatio=[0.9]
   Logging Level	Specifies the amount of details to log. Select one of the following values: On – Set the logging level to include comprehensive and detailed logs (creates larger files) Off – Set the logging level to include log errors (creates smaller files) Note: Setting the logging level to ALL may generate an excessive amount of debugging information. You should lower the logging level after you have retrieved the debugging information you require. The ALL string does not mean the logging level is set as ALL. Strings such as ALL, INFO, and WARN appear in the log files irrespective of setting the logging level to ON or OFF.

4. Click Save.

1. Modify the LOG_DIR setting in sandbox.cfg.
2. Run the setupfiles.sh script to apply the changes.

• jetspeed.log
• jetspeedservices.log
• torque.log
• turbine.log
• access.log