Fixes are available
APAR status
Closed as program error.
Error description
In Rational Application Developer v7.0.0.6, in a new workspace, if a Rational Application Developer v6.0 project interchange is imported BEFORE the installed JREs list is populated, then during the import, the list gets populated but the JRE names are incorrect. They all say "runtimeJRE". Here are the recreate steps in Rational Application Developer v7.0.0.6: 1) open a NEW workspace but do NOT click on the "servers" view. 2) window -> preferences -> Java -> Installed JREs, does not show any IBM WebSphere JREs yet. 3) import a project interchange that was created using RAD v6.0. During the import notice that the "servers" view is selected and the WebSphere Applicaiton Server v6.0 and WebSphere Applicaiton Server v6.1 servers are created at that time. 4) After the import go back to the Installed JREs list and you will see that several of the IBM JREs are listed with wrong names. They all have the same name "runtimeJRE". This problem does NOT happen if you click on the "servers" view before importing the project interchange file. In that case, the IBM JREs are created when you click on the "servers" view, and they have the correct names. So, that can be used as a workaround.
Local fix
a workaround is to click on the servers view first, and wait for the websphere servers to be created. that will populate the installed JREs list with the correct names.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * Toolkit v6.1.1 and Rational Application * * Developer v7.0. * **************************************************************** * PROBLEM DESCRIPTION: The Installed JRE entries for the * * various WebSphere Application Server * * installs are all listed as runtimeJRE. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Installed JRE entries for the various WebSphere Application Server installs are all listed as runtimeJRE. This was caused by the JREs being created before the underlying ResourceBundle was instantiated.
Problem conclusion
The controlling logic to instantiate the ResourceBundle was modified to ensure it happened before the Installed JREs were created. The fix for this APAR is currently targeted for inclusion in WebSphere Application Server Toolkit fix pack v6.1.1.7 and Rational Application Developer fix pack v7.0.0.7. Please refer to the Recommended Updates page for WebSphere Application Server Toolkit delivery information: http://www.ibm.com/support/docview.wss?uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK65079
Reported component name
WEBAPP SERVER A
Reported component ID
5724J0820
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-04-25
Closed date
2008-04-29
Last modified date
2008-04-29
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
WEBAPP SERVER A
Fixed component ID
5724J0820
Applicable component levels
R610 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
24 October 2021