Thanks for all your support for our beta program so far. Here’s the latest beta of WebSphere® Application Server Liberty Profile and WebSphere Developer Tools (WDT).

Check out our Java EE 7 progress here!

Look out for more betas over the coming months. Some of the features in previous betas are now available and supported in production in WebSphere Application Server Liberty Profile V8.5.5.

Get it now! Give feedback on dWAnswers

What’s in the Liberty beta for June 2015?

In the June 2015 Liberty beta, we’ve mostly focused on quality and on tidying up the Java EE 7 features we’ve been implementing over the previous betas, oh and doing a whole bunch of bug fixes.

Liberty runtime

OpenID Connect Client feature Liberty OpenID Connect Relying Party supports multiple OpenID Connect providers. You create multiple openidConnectClient elements and multiple authentication filters. Each openidConnectClient element defines one Single-Sign-On relationship between Liberty profile and one OpenID Connect provider. Liberty OpenID Connect Client and Liberty OpenID Connect Provider support OAuth 2.0 Form Post Response Mode specification, http://openid.net/specs/oauth-v2-form-post-response-mode-1_0.html . When configure Liberty OpenId Connect Client to use implicit grant type and response_mode=form_post , it can participate in web Single-Sign-on with OpenID Connect Provider that is running in a different firewall.

OpenID Connect Server feature Liberty OpenId Connect provider can delegate user authentication to a third-party OpenId Connect provider. To enable this authentication delegation, you configure the OP as an OpenID Connect relying party.



WebSphere Developer Tools

New and improved feature conflict dialog We’ve added tons of new features for the Liberty server that can be installed and enabled on the fly. To help solve feature dependency issues we have a new and improved feature conflict dialog that provides information more concisely and clearly. Problem features are flagged and each feature lists the features it is in conflict with. Simply add and remove features within the dialog to resolve conflicts.

Admin Center

Supports push notifications for collective changes Enable the websocket-1.1 feature in the collective controller that is hosting Admin Center to enable push notifications. Admin Center will automatically detect push notification support and register for updates when the page loads, which reduces overall system resource utilization and gives near real time updates to changes in your environment.

What’s already in there?

In the May 2015 beta, we made it easier to configure a Web Profile or Java EE 7 server and done a whole bunch of things in the WebSphere Developer Tools for Eclipse to support our runtime updates in previous betas.

Previously we also updated Admin Center so that it now supports push notifications for collective changes – simply enable websocket-1.1 in the collective controller which is hosting Admin Center to enable push notifications. Admin Center will automatically detect push notification support and register for updates when the page loads, which reduces overall system resource utilization and gives near real time updates to changes in your environment.

In earlier betas, we added JSF 2.2, Remote EJB support, CDI 1.2, JSP 2.3 and EL 3.0, application client 1.0, JASPIC 1.1, JACC 1.5, SIP Servlets 1.1 and tools, SPNEGO support, OSGi App integration, JDBC 4.1, OSGi & Web 3.1 facet configuration for OSGi bundles, and JAX-RS 2.0 client wizard; we fixed a shedload of bugs and added things like support for remote development, auto-scaling and dynamic routing, Real-Time Communications (WebRTC) and CouchDB; finally, there was JAX-RS 2.0, Java Batch, JMS 2.0, JPA 2.1, bean validation 1.1, JSON-P 1.0, EJB 3.2 Lite, concurrent-1.0, Servlet 3.1, OpenID Connect, Java 8 toleration, WebSockets, a facelift for the Liberty Repository…

Go take a look at the previous beta announcements for a full list:

Get it now! Give feedback on dWAnswers