 |
|
Adapters – WorkLight components that facilitate bidirectional communication to enterprise information systems, including data retrieval and transactions. Adapters support both synchronous and asynchronous communication. They can be specific to an enterprise application such as SAP R/3 or Oracle Siebel, or generic, supporting a widely-used technology such as SQL or Web Services. Adapters are configured using a simple XML files, and are extensible via Java-based SDK. |
| |
|
Data Retrieval Mechanism – WorkLight implements intelligent data retrieval logic that determines when to access backend systems.
|
| |
|
Authentication and Access Control Mechanisms – WorkLight uses JAAS to integrate with existing authentication systems, supporting multiple authentication schemes, user directories, single sign-on, and multi-factor schemes. Every connection to WorkLight is authenticated and encrypted so that any incoming request is associated with a known user. This permits WorkLight to enforce a user's access privileges and provide a highly-personalized experience. WorkLight's patent-pending Declarative Item Level Access Control technology enables controlled access to data from multiple sources without duplicating existing access control logic or requiring credential caching. |
| |
|
Data Cache – WorkLight decouples client access to data from the retrieval of data from information systems. To accomplish this, WorkLight implements a cache that buffers clients from information systems, and is governed by policies configured by system administrators. |
| |
|
Integration Layer – This component is responsible for managing the communication processes to enterprise applications. It ensures that load exerted on enterprise applications does not exceed pre-configured rules; it implements a uniform model for all incoming data, regardless of the system of origin; it maintains the freshness of data stored in the WorkLight cache; and it guarantees integrity of enterprise data when performing transactions. |
| |
|
Secure Provisioning – WorkLight includes a secure provisioning server that seamlessly integrates with existing aggregation sites' provisioning processes. It generates unique per-user per application instance one time ‘add-to’ URLs to initiate provisioning. It associates application instances with users and containers and securely verifies the association on every access to prevent unsanctioned duplication and distribution. |
| |
|
Widget Framework – WorkLight’s unique “Write Once – Run Anywhere” widget framework enables web 2.0 application developers to build an application once and make it available on multiple web 2.0 environments, including social networks, smart mobile phones, personalized homepages, and desktop widget engines. The widget framework automatically generated wrappers for all environments, supports new environments as they become popular, makes widgets behave natively in the environment they run in (e.g. allows docking for desktop widgets), provides abstractions to common environment services, and allows the developer to customize behavior and look and feel for each environment when necessary. |
| |
|
Web 2.0 Security – WorkLight protects Web 2.0 client applications by implementing multiple layers of security using patent pending technologies to thwart Web attacks such as XSS, XSRF, and various forms of phishing. Among other measures, WorkLight employs web security best practices; enables the SSL trust model by providing full-window authentication dialogs making server address and SSL indicators explicit even when running within a 3rd party containers; and uses high-entropy random identifiers to ensure widget and container authenticity. |
| |
|
Web 2.0 Serving – The process by which WorkLight supplies data to Web 2.0 client applications. Web 2.0 technologies such as RSS and AJAX generate a large number of server requests through RSS server polling or by generating multiple requests per page-view (AJAX). WorkLight's serving mechanism supports high transaction loads while keeping latency low. Serving performance is extremely important since it has a significant effect on the end-user computing experience. |
| |
|
Catalogs – Facilities by which end users select the proprietary information from enterprise applications they choose to view. |
| |
|
| |
|
Widget catalog – Allows users to browse, locate, and install web-based and desktop widgets published by the company, partners or peers |
| |
|
Stream catalog – Allows users to subscribe to a set of related data items based on a single backend enterprise system via an RSS feed. For instance, a stream can contain Sales Opportunity records from a CRM system or Invoices Past Due from an ERP system. |
|
| |
|
Stream Composition Facilities – A web-based facility is provided through which end users can define new stream channels (i.e. RSS feeds). |
| |
|
APIs/SDKs – WorkLight supports a wide variety of “out-of-the-box” Web 2.0 interfaces. To support additional interfaces, WorkLight provides application developers with APIs and a developer’s kit. Through these APIs, WorkLight handles the security, access control, application provisioning, proxying, data integration, data and formatting and retrieval, so that application developers can focus on presentation, usability and application logic. |
| |
|
Management Facilities – WorkLight is designed to operate within the existing corporate IT environment. As such, it incorporates elements designed to ease and streamline deployment and ongoing management. |
| |
|
Examples of provided functionality include the following: |
| |
|
| |
|
Integration with enterprise management systems (EMS) through a JMX interface, so that operators can monitor the WorkLight server through their central console. |
| |
|
Web-based administration UI. |
| |
|
XML-based configuration facilities for adapters and information channels. |
| |
|
Statistics gathering capabilities for WorkLight usage. |
|
| |
|
|