18 Managing Oracle Mediator Service Components and Engines

This chapter describes how to manage Oracle Mediator service components and engines using Oracle Enterprise Manager Fusion Middleware Control. It provides instructions for viewing recovering faults, and attaching and detaching Mediator policies.

This chapter includes the following sections:

18.1 Recovering From Oracle Mediator Service Component Faults

You can monitor Mediator service component faults and perform individual and bulk recoveries for faults that are identified as recoverable.

To manage Mediator service component faults:

  1. Access the SOA Component home page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select Home.
    2. Select the Deployed Composites tab.

    3. In the Composite section, select a specific SOA composite application.

    1. Expand soa-infra, and then select a specific SOA composite application.

  2. Select the Mediator service component in the Component Metrics section.

  3. Click Faults.

    The Faults page displays the following information:

    • A utility that you can use to search for a specific fault by specifying criteria and clicking Search. Click the Help icon for more information. By default, faults are not displayed the first time you access this page. You must click Search to display any faults.

    • Faults that occurred in the service component, including the error message, whether you can recover from the fault, the time at which the fault occurred, service component instance ID, activity in which the fault occurred, and a link to a log file describing the fault.

    Description of med_srveng_fault.gif follows
    Description of the illustration med_srveng_fault.gif

    Mediator service component faults that are marked as recoverable can be recovered.

  4. Select faults for recovery using one of the following methods.

    For... Then...
    Single fault recovery There are three options from which to choose for single fault recovery. Perform any of the following actions to recover a single fault.
    • Click the row of the fault that has been identified as recoverable. With the row highlighted, select a specific action from the Recovery Action list, as described in Step 5.

    • In the Recovery column, click the Recover link to access the Faults page of the instance audit trail to perform fault recovery. Figure 18-1 illustrates the fault page.

    • In the Error Message column, click the message of a fault that has been identified as recoverable. This displays complete fault details, including the fault ID, fault time, fault location, fault type, and error message text. Click Recover Now to access the Faults page of the instance audit trail to perform fault recovery. If there is no Recover Now option, the fault is not recoverable.

    Bulk fault recovery There are two options from which to choose for bulk fault recovery. Perform the following steps to recover multiple faults.
    1. Do one of the following:

      • Use Shift+Click or Control+Click to select specific faults in the rows.

      • From the Select menu, choose Select All Recoverable. Then use Shift+Click or Control+Click to deselect the faults to not include in the recovery operation.

    2. Select an action from the Recovery Action list, as described in Step 5.

      Note: Only the actions applicable to all selected faults are available.

    Recovery of all faults Perform the following steps to recover all faults.
    1. From the Select menu, choose Select All Recoverable.

    2. Select an action from the Recovery Action list, as described in Step 5.

      Note: Only the actions applicable to all selected faults are available.


    Figure 18-1 Fault Tab on the Mediator Instance Detail Dialog

    Description of Figure 18-1 follows
    Description of "Figure 18-1 Fault Tab on the Mediator Instance Detail Dialog"

  5. If you did not already select a recovery method in the above step, select one of the following actions from the Recovery Action list.

    Action Description
    Retry Retries the instance directly. An example of a scenario in which to use this recovery action is when the fault occurred because the service provider was not reachable due to a network error. The network error is now resolved.
    Abort Terminates the entire instance.
    Replay Replays the entire scope activity again in which the fault occurred.
    Rethrow Rethrows the current fault. BPEL fault handlers (catch branches) are used to handle the fault. By default, all exceptions are caught by the fault management framework unless an explicit rethrow fault policy is provided.
    Continue Ignores the fault and continues processing (marks the faulted activity as a success).

For more information, see the following documentation:

18.2 Managing Oracle Mediator Policies

Oracle Fusion Middleware uses a policy-based model to manage web services. Policies apply behavioral requirements and security to the delivery of messages. You can view, attach, and detach policies for Mediator service components in currently deployed SOA composite applications.

The Policies page of the Mediator Component Home page provides the following information about a Mediator component instance:

  • Policy Name: The name of the policy.

  • Policy Reference Status: A toggle button that allows you to enable or disable a policy. Disabling a policy temporarily turns it off without detaching it. If the button says Disable, the policy is enabled; if it says Enable, the policy is disabled.

  • Category: The category of the policy. It has the following values: Management, Reliable Messaging, MTOM Attachments, Security, and WS-Addressing.

  • Total Violations: The total number of violations since the SOA Infrastructure was restarted.

  • Security Violation: The number of violations in each category. Category can have the following values: Authentication, Authorization, Confidentiality, and Integrity.

Note:

Before attaching policies, see Oracle Fusion Middleware Security and Administrator's Guide for Web Services for definitions of available policies and details about which ones to use in your environment.

To manage Mediator policies:

  1. Access the SOA Composite home page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select Home.
    2. Select the Deployed Composites tab.

    3. In the Composite section, select a specific SOA composite application.

    1. Under soa-infra, select a specific SOA composite application.

  2. Select the Mediator service component in the Component Metrics section.

  3. Click the Policies tab.

  4. View the policies attached to a Mediator component.

    Description of med_comphome_pol1.gif follows
    Description of the illustration med_comphome_pol1.gif

  5. Click Attach/Detach to attach or detach a policy.

  6. If multiple components are available, select the service or component to which you want to attach the policy.

    The Attach/Detach Policies page appears with all attached policies displayed in the upper pane and all available policies displayed in the lower pane.

    Description of med_comphome_pol2.gif follows
    Description of the illustration med_comphome_pol2.gif

  7. To attach a policy, select the policy in the lower pane and then click Attach.

  8. To detach a policy, select the policy in the upper pane and then click Detach.

  9. When you finish attaching or detaching policies, click Validate.

  10. If any validation errors occur, make the necessary corrections and run the validation until no more errors occur.

  11. Click OK.

    The dialog closes and the attached policies appear in the policies table.

