Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite
11g Release 1 (11.1.1)
  Go To Table Of Contents
Go To Index


12 Configuring Oracle Mediator Service Components and Engines

This chapter describes how to configure Oracle Mediator (Mediator) service components and service engines.

This chapter includes the following topics:

12.1 Introduction to Configuring Oracle Mediator

You can configure the properties of Mediator Service Engine by setting the parameters mentioned in this chapter. These parameters can be set in the following ways:


You do not need to restart the server for changing these properties.

12.2 Configuring Audit-Level Flags

You can configure the Mediator-specific auditLevel flag for audit levels. The value of this flag overrides the value of the global SOA infrastructure audit-level flag. The possible values of this flag are:

The default value of this flag is Inherit.


Audit levels were known as instance tracking levels in the Oracle Application Server 10g releases.

12.3 Configuring Metrics-Level Flag

You can set the Mediator-specific flag metricsLevel for configuring the Dynamic Monitoring Service (DMS) metrics level. DMS metrics are used to measure the performance of application components. The possible values of this flag are:

12.4 Configuring Parameters for Parallel Infrastructure

You can configure the parallel infrastructure by setting the following parameters:

12.5 Configuring Parameters for Error/Retry Infrastructure

You can configure the error/retry infrastructure by setting the following parameter:

12.6 Configuring Parameters for Heartbeat Framework

The heartbeat infrastructure is a part of the Mediator Service Engine and is used to detect the absence of a Mediator Service Engine instance due to failure or shutdown of a node. The heartbeat infrastructure creates a unique identifier for each instance of the Mediator Service Engine and performs the necessary house-keeping tasks, if a Mediator Service Engine fails. The heartbeat infrastructure consists of a heartbeat thread. The heartbeat thread periodically updates the time stamp associated with each Mediator Service Engine's unique identifier. By updating the time stamp associated with it, a Mediator Service Engine announces its presence to the other Mediator Service Engines. The heartbeat thread also checks if there are unique identifiers that have not been updated for a particular period of time. You can configure the heartbeat Framework by setting the following parameters:

By configuring these parameters, you can specify the period used by the heartbeat thread to detect the failure of a Mediator Service Engine.


  • The default value of the ContainerIdLeaseRefresh parameter is 60 seconds.

  • In case of unplanned outages, you must wait as much time as specified as the ContainerIdLeaseRefresh interval, after restarting the server. The server needs this much time to complete the instances still in the running state.