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 February?

JPA container 2.1

The jpaContainer-2.1 feature provides a JPA container implementation without limiting you to the core JPA function in EclipseLink. You can plug in any version of any third party JPA persistence provider implementation that is compliant with the JPA 2.1 specification, including EclipseLink with extensions like MOXy and JPA-RS.

Transport Security 1.0

The transportSecurity-1.0 feature is a superset of the ssl-1.0 feature. You will now be able to call out a global default for outbound SSL, which no longer has to be shared with the default inbound SSL setting. This will allow you to set the outbound default globally rather then having to specify the SSL setting for each component.

Admin Center update

The Java Batch tool of the Admin Center (the adminCenter-1.0 feature) has been extended to allow you to stop and restart job instance executions. A new column in the Java Batch tool dashboard called “Actions” makes it easy for you to manage the Java Batch job instances, in addition to viewing their progress.

Logstash Collector and Bluemix Log Collector update

In the garbage collection events for logstashCollector-1.1 and bluemixLogCollector-1.1, we have added a new field: ibm_maxHeap. The ibm_maxHeap field indicates the maximum heap size that the JVM allows. The Liberty memory dashboard for Kibana 4 has been updated to show the ibm_maxHeap value in the liberty_gcHeap graph.

Liberty: Audit extension

As we bring in the full audit functionality, the Feb beta extends the basis authentication and audit management events to include form login authentication, client certificate authentication and runAs servlet delegation.


  • A new Logging attribute isoDateFormat=true/false has been added for the server configuration. It allows you to configure the Liberty server to write dates in logs/trace/FFDC in ISO-8601 format.
  • A new option --isoDateFormat has been added for the binaryLogging command. You can now view the logs with the dates in ISO-8601 format.

  • This gives you the ability to change the format of the dates written in the Liberty logs/trace/FFDC between the system locale and the standard ISO-8601 formats. It enables you to customize the date and time format in the Liberty logs, to your liking of standard ISO-8601 format or the locale format set by the system.

Spnego 1.0 update

The spnego-1.0 feature now can consume the SPNEGO token and Kerberos token; SPNEGO can now support other clients that can only create the Kerberos token.

What’s already in there?

The January 2017 beta included Logstash Collector and Bluemix Log Collector updates.

Take a look at the previous beta announcements for a full list of stuff added since the 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 *