MxLoader

 View Only

  • 1.  MxLoader vs Flat File imports

    Posted 10-11-2023 05:47

    Hi,

    I'm just wondering if anyone could give me their opinion of the differences between using the MxLoader for data impots into Maximo vs using a Flat File through the Maximo UI.

    One of the biggest challenges i have is that the  MxLoader is not "officially" supported by IBM. However, there must be a point in the process from pressing the "Run" button in MxLoader to the data being inserted into the Maximo database that IBM do pick up the support.

    I was hoping someone already had a diagram/image showing the differences between a MxLoader data import vs a Flat File import before i created one myself. I know for most of the process they are doing the exact same thing anyway.

    Thanks 



    ------------------------------
    Matthew Atkinson
    EAMC
    ------------------------------


  • 2.  RE: MxLoader vs Flat File imports

    Posted 10-11-2023 09:28

    MXLoader is not officially supported but uses the same Object Structures which you will do using Maximo UI Import. 

    If you draw the diagram internal processing will remains same as when data loading is happening it is going through same layers of processing as Maximo UI Import will do.

    Maximo UI Import is not recommended if data amount is high as it impacts Maximo performance while MXLoader have batch load mode which you can play with and load much high amount of data. Same goes for exporting data from Maximo vs MX Loader. 



    ------------------------------
    Prashant Sharma
    Sedin Technologies
    Connect with me @ https://www.linkedin.com/in/psharmamaximo/

    #IBM Champion 2022
    #IBM Champion 2023
    ------------------------------

    Original Message


  • 3.  RE: MxLoader vs Flat File imports

    Posted 10-12-2023 19:31

    Sorry, no diagram.

    As already stated this is going through the same object structures and processing as for flat/XML files.  So, in that sense, it is fully supported as all this is doing is converting the MXDataload sheet into XML and processing that XML through the Object Structures.

    If you use a flat file, you must have the Object Structure marked as supporting flat files meaning you will have to create an alias for each conflicting column, whereas, with the MXLoader it converts to XML and therefore no issue and saving you some gried.

    The MXDataloader is fast and visual, whereas, using a flat file import you have to look at the import processing to see if it was successful.

    The flat file can be run via cron task meaning you can simply add the sheet to a folder, then cron will then pick it and process it.  Great to user isolation as they don't need to have a Maximo license.

    Hope that helps.



    ------------------------------
    Regards,
    Craig Kokay
    ISW
    Maximo Practice Manager
    eMail: ckokay@isw.net.au
    Phone: +61-411-682-040

    #IBMChampion2023
    ------------------------------

    Original Message


  • 4.  RE: MxLoader vs Flat File imports

    Posted 10-11-2023 10:27

    MXLoader utilizes either the SOAP or REST API depending on whether you choose the service as OS (SOAP) or REST on the config tab.

    All the APIs (flat file, IFACE table, REST API, SOAP API, etc.) for MIF are supported by IBM in the sense that the framework capabilities and the object structures we ship are supported. That being said, customers can create their own object structures or modify our object structures. While these will typically work, it doesn't mean that all functionality would work as the customer expects. The object structures we ship we sometimes need to provide processing classes to handle some of the more complex operations such as executing the asset move logic when the location/parent asset are changed. 



    ------------------------------
    Steven Shull
    IBM
    ------------------------------

    Original Message


Related Content