IBM Support

IJ36434: ERROR 500: "BMXAA9278E - THE JSON PATH USER WAS NOT FOUND" IS SHOWN WHEN PERFORMING INBOUND PROCESSING FOR AN ASSET.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • DESCRIPTION: Inbound processing doesn't allow to create an Asset
    without entering user data.
    
    STEPS TO REPRODUCE:
    1) Use OOB Object structure: MXASSET; Enterprise service:
    MXASSETInterface; External System; EXTSYS1
    
    2) Go to JSON Mapping; Create a new Mapping; Map Name:
    EXTSYS1.MXASSETInterface.IN
    
    3) Object Structure: MXASSET; Direction: Inbound Processing
    JSON Data is as below:
    {    "asset": "string",
       "details": "string",
       "siteid": "string",
       "user":
       [
           {
               "asset": "string",
               "person": "string"
           }
       ]
    }
    
    4) Switch to Properties tab of JSON Mapping:
    EXTSYS1.MXASSETInterface.IN
    
    (a) Under JSON Object Mapping; Process Order: 1; you have
    Object Name: Asset; Object Path: ASSET; Property Path: /
    
    (b) Click on Map More Objects; Process Order: 2; Object Name:
    ASSETUSERCUST; Object Path: ASSET/ASSETUSERCUST; Property Path:
    //user; Relation Property Name: user
    
    (c) Under JSON Properties Mapping for Process Order 1
    Target Attribute Source Property
    ASSETNUM	 $.asset
    DESCRIPTION	 $.details
    SITEID		 "BEDFORD"
    
    (d) Under JSON Properties Mapping for Process Order 2
    Target Attribute Source Property
    PERSONID	$.person
    ASSETUM		$.asset
    SITEID		"BEDFORD"
    ISCUSTODIAN	true
    
    
    5) Now, send a POST Request via Postman. The message is in JSON
    format and includes both Asset and User data. This works fine
    and the Asset+ Custodian is created in Maximo successfully.
    
    URL: http://maximohost/meaweb/es/EXTSYS1/MXASSETInterface
    Headers:
    maxauth: bWF4YWRtaW46bWF4YWRtaW4=
    Content-Type: application/json
    Sample Json data
    {    "asset": "TESTJ1",
       "details": "Mapping Test Asset",
       "siteid" : "BEDFORD",
       "user":
       [
           {
               "asset": "TESTJ1",
               "person": "MAXADMIN"
           }
       ]
    }
    
    Review this asset: TESTJ1 is created successfully at Maximo and
    under Common actions: Associate User and Custodian; MAXADMIN is
    listed under Users and Custodians; Person.
    
    
    6) Send another POST request, this time by removing the user
    data.
    
    URL: http://maximohost/meaweb/es/EXTSYS1/MXASSETInterface
    Headers:
    maxauth: bWF4YWRtaW46bWF4YWRtaW4=
    Content-Type: application/json
    
    Sample Json data
    {    "asset": "TESTJ2",
       "details": "Mapping Test Asset",
       "siteid" : "BEDFORD"
    }
    
    We get an error:
    
    Error 500: BMXAA9278E - The JSON Path user was not found.
    
    
    RESULT: POST request cannot be sent without user information as
    seen for the second asset - "TESTJ2".
    
    EXPECTED RESULT: POST request should be allowed to send without
    user information.
    
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.2
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When posting an oslc transaction in JSON format including    *
    * only the parent object (and not including a child object)    *
    * the transaction errors indicating JSON path is invalid       *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: | Release 7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ36434

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-12-07

  • Closed date

    2022-01-07

  • Last modified date

    2022-01-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
08 January 2022