IBM Support

PI17480: AUTO SYNC OF FILEREGISTRY.XML IN THE DEPLOYMENT MANAGER ENVIRONM ENT THROUGH VIRTUAL MEMBER MANAGER APIS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • While performing CRUD operations through virtual member
    manager (VMM) APIs in the deployment manager profile the
    changes are reflected only in the file registry of the
    deployment manager profile and those changes are not
    replicated to all the federated nodes in the deployment
    manager.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 making changes to the file      *
    *                  registry at the deployment manager profile  *
    *                  level.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Changes made to the file registry at    *
    *                      deployment manager profile level are    *
    *                      not synced with the federated nodes     *
    *                      during autosync.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a user or group is created from the deployment manager
    profile those changes are not persisted and synced to the
    nodes that are federated under the deployment manager since the
    file registry file is not a configuration file. When auto sync
    service runs periodically it is not able to recognize this
    file regsitry file as a file which has been modified and
    therefore it is ignored during the auto sync process.
    

Problem conclusion

  • Any changes made to the file registry of the deployment
    manager profile will now be synced to all the nodes that are
    federated under it as part of the auto sync process.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.3.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI17480

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-09

  • Closed date

    2014-07-14

  • Last modified date

    2014-07-14

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022