PH50114: THE SECURITY.XML DOES NOT GET UPDATED FOR A WAS 8.5.5.21 NODE DURING SYNC PROCESS WITH A WAS 8.5.5.22 DMGR.

APAR status

• Closed as program error.

Error description

• When federating a WAS 8.5.5.21 node to a WAS 8.5.5.22 DMGR the
  security.xml file does not get updated during the sync process
  .
  An IllegalArgumentException or FileNotFoundException
  may be seen in the trace.
  
  Additional symptoms:
  The security.xml file in any WAS 8.5.5.19 - 8.5.5.21 node is not
  getting updated during synchronization if the DMGR is at
  8.5.5.22 or 8.5.5.23
  
  The DMGR log may also show
  ADMN1006I: An attempt is made to synchronize the XYZ node...
   FATAL ERROR:  ''
  or
  Back from folder filter extension;
  com.ibm.ws.management.bla.sync.BLASyncFilter@1234567, true
   FATAL ERROR:  ''
                                                           .
  

Local fix

• Update node to WAS 8.5.5.22
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  with a deployment manager on version        *
  *                  8.5.5.22                                    *
  *                  and managed node on version 8.5.5.19 -      *
  *                  8.5.5.21.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: When federating a WAS 8.5.5.19 -        *
  *                      8.5.5.21                                *
  *                      node to a WAS 8.5.5.22 DMGR the         *
  *                      security.xml file does not get synced.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When federating a WAS 8.5.5.19 - 8.5.5.21 node to a WAS
  8.5.5.22
  DMGR the
  security.xml file does not get synced. An
  IllegalArgumentException
  or FileNotFoundException may be seen in the trace.
  

Problem conclusion

• The transformMetadata.xml file should not include security.xml.
  It has been removed.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.24. For more information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• 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