PI93411: Saving changes to member's configuration files via Admin Center's Server Config tool will get applied to the controller instead.

Fixes are available

APAR status

Closed as program error.

Error description

When using Admin Center's Server Config tool, any changes to
a member's config file that is being accessed indirectly
(via a controller) will cause the file to instead be saved
to said controller, either updating the contents of its
equivalently named file (like server.xml) or creating a new
file.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Liberty Administrative     *
*                  Center's Server Config tool                 *
****************************************************************
* PROBLEM DESCRIPTION: Saving changes to a collective member's *
*                      configuration files via Admin Center's  *
*                      Server Config tool will cause them to   *
*                      be applied to the collective controller *
*                      instead.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When accessing Liberty Admin Center's Server Config tool through
a collective controller, any changes to a collective member's
config file will cause the file to instead be saved to the
collective controller, either updating the contents of its
equivalently named file (like server.xml) or creating a new file
if one does not exist.

Problem conclusion

The fix causes the collective member's config file to be
correctly saved to the collective member instead of the
collective controller.

The fix for this APAR is currently targeted for inclusion in fix
pack 18.0.0.1.  Please refer to the Recommended Updates page for
delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Enable Admin Center on the collective member and access it
directly to change its configuration via the Server Conig tool.
Alternatively, make changes to the configuration files directly
(or via WDT in Eclipse) instead of through Admin Center.

Comments

APAR Information

APAR number
PI93411
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-06
Closed date
2018-03-05
Last modified date
2018-03-05

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
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

RCD0 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":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI93411: Saving changes to member's configuration files via Admin Center's Server Config tool will get applied to the controller instead.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

RCD0 PSY

Document Information

Share your feedback

Need support?