Installing a MobileFirst Interim Fix? Don't forget to sync up Maximo Anywhere as well.
Shane Howard 270000C70V Visits (10836)
It's been awhile since my last blog on Maximo Anywhere but this latest topic has come up a few times and I wanted to share some information on what is required if you are updating your MobileFirst application with an interim fix. As some of you may of run in to there are situations which may require you to update your MobileFirst application with a later interim fix, what you may not know is that Maximo Anywhere uses specific MobileFirst libraries during it's build and if you do not ensure they are updated as well you may end up with some undesired results.
One of the main issues is when your run time is built using older versions of the libraries then the MobileFirst server, it will cause a migration to happen. During this migration some information may be stripped out of the war file, such as the attachment servlet. When your war is migrating from one version to another during the deploy you will be able to see a message similar to the following in your MobileFirst Server Configuration Tool.
This is only one issue, but you may see instances where your issues are not fixed or addressed by the latest interim fix as well.
So how do we prevent these issues? It's as simple as copying the new libraries over to the MaximoAnywhere build folder.
After installing your Interim Fix and updating MobileFirst take a look at the following folders and copy the four libraries you see below.
Place these files in the
This is a little shorter then normal, but should be helpful with future Anyw