IBM Support

IJ24095: WHEN THE LIBRARY.XML IS MODIFIED BY A TENANT AND IMPORTED THE CHANGES ARE GLOBAL AND AFFECTS ALL TENANTS

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:
    
    When the LIBRARY.xml is modified by a
    Tenant and imported the changes are global and affects all
    tenants.
    
    
    PROBLEM:
    
    When loading customized system xml files
    into a multi-tenant Maximo, cause the changes to be seen in all
    tenants. This is causing invalid bindings in the tenants that
    do not have the full changes associated with the modified
    system xml files.
    
    
    PERFORMANCE ISSUE: No.
    
    STEPS TO
    REPRODUCE:
    
    1. Login as the Tenant.
    
    2. Ensure any database
    configurations needed for the modification are already
    completed. In this case, the eg_attr attribute was added to the
    WORKLOG table.
    
    3. Go to Application Designer and export the
    System LIBRARY xml.
    
    4. Save the LIBRARY.xml file to local
    folder.
    
    5. Open the LIBRARY.xml file in an XML editor.
    
    6.
    Search for the location in the XML file that needs to be
    modified or have lines added.
    
    7. Modify the file as needed and
    save it.
    
    8. Import the modified XML logged in as the same
    Tenant.
    
    9. After Tenant is modified and the MxServer restart
    has been completed, they check the change. Log back in to
    Maximo as Tenant and go to an application where the change
    should be displayed. The change displays as expected.
    
    10. Log
    in as another Tenant and go to the same application to see if
    the change is shown. In this case, it is showing as an invalid
    binding because this tenant does not have the eg_attr attribute
    added to the WORKLOG table.
    
    
    CURRENT ERRONEOUS RESULT:
    
    When
    the LIBRARY.xml is modified by a Tenant and imported the
    changes are global and affecting all tenants. The changes done
    by a tenant affect all tenants.
    
    
    EXPECTED RESULT:
    
    The changes
    done by a Tenant should affect only the current
    tenant.
    
    
    ENVIRONMENT (SYSTEM INFO):
    
    Multi-tenant Maximo
    7.6.1.1
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * N/A                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * WHEN THE LIBRARY.XML IS MODIFIED BY A TENANT AND IMPORTED    *
    * THE CH ANGES ARE GLOBAL AND AFFECTS ALL TENANTS              *
    ****************************************************************
    

Problem conclusion

  • Fixed in LabelCacheMgr.java and WebClientRuntime.java
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ24095

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-02

  • Closed date

    2021-08-09

  • Last modified date

    2021-08-09

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

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:
10 August 2021