Interoperability with AquaLogic Products

The interoperability between WLI and AquaLogic products provides a first step toward BEA Workspace 360 and BEA microService Architecture (mSA). In addition, integration with ALSAM and ALER provides capabilities for implementing SOA.

Integration with AquaLogic Service Bus

ALSB is part of the BEA AquaLogic family of service infrastructure products. It manages the routing and transformation of messages in an enterprise system. Combining these functions with its monitoring and administration capability, ALSB provides a unified software platform for implementing Service-Oriented Architecture (SOA). ALSB integrates seamlessly with other BEA products – WLS, WLP, and AquaLogic Data Services Platform (ALDSP) – for creating, consuming, and orchestrating services.

Integration of WLI with ALSB provides a cost-effective solution for building, connecting, and managing integrated process-driven services within and outside the enterprise, by combining the power and flexibility of WLI with the high-performance, stateless mediation of ALSB.

Table 13-1 Integration with ALSB: Features
Feature	Description
Ease of installation	You can install WLI and ALSB in the same BEA_Home. You can deploy WLI and ALSB applications in either a single domain (with a unified run time) or in separate domains. This feature helps you reduce hardware cost, and leverage common resources, libraries, and plug-ins.
Unified design environment	ALSB and WLI projects can be created in the same workspace. Developers can navigate easily between ALSB and WLI design perspectives.
Tight integration with ALSB	WLI processes can invoke external services through ALSB proxy services via ALSB Transport (ALSBT) controls. External clients can invoke WLI processes as ALSB business services. Developers can, at design time, search for RMI-based ALSB proxies and use them in WLI processes. Security and transaction contexts are seamlessly propagated from ALSB to WLI and vice versa.
Aggregated deployment	While deploying applications, you can deploy WLI and ALSB projects from the same workspace.

Integration with AquaLogic Enterprise Repository

BEA AquaLogic Enterprise Repository (ALER) is a SOA repository that provides the tools to manage and govern the metadata for any type of software asset, from processes and services to patterns, frameworks, applications, components, and data services. ALER maps the relationships and interdependencies that connect those assets to improve impact analysis, promote and optimize their reuse, and measure their impact on the bottom line.

Search for services stored in ALER and use them in WLI

You can select services from ALER and use them in WLI processes. You can, for example, search for a specific web service, retrieve the WSDL from ALER, and use it to generate a service control in a WLI process. You can search for assets based on keywords or the type of service (WSDL- or XML-based).

When a service that is stored in ALER is modified, ALER alerts existing users of the service about the change.

Store metadata about WLI artifacts in ALER

You can store metadata about WLI assets in ALER. The metadata includes information that can be used to make the WLI asset discoverable by other products for reuse.

Integration with AquaLogic Enterprise Security

BEA AquaLogic Enterprise Security (ALES) is a fine-grained entitlement management solution that combines centralized policy management with distributed policy decision-making and enforcement. This combination provides management and control of your critical applications and resources with uncompromised performance and reliability, allowing you to adapt to changing business requirements quickly and easily.

Integration of WLI with ALES allows administrators to implement policy-driven security, providing increased security for application- and system-level resources.

Manage users, groups, and roles, and configure policies for applications from a single ALES administration console, regardless of whether the applications are deployed on a single WLI domain/server or on multiple WLI domains/servers.
Create user- and group-based policies for WLI in addition to role-based policies.
Create policies with conditions. A user can, for example, be permitted to start a process only on a week day.
Create policies with attributes. An employee can, for example, be permitted to start a process or execute a node of a process for only as long as the employee is in the finance department and has the role of a manager.
Use ALES run-time APIs to implement security (authentication, authorization, and so on) in WLI applications.

Integration with AquaLogic Data Services Platform (ALDSP)

ALDSP provides the tools and frameworks necessary for rapid development and deployment of data services. Data services encapsulate the logic for reading, writing, and transforming information, insulating data consumers from having to contend with multiple data source formats and connection mechanisms.

WLI applications can use the ALDSP control to access data services that are deployed using ALDSP.

Integration with AquaLogic Business Process Management (ALBPM)

ALBPM integrates the modeling, implementation, execution, and monitoring of end-to-end business processes to support continuous optimization of the entire business process life cycle.

WLI processes (JPDs) can be exposed as web services, which can then be called by ALBPM applications.