Here’s the latest WebSphere Liberty beta and WebSphere Developer Tools (WDT).

Thanks to your support for our regular beta programme, we are able to release new Liberty features every few months. Most recently, in December.

Look out for more betas over the coming months.

Get it now! Ask a question on Stack Overflow

What’s in the WebSphere Liberty beta for December?

transportSecurity-1.0 feature

The transportSecurity-1.0 feature adds an alternate name to the ssl-1.0 configuration.

Superseding ssl-1.0, the transportSecurity-1.0 feature decouples enabling the transport security from the implied protocol. The ssl-1.0 feature does not control the enabled transport layer protocols (that is controlled by the JVM security settings), but the name had been interpreted by some to imply the SSL protocol version. As with all features, ssl-1.0 will never be removed, but we are looking for feedback on the the new transportSecurity-1.0 feature and whether or not it is an improvement in the feature name.

MongoDB Integration 2.0 feature update

The mongodb-2.0 feature has been updated to include SSL support. You can now create an SSL connection from Liberty to a MongoDB database. When defining a mongo instance in the server.xml there is now an sslEnabled option, which takes a boolean value to indicate an SSL connection. There is also an option sslRef, which is used to provide a reference to a Liberty SSL configuration. This can be used to specify a truststore if needed to ensure that Liberty will trust the certificate of the MongoDB server. If no sslRef is specified then the default SSL configuration will be used.

What’s already in there?

The November/December 2016 beta included the Liberty Audit feature, IBM Hybrid Connect for Liberty, Logstash and Bluemix log collector improvements, the new JSON Web Token feature and running Liberty as a Windows service.

Take a look at the previous beta announcements for a full list of stuff added since the 16.0.0.2 release in June 2016:

Get it now! Ask a question on Stack Overflow

Join The Discussion

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