Policy properties

Control and update connection properties and other operational properties at run time by overriding message flow and message flow node properties with a policy.

To control message flow behavior at run time, create a policy in a policy project with the IBM® App Connect Enterprise Toolkit and deploy the policy project, either directly to the integration server or in your BAR file.
You can change, delete, or redeploy the following types of policy after they are deployed:
  • ActivityLog
  • Aggregation
  • CDServer
  • CICSConnection
  • Collector
  • CORBA
  • EmailServer
  • FtpServer
  • IMSConnect
  • JDEdwardsConnection
  • Kafka
  • MonitoringProfiles
  • MQEndpoint
  • MQTTPublish
  • MQTTSubscribe
  • ODMServer
  • PeopleSoftConnection
  • Resequence
  • SAPConnection
  • SecurityProfiles
  • SiebelConnection
  • SMTP
  • Timer
  • UserDefined
  • WorkloadManagement

For these types of policy, when you redeploy the policy project, all message flows that are using the policy are stopped and restarted.

The following types of policy cannot be redeployed, so you must delete all deployed resources from the integration server and then deploy a new version of the policy:
  • DotNetAppDomain
  • HTTPConnector (deprecated)
  • HTTPSConnector (deprecated)
  • JavaClassLoader
  • JDBCProviders
  • JMSProviders
  • TCPIPClient
  • TCPIPServer
  • WXSServer
  • Policy Sets & Policy Set Bindings

The following topics describe the properties that you can change by using policies. If you use the deprecated mqsicreateconfigurableservice command in your scripts to create policies, you must use the short version of the policy name. Where they are different from the name of the policy, these short names are included after the policy names in the titles of the following topics.

Monitoring profiles and policy sets and bindings are forms of policy that can be used to override properties at run time. For more information about these types of policy, see Monitoring profiles and Policy sets.