WebSphere Service Registry and Repository V6.3.0 Fix Pack 1
Downloadable files
Abstract
This is Fix Pack 1 for IBM WebSphere Service Registry and Repository V6.3.0.
Download Description
Fix Pack 1 is the first maintenance release for the WebSphere Service Registry and Repository V6.3.0 product shipped June 2009.
Important notes:
If deploying to WebSphere Application Server v6.1 it is recommended that you apply APAR PK79489 before applying WebSphere Service Registry 6.3 Fix Pack 1. This APAR is available in WebSphere Application Server Fix Pack 25
If you are deploying to WebSphere Application Server v7 then please ensure you have at least Fix Pack 5.
Additional steps might be required to upgrade your configuration profiles.
If you have NOT modified any configuration items in either the basic profile or governance enablement profile, then simply use the WSRR Web UI to load the new basic profile and/or governance enablement profile from the v6.3.0.1 file system.
The profiles can be found at:
<WSRR_INSTALL_ROOT>/install/config/BasicProfile_v63.zip
<WSRR_INSTALL_ROOT>/install/config/GovernanceEnablementProfile_v63.zip
Where <WSRR_INSTALL_ROOT> is the install location for WSRR v6.3.0.1.
Because configuration profiles names must be unique, name the updated basic profile BasicProfile_v6301, and name the updated governance profile GovernanceEnablementProfile_v6301.
Once loaded, the appropriate profile can be made active and the original profiles deleted from the system.
If you HAVE modified either the basic profile or governance enablement profile, export the modified profile and perform a difference comparison between the exported profile and the WSRR 6.3.0.1 profile. Then, merge any of your changes into the files from v6.3.0.1. When you are satisfied that the merge is complete, load the modified v6.3.0.1 profile into WSRR.
Because configuration profiles names must be unique, name that the updated basic profile BasicProfile_v6301, and name the updated governance profile GovernanceEnablementProfile_v6301.
The following APARs are fixed in this fix pack.
IZ51665 Promotion fails if environment filtering is applied to the object being promoted
IZ52622 Notification emails do not have the FROM header set
IZ54672 SQL errors and transaction timeouts during view graph, export or upgrade
IZ55280 Performance of make governable and transition operations is poor with complex entity graphs
IZ55426 WSDLPort/SOAPAddress not governed when a service endpoint business model is governed
IZ55751 Promotion to production possible even if there are no production endpoints
IZ56223 Studio only generates the SACL and corresponding lifecycle taxonomy if generateUI is set to true
IZ56222 When generating business models in Studio the 'gep63' and 'gpx63' prefixes are converted to uppercase.
IZ57479 Fixes to service registry for 6.3.0.1
Performance and concurrency improvements
Business model wizard: "Unable to deserialize user storage object", now resolved
Load document wizard when loading multiple objects fails to display them all
Impact analysis of business modelled relationships improved
Impact analysis was not returning governance related objects
Impact analysis returned wsdlInput relationship as inputMessage, now corrected
Improvements for Internet Explorer 6
getClassificationSystems returned the wrong number of classification systems, now corrected
In the business model wizard a dependent document was loaded into the registry twice, now resolved
WS-I validator on WAS 7 produced extra validation errors, now removed
ServiceMessages no longer correlated if NoSchemaTypes is set in the correlator
GSR1438E due to incorrect correlation of ExtensionLogicalObject services corrected
GSR0512E when deleting a WSDL resolved
Activating some profiles failed with 'GSR0800E: A business model system could not be created.', now resolved
Event Handler configuration now loads with security enabled
SCA OWL file updated
Service registry install updated to enable SDK 1.6.0 SR5, required for WAS 7.0.0.5
Install now accepts spaces in administrator group names
WASX8009E: Invalid parameter during update corrected
Load document 'Finish' button remained greyed-out despite collection being complete, now resolved
NameNotFoundException resolved for service discovery plug-in
DB2 for z/OS enhancements
DB2 database names restricted to 8 characters (to reflect an underlying restriction in DB2)
CLI enabled for WebSphere AppServer v7
Update process does not update the ServiceRegistry ear file
Database deadlock when more than 1 user performs the create operation at the same time
(Note, if you are using DB2, to benefit from the changes made to prevent deadlocks you must restart DB2 after applying Fix Pack 1).
IZ57480 Fixes to studio for 6.3.0.1
Process hang when regenerating a customized profile has been resolved
IllegalArgumentException error when importing a service registry document has been resolved
Improvements to the task menu
"An error has occurred. See the log file /tmp/63code/configuration/1245262137596.log" has been resolved for installation on SuSE Linux
Problems encountered while processing "delete resources" has been resolved for deleting a configuration project
Sample reports added
UML models added for classification systems
boundSCAimport label corrected to boundSCAImport when generating elements
OWLs now generated with wsrr:default instead of wsrr:defaultValue
IZ57492 Fixes to the Governance Enablement Profile for 6.3.0.1
Errors when loading an XSD as a relationship target resolved
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
