Deployment errors and failures
It is important to remember that both MessageManager and RunMaps have to be deployed, one after the other. Deploying MessageManager will not include the RunMaps. Failing to deploy RunMaps will cause export run maps to fail with condition code 3 (map not available).
The msg_mgr.msd provides three different deployment definitions for MessageManager and one for RunMaps, all preconfigured for a default Windows platform. The following should be checked:
| Check | Notes |
|---|---|
| Build and transfer maps | This should display the mmgr folder on the server that is going to run Message Manager. If it is not correct, the global search/replace failed and has to be redone. Showing a Windows path when the server is a UNIX variant is an indication the global search/replace failed or was not done at all |
| Generate and transfer Launcher Control File | Must be configured to point to the systems folder on the server and must be done manually for all deployment scripts that have it check marked |
| Transfer Additional Files | Must be configured to point to the mmgr folder on the server and must be done manually for all deployment scripts that have it check marked. You have to press ENTER for the path to take, simply clicking OK after editing a path will result in the edited path being lost. This option is only necessary if transferring files to a server or different Windows drive. For example, if the mmgr.mrn file is being transferred to a UNIX server. If the design and runtime installs are the same, (deploying and running on the same Windows machine, this option can be left unchecked). |