IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Policy properties

The following policies are stored within Integration Registry and are defined by their names and properties. You can use the supplied services to create and update policies.

You can use the following methods for creating and administering policies within Integration Registry:

By using the IBM® Integration Web Administration Interface.
For more information, see Configuring workload management by using the web user interface.
By using the IBM Integration API.
For more information, see Configuring workload management policies by using the IBM Integration API.
By running the commands directly from a command console.
For more information, see Configuring workload management policies by using a command console.

Changes to policies will take effect from the next time a message flow that uses the policy is called.

Note: If you change the IBM Integration Web Administration Interface port number after creating a policy, you will no longer be able to access that policy through REST API, the IBM Integration Web Administration Interface, and IBM Integration Toolkit. After you change the port number, you must re-create your policies.

Follow the link to the policy that you want to use to view the available properties:

WorkloadManagement policy

WorkloadManagement policy

The policy name identifies the WorkloadManagement policy to use.

Changes to the property values take immediate effect. You do not need to restart the integration server.

Supplied policies that are created for each broker	Properties for each policy that is defined	Description of properties
None	additionalInstances	The number of additional threads that the broker can use to service the message flow. The value can be any positive integer. This property is optional. The default value is not set.
	commitCount	For WebSphere® MQ messages. Specifies how many input messages are processed by a message flow before a sync point is taken (by issuing an MQCMIT). The value can be any positive integer. This property is optional. The default value is not set.
	commitInterval	For WebSphere MQ messages. Specifies a time interval at which point a commit is taken, when the commitCount property is greater than 1 (that is, where the message flow is batching messages), but the number of messages that are processed has not reached the value of the commitCount property. The value can be any positive integer. This property is optional. The default value is not set.
	maximumRateMsgsPerSec	The maximum rate the message flow can process messages at. The maximum rate is specified as the total number of input messages processed every second. If necessary, a processing delay is introduced in order to keep the input message processing rate under the maximum rate setting. To activate, the value can be any positive integer. A value of zero disables the maximum rate mechanism. This property is optional. The default value is not set.
	notificationThresholdMsgsPerSec	The threshold rate where a notification message is published when the message rate exceeds the value that is given. The message rate is a measure of the total messages processed every second. To activate, the value can be any positive integer. A value of zero disables the notification threshold mechanism. This property is optional. The default value is not set.
	processingTimeoutSec	The time in seconds a message can take to be processed in a message flow before the timeout action is taken. The time is taken from the point a message is received on an input node. This property is optional. The default value is 0. Any positive integer value is valid.
	processingTimeoutAction	The action to take when the processingTimeoutSec has been exceeded. This property is optional. The default value is not set. A value of `restartExecutionGroup` will cause the integration server to be restarted.
	startInstancesWhenFlowStarts	Specifies whether all additional instance threads are to start when the flow starts. Both flow and node-scope instances start if this option is set to true. The value can be true or false. This property is optional. The default value is not set.
	startMode	You can configure the run state of message flows and applications when you deploy, or when you restart, an integration server. The value can be Maintained, Manual, or Automatic. This property is optional. The default value is not set.

bn58450_.htm |

Last updated Friday, 21 July 2017