Using workload balancing

This section discusses the Energizer for IMS Connect product DataStore Router component and how to use it to balance the workload.

Workload routing directs a transaction to the datastore that is best equipped to process that transaction.

The DataStore Router, a feature within Energizer, routes the incoming request to a single datastore.

The components of the DataStore Router eliminate the need for the application or a message exit to specify which datastore the transaction request should be sent. The DataStore Router sends the request to the appropriate datastore while taking into account unique processing characteristics — such as affinities, workload balancing, and resource availability.

If you disable routing, the client or a customer message exit must specify the datastore destination or the message will be rejected by IMS Connect. The DataStore Router components are discussed in detail in this section.

Transactions

Routing transactions to different datastores can improve system performance and availability by transferring workloads to the datastores that have the capacity to handle them. For example, you may want to route transactions for some of the following reasons:

  • Datastore availability
  • Varying processor speeds
  • Newer, more dependable datastores
  • Varying auxiliary storage capacity
  • Varying memory
  • Changing environment

Prerequisites

Before you can use the DataStore Router, the datastores and the activity status of each must be defined to Energizer.

For more information about how to create DataStore Router Option Members, see Adding-a-DataStore-Router-Configuration-member.

Note

If you make any changes to the DataStore Router configuration member, you must reload the DataStore Router configuration member for the changes to take effect. For more information, see Reloading-router-options.

DataStore Router components

When IMS Connect receives a message, it is sent to the appropriate message exit.

If no errors are found, Energizer invokes the DataStore Router to determine which datastore can handle the request.

Before a message can be routed to a specific datastore, several factors must be evaluated. The DataStore Router uses its components to match the incoming request to a single datastore. If all routing components are defined as active, the components are invoked in the following order:

  1. Affinity Manager
  2. Load Balancer
  3. Resource Status Checker

The Energizer DataStore Router configuration member name field allows you to create and store multiple router configurations with different processing environments and datastore definitions. Load balancing methods, WLM and Statistical are discussed in Load-Balancer.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*