Maximo Spatial

  • 1.  mxe.map.queryLimit system property and risk of performance issues

    Posted Thu February 29, 2024 10:16 AM

    Hi all,

    We have customized the Work Order Tracking application for a client so that a pin will be visible on the map for each asset present in the multiple asset and location section (MULTIASSETLOCCI).

    Our client has some work orders with large numbers of assets.

    Here is an example of how it looks for a work order with 457 assets:

    The mxe.map.queryLimit system property limits the number of records that can be displayed on the map to 500.  So, when accessing the map on a work order with more than 500 assets, we get the following message:

    I could increase the value on the mxe.map.queryLimit property, but I'm worried we'd end up running into performance and/or timeout issues.

    I have looked for information/recommendations on this but haven't found any.

    Would anybody know where I could find this type of information?

    Gaétan Savard



    ------------------------------
    Gaétan Savard
    ------------------------------


  • 2.  RE: mxe.map.queryLimit system property and risk of performance issues

    Posted Fri March 01, 2024 02:18 PM

    Are you using Maximo Spatial?  If yes, what version? There is a tool called WORelatedRecordsTool that you can enable (either in Map Manager or App Designer) for use on your map tool bar.  When enabled, this tool will show you a pin on the map for each asset in the Multi Asset, Loc, CI table. See screenshots below.



    ------------------------------
    Lacey Lurges
    ------------------------------



  • 3.  RE: mxe.map.queryLimit system property and risk of performance issues

    Posted Mon March 04, 2024 11:16 AM

    Hi Lacey,

    Maximo is presently at 7.6.1.1, Spatial 7.6.0.5, which does not have this tool available.

    We have a test environnement which is at Maximo 7.6.1.3, Spatial 7.6.1.1.  I'll run some tests there with this tool, to see if it runs into the same limitations imposed by the system property.

    Thank you for the information.  I'll post the results of my tests here.



    ------------------------------
    Gaétan Savard
    ------------------------------



  • 4.  RE: mxe.map.queryLimit system property and risk of performance issues

    Posted Tue March 12, 2024 02:37 PM

    Hi Lacey,

    Is this new tool also subject to the limitation imposed by the mxe.map.queryLimit property?

    As I mentionned, I am worried that changing the value of this property, which is currently set to 500, for a larger number (1000, 2000...) might end up causing performance issues in Maximo, or lost of connection for the user.

    Would you have any documentaion/information/recommendation as to what we should set the value of this property to?

    Any help would be appreciated.



    ------------------------------
    Gaétan Savard
    ------------------------------