For more information, see the following documentation:

18.3 Recovering From Oracle Mediator Service Engine Faults

You can monitor and perform individual and bulk fault recoveries for Mediator service engines that are identified as recoverable. All Mediator service component faults, regardless of the SOA composite application instance of which they are a part, can be viewed in the Mediator service engine.

To manage Mediator service engine faults:

  1. Access the SOA Composite home page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select Service Engines > Mediator.
    1. Right-click soa-infra.
    2. Select Service Engines > Mediator.


    The Mediator Engine home page appears.

  2. Click Faults.

    The Faults page displays the following:

    • A utility so you can search for a specific fault by specifying criteria and clicking Search. Click the Help icon for more information. By default, faults are not displayed the first time you access this page. You must click Search to display any faults.

    • Faults that occurred in the service component, including the error message, whether you can recover from the fault, the time at which the fault occurred, service component instance ID, activity in which the fault occurred, and a link to a log file describing the fault.

    Description of med_srveng_fault.gif follows
    Description of the illustration med_srveng_fault.gif

    Mediator service engine faults that are marked as recoverable can be recovered.

  3. Select a fault or faults.

    As with fault recovery at the SOA Infrastructure level, SOA composite application level, and Mediator service component level, you can perform single fault recovery, bulk fault recovery, and recovery of all faults. See Step 4 of Section 18.1, "Recovering From Oracle Mediator Service Component Faults" for instructions on selecting faults to perform these types of recovery.

  4. If you did not select a recovery action in the previous step, select an action from the Recovery Action list.

    Action Description
    Retry Retries the instance with an option to provide a retry success action. An example of a scenario in which to use this recovery action is when the fault occurred because the service provider was not reachable due to a network error. The network error is now resolved.
    Abort Terminates the entire instance.
    Replay Replays the entire scope activity again in which the fault occurred.
    Rethrow Rethrows the current fault.
    Continue Ignores the fault and continues processing (marks the faulted activity as a success).

  5. Perform the following additional monitoring tasks from within the faults table:

    1. Click the Show only recoverable faults check box to only display faults from which you can recover.

    2. From the Fault Type list, select to display all faults, system faults, business faults, or OWSM faults in the faults table. Click Help for a description of these fault types.

    3. From the View list, select Columns > Fault ID to display the fault IDs for each error message. The fault ID is automatically generated and uniquely identifies a fault. The fault ID is also displayed when you click an error message.

    4. In the Composite column, click a specific SOA composite application to access its home page.

    5. In the Component column, click a specific service component to access its home page.

    6. In the Component Instance ID column, click a specific service component ID to access task details about the instance (for example, the current state of a task). Note that rejected messages do not have a component instance ID.

For more information, see the following documentation:

18.4 Skipping Resequenced Messages

When a resequencing group is in the timed out state, you can skip the message that is blocking the group to begin processing again. In some cases, such as when there is no timeout duration set, a standard resequencing group might wait indefinitely without timing out and remain in the running state. In this case, you can skip the sequence ID it is waiting for even though the group has not yet timed out.

18.4.1 Skipping to the Next Sequence ID in a Running Group

When a standard resequencing group is running and you know the next message is not going to arrive within the specified timeout duration (or there is no timeout duration), perform the following steps to skip the next expected sequence ID and begin processing the next available message.

To skip to the next sequence ID in a running group:

  1. Access the SOA Component home page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select Home.
    2. Select the Deployed Composites tab.

    3. In the Composite section, select a specific SOA composite application.

    1. Expand soa-infra, and then select a specific SOA composite application.

  2. Select the Mediator service component in the Component Metrics section.

  3. Do one of the following:

    • In the Recent Instances list, click the group ID of the group for which you want to skip sequence IDs.

    • Click the Instances tab, perform a search for the instance, and in the results list, click the group ID of the group for which you want to skip sequence IDs.

    The Mediator Resequencing Group Dialog appears.

    Figure 18-2 Mediator Resequencing Group Dialog with Skip Option (Running)

    Description of Figure 18-2 follows
    Description of "Figure 18-2 Mediator Resequencing Group Dialog with Skip Option (Running)"

  4. To skip to the next sequence ID, click Skip.

    Note:

    The Skip button only appears on the dialog for groups configured for the standard resequencer, and not best effort or FIFO resequencers. When you skip a message, it is always in the skipped state and is not purged by the purge scripts.

18.4.2 Skipping to the Next Sequence ID in a Timed Out Group

When processing of a resequencing group stops while waiting for an expected message, the group is in a timed out state and no messages are processed. To remedy this, you need to skip the message that caused the timeout and move on to the next available sequence ID.

To skip to the next sequence ID in a timed out group:

  1. Access the SOA Component home page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select Home.
    2. Select the Deployed Composites tab.

    3. In the Composite section, select a specific SOA composite application.

    1. Expand soa-infra, and then select a specific SOA composite application.

  2. Select the Mediator service component in the Component Metrics section.

  3. Do one of the following:

    • In the Recent Instances list, click the group ID of the group that is timed out.

    • Click the Instances tab, perform a search for the instance, and in the results list, click the group ID of the group that is timed out.

    The Mediator Resequencing Group Dialog appears.

    Figure 18-3 Mediator Resequencing Group Dialog with Skip Option (Timed Out)

    Description of Figure 18-3 follows
    Description of "Figure 18-3 Mediator Resequencing Group Dialog with Skip Option (Timed Out)"

  4. To unlock the group and start processing the next instance in the group, click Skip.

    Note:

    Mediator will not process any messages with sequence IDs between the sequence ID of the last message processed and the next message processed.