Configure service integration HA without using message engine policy assistance

 

+

Search Tips   |   Advanced Search


Overview

This page discusses configuring high availability and workload sharing of service integration without using messaging engine policy assistance.

We can create messaging engines, and their associated policies, as part of the procedure, by using either...

Relevant core group policies and match criteria are created automatically.

When you set up a service integration environment, you create bus members, either servers or clusters, that run messaging engines. For high availability, where the messaging engine can fail over, or workload sharing, where multiple messaging engines share the load on a destination, we need to create a cluster bus member and configure high availability and workload sharing characteristics of the messaging engines.

If you do not require high availability or workload sharing, we can use a simple configuration and create a server bus member. We do not need the steps described in this topic.

The high availability and workload sharing characteristics of the messaging engines in the cluster are set by core group policies. To see the policies that are configured in the system, we can use the administrative console to open the Policies page. In the navigation pane, click

Servers | Core groups | Core group settings | core_group_name | [Additional Properties] Policies

One of the available policies is the default service integration policy, "Default SIBus Policy", which is the policy that a messaging engine uses unless you configure the system so that the engine uses another policy. The default policy is sufficient for many purposes and you might not need to alter the policy configuration. It is not advisable to alter the default service integration policy, because those changes will affect all messaging engines that the policy manages. Therefore, it is better to create and configure one or more new specific policies.

  1. Create a cluster, if it is not created already.

  2. Add the cluster to the service integration bus.

    A single messaging engine that uses the default service integration policy is created automatically.

    For high availability without workload sharing, we can use this configuration and do not need to change it further.

  3. For high availability when you want to configure the messaging engine behavior, create and configure a policy for the messaging engine. Create a policy with the type "One of N".

  4. For workload sharing without high availability, use the following steps:

    1. Add as many messaging engines as you require to the cluster.

      Typically, a workload sharing configuration has one messaging engine for each server in the cluster.

    2. Create and configure a policy for each messaging engine in the cluster. Create policies with the type Static.

  5. For workload sharing with high availability, use the following steps:

    1. Add as many messaging engines as you require to the cluster.

      Typically, a workload sharing configuration has one messaging engine for each server in the cluster.

    2. Create and configure a policy for each messaging engine in the cluster. Create policies with the type "One of N"

  6. To use an external high availability (HA) framework to manage high availability or workload sharing behavior, use the following steps:

    1. If you require workload sharing, add as many messaging engines as you require to the cluster. Typically, a workload sharing configuration has one messaging engine for each server in the cluster.

    2. Create and configure one policy for the messaging engines in the cluster. Create a policy with the type "No operation".

 

Next steps

If you created a high availability configuration for service integration, we might also want to configure high availability for the transaction service.

If you created a workload sharing configuration, we might want to deploy a queue destination to the cluster, so that the queue is partitioned across the set of messaging engines.