Modular Messaging Help

Print | Back | Fwd | Close Home | Search | Site Index

Re-deploying caller applications

If you have made changes to a caller application, it can be deployed again. When re-deployment succeeds, new callers have access to the updated version of the caller application immediately. Any callers using the existing version of the caller application at the time it is re-deployed continue to interact with the old version as long as they remain connected to the caller application. Temporarily, therefore, more than one version of the caller application can be stored and running on an MAS.

Each caller application contains an embedded identifier and a revision number. The revision number is incremented each time that the caller application is saved.

Even if a caller application’s *.uma file is renamed or copied by Windows Explorer, the application’s embedded identifier does not change and the MAS treats it as the same application.

An MAS that is contacted by the Caller Applications Editor and asked to deploy an application checks to see if it already has a copy of the application deployed. If the MAS already has an application with the same embedded identifier and the same or a higher version number, it does not accept the re-deployment, regardless of the file name on the application.

If, however, you use the Save as option from Caller Applications Editor to rename an application, the new version of the *.uma file has a new embedded identifier and revision number; so the application is treated as a different application, and you can successfully deploy it.

Top of page