IBM Support

IJ13029: REGISTERED IOT DEVICE TYPES DO NOT APPEAR ON MAP DATA SCHEMAS WHEN MXE.OSLC.IGNORECOLLECTIONREF IS SET TO 1

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

  • ERROR DESCRIPTION:Ø
    Steps to reproduce in IoT Connection:
    Go through the IoT wizard.
    On the Register Device Types page, select a device type and
    choose Register as Asset.
    The device type is removed from the table.
    Select Next to move to Map Data Schemas.
    The device type that you just registered does not appear in
    this table.
    
    This issue occurs when the mxe.oslc.ignorecollectionref
    property is set to 1.  This property is not ususally present in
    QA environments. (I believe it is installed with Anywhere).
    But the behavior can be verified without Anywhere or IoT
    installed.
    
    Leave the Maximo classic tab open and open a new browser tab in
    the same session.
    Paste the following URL:
    <maximo URL>/maximo/oslc/os/mxapiasset?l
    ean=1&collectioncount=1&oslc.select=assetnum,description&oslc.wh
    ere=location=%22BR430%22
    Note that no _collectionref values are included in the results.
    
    Go back to the Maximo tab and set the Global Value to 0.  Save
    and Live Refresh.
    In the second tab, resubmit the request.
    Note that the _collectionref values appear now.
    
    To reproduce manually:
    Go to System Properties.
    Create a new property having these values:
     Name: mxe.oslc.ignorecollectionref
     Description: Should OSLC responses exclude the
    collectionref?
     Data Type: YORN
     Global Value: 1
    Save and Live Refresh
    

Local fix

  • Set the property value to 0.  If Maximo Anywhere is installed,
    this may adversely affect performance.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users using oslc rest api                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * if the property mxe.oslc.ignorecollectionref is set to 1 -   *
    * the collectionrefs are not sent as part of the json.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * This should not be set to 1 - this should always be passed   *
    * using the query parameter ignorecollectionref=1              *
    ****************************************************************
    

Problem conclusion

  • do not use the property mxe.oslc.ignorecollectionref - always
    use the query parameter to do the same
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ13029

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-24

  • Closed date

    2019-01-25

  • Last modified date

    2019-01-25

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

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

Document Information

Modified date:
25 January 2019