Migrating Enterprise Environment

These sections provide specific procedures for upgrading an existing environment running on ALBPM Enterprise 5.7.2 to ALBPM Enterprise 6.0.x.

Follow the procedures in these section to upgrade to ALBPM 6.0, re-using the existing ALBPM 5.x Directory and Engine databases.

The first time you start ALBPM 6.0 Process Administrator during the upgrade, it will automatically alter the schema structure of the Directory database. Likewise, when you first start each Engine, it will alter the schema structure of the Engine database. This means that pre-existing process instances will continue their execution on the new 6.0 environment.

Important: You must perform a full back-up of your 5.x installation, including all databases involved. Your 5.x installation will become unusable after the upgrade. During the the upgrade procedures, the database structures are converted to the new version and will no longer be compatible with version 5.x.
Important: The database (JDBC) users configured for the Directory and Engine Databases must have enough privileges to perform SQL DDL (Data Definition Language) operations (like ALTER, CREATE and DROP statements). Otherwise, the Process Administrator application and the Engine will fail to migrate the structures of their SQL tables and will not to start. This is only needed for the first time you start Process Administrator and each Engine.

Follow all these sections in the order presented. Some sections only apply to specific environments and may be safely skipped otherwise.

  1. Installing ALBPM 6.0 Enterprise
    The first step of the upgrade process is to download and install ALBPM 6.0.
  2. Upgrade steps for ALBPM WE Environments
    Follow these steps only if you are upgrading from an ALBPM WE (WorkSpace Extensions) 5.7 environment.
  3. Un-Deploying 5.7 J2EE Applications
    On ALBPM 5.7 environments running on WebLogic or WebSphere you must first stop and un-install all ALBPM-related .EAR and .WAR applications.
  4. Upgrade ALBPM 5.5 DB structures
    If upgrading from version 5.5.x, you must first run a set of SQL scripts on your existing ALBPM databases. You can safely skip this section if upgrading from version 5.7.x.
  5. Configuring Directory DB
    After installing ALBPM 6.0, you must run ALBPM Admin Center to create a new Directory configuration that will connect to your existing 5.x Directory database.
  6. Starting Process Administrator
    After creating a new Directory configuration pointing to your existing 5.x Directory database you must start ALBPM's Process Administrator to continue with the upgrade procedures.
  7. Re-Configuring Engine DB
    This version of ALBPM includes new JDBC drivers provided by BEA. You must re-configure your Process Execution Engines to use the new drivers.
  8. Validate Engine properties
    Validate that the existing configuration properties of your Engine still apply for your new ALBPM 6.0 environment.
  9. Re-Configuring External Resources
    Some External Resources (formerly "Service Endpoints") need to be re-configured for 6.0. You must change your SQL Database External Resources to use the new JDBC drivers provided by BEA.
  10. Re-Deploying Migrated Projects
    Before starting your Process Execution Engines, you must have your projects migrated to 6.0 and re-publish them to your Enterprise environment.
  11. WebSphere-Specific Upgrade Steps
    If you are upgrading an ALBPM for WebSphere environment, follow these additional steps.
  12. WebLogic-Specific Upgrade Steps
    If you are upgrading an ALBPM for WebLogic environment, follow these additional steps.
  13. Start Execution Engines
  14. Final steps for ALBPM WE Environments
    If you are upgrading from an ALBPM WE (WorkSpace Extensions) 5.7 environment, follow these additional steps.