What's New in ALBPM 6.0 Enterprise

This section provides an overview of the main new features, improvements and changes in this release of AquaLogic BPM Enterprise (all editions).

New features

  • There is a new Configuration Wizard which provides a simple way for configuring a complete ALBPM Enterprise installation. It covers the most common configuration tasks, including: creation of Directory Service database, creation of Engine definition and database, complete creation of WebLogic domain, and deployment of a sample project.
  • ALBPM Directory Service can be configured in a Hybrid configuration where authentication and authorization can be delegated to Microsoft Active Directory or Sun One Directory Service while the rest of the metadata resides in a transactional RDBMS. This avoids the need for replication of participants and entitlements data.
  • ALBPM now includes JDBC drivers for the most popular DBMS. This means you can integrate with Oracle, DB2 and Microsoft SQL Server right out of the box.
  • ALBPM RSS Feeds Web Application allows end users to participate in business processes using their RSS Reader of choice being able to authentication and register with a specific view RSS Feed. Each View accessible through WorkSpace can be accessed from an RSS Reader like Outlook.
  • PAPI WebService 1.0 has been deprecated in favor of the new PAPI WebService 2.0. PAPI-WS 1.0 is accessible through ALBPM WorkSpace while PAPI-WS 2.0 is accessible through its own new Web Application (papiws). This new version is functionally equivalent to the native Java PAPI, and adheres to the WS-Security specification using the UserNameToken Profile implementation as well as HTTP Basic Authentication.
  • Native integration with AquaLogic Service Bus 2.6. You can now easily consume ALSB services from ALBPM and also register a business process in ALSB. In addition, a Custom Transport has been implemented over RMI to enforce security and transaction propagation when ALSB and ALBPM run on the same domain. This transport is provided as an Enterprise Application (.ear) which serves as a plugin for ALSB.
  • Web Services in ALBPM now include support for WS-Security, Document-Literal style and WS-I compliance.

Changes and Improvements

  • Configuring ALBPM Directory Service purely on top of LDAP provider is no longer possible.
  • ALBPM project directories do not use the .fpr extension anymore.
  • The Directory configuration file directory.properties is now XML-based and changes its name to directory.xml.
  • ALBPM JSR-168 Portlets have been deprecated in favor of the new WorkSpace deployable in WebLogic Portal (WLP) 10.0 and ALUI 6.1MP1. This new interface matches the WorkSpace functionality as well as supporting SSO.
  • It is now simpler to deploy ALBPM projects on WebLogic and WebSphere editions of ALBPM Engine. It is no longer necessary to generate and deploy an EAR file for each ALBPM project. Only the Engine EAR needs to reside in the J2EE container. The Engine application dynamically loads the project models and executable code from the Directory Service.
  • ALBPM WorkSpace Extensions (for integration with ALUI) is now included with ALBPM Enterprise. This consolidates the installation and setup on a single install package.