Migrating Project Code

These sections provide specific procedures for migrating existing code based on ALBPM 5.7.2 into ALBPM 6.0.x. You must migrate your project code with ALBPM Studio before upgrading an existing ALBPM Enterprise environment.

  1. Import 5.7 project into Studio 6.0
    Follow this procedure to import an ALBPM project developed with version 5.7 into ALBPM Studio 6.0.
  2. Fix External Resources
    Due to improvements to the way ALBPM handles integration with other external systems, you might need to do some minor changes to the External Resources of your projects.
  3. Changes in Standard Components
    Some standard components of the catalog are no longer available on this version, and others are now deprecated. This version also provides new components, which can cause conflicts when migrating old code.
  4. Changes in Dashboards
    The Dashboard components have been improved on ALBPM 6.0. They use a new graphics layer and provide new functionality. As a result, you might need to modify some of your existing 5.7 Dashboards to make them fully compatible with this new version.
  5. Changes in Implicit Java Classpath
    Implicit directories added into Studio's Java "classpath" have changed in version 6.0.
  6. Changes in PBL
    Changes in Process Business Language
  7. Changes in Transformations
    The deprecated feature of Transformations have been removed on ALBPM version 6.0.