Policies Vs Configurable Services in IBM APP Connect
Policies and uses of policies:
Policies are introduced in the recent IBM APP Connect Enterprise version (ACE – 11. x), before the policies we had configurable services in prior versions. Policies are reusable XML documents that are defined by the XML schema definition called Policy.XSD which can be used by developers, administrators, testers, and operators.
These properties control configurations like
- Node properties
- Flow rate
- Connection credentials
- Certain aspects of message flow behavior.
Policies can be referenced to the entities to control
- Message flows
- Message flow nodes
- Integration servers.
In IIB versions, configurable services are runtime properties that can be used to change the flow or node level properties at run time.
- Policies in ACE are replacements for configurable services in IIB.
- If we try to create configurable services using mqsicreateconfigurableservice it will create an equivalent policy in ACE.
- The mqsicreateconfigurableservicecommand to create an object name for a broker external resource.
- This command in ACE will create equivalent policies in the default policy project which get associated with the integration node.
- These policies get inherited with all integration servers present in the integration node.
- Override policies are inherited by an integration server by deploying an updated version or by placing an updated policy in the overrides sub-directory in the integration server directory.
- We can deploy the policy project as part of the application in a single bar file or the policy project can be deployed separately as an independent bar file.
- Once the policies get deployed policies are shown in the toolkit or Web UI.
Policies are visible in different ways:
Through ACE toolkit