Fixes are available
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
This APAR is a collection of defects that are applicable to version 8 Profile Mangement Tool and WebSphere Customization Toolbox
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IBM WebSphere Application Server V8.0 * * users of the Profile Mangement Tool and * * WebSphere Customization Toolbox * **************************************************************** * PROBLEM DESCRIPTION: Five problems are fixed with this * * APAR. * * (1) Creating a secureproxy profile * * using manageProfiles.sh (or * * manageProfiles.bat) does not * * instantiate the https port * * (2) The Profile Management Tool for * * z/OS collects the certificate * * expiration date in a fixed format * * that is not appropriate for the * * active locale. * * (3) After creating a profile for * * WebSphere Application Server for z/OS * * the manage profiles log file contains * * a number of "Read-only file system" * * error messages. * * (4) During profile creation user * * specified host name is not passed on * * to the default personal and root * * signing certificate generators, * * instead the host name of the system * * is used. * * (5) Creation of an unusable entry in * * WebSphere Customization Toolbox (WCT) * * when a read only WebSphere Plugin * * location is specified to the tool. * **************************************************************** * RECOMMENDATION: * **************************************************************** The description of the five problems fixed by this APAR are given. The order corresponds with each problem description given in the Problem Description section. PMT referes to the Profile Management Tool below. (1) If manageProfile.sh (or manageProfiles.bat) is invoked with the -startingPort parameter to create a secureproxy profile with then startingPort value is not handled well and the https port in the profile created is not instantiated. This problem does not exist in the PMT GUI interface. (2) The PMT for z/OS collects the certificate expiration date in a text widget and requires the user to specify the expiration date in YYYY/MM/DD format, which may be inappropriate for the locale. (3) There are a few places in the configuration actions that run when creating a profile for WebSphere Application Server for z/OS where chmod commands are issued that do not use the "-h" option. The "-h" option instructs the chmod command to not attempt to change the permissions of files that are the target of symbolic links. Because the "-h" option is not used, the chmod command attempts to change the permissions of files that are the targets of symbolic links and because these files are located in the WebSphere Application Server install image, which is normally mounted as a read-only file system, the "Read-only file system" error messages are generated. (4) This problem occurs when creating a profile via either the PMT GUI interface or the command line manageProfiles.sh and if the user specifies a host name overriding the default system host name. In this case the generated default personal and root signing certificate distinguished name (DN) values incorrectly include the system host name, rather than the user specified host name value. (5) This problem occurs when the WebSphere Customization Toolbox (WCT) is supplied a WebSphere Plugin (Plugin) location that gives read only permission to the tool. This can happen when a user who has launched WCT is different from the user who has write permission to the Plugin directory and the file permission does not allow the WCT user to write to the Plugin directory. Under these circumstances WCT erroneously creates a metadata entry for the Plugin location specified instead of reporting an invalid location. However, because of lack of write permission the plugin location will not be processed and a failure will result. However, this erroneous location is not only remembered by WCT but also can not be deleted by the user to recreate with valid Plugin locations.
Problem conclusion
Code changes were made to fix the 5 problems. The fix for this APAR is currently targeted for inclusion in fix pack 8.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
Comments
APAR Information
APAR number
PM38947
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-11
Closed date
2011-07-22
Last modified date
2011-08-17
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
R800 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.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
27 October 2021