Maximo Anywhere

Maximo-ICON.png

Maximo

Learn how to increase the operational efficiency of the assets you manage, and improve overall equipment effectiveness by using IoT data and AI.

Maximo-ICON.png

TRIRIGA

Reduce the operational costs of the facilities you manage, and create more engaging occupant experiences through the application of IoT data and AI.

Maximo-ICON.png

Engineering

Learn how IoT data and AI are being applied to transform the end-to-end engineering lifecycle.

Maximo Anywhere 7.6.4 - How to manage your deployments

By Shane Howard posted Thu March 26, 2020 01:47 PM

  

Hi All,

As you move forward with your upgrades and implementations to Maximo Anywhere 7.6.4 you may of been wondering where your applications are being stored now that the MobileFirst runtime no longer exists.  We had a few questions on this during our enablement so I wanted to write a quick blog to go over the new Deployment tab in the Anywhere Administration application. 

When you initially do the Anywhere applications install, or run a subsequent build it uploads the applications to Maximo now instead of MobileFirst. The applications are uploaded either manually via the deployment application or during the build process using CURL and stored in the MAXAPPDATA table. 
 

Once uploaded the data on your application is presented via the Deployment tab in Anywhere Administration as seen below. (Ignore the application name as it pulls this from the app.xml where I had made a change to the name. )


A few more notes on what you’re looking at above.


Active Deployments for Shane’s Work Execution (IBM Maximo Work Execution) shows the latest deployed application, its version and who deployed it.   So, you can see I built and deployed this 7.6.4 application on March 23, 2020 using the user Mike Wilson.

 
You also have the option of “New Deployment” which you can use if you wish to upload the application zip in the IBM\Anywhere\MaximoAnywhere\bin folder manually outside of the build process.

We also have the Inactive Deployments table, when you do a new build your previous active deployment ends up in this table.  The icon with the gear allows you to activate the deployment again, this is particularly useful if you push out a build with an error and need to quickly revert back.  You can manage your inactive deployments and remove them to clean up the view using the trash can.

 
That’s all I have for this blog; I will continue to write new material as I use to on Developer Works.  If you have any comments please leave them below, as well if there is any documentation you are looking for more detail on feel free to request.


#764
#deployment
#deploy
#app
1 comment
77 views

Permalink

Comments

Fri June 26, 2020 03:56 AM

Hi Shane ,
Need some inputs regarding how we can have IDE e.g. eclispe based envrionment set up to develop changes in 7.6.4 ,