InterMapper 5.2 introduces an expanded SDK, including the ability to export many of the files in the InterMapper Settings folder via an HTTP API. We have created two scripts, one for Windows, one for everything else, to make use of the HTTP API to implement cloning of an InterMapper installation.
Users are often reluctant to stop their running InterMapper installations for any number of good reasons. Because this cloning operation can be performed while the InterMapper installation being cloned is still running, it is useful to the user in several scenarios:
1) A ready-to-use alternate in case of primary failure. You can keep a second InterMapper installation ready to start up in the event of failure of the primary installation. By periodically executing the cloning script via a scheduler such as cron or at, you can automatically update this alternate, so that it will be guaranteed to be up-to-date as of your last script execution.
2) An easy way to create a test installation without stopping your primary installation. By using this script, you can, without stopping your primary InterMapper installation, clone an existing installation to use in testing a new release of InterMapper before committing it to production.
3) As a demo of the API. If you think you might be able to make use of an HTTP API, these scripts provide a working example of how to use it.
Several notes:
1) While the InterMapper installation being cloned must be running, the target InterMapper installation must not be, as the cloning script must be able to overwrite files there.
2) The cloning script copies the entire InterMapper Settings folder, except for the Chart Data folder and the InterMapper Logs folder. Thus, it is not an appropriate tool for making a complete backup of your InterMapper installation.
3) The cloning script only copies the InterMapper Settings folder; it does not copy InterMapper itself. You must manually install InterMapper on any alternate machine.
To download the scripts:
Windows version
Mac/Linux/Unix version
More reading:
Complete information about the scripts and their use
HTTP API Overview (There's a lot more to it than I've mentioned here.)
You need to be a member of iMapper Community to add comments!
Join iMapper Community