MxLoader now supports Web Services

By default MxLoader uses plain Object Services through HTTP calls. These services are automatically exposed when an Object Structure is created in Maximo. Using Web Services is possible to have more control over data defining processing classes, user exit classes, XSL maps, and processing rules.

MxLoader 5.1 now allows to use Web Services as well. To enable MxLoader to work with Web Services you need two settings in the Config sheet:

  • Server address must be changed to http://[MXHOST]/meaweb/services/
  • Use Web Service option must be set to ‘True’

When a WebService is defined from an Object Structure you can just specify the WS name in cell A2 as you normally do. However, when the WebService is defined from an Enterprise Service you have to specify the web service name with a dotted notation in cell A2 with format [EXTSYSNAME]_[ESNAME].[OSNAME]. For example, if your External System is ‘MYEXTSYS’ your Enterprise Service is named ‘MYESVC’ and based on ‘MXASSET’ you have to specify MYEXTSYS_MYESVC.MXASSET in cell A2.

You can download MxLoader from here.

Please use MxLoader forum to report any issue.

MxLoader now supports Web Services

4 thoughts on “MxLoader now supports Web Services


  2. This is out of date correct? The new version of MxLoader 8.4.1 has the
    OS Service Context Root
    OSLC Service Context Root
    API Service Context Root
    XML Namespace
    Which will build a REST URL soi we no longer touch the Server Address URL and by telling it we are using REST Service it will pick what is needed and build the URL?

    Just want to double check as I can find no new documentation for Mxloader that spells this out? Is there a more recent manual for Mxloader that shows more info about REST and samples to what you fill in for its use?

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top