Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
  • 1.  Does Anywhere's lookup data JSON datastore have indexes?

    Posted Wed April 28, 2021 09:11 PM
    Anywhere Work Technician 7.6.4:

    I've been told that Anywhere stores it's lookup data in a local JSON datastore.

    Assuming that's correct, does the JSON datastore have indexes? (or an equivalent mechanism?)

    I'm troubleshooting a lookup data performance issue in Anywhere. And I am just trying to understand what can be done / how it works.

    Thanks.


    #MaximoAnywhere
    #Maximo
    #AssetandFacilitiesManagement


  • 2.  RE: Does Anywhere's lookup data JSON datastore have indexes?

    Posted Thu April 29, 2021 08:48 AM
    I'm not positive on 7.6.4 specifically but I would be extremely surprised if they removed it with the new architecture. Earlier versions that used MobileFirst (<=7.6.3.1) did and burned us multiple times because of it because you'd add a new indexed attribute to an existing object and it wouldn't be updateable over the air anymore. We opened a RFE (IBM Software RFE Community: View request) that was initially approved but has since been rejected (though is moot now since it's not on MobileFirst).

    The way it worked then (and the attributes still exist so I assume the same) is on the resource in the app.xml specify index="true" and if you want it to be an exact search, have the isExactMatchIndex="true" on it as well. That should index that attribute in the resource for searching.

    ------------------------------
    Steven Shull
    Director of Development
    Projetech Inc
    Cincinnati OH
    ------------------------------



  • 3.  RE: Does Anywhere's lookup data JSON datastore have indexes?

    Posted Thu April 29, 2021 11:13 AM
    Maximo Anywhere 7.6.4 indeed does still use a JSON store, and as indicated by Steven the use of index="true" and isExactMatchIndex="true", indeed assists in performance. If you do indeed change the shape of the JSON resource (i.e. you add new attributes) you will best be served by flushing the cache and reloading the data source (especially in development.) In production you will hopefully have learned from your development journey whether or not you need to flush data/cache in production to avoid the issue to which Steven refers.

    ------------------------------
    Bradley K. Downing , MBA
    IBM Certified Adv. Deployment Prof. Maximo v7.6.1
    IBM
    Bakersfield CA
    ------------------------------