• Call us: +91 9501707741
  • tutorialzdiary@gmail.com


SERVICE BUS 11g Tutorials

Chapter 1: Introduction
Chapter 2: What is Service Bus ?
Chapter 3: OSB Architecture
Chapter 4: OSB Components
Chapter 5: OSB Protocols
Chapter 6: Reporting & Monitoring
Chapter 7: Error Handling

SERVICE BUS 11g Training

Oracle Service Bus 11g Training Course

SERVICE BUS 11g Installation

Part 1: Oracle Service Bus Installation
Part 2: Start and Stop Server

SERVICE BUS 11g Interview Questions and Answers

Part 1: OSB Basics
Part 2: Installation
Part 3: OSB Architecture & Components
Part 4: OSB Message Flow

Chapter 6: Reporting & Monitoring

Oracle Service Bus has out of box monitoring and reporting features that increase support team productivity as they get to see everything on dashboard. Oracle Service Bus provide monitoring capabilities through dashboard that allows us to monitor the health of the system and notifies us when alerts are generated in your services. Along with system health, we can also see services health and take corrective action accordingly.

You can monitor Oracle Service Bus at run time to know how many messages in a particular service have processed successfully and how many have failed.

We can see below things through OSB monitoring framework.

1. How many messages were processed successfully or failed
2. Which project the service belongs to
3. Average execution time of message processing
4. Number of alerts associated with the service.

We use Alerts in Oracle Service Bus monitoring. We have following alerts in OSB.

1. SLA Alerts
2. Pipeline Alerts

SLA Alerts

SLA stands for Service Level Agreements and as the name suggest , SLA alerts are used to alert someone when these agreements gets violated. We can define SLA’s in OSB and when it gets violated, we see these alerts in OSB dashboard (SLA Alert tab).

E.g. We invoke external service from OSB and at design time agreement has been made that external service provide the response within 1 minute. So we configure the same in OSB and when ever external service respond after 1 minutes, SLA alert got generated and can be seen on dashboard.

Pipeline Alerts

Pipeline alerts can be generated in message flow. We use alert action in message flow to generate this alert. We use this alert as per our requirement. Sometime we do use it in error handling and sometime we use it main message flow.

We need to have alert destination for every alert. In alert destination, we can perform following operations.

1. Send email
2. Send message to JMS

There are two others actions in OSB that we use for monitoring and reporting.

1. Log action
2. Report action

Log action

Log action is used to log the message to server log file. OSB is a stateless tool so we use this action to see the message in case we have any failure. We can set different severity for log as mentioned below.

1. Debug
2. Info
3. Warning
4. Error

Report action

Report action is used to report incoming or outgoing messages. We can define the key that is used to report some key field in the message. We can also define more than one key in reporting.


Training Enquiry