WebSphere Adapter for FTP

Configuring logging properties

Use the administrative console to enable logging and to set the output properties for a log, including the location, level of detail, and output format of the log.

About this task

Before the adapters can log monitored events, you must specify the service component event points that you want to monitor, what level of detail you require for each event, and format of the output used to publish the events to the logs. Use the administrative console to perform the following tasks:
  • Enable or disable a particular event log
  • Specify the level of detail in a log
  • Specify where log files are stored and how many log files are kept
  • Specify the format for log output

    If you set the output for log analyzer format, you can open trace output using the Log Analyzer tool, which is an application included with your process server. This is useful if you are trying to correlate traces from two different server processes, because it allows you to use the merge capability of the Log Analyzer.

For more information about monitoring on a process server, including service components and event points, see the documentation for your process server.

You can change the log configuration statically or dynamically. Static configuration take effect when you start or restart the application server. Dynamic, or runtime, configuration changes apply immediately.

When a log is created, the detail level for that log is set from the configuration data. If no configuration data is available for a particular log name, the level for that log is obtained from the parent of the log. If no configuration data exists for the parent log, the parent of that log is checked, and so on up the tree, until a log with a non-null level value is found. When you change the level of a log, the change is propagated to the children of the log, which recursively propagate the change to their children, as necessary.

To enable logging and set the output properties for a log, use the following procedure.

How to perform this task

  1. In the navigation pane of the administrative console, click Servers > Application Servers.
  2. Click the name of the server that you want to work with.
  3. Under Troubleshooting, click Logs and trace.
  4. Click Change Log Detail Levels.
  5. Specify when you want the change to take effect:
    • For a static change to the configuration, click the Configuration tab.
    • For a dynamic change to the configuration, click the Runtime tab.
  6. Select the packages whose logging level you want to modify. The package names for WebSphere® Adapters start with com.ibm.j2ca:
    • For the adapter base component, select com.ibm.j2ca.base.
    • For the adapter base component and all deployed adapters, select com.ibm.j2ca.base.*.
    • For a specific adapter, select its package name.
      Adapter Package Name
      WebSphere Adapter for Email com.ibm.j2ca.email
      WebSphere Adapter for Flat Files com.ibm.j2ca.flatfile
      WebSphere Adapter for FTP com.ibm.j2ca.ftp
      WebSphere Adapter for JDBC com.ibm.j2ca.jdbc
      WebSphere Adapter for JD Edwards EnterpriseOne com.ibm.j2ca.jde
      WebSphere Adapter for SAP Software com.ibm.j2ca.sap
      WebSphere Adapter for Siebel Business Applications com.ibm.j2ca.siebel
  7. Click the package name and select the logging level.
    Logging Level Description
    Fatal The task cannot continue or the component cannot function.
    Severe The task cannot continue, but the component can still function. This logging level also includes conditions that indicate an impending fatal error, that is, situations that strongly suggest that resources are on the verge of being depleted.
    Warning A potential error has occurred or a severe error is impending. This logging level also includes conditions that indicate a progressive failure, for example, the potential leaking of resources.
    Audit A significant event has occurred that affects the server state or resources.
    Info The task is running. This logging level includes general information outlining the overall progress of a task.
    Config The status of a configuration is reported or a configuration change has occurred.
    Detail The subtask is running. This logging level includes general information detailing the progress of a subtask.
  8. Click Apply.
  9. Click OK.
  10. To have static configuration changes take effect, stop and then restart the process server.
Related tasks
Enabling tracing with the Common Event Infrastructure (CEI)
Changing the log and trace file names

Terms of use |

Last updated: Mon 30 Oct 2006 03:48:54

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)