What's New in WSRR Version 8.5
DavidSeager 110000C5XS Visits (10029)
WebSphere Service Registry and Repository version 8.5 has been released for download, and I've worked on the release. Can't get to Impact this year to attend the WSRR sessions? Then I invite you to read about what is new in WSRR V8.5. For a 2 minute video showing you just what the new features are, check out the video on our YouTube channel.
First I must state that the following information is all my own recollection. There may be inaccuracies, and no warranty is given as to the accuracy of the descriptions. For the official line, check out the offi
The Business Space User Interface was decommissioned and replaced with a faster performing and more user friendly interface, which is self contained within WebSphere Service Registry and Repository.
The "dashboard" UI is entirely new and replaces the old Business Space UI. However it is extremely similar; widget, Web 2.0, AJAX based. It still has the concept of separate dashboards, called "Views", with multiple pages where you arrange and wire widgets together.
However now we are in control of the code base, so we have added menus to configure things like lock down mode and default permissions directly into the UI. Adding a custom widget is now as simple as uploading a ZIP using the UI.
Additionally, sharing spaces and permissions used to be on the basis of groups or users. Now you can map view permissions using WSRR roles themselves, so you can say users in the WSRR development role are allowed to view the "Development" view. This means no more mapping LDAP groups to WSRR roles for WSRR access control, then having to share spaces to LDAP groups. Now you can just use WSRR roles throughout.
A further advantage of the UI being self contained is that the installation is far simpler. Now the dashboard UI is installed when you create a WSRR profile in WebSphere Application Server (or deploy WSRR to a cluster), and the WSRR database scripts create everything needed on the DB side. There is no need to run separate commands to deploy the UI or register the widgets. When a fix pack comes along you will no longer need to run a separate command to update the WSRR widgets; they are part of the WSRR EAR. You also don't need to configure those pesky endpoints any more.
All this is gravy, but what about the actual UI itself? The dashboard UI can now do tricks like pre-loading the business model information needed to render objects, and all the request are asynchronous. The UI no longer needs to provide a general framework for iWidgets and is closely tied into WSRR. The upshot of this is that it is a bit quicker than the old Business Space UI and feels much snappier.
For a video tour of the new dashboard, check out this Dash
Adds Google Chrome browser support, and the newer and more advanced browser versions for Mozilla Firefox and Microsoft Internet Explorer (IE).
Of course some of the speed increases are due to us being able to support Chrome and the latest Firefox and Internet Explorer web browsers. Not much more to say about these browsers, and I can't comment on which is the fastest, you'll have to try them all yourself :)
Support for WebSphere Application Server V8.5.
WSRR 8.5 of course runs on WebSphere Application Server 8.5 full profile, that being the traditional WAS we all know and love. It does not run on any other levels of WAS, and it does not run on the Liberty Profile. Of course we support clustering, federated servers and all that good stuff.
Supports IIB Work Load Management (WLM) policy specification and management for usage with IIB objects modelled in WebSphere Service Registry and Repository.
Since WSRR 8.0 we have policy editors in the UI for WS-MediationPolicy policies for DataPower. Now in 8.5 there is additionally a new editor which creates Work Load Management policies as used by IBM Integration Bus V9.0. Now IIB cannot actually pick up these policies and enforce them out of the box, it's not like the WS-MediationPolicy support you get in DataPower. But you can attach them to IIB flows registered in WSRR to show which policies are being enforced in the IIB runtime. You can also export these policies from WSRR and import them into IIB and then attach them to flows in IIB.
A future developerWorks article series will explore the WSRR and IIB integrations fully, and will show what is possible with this policy editor.
Provides the ability to proactively notify consumers of a service that a change is coming for the consumed service.
Otherwise known as "email owner" and "email consumer", this feature allows you to email the owner of a service registered in WSRR, to notify them of something like wanting to use their service. The feature takes the "owner email" field from the service object and pre-fills an email-like dialog with the owner and optionally a message body using an email template. You then edit the message, add any CCs or BCCs and hit send, and the email is sent.
The feature can also email the consumers of a service, perhaps to notify them of downtime or that a new version is available. To do this, you click "Email consumers" and WSRR will find all consumers of the service version you are looking at, by following the Service Level Definition and Service Level Agreement contracts between the service and its consumers. Again the email addresses are pulled from the "owner email" field on the consumer services (or applications or processes) and pre-filled into the email form.
The template feature of WSRR was enhanced for this work - you can easily add a link to the dashboard into the email by specifying the view and page IDs, rather than getting the URL from the web page where you want the user to go when they click the link. You can also now set the email subject in a template, so the subject is specific to a template, rather than before where there was only one subject for all emails from WSRR.
WSRR can also store a copy of the sent email into the Sent folder of your mail server, for the user ID you are using to send all the emails from WSRR. This works for both proactive email and the older email-based subscriptions.
We have a vide
In the classic Web UI it was possible to bring up a list of objects, either by clicking on a type to show, or running a search. Then you could see a list of filters of various types such as the object type, classification or state. Clicking on a filter would filter down the list, much like on Amazon or other sites.
Now this feature has come to the dashboard UI, where you can filter a collection of items by classification, type or state. Firstly the new function works entirely in the web browser in memory, so it is pretty fast. Secondly for the filters of the same type (classification of the same root class or system, object type or state) the filters are additive, so you could for example filter down to all objects of type Service Version or Process Version, and in the In Production state.
The filtering feature makes finding things pretty easy when they are all classified up correctly. You can drill down a set of results by geography, or line of business, or whatever you have used to classify them.
Check out the vide
Now WSRR stores service definitions using WSDL and XSD documents, and sometimes these definitions are split into several different documents, each dependent upon one another. For example, the WSDL that stores the endpoints can be separate from the WSDL that stores the interface of the service, which is separate from the XSD that stores the definition of the objects that the service expects.
This can make downloading all the docs you need to author a service client tricky, you have to click around a fair bit to find where they are in the WSRR object model. With this feature, there is a link on the Action menu called "Download Service Definition Documents" which basically zips up all the WSDLs and XSDs that a service uses to define itself. You can then take the zip and import it into your tooling to create a service client.
See a demonstration vide
Provides web service information to IBM API Management. Lets you select web services from WebSphere Service Registry and Repository for API Management so that a Simple Object Access Protocol (SOAP) API can be created.
Now this one is interesting, and only makes sense given the API
Basically this means WSRR has APIs that can be used by IBM API Management to import web services into API Management. Of course WSRR has always had such APIs, but API Management V3 will be able to import web services from WSRR to make into APIs. This brings us one step closer to the convergence Gartner are talking about - you can govern and control internal SOAP-based web services using WSRR, and then when ready, expose them as APIs to the outside world (or other areas of your business) using IBM API Management, which will pull the definitions from WSRR.
This is something I'm quite keen to see and try out, when IBM API Management V3 GAs on 9th May.
That's it, for more information check out the videos or go to one of the various WSRR
How soon will you pick up WSRR V8.5?