Maximo

Maximo

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

 View Only

  • 1.  Maximo Rest API Error

    Posted Mon June 15, 2020 11:04 AM
    We are facing one issue with Maximo REST API.

    We have created a new OS "Z_RFQ". Now using the below link External application is trying to hit the REST URL.
    The Object Strcture "Z_RFQ" has been created with "Use Object Structure for Authorization Name?" equal to 1.
    The security group has been granted access for all the sig options related to "Z_RFQ".

    https://xxxx.yyyyyy.com/maximo/api/os/z_rfq/

    We are getting the below error in external application system.

    "oslc:Error": {
    "oslc:statusCode": "404",
    "spi:reasonCode": "BMXAA4216E",
    "oslc:message": "BMXAA4216E - Unknown Object named Z_RFQ has been encountered. Gather the logs from the <HOME> directory and determine the cause and source of the error.",
    "oslc:extendedError": {
    "oslc:moreInfo": {
    "rdf:resource": "https://mxxxx.yyyyyy.com/maximo/api/error/messages/BMXAA4216E"



    But when are using the Maximo Out of the Box OS for Maximo REST URL.
    https://xxxx.yyyyyy.com/maximo/api/os/MXAPIASSET/

    https://xxxx.yyyyyy.com/maximo/api/os/MXAPIADDRESS/

    We are able to see the result for this. It is working with Maximo

    Is there any more setting that needs to be enabled for Maximo Object Structure to be used in Maximo Rest integration ?

    ------------------------------
    keshav ravindran
    ------------------------------



    #Maximo
    #AssetandFacilitiesManagement
    #MaximoIntegrationandScripting


  • 2.  RE: Maximo Rest API Error

    Posted Tue June 16, 2020 09:06 AM
    I can't say I've seen this issue before. Did you load the object structure in an unusual way (such as a DBC file)? It almost seems like there is a cache issue where your JVM doesn't recognize the object structure. There can be issues related to object structure cache when you have bad references, so I would try restarting the server and see if you getting any errors in the logs on startup trying to load the cache.

    Unrelated, but unless you need to use OSLC functionality, I would recommend providing the lean=1 query parameter. You'll eliminate the namespaced JSON that you see above which will reduce the size of your message payloads. IBM covers a lot of good information about the API here: https://developer.ibm.com/static/site-id/155/maximodev/restguide/Maximo_Nextgen_REST_API.html

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

    Original Message


Related Content