You create one or more core group policies for service
integration to control the behavior of the messaging engine, or engines,
in a server cluster. The policies support behavior such as high availability,
workload sharing or scalability in a server cluster.
Before you begin
Ensure that you want to use the following procedure. As an
alternative, you can create a policy by using messaging engine policy
assistance when you add a server cluster to a bus. You create messaging
engines and their associated policies as part of the procedure, and use
predefined messaging engine policy types that support frequently-used
cluster configurations. Alternatively, you can use a custom policy
type and configure the messaging engine policy as you require, and
the relevant core group policies and their match criteria are created
automatically.
Continue with the following procedure to create a
core group policy for messaging engines if you are familiar with it.
Otherwise, it is easier to create a policy by using messaging engine
policy assistance when you add a server cluster to a bus.
Decide
what type of core group policy you need to create for the configuration
you require. For service integration, the following types of core
group policy apply:
- Static. Use this type of policy for a workload sharing or scalability
configuration without high availability. Create one policy for each
messaging engine in the cluster.
- One of N. Use this type of policy for a high availability configuration,
or a workload sharing configuration with high availability. You create
one policy for each messaging engine in the cluster.
- No operation. Use this type of policy when you use an external
high availability framework to manage the messaging engines in the
cluster. You create one policy for all the messaging engines in the
cluster. The configuration might be high availability, or workload
sharing with high availability.
For further information, see
Policies for service integration.
About this task
A policy is a component of a core group. A core group can
have a number of different policies; each policy applies to a particular
high availability group and determines the high availability behavior
of resources in that group. For service integration, the resources
that you want to control are the messaging engines. Typically, you
create one policy for each messaging engine in the cluster, unless
you want the messaging engines to be managed by external high availability
framework.
To create a policy for a messaging engine, use the administrative
console to complete the following steps.
Procedure
- In the navigation pane, click . A list of currently configured core group policies is
displayed.
- Click New.
- Select one of the following options from the Policies list.
Only the following policy types are applicable to service integration:
- Static
- A messaging engine cannot fail over in a WebSphere® Application Server cluster.
- One of N
- A messaging engine can fail over in a WebSphere Application Server cluster.
- No operation
- A messaging engine is managed by an external high availability
framework such as IBM HACMP. This option is for use with an external
high availability cluster.
Do not select any other policy type, because they
because they are not supported for the service integration bus component.
- Click Next. The
policies configuration page is displayed.
- Enter a Name that is unique in the
scope of the core group.
- Click Apply or OK.
- Configure the policy. See Configuring a core group policy for messaging engines.
- Save your changes to the master configuration.