APAR status
Closed as documentation error.
Error description
This APAR describes the issues that customers encountered with IBM WebSphere Application Server Version 9.0. These issues were resolved as knowledge center updates in December, 2018.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: This APAR provides a cumulative list of * * the documentation issues for November, * * 2018 * * that affect users of IBM WebSphere * * Application Server Version 9.0. * **************************************************************** * PROBLEM DESCRIPTION: The Knowledge Centers for WebSphere * * Application Server Version 9.0 need * * to reflect customer enhancement * * requests received in problem * * management records (PMRs). These * * enhancements can include fixing * * technical inaccuracies or clarifying * * vague information. * **************************************************************** * RECOMMENDATION: * **************************************************************** See the Problem conclusion section for a description of the issues, which are described in customer PMRs, and the documentation change or changes that will address these issues
Problem conclusion
Note: As we update our knowledge centers, the following Version 9.0 modifications will be available. To access the latest on-line documentation, go to the product library page at http://www.ibm.com/software/webservers/appserv/library and select the version and product that is appropriate for your WebSphere Application Server environment. The following Version 9.0 issues will be addressed: ID: PH05689 Problem: Currently in topic, Implementing RESTful views of an EJB with local interfaces, there is NOTE at the end of the topic that identifies a property with the name: com.ibm.webshere.jaxrs.server.DisableIBMEJBJAXRSInEJBJarSupport The third term is webshere and should be websphere. Resolution: PH05126 is correcting the spelling in the code and the knowledge center topic, Implementing RESTful views of an EJB with local interfaces, is updated. The NOTE containing this misspelled property will be updated so that the property reads: com.ibm.websphere.jaxrs.server.DisableIBMEJBJAXRSInEJBJarSupport This update applies ONLY to V8.5.5 level of the knowledge center. For V8.5.5.15 and ealier use: com.ibm.webshere.jaxrs.server.DisableIBMEJBJAXRSInEJBJarSupport For beyond V8.5.5.15 use: com.ibm.websphere.jaxrs.server.DisableIBMEJBJAXRSInEJBJarSupport --------- ID: #465 (GHE) Problem: WebSphere Application Server 9.0 fixpack 2 (9.0.0.2) updated the remote migration code considerably. A new parameter was added to the createRemoteMigrJar command to allow for additional compatibility with the changes. The new parameter, -allPlugins, is not documented presently in the Websphere Application Server Knowledge Center and should be. Resolution: Topic, createRemoteMigrJar command, is update to add the -allPlugins parameter description that reads: -allPlugins This is an optional parameter when migrating to WebSphere Application Server Version 9.0 fixpack 2 (9.0.0.2) or later. The -allPlugins parameter allows any plugins to the WebSphere Application Server Version 9.0 migration framework to be included automatically in the jar file. The -allPlugins parameter allows migrating of stacked products (for example, WebSphere Portal) that include their own modules in the plugins directory. These stacked products need their own modules to be collected into the remote jar in order for the migration to succeed. Note: In previous versions of WebSphere Application Server, the -allPlugins parameter was passed automatically and any plugins to the WebSphere Application Server migration framework were included automatically in the jar file. In WebSphere Application Server Version 9.0 fixpack 2 (9.0.0.2), use of -allPlugins is NOT automatic and must be directly used. -------- ID: #513 (GHE) Problem: Topic, Configuring the hang detection policy, describes setting generic JVM arguments. Argument in Step #5 of the topic for com.ibm.websphere.alarmthreadmonitor.checkinterval.millis needs to be specified in this step as: -Dcom.ibm.websphere.alarmthreadmonitor.checkinterval.millis Otherwise an error can occur in its use. Resolution: Topic, Configuring the hang detection policy, is updated to that the JVM generic argument is specified as: -Dcom.ibm.websphere.alarmthreadmonitor.checkinterval.millis This update also applies to V8.5.5 knowledge center. ------- ID: #970 (GHE) Problem: There are deficiencies in the message documentation for CWWKS messages in the knowledge center, such as missing ranges and categories -- by way of example, a few message identifiers that cannot be assigned to any category: CWWKS5421E CWWKS6045E CWWKS0800E CWWKS1406E CWWKS1607E CWWKS1920E CWWKS2862E CWWKS9400A Total missing 370 identifiers the subcategory and at 294 is not even the main category Resolution: The knowledge center is updated to incorporate these messages in the next release of the Liberty knowledge center. --------
Temporary fix
Comments
APAR Information
APAR number
PH05689
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
900
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-11-27
Closed date
2018-11-27
Last modified date
2019-03-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 November 2021