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. Then, deploy the policy project, either directly to the integration server or in your BAR file.

Monitoring profiles and policy sets and bindings are also 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.

Business transaction policies contain the business events that are monitored during business transactions, and they are defined when the business transaction definition is created in the web user interface. You can also create business transaction policies by using an external editor, and then deploy them. However, you cannot create or edit them by using the policy editor in the IBM App Connect Enterprise Toolkit. For more information about this type of policy, see Creating a business transaction definition.

You can change, delete, or redeploy policies after they have been deployed. For the following types of policy, all message flows that are using the policy are stopped and restarted when you redeploy the policy project:
  • ActivityLog
  • Aggregation
  • Amazon CloudWatch
  • Amazon DynamoDB
  • Amazon EC2
  • Amazon EventBridge
  • Amazon Kinesis
  • Amazon RDS
  • Amazon S3
  • Amazon SES
  • Amazon SNS
  • Amazon SQS
  • Anaplan
  • Asana
  • AWS Lambda
  • BambooHR
  • Box
  • Calendly
  • CICSConnection
  • CMIS
  • Collector
  • Confluence
  • Connect:Direct Server (CDServer)
  • CORBA
  • Coupa
  • DocuSign
  • DropBox
  • EmailServer
  • Eventbrite
  • Expensify
  • flexEngage
  • FTP Server
  • GitHub
  • GitLab
  • Gmail
  • Google Analytics
  • Google Calendar
  • Google Chat
  • Google Cloud BigQuery
  • Google Cloud Pub/Sub
  • Google Cloud Storage
  • Google Contacts
  • Google Drive
  • Google Groups
  • Google Sheets
  • Google Tasks
  • Google Translate
  • Greenhouse
  • HTTP Proxy
  • HTTP Request
  • HubSpot CRM
  • HubSpot Marketing
  • IBM Cloud Object Storage S3
  • IBM Cloudant
  • IBM Engineering Workflow Management
  • IBM FileNet Content Manager
  • IBM Food Trust
  • IBM Maximo
  • IBM OpenPages with Watson
  • IBM Supply Chain Intelligence Suite
  • IBM Sterling Inventory Visibility
  • IBM Watson Discovery
  • IBM Weather Company Data Limited Edition
  • IMS Connect
  • Insightly
  • JDEdwards Connection
  • Jenkins
  • Jira
  • Kafka
  • LDAP
  • Magento
  • MailChimp
  • Marketo
  • Microsoft Active Directory
  • Microsoft Azure Blob storage
  • Microsoft Dynamics 365 for Finance and Operations
  • Microsoft Dynamics 365 for Sales
  • Microsoft Entra ID
  • Microsoft Excel Online
  • Microsoft Exchange
  • Microsoft OneDrive for Business
  • Microsoft OneNote
  • Microsoft Power BI
  • Microsoft SharePoint
  • Microsoft Teams
  • Microsoft To Do
  • Microsoft Viva Engage
  • monday.com
  • MQEndpoint
  • MQTTPublish
  • MQTTSubscribe
  • ODMServer
  • Oracle E-Business Suite
  • Oracle Human Capital Management
  • PeopleSoftConnection
  • Resequence
  • Salesforce
  • Salesforce Account Engagement
  • Salesforce Commerce Cloud Digital Data
  • Salesforce Marketing Cloud
  • SAP Ariba
  • SAP Connection
  • SAP OData
  • SAP SuccessFactors
  • Security Profiles
  • ServiceNow
  • Shopify
  • Siebel Connection
  • Slack
  • SMTP
  • Snowflake
  • Square
  • SurveyMonkey
  • TCPIP Client
  • TCPIP Server
  • Timer
  • Trello
  • Twilio
  • UKG
  • User Defined
  • WordPress
  • Workload Management
  • Wufoo
  • Yapily
  • Zendesk Service
The following types of policy are non-dynamic and cannot be deployed while applications and message flows are using them, so you must restart all applications as part of the deploy operation:
  • DotNetAppDomain
  • JavaClassLoader
  • JDBCProviders
  • JMSProviders
  • WXSServer
  • Policy sets & policy set bindings

You can restart all applications as part of the deploy operation by specifying the --restart-all-applications parameter on the mqsideploy or ibmint deploy command. If you try to redeploy a non-dynamic policy by using the Toolkit, the redeploy fails and you are given the option of restarting all applications and redeploying.

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.