Compiling Monitor Models
Once a monitor model has been edited in the Monitor Model editor, the EAR file that represents the deployable unit of the model must be built. Right-clicking on the Monitor Model and selecting Generate Monitor JEE Projects will achieve this task.
Once completed, the application can be deployed on the Monitor server.
In rare cases, the compilation can get confused in ID. A solution to this is to delete the generate code and then re-compile from scratch. To achieve this, switch to the
Resource Eclipse perspective and delete the two projects which are called:
When the monitor model is changed, this recipe needs to be repeated in order for the changes to take effect. In principle, it should be possible to simply re-deploy the new EAR with the existing one still published but practice has shown this to be extremely problematic. My strongest recommendation is to:
If after making a change to your model you find that there is no obvious runtime change, carefully check that you have rebuilt and republished the EAR model. It is not an uncommon error to make a change to the model and neglect to rebuild and republish.
It takes a few minutes to un-deploy, build and re-publish. You will need a machine with sufficient resources to make this a workable recipe.
It has also been noticed that even though the deployment of the new model appears completed from the ID Servers view, work is still on-going as shown in the console log. When I publish new models, I keep an eye on the console log to ensure all work has completed before progressing with new tests. Specifically, I continuously see the EAR being published, it saying it is started … a minute passes … it says it is stopped and then finally it says it is started again.
Versioning Monitor Models
If we wish to create a new version of a Monitor Model while maintaining the data already collected, we do this by we update the Model Version timestamp to be a later value.