Updating an application binding project

Either update the existing application binding to specify the new version of the application, or create a new application binding for the new version of the application.

1. In the Project Explorer view, locate the existing application binding for the application, expand the META-INF folder for the application binding project, and double-click on the application.xml, bundles.xml, or deployment.xml file. The application binding editor opens. For a guide to using the application binding editor, see The application binding editor.
2. In the application binding editor, click Browse by the application name, and select the new version of the application.
3. Make any changes that you require to the CICS bundles that are deployed with the application binding.
   1. Click Add or Remove to change the selection of CICS bundles that are deployed with the application binding.
   2. Double-click on any of the CICS bundles to edit them. Update and reversion the CICS bundles and add the new versions to the application binding, in the same way as described in Updating an application project for the CICS bundles for the application.
4. To edit any of the policies that are deployed with the application binding, double-click on the name of the policy in the list in the application editor to open the bundle manifest editor. When you have updated the policy, use the bundle manifest editor to increment the major, minor, or micro version numbers for the CICS bundle according to your versioning policy, and save your changes. Include the updated CICS bundle containing the policy in the application binding, and remove the old version.
5. On the Deployment tab of the application binding editor, check that each of the CICS bundles for the application, and each of the CICS bundles deployed with the application binding, is bound to a suitable region type. Use the switch button to switch between working with the region types, and working with the CICS bundles.
   1. Any CICS bundles that are not yet bound to any region type are marked with the letter X. Working with the CICS bundles, select each new CICS bundle and use the check boxes to specify the region types where it is to be deployed.
   2. Any region types that are specified in the application binding, but cannot be found in the current version of the platform project associated with the application binding, are marked with an exclamation point. Check that you are working with the correct version of the platform project. If you have removed the region type from the platform, or changed to a platform that does not include the region type, clean up the application binding project. Working with the region types, select each unwanted region type and uncheck all the CICS bundles specified for that region type.
6. When you have completed your updates to the application binding, use the Version field in the application binding editor to increment the major, minor, or micro version numbers for the application binding according to your versioning policy, then save your changes.
   Tip: The version number for the application binding does not have to be the same as the version number for the application. However, according to the principles of semantic versioning, you should update the version number for the application binding to reflect the largest change in the application, or in the CICS bundles deployed with the application binding.