WSO2 Business Process Server v3.0.1 Documentation

##### Overview

- Home
- Release Note
- WS-BPEL Compliance
- License

##### Downloads

- Releases

##### Installation Guide

- Installing WSO2 BPS

##### Quick Start Guide

- Modeling the process
- Deploying the process
- Testing the process

##### User Guide

- Deploying BPEL Processes
- Deploying Human Tasks
- Managing BPEL processes
- Managing BPEL process instances
- QoS for BPEL processes
- Securing BPEL processes
- Invoking secured partner services
- Versioning
- Management API

##### Human Task Guide

- Human Tasks Quick Start Guide
- Deploying HumanTasks
- Managing Tasks
- Developing a Human Task Artifact
- Human Task Management and Configuration
- Human Task Concepts

##### Administrator Guide

- External data sources Configuration
- Registry Configuration
- Events
- Unified Endpoints
- BPEL Extensions
- Transaction Factory Configuration
- Message Exchange Interceptors
- OpenJPA specific properties
- JMS Transport Configuration
- Process Instance Cleanup Tasks
- Process Hydration and Dehydration
- Enabling Peer-to-Peer(P2P) Communication
- Setting up a BPS Cluster

##### Best Practices

- Process Deployment Best Practices

##### Concepts

- Process Versioning
- Process instance events
- Partner links

##### WS-BPEL Extensions

- Activity Failure and Recovery
- Extension Activities and Extensible Assign Operations
- XPath Extensions
- Iterable ForEach
- Flexible Assigns
- BPEL4People Extension

##### Samples

- HelloWorld
- If-Else
- ForEach
- While
- Repeat Until
- Flow and Links
- Pick
- Synchronous and Asynchronous Service Invocations
- Fault Handling
- Split
- XslTransform
- Compensation Handler
- Event Handler

##### Resources

- FAQ
- External Articles
- Library
- Source Code

##### Community

- Forum
- Mailing Lists

##### Project Information

- Issue Tracking

# Monitor Logs

Logs can be displayed as System logs or application logs.System Logs shows the log events of the system logs depending on the product. Application logs filter logs by the application, it can be services or web applications. There are two ways to configure system logs, 1) through Memory Appender where logs will be taken from the memory, 2) BAMLogEventAppender where logs will be published to bam and log events will be taken from BAM storages. Only the latest daily logs messages will be displayed in the UI where the logs events can be filtered accordingly. Log events are archived daily per tenant per product per date and can be downloaded for further analysis.

The log messages, displayed in this page are obtained from a memory appender. Hence, the severity(log level) of the displayed log messages are equal or higher than the threshold of the memory appender. For more information on appenders, loggers and their log levels, please visit here.

### Log files on disk

The location of the log files on disk is specified in the log4j.configuration file.

## View Logs

This log events are displayed from bottom-up manner. You can also search for a particular log by a keyword using the Search Logs feature.

1. In the navigator, under Monitor, click Logs. The System Logs/Application Logs page appears.�
2. In the View list, select the category of logs you want to view. The available categories are,

INFO �- Information messages WARN �- Warning messages ERROR �- Error messages DEBUG �- Debug messages TRACE �- Trace messages FATAL -�Fatal error messages

Figure 1: Monitor Logs

Figure 2: Archived Logs

To filter out application specific logs, go to Monitor -> Application Logs. This will display application specific logs.

Figure 3: Application Logs