 |
|
Worklight 4.2 Overview |
| |
|
Watch an overview of Worklight's new release for enterprise architects and application developers, addressing mobile challenges in team development, enterprise integration and application management. |
 |
| |
|
View comprehensive release notes for Worklight 4.2. |
|
 |
|
| New Environments |
|
| Release 4.2 introduces support for the following environments and the native and JavaScripts APIs they provide: |
|
 |
|
Apple's iOS 5 |
|
|
|
Android 4.0 Ice Cream Sandwhich |
|
|
|
Windows Phone 7.5 Mango |
|
|
|
| Application Development |
|
|
|
|
Support for PhoneGap 1.0 - Release 4.2 includes PhoneGap version 1.0 as part of its client run-time. |
|
| |
|
OS X10.7 Lion and Xcode 4.2 - Developers of iOS apps can now run the Worklight 4.2 Studio on Mac OS X 10.7 Lion |
| |
|
as well as use Xcode 4.2 to add native Objective-C code to their native and hybrid apps, build their apps, run them in the iOS emulator, and package them for the App Store. |
|
|
|
|
Prototype 1.7 - The Worklight client run-time framework has been upgraded to support the Prototype 1.7 library. |
|
|
|
|
Enhanced Builder Granularity - Release 4.2 includes an enhanced builder functionality for creating hybrid mobile |
| |
|
apps. The new builder is seamlessly integrated into the Worklight Studio. With the new builder, developers can build only specific environments at a time, instead of building all supported environments on each Build action. |
|
|
|
Centralized Build - The Worklight Builder is now available as a standalone application that can be integrated with a |
| |
|
central build service, effectively enhancing the collaboration and automation of the development process. See the Worklight 4.2 Developer's Reference Guide for details. |
| |
|
| |
 |
|
|
| |
| |
|
For performance reasons, custom notification states are not automatically saved by the Worklight Server. Release 4.2 introduces a new API is introduced thato saves these notification state. See the Worklight 4.2 Developer's Reference Guide for more details. |
|
|
|
Simplified New Environment Template - In release 4.2, the HTML, CSS, and JavaScript templates that are |
| |
|
automatically generated upon creation of a new environment are simpler and easier to understandhave been simplified. |
| |
|
• |
|
The new app HTML template no longer contains the "content" and "auth" div elements. This makes it immediately |
| |
|
|
|
compatible with third-party JavaScript toolkits such as Sencha Touch and jQuery Mobile. |
| |
|
• |
|
The JavaScript templates no longer require knowledge of object-oriented JavaScript development. |
|
|
|
Remote On-device Debugging - With Worklight 4.2, developers can use tools such as weinre to remotely inspect |
| |
|
their app, running on an emulator or a physical mobile device. See the Worklight 4.2 training modules for further details. |
|
|
|
Studio Preview - The Worklight 4.2 Studio now allows developers to preview an app in a specific environment directly |
| |
|
in the Eclipse's project browser by invoking a context-menu option. |
|
|
|
Disconnect From the Worklight Server - In release 4.2, the WL.Client.init() function allows developers to initialize the |
| |
|
app without attempting to connect to the Worklight Server (instead of trying to connect and handling a connectivity failure). This improves the application's startup performance in offline mode and simplifies the application code. |
|
|
|
Android Widgets - In release 4.2, developers can use Worklight’s Java API for Android to write widgets that |
| |
|
communicate with the Worklight Server and retrieve backend corporate data. Refer to the Worklight 4.2 Java API for Android guide for details. |
|
|
|
JavaScript Access to Native BlackBerry Dialog Boxes - In release 4.2, the WL.SimpleDialog client-side API now |
| |
|
renders native dialog boxes on BlackBerry devices. |
|
|
|
Windows Phone 7 Fragments - Fragments in Windows Phone 7 are now supported by the Worklight Studio. |
| |
|
Developers can now split WP7 apps into multiple HTML files and use the fragments and page mechanism to load them in run- time, thereby minimizing application load time, facilitating simultaneous development of the application, and improving code maintainability. |
|
|
|
| Authentication and Integration |
|
|
|
Support for Complex Login Scenarios - Release 4.2 introduces new server-side components that allow developers to |
| |
|
implement complex, multi-step login scenarios in server-side JavaScript adapters. In addition, Release 4.2 contains a simplified template for development of in-app login screens and authentication sequences. Refer to the Worklight 4.2 Developer's Reference Guide and training modules for details. |
|
|
|
Out-of-the-box support for Kerberos, NTLM, Basic, and Digest authentication for HTTP integration - |
| |
|
Simplifying integration with HTTP-based services that require authentication. Integration with Kerberos, NTLM, Basic, and Digest authentication can be easily achieved by simple configuration of the HTTP adapter, without having to write server-side code. |
|
|
|
Simplified Proxy Configuration for HTTP Integration - Release 4.2 introduces easy and flexible configuration of |
| |
|
HTTP-based services that must be accessed via proxy. Proxy settings can be defined separately for each adapter, including support for authenticating proxies and HTTPS proxies. |
|
|
|
SOAP Eenvelopes Signing with X509 Certificates - Enabling secure exchange of messages between the Worklight |
| |
|
Server and back-end applications that support X509 certificates. |
|
|
|
Server-side JavaScript Debugging - Enabling developers to fully debug their server-side JavaScript code, using Eclipse |
| |
|
Helios's JavaScript debugger. See the Worklight 4.2 training modules for further details. |
|
|
|
| Runtime, Security and Management |
|
|
|
Support for WebSphere Application Server 7 and Higher - With Release 4.2, administrators can package the |
| |
|
Worklight Server, together with its customer-specific properties and code, to create a deployable on WebSphere Application Server versions 7 and higher. Learn more |
|
|
|
Revamped Push Notification Model - Release 4.2 introduces a new server-side API for pushing notifications to mobile |
| |
|
devices using the Apple and Google notification services. It also introduces matching JavaScript and Objective-C APIs for subscribing to notifications and handling them on the client side. The new API methods provide greater flexibility in supporting the following scenarios: |
|
| • One application running on multiple devices |
| • Multiple event sources used in the same application |
| • Multiple applicatitons using the same event source |
| • Multiple users logging into the same application |
|
| |
|
For performance reasons, custom notification states are not automatically saved by the Worklight Server. Release 4.2 introduces a new API is introduced thato saves these notification state. See the Worklight 4.2 Developer's Reference Guide for more details. |
|
| |
|
Enhanced Remoted Disable - When disabling an app remotely via the Worklight Console, administrators can now |
| |
|
specify a link to an application store, where a new version of the app is available. When such a link is specified, the app will display a button that redirects the user to the applicable store at the specified location, allowing immediate downloading of the new app version. |
|
|
|
Backgroud Mode Behavior - Before an application enters background mode, iOS saves a screenshot of the app that is |
| |
|
displyed to the user while the app is retrieved. In 4.2, developers can control the behavior of the app prior to entering background mode through a set of predefined options or custom JavaScript code. Refer to the Worklight 4.2 Developer Reference Guide for additional details. |
|
|
|
