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 March.

Look out for more betas over the coming months.

Get it now! Ask a question about the beta

What’s in the WebSphere Liberty beta for May?

Social Login feature

Social login is a form of web single sign-on using that uses existing user information in one social medium such as Facebook, Twitter, Google, Github, and or Linkedin to sign a user into a website instead of creating a new login account specifically for that website. WebSphere Liberty server offers social login functionality by adding the socialLogin-1.0 feature, and allows users to select a social media account to sign in to a web site hosted on a Liberty server. Login with a social media account is a fast and convenient way for users to log into your application or website hosted on a Liberty server.

Transport Security feature update

Outbound SSL filtering support has been added. For outbound SSL connections you will now have the ability to configure a SSL configuration to use the base on the host or the host and the port the outbound call is going to.

API Discovery feature update

This feature updates the Swagger libraries that are part of the apiDiscovery-1.0 Liberty feature to their most recently released open source levels.

The Swagger libraries, UI and code generation tool have been updated to their latest levels to match the current development experience with open source. This includes fixes and enhancements up to Swagger-core v1.5.12.

Enhancement to the Java Batch Tool on the Admin Center

You can now restart a job instance with updated parameters. The confirmation dialog that is displayed allows you to add, remove, and alter job parameters for a restart request.

MicroProfile Config feature

With the mpConfig-1.0 feature, you can directly use the Config APIs to retrieve configuration without the need to know where the properties are defined. The properties can be dynamically updated and then retrieved by the applications without the application restarting. The configuration can be located in multiple sources, and has a priority system. If the same property is specified in multiple config sources, the value from the config source with the highest priority will be used. The properties can be overwritten by users in different environments.

MicroProfile Fault Tolerance feature

With the mpFaultTolerance-1.0 feature, you can make the service invocation resilient via retry, fallback, timeout, circuit breaker and bulkhead functionalities. If a service invocation fails, a retry can be performed. After some retries, a fallback operation can be specified. Indefinite waiting is no longer a problem as the timeout can be specified on service invocation. Repeating timeouts are solved by the functionality of the circuit breaker. You will not need to package fault tolerance libraries into your applications any more.

What’s already in there?

The April Liberty beta included the Validator feature and Logstash Collector and Bluemix Log Collector updates.

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 *