Since delivering Java EE 7 Full Platform compliance back in June, we’ve been finishing off some of the other features that we’ve beta’d over the past few months.

WebRTC The new WAS Liberty rtcomm-1.0 and sipServlet-1.1 features provide the middleware functionality that enterprises need to embed real-time communications into web and mobile applications. The Rtcomm feature supports JavaScript developers through a set of open source SDKs and samples available in GitHub. It also includes a set of back-end services for WebRTC endpoints including a registry, call queues, gateway, and third-party call control. The SIP Servlet programming model is now also available for advanced signaling applications, including support for both SIP and Rtcomm endpoints. Get started at WASdev.net/webrtc!

SIP Tools Create and edit SIP 1.1 applications for deployment to the Liberty Beta runtime. Use the SIP Project and SIP Servlet wizards to create your applications:





The SIP Servlet wizard enables you to specify the servlet selection type, in addition to the method stubs you want to generate in your SIP servlet class:





You can edit your deployment configuration using the SIP deployment descriptor editor:





Working with job parameters for Java batch job submission It’s now easier to work with job parameters for Java Batch job submission. We’ve enhanced the launch configuration to show you a list of the job parameters that are being used in your job file. This will help you avoid possible typos and makes adding the job parameter name as easy as selecting an item from a combo list. The combo list shows you only the job parameters you haven’t yet added to the launch configuration. You can still add parameters by typing the name if you want, but you’ll be warned if this job parameter does not exist in your job file.









SAML 2.0 Security Assertion Markup Language is a data format for exchanging authentication and authorisation data. Liberty supports the SAML web browser single sign-on profile with HTTP Post bindings. Liberty acts as a SAML service provider. Using the SAML web SSO feature, a web user authenticates to a SAML identity provider which produces a SAML assertion. Liberty uses the SAML assertion to establish a security context for the web user without the requirement of on-premises user registry.

APIs to create SPNEGO token We now provide APIs to create the SPNEGO token. Applications can use these APIs to create the SPNEGO token based on different parameters like the native credentials, the user subject information, user name, and password. The applications can send this token in the request to services that can handle SPNEGO authentication.

Servers and Runtime Explorer view The Servers and Runtime Explorer view now has a new menu option, Open Log Files. Viewing log files for Liberty servers is now easier because you can open the Message Log file and Trace file within the Eclipse workbench using the default editor. You can view log files for local as well as remote servers with this option:



Health Management for WAS Liberty The Health Management feature constantly monitors the health conditions of Liberty servers. When a specified health issue is detected, the defined corrective and/or diagnostic actions are automatically executed. The Health Management feature automatically detects and corrects the Liberty server health problem, therefore reducing downtime in the environment. The Health Management feature works well with the dynamic routing and auto-scaling features of Liberty. When a health problem is detected, an alternate Liberty server can be started and new requests can be routed to the new Liberty server automatically. Here’s video of the new Health Management capability.

Maintenance mode of WAS Liberty A Liberty server or the host of a Liberty server can be placed into maintenance mode. When a host or server is in maintenance mode, dynamic routing will route new requests around the host or server in maintenance mode. If placing a host or server into maintenance will cause an auto-scaling breach of policy, auto-scaling will start another Liberty server to handle the workload. Host or server maintenance operations can be done without service distractions with the Liberty maintenance mode feature. Maximum benefits are achieved when maintenance mode feature is combined with the dynamic routing and auto-scaling features. The Liberty server can be put into maintenance mode before the maintenance operation so that there are adequate Liberty servers running to handle the workload.