Change the Version and Revision Number in Metadata

Increase the revision number of the policy each time you customize the policy and deploy it.

Management Tier checks whether the policy version and revision stored in the database matches with the metadata in the policy JAR file that you are deploying. If that matches, the REST API returns an HTTP 200 code saying OK but no deployment happens.

To deploy the customized policy JAR, you must increase the revision number of the policy. You could also modify policy description to document the changes made to the policy.

To change the version / revision number in metadata:

1. Open the policyXXX.json file in a text editor.
2. Change the policy.description attribute.
   For example, change:"policy.description" : ""Transforms a JSON payload into a XML payload” to "policy.description" : ""Transforms a JSON payload into a XML payload after….”.
3. Save the changes and close the text editor.
4. Move to the folder that contains the metadata.json file.
5. Open the metadata.json file in a text editor.
6. Change the revision attribute.
   For example, change "version": "1.0", "revision": "1" to "version": "1.0", "revision": "2".
7. Save the changes and close the text editor.