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.

You must first migrate the code of all the ALBPM projects that are published. Refer to Migrating Project Code for detailed procedures on how to migrate existing 5.x projects to 6.0. Also, make sure the migrated project code is compatible with the previous versions of the project.

You must follow this procedure for all ALBPM projects (and versions) you have published on your Enterprise environment.

Login to the Process Administrator.
Click on Projects.
For each project that you must re-publish:
1. Press Publish.
2. Select Exported Project and browse for the exported (.exp) project file.
3. Check the Republish a previous version and Deploy processes after publishing them options.
4. Press OK to continue with the normal publish&deploy procedures.
  The Choose Version page will appear
5. On the Version drop-down, select the project version you are replacing and press Next.
  Note: If you get an "Incompatible Version" message, it means the code you are trying to publish is not compatible with the currently published code. Potential causes:
  - You accidentally broke compatibility of your project code when migrating the project code from 5.x to 6.0.
  - You saved and exported the project with a version of Studio prior to 5.7.2 before opening it in 6.0.
  - You saved and exported the project with a version of Studio prior to 6.0.1 before publishing via Process Administrator.
6. Press Next to go to the Publication Info page.
  You will see the publication information, including the mappings to existing variables, roles and external resources.
7. Press Publish to go to the Deployment Topology page.
  You should accept the default selections to re-deploy the project to the same Engine.
8. Press OK to finish the deployment of the project.