Originally published by Robert Laird.

WSRR 8.5.5, released in March 2015, is all about simplification of the SOA Registry & Repository experience. You can read more about What’s New in WSRR 8.5 and 8.5.5 to get the full story.

One point that’s easily lost in all of the exciting new user interface and wizards for loading and consuming services is that there have been significant performance improvements in WSRR 8.5 and especially WSRR 8.5.5. We’ve seen significantly faster database access and retrieval in WSRR 8.5.5 that translates into faster response for WSRR users, and one can argue that alone is worth having your enterprise consider upgrading to WSRR 8.5.5. In particular, WSRR 8.5.5 provides:

• Improvements to write performance, particularly for large updates.

• Significant performance improvement in WSDL load particularly for medium and large WSDLs.

• Significant improvement in text search index update. Frequency of 15 seconds for index update is now feasible even on large data sets. Can
be applied to existing profiles, but needs to be explicitly enabled.

• There are new recommendations for database log sizes that are particularly useful for WSRR implementations performing large promotions and loading large WSDLs. You can find the specific recommendations here.

We’ve put a lot of effort and work into documenting the process for upgrading to 8.5.5 from WSRR V6.3, V7.0, V7.5, or V8.0. Note that upgrading from V8.5 to V8.5.5 is like installing a fix pack. That is, there is no migration of configuration or database when upgrading from V8.5 to V8.5.5. You can find the detailed instructions and an example for upgrading to WSRR 8.5.5 in our Knowledge Center. There are 7 steps to upgrading:

1. Install WSRR V8.5.5.

2. On the source system, capture the configuration profile.

3. On the target system, load the configuration profile.

4. Use the manage content interface of the target system web UI to migrate the content from the source WSRR system. For those using DB2, it’s critical that you run DB2 RUNSTATS after the WSRR DB2 database is first created just after loading the profile and after the data is loaded from the source system. If you do not, DB2 will generally not use the indexes to access data from the database, which is likely to slow down performance. For more information on DB2 performance, see the “WSRR Governance and Runtime Databases” section of WSRR Performance Optimization.

5. Run selected upgrade plug-ins on the migrated data to convert it so that it you can use new features implemented with WSRR V8.5.5.

6. When upgrading from Version 7.5 or Version 8.0, you can export existing Business Space spaces, and import them into the dashboard.

7. After performing a migration, re-index text so that the text search works in both the dashboard and web UI.

Join The Discussion

Your email address will not be published. Required fields are marked *