Copies of the Evaluated Configuration Guides may also be obtained by emailing email@example.com.
|AquaLogic Interation Publisher 6.4|
The TOE is a product suite for business process management (BPM), or creating, executing, and optimizing business processes. It enables collaboration, business, and information technology (IT) to automate and optimize business processes. The TOE provides security functions that control user access to business process definitions and active instances of those processes. Users may be granted or denied access based on their organization affiliation, assigned group, assigned role, assigned groups, or identity, which is verified by the TOE. The components of the TOE are:
The BEA AquaLogic BPM Studio provides the environment for both designing and developing a process. It has an external interface that can be used by business analysts, business architects, and developers.
The BEA AquaLogic BPM Process Execution Engine orchestrates all processes and their resources—people, organizations, applications, and systems—managing proper sequence, enforcing business rules, and auditing each step to ensure process execution, escalation, and exception management.
The BEA AquaLogic BPM WorkSpace provides the external interface through which a participant interacts with the Process Execution Engine.
The BEA AquaLogic BPM Process Administrator is the console that provides the external interface that enables administrative management of, organizational information: participants, roles, groups, permissions, categories), engines: add, remove, start, stop, general configuration information: connectivity information to external databases and systems, and publish, Deployment, and undeployment of projects.
The BEA AquaLogic BPM Archive Viewer (Archive Viewer) is a web application that provides the external interface that provides IT administrators and business users with historical activity data for business processes that had previously run in the Process Execution Engine.
The BEA AquaLogic BPM Log Viewer (Log Viewer) provides the external interface that enables administrators to read information logged by the Process Execution Engine.
The BEA AquaLogic BPM Admin Center (Admin Center): provides the external interface designed to help administer a BEA AquaLogic BPM implementation. The primary focus of Admin Center is to setup and configure the BEA AquaLogic BPM installations
The Target of Evaluation (TOE) is AquaLogic® Interaction Publisher 6.4 MP1 Patch 1, henceforth referred to as Publisher.
Publisher is a web-based software application that functions as a remote server of AquaLogic Interaction (ALI) to provide the services required to deploy content-driven applications, such as a customer support knowledge base or sales support center, where users can create and manage Web content without HTML skills. Publisher is not a stand-alone product; rather it integrates directly with ALI and depends on ALI portal pages and security functions. ALI, in turn, is the base portal application and framework for the BEA AquaLogic User Interaction (ALUI) product family. ALI integrates custom-developed applications and ALUI components into a cohesive web-based work environment that is viewed from a user’s web browser.
Publisher supports the definition of structured content types, web browser form-based data entry, and publishing of content by combining data values with a text presentation template and copying the result to a file system or FTP server. Publisher enables users to:
Publisher also provides a workflow function that enables an organization to manage the review, approval, and publishing of content using structured and repeatable processes. Authorized users define workflows, which consist of an ordered list of workflow activities, each of them assigned to a user or group of users. Publisher provides portlets that enable tracking of personal workflow assignments and content items in workflow by folder
Publisher implements user data protection by applying a role-based access control policy to folders in the folder hierarchy. All objects within a folder are subject to the access controls applied to the containing folder. Additionally, Publisher supports security management by defining security management roles and restricting security management activities to defined roles.
Publisher integration with ALI uses several ALI functions including: user and group management; document storage and management; content search; object security; and user identification and authentication.
|AquaLogic Interaction Collaboration 4.2||AquaLogic Interaction 6.1 with AquaLogic Interaction Development Kit|
The Target of Evaluation (TOE) is AquaLogic® Interaction Collaboration 4.2 MP1, henceforth referred to as Collaboration. Collaboration is part of the AquaLogic User Interaction (ALUI) suite of products and is designed to work with AquaLogic Interaction 6.1 with AquaLogic Interaction Development Kit 6.0, hereafter referred to as ALI.
Collaboration is not a stand-alone product; rather it integrates directly with ALI and depends on ALI portal pages and security functions. Collaboration functions as a remote server of ALI by providing Collaboration data and application functions in portlets and application views to ALI users. A collection of Collaboration web services provide the communication mechanism for this exchange of portlet data between ALI and Collaboration.
Collaboration is a web application featuring a collection of collaboration tools that help users organize, share, and manage information. Collaboration facilitates teamwork among members of a project team by providing a unified online workspace for project members to share information. Collaboration can have many projects and project information can be accessed from any ALI community page or My Page that contains a Collaboration portlet.
AquaLogic Interaction (ALI) is the portal platform for the BEA AquaLogic User Interaction (ALUI) suite of products. A portal is a Web site that gives users a single point of access to applications and information in a single unified interface. ALI includes a portal infrastructure, a user interface (UI), a document content management system, and a search function. ALI integrates applications and ALUI components into a cohesive Web-based environment that can be customized and personalized to meet the internal and customer-oriented portal needs of large enterprise companies.
AquaLogic Interaction Development Kit 6.0 (IDK) offers Java platform and .NET client-side libraries that provide connectivity to Web services-based application programming interfaces (APIs) for ALI.
ALI’s portal framework integrates applications by using portlets and also supports virtual community workspaces. Portlets are one of the mechanisms that end users use for accessing data and applications from portals. Portlets enable the integration of functionality from external systems in the portal page, thus providing a single entry point (or window) for a wide range of content and services. Portlets can be used for everything from displaying useful information to building integrated applications that combine functionality from multiple systems. The ALI portlet architecture conforms to Service-Oriented Architecture (SOA) and leverages the key SOA interfaces and protocols: HTTP and SOAP. SOA is an IT strategy that organizes the discrete functions contained in enterprise applications into interoperable, standards-based services that can be combined and reused quickly to meet business needs.
Most of the ALI portal’s end-user and administrative functionality and tools are packaged and implemented as portlets. ALI organizes this functionality into categories and implements each category in a set of portlets. The categories include the following:
The IDK APIs (included with both the Java and .NET versions of the IDK) provide support for portlet development, including manipulating settings, accessing user information, and managing communication with the portal. Security is enforced by the portal in exactly the same way as when the functionality is executed from within the portal. In the ALUI web services architecture, most portlets are hosted remotely and connect to a back-end application for data or functionality. The remote portlets can access an API provided by the IDK called the Programmable Remote Client (PRC). The PRC API provides interfaces to perform object-oriented access into the portal’s SOAP API, which exposes elements of the portal API.
The IDK also enables developers to create remote authentication services. The IDK Authentication API provides an abstraction from the necessary SOAP calls and enables developers to simply implement an object interface for the external authentication service.
The AquaLogic Interaction Development Kit (IDK) enables Java and .NET developers to build and deliver user-centric composite applications through AquaLogic Interaction. The IDK provides interfaces for pagelets, portlets and integration web services – authentication and profile services, crawlers, and search services. The 6.0 release of the IDK includes a proxy Application Programming Interface (API) used to create pagelets for implementation in AquaLogic Interaction.