Table of Contents

Search

  1. Preface
  2. The Application Integration Console
  3. Process Server Configuration
  4. Deployed Assets
  5. Process Schedules
  6. Processes
  7. Process Server Health
  8. Process Metrics
  9. Connections
  10. Guides
  11. Logs

Monitor

Monitor

Logging

Logging

On the Logging
tab
, you can select logging levels for the Process Server and for processes.
The Logging tab with a list of Process Server and process logging properties
Property Name
Description
Server Logging Level
By default, Process Server generates a log of server events, including server property configuration changes, BPR deployments, server stop and start, and process failures.
You can configure one of the following logging levels for the Process Server:
  • Info (default)
  • Error
  • Warning
  • Critical
  • Verbose (includes all levels)
  • Off (No logging occurs)
Process Logging Level
By default, Process Server generates an execution log for running processes. You can view or download an execution log for a running or completed process. An execution log provides start and end times for activity execution and helps you troubleshoot faulted processes.
You can configure one of the following logging levels for running processes:
  • None:
    The Process Server does not log any information. Use this option to enhance engine performance.
  • Execution:
    This is the default option. The Process Server logs all execution statements except for
    Will Not Execute
    statements. Select
    Execution
    to decrease the size of the log file.
  • Execution with Service Data:
    The Process Server logs all execution and fault information, as well as some WSIO activity information. For execution information, Process Server logs deadpath states, terminations, ready-to-execute, and so on. For WSIO, Process Server logs invokes, picks, and receives, but excludes information related to data assignment and changes.
  • Execution with Data:
    The Process Server logs all execution statements except for
    Will Not Execute
    statements, but includes variable, expression, and partner link data. Select
    Execution with Data
    to decrease the size of the log file.
  • Full
    : The Process Server logs all execution statements
    Will Not Execute
    statements for deadpath activities. For example, the Process Server logs all fault handling statements that are not executed.
You can also set the process logging level to
System Default
on the
Deployed Process Version Detail
page. When you set the logging level to system default, the logging level for the process version corresponds to the process logging level property that is set on the corresponding Process Server.
To improve processing speed, perform no logging or minimum logging. Informatica recommends that you use the
None
or
Terse
logging levels.
Max Buffer Size
The number of state changes, data changes, and other logging events that the Process Server holds in a buffer before writing them to the database.
Default is
200
.
Persist Interval (seconds)
The number of seconds that the Process Server waits before flushing the buffer and writing log events from memory to the database.
Default is
30
.
Min Threads
The minimum number of threads that the Process Server initiates upon startup to log process events.
Default is
5
.
Max Threads
The maximum number of concurrent threads that can be active at any point of time for logging process events.
Default is
150
.
Log all messages
If enabled, logs data of each WS message going to and from the Process Server, including OData requests, and SOAP envelope, headers, and body. All HTTP messages are logged to the file system.
Logging Base Directory
Root directory for log files. The default base directory is the location pointed to by the
java.io.tmpdir
property. When messages are logged, each engine will create message log files under the root directory under
<BASE_LOGGING_DIRECTORY>/engine<id>/
.
The configuration for the base logging directory can contain ant-style parameters that are resolved relative to system properties and environment variables. For example,
${CATALINA_HOME}/
logs will create log files relative to the
CATALINA_HOME
environment variable used to start your Tomcat server.