Chapter 3. Migrating Business Central as design environment only

Procedure

1. Locate the bin/.niogit directory in your current Business Central distribution for Red Hat JBoss BPM Suite 6.4 and locate the same directory in your new Red Hat Process Automation Manager 7.0 installation.

   Example:

   $ ~/$JBOSS_HOME/bin/.niogit

   $ ~/$RHPAM_HOME/bin/.niogit

2. In your command terminal, copy the .niogit directory from your current Business Central distribution for Red Hat JBoss BPM Suite 6.4 to the bin folder of the new Red Hat Process Automation Manager 7.0 installation directory:

   cp -r /$JBOSS_HOME/bin/.niogit  /$RHPAM_HOME/bin/

   The copied .niogit folder is the directory that the migration tool will prepare for Red Hat Process Automation Manager 7.0. The original .niogit folder remains in your Red Hat JBoss BPM Suite 6.4 installation and will not be modified by the migration tool in this procedure.

3. In the Red Hat Process Automation Manager 7.0 bin directory, delete the .index directory. You must delete this folder because Red Hat Process Automation Manager 7.0 comes with certain updates that are not compatible with Red Hat JBoss BPM Suite 6.4. The bin directory will be re-indexed after the migration when you start Red Hat Process Automation Manager 7.0.
4. Note the path to the copied .niogit directory for Red Hat Process Automation Manager 7.0. The path will be required when you run the migration tool.

5. If you have specific dependencies, repositories, or pluginRepositories that you want to add, remove, or update as part of the project migration, create a pom-migration.json file containing these elements. When you run the migration tool, the tool will prompt you if you want to include this file in the migration.

   The pom-migration.json file requires the following sections:

   • "dependencies":[]
   • "repositories-add":[]
   • "repositories-remove":[]
   • "repositories-update-urls":[]
   • "pluginRepositories-add":[]
   • "pluginRepositories-remove":[]
   • "pluginRepositories-update-urls":[]

   If any of these elements do not apply to your project, include them as empty sections to prevent parsing errors.

   Example pom-migration.json file:

   {
     "dependencies":[
   
       {"groupId":"junit", "artifactId":"junit", "version":"4.12", "scope":"test"},
       {"groupId":"com.thoughtworks.xstream", "artifactId":"xstream", "version":"4.12", "scope":"test"}
   
     ],
   
     "repositories-add":[
       {
         "id":"jboss-public-repository-group",
         "name":"JBoss Public Repository Group",
         "url":"http://repository.jboss.org/nexus/content/groups/public/",
         "releasesEnabled":true,
         "releasesUpdatePolicy":"never",
         "snapshotEnabled":true,
         "snapshotUpdatePolicy":"never"
       },
       {
         "id":"kie-internal-staging-repository-group",
         "name":"KIE Internal Staging Repositories",
         "url":"https://origin-repository.jboss.org/nexus/content/groups/kie-internal-group",
         "releasesEnabled":true,
         "releasesUpdatePolicy":"never",
         "snapshotEnabled":false,
         "snapshotUpdatePolicy":"never"
       }
     ],
   
     "repositories-remove":[
       {
         "id":"productization-repository", "url":"http://download.lab.bos.redhat.com/brewroot/repos/jb-ip-6.1-build/latest/maven/"
       }
     ],
   
     "repositories-update-urls":[
       {
         "id":"guvnor-m2-repo", "url":"http://localhost:8080/business-central/maven3/"
       }
     ],
   
     "pluginRepositories-add":[
   
       {
         "id":"jboss-public-repository-group",
         "name":"JBoss Public Repository Group",
         "url":"http://repository.jboss.org/nexus/content/groups/public/",
         "releasesEnabled":true,
         "releasesUpdatePolicy":"never",
         "snapshotEnabled":true,
         "snapshotUpdatePolicy":"never"
       },
       {
         "id":"kie-internal-staging-repository-group",
         "name":"KIE Internal Staging Repositories",
         "url":"https://origin-repository.jboss.org/nexus/content/groups/kie-internal-group",
         "releasesEnabled":true,
         "releasesUpdatePolicy":"never",
         "snapshotEnabled":false,
         "snapshotUpdatePolicy":"never"
       }
   
     ],
     "pluginRepositories-remove":[],
     "pluginRepositories-update-urls":[]
   }

   Example pom-migration.json file with dependencies only:

   {
     "dependencies":[
   
       {"groupId":"junit", "artifactId":"junit", "version":"4.12", "scope":"test"},
       {"groupId":"com.thoughtworks.xstream", "artifactId":"xstream", "version":"4.12", "scope":"test"}
   
     ],
     "repositories-add":[],
     "repositories-remove":[],
     "repositories-update-urls":[],
     "pluginRepositories-add":[],
     "pluginRepositories-remove":[],
     "pluginRepositories-update-urls":[]
   }

6. Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:

   • Product: Process Automation Manager
   • Version: 7.0
7. Download Red Hat Process Automation Manager 7.0.0 Add-Ons and extract the downloaded rhpam-7.0.0-add-ons.zip file to a temporary directory.
8. In the extracted rhpam-7.0.0-add-ons folder, extract the rhpam-7.0-migration-tool.zip sub-folder. The migration tool is in the bin directory.

9. In your command terminal, navigate to the temporary directory where you extracted the rhpam-7.0-migration-tool folder and run the migration tool. The $RHPAM_NIOGIT_DIR portion is the path to the .niogit directory that you previously copied to the Red Hat Process Automation Manager 7.0 installation.

   On Linux or UNIX-based systems:

   $ cd $INSTALL_DIR/rhpam-7.0-migration-tool/bin
   $ ./migration-tool.sh -t $RHPAM_NIOGIT_DIR

   On Windows:

   $ cd $INSTALL_DIR\rhpam-7.0-migration-tool\bin
   $ migration-tool.bat -t $RHPAM_NIOGIT_DIR

   In the command prompt that appears, the following options are displayed:

   • Project structure migration: Migrates the Red Hat JBoss BPM Suite 6.4 project repository structure to the new project-oriented structure used in Red Hat Process Automation Manager 7.0.
   • System configuration directory structure migration: Migrates the system.git repository structure used in Red Hat JBoss BPM Suite 6.4 to the new structure used in Red Hat Process Automation Manager 7.0. This migration option requires the project structure migration to be executed first.
   • Forms migration: Migrates forms created in the Red Hat JBoss BPM Suite 6.4 forms designer to the new forms designer. This migration option requires the project structure migration and system configuration directory structure migration to be executed first.
   • POMs migration: Updates pom.xml files with dependencies required for Red Hat Process Automation Manager 7.0. This migration option requires the project structure migration, system configuration directory structure migration, and forms migration to be executed first.
   • All: Runs all migration options in sequence.
   • Exit: Exits the migration tool.

10. Select the option to run All migrations in sequence.

    Note

    If you prefer to run one migration option at a time, select and run the first individual migration option. After the tool runs, re-run the Business Central migration tool and select the next individual migration option in the sequence.

11. Enter yes each time you are prompted to run a specific migration option.

    For the POMs migration option, if you want to include a path to an external pom-migration.json file that you created previously, enter yes when prompted and enter the path.

12. After the tool finishes running, enter the option to Exit the migration tool.

    The .niogit directory structure is now compatible with Business Central in Red Hat Process Automation Manager 7.0. Project directories are in separate repositories and all other related configurations have been migrated. You can navigate to the new .niogit directory to inspect the restructured contents.

Procedure

1. In a local directory, create a clone of the Git repository containing the projects to be migrated (if the repository has not been cloned already).

   $ cd $REPO_DIR/
   $ git clone $GIT_REPO_URL

2. Note the path to the cloned Git repository. The path will be required when you run the migration tool.
3. Create an output directory where a copy of the newly migrated repository or repositories will be placed after the migration tool runs. You can also use an existing directory as an output location. Note the path to this output directory. The migration tool operates on a copy of the cloned repository and will prompt you for the new output directory path when you run the tool.

4. If you have specific dependencies, repositories, or pluginRepositories that you want to add, remove, or update as part of the project migration, create a pom-migration.json file containing these elements. When you run the migration tool, the tool will prompt you if you want to include this file in the migration.

   The pom-migration.json file requires the following sections:

   • "dependencies":[]
   • "repositories-add":[]
   • "repositories-remove":[]
   • "repositories-update-urls":[]
   • "pluginRepositories-add":[]
   • "pluginRepositories-remove":[]
   • "pluginRepositories-update-urls":[]

   If any of these elements do not apply to your project, include them as empty sections to prevent parsing errors.

   Example pom-migration.json file:

   {
     "dependencies":[
   
       {"groupId":"junit", "artifactId":"junit", "version":"4.12", "scope":"test"},
       {"groupId":"com.thoughtworks.xstream", "artifactId":"xstream", "version":"4.12", "scope":"test"}
   
     ],
   
     "repositories-add":[
       {
         "id":"jboss-public-repository-group",
         "name":"JBoss Public Repository Group",
         "url":"http://repository.jboss.org/nexus/content/groups/public/",
         "releasesEnabled":true,
         "releasesUpdatePolicy":"never",
         "snapshotEnabled":true,
         "snapshotUpdatePolicy":"never"
       },
       {
         "id":"kie-internal-staging-repository-group",
         "name":"KIE Internal Staging Repositories",
         "url":"https://origin-repository.jboss.org/nexus/content/groups/kie-internal-group",
         "releasesEnabled":true,
         "releasesUpdatePolicy":"never",
         "snapshotEnabled":false,
         "snapshotUpdatePolicy":"never"
       }
     ],
   
     "repositories-remove":[
       {
         "id":"productization-repository", "url":"http://download.lab.bos.redhat.com/brewroot/repos/jb-ip-6.1-build/latest/maven/"
       }
     ],
   
     "repositories-update-urls":[
       {
         "id":"guvnor-m2-repo", "url":"http://localhost:8080/business-central/maven3/"
       }
     ],
   
     "pluginRepositories-add":[
   
       {
         "id":"jboss-public-repository-group",
         "name":"JBoss Public Repository Group",
         "url":"http://repository.jboss.org/nexus/content/groups/public/",
         "releasesEnabled":true,
         "releasesUpdatePolicy":"never",
         "snapshotEnabled":true,
         "snapshotUpdatePolicy":"never"
       },
       {
         "id":"kie-internal-staging-repository-group",
         "name":"KIE Internal Staging Repositories",
         "url":"https://origin-repository.jboss.org/nexus/content/groups/kie-internal-group",
         "releasesEnabled":true,
         "releasesUpdatePolicy":"never",
         "snapshotEnabled":false,
         "snapshotUpdatePolicy":"never"
       }
   
     ],
     "pluginRepositories-remove":[],
     "pluginRepositories-update-urls":[]
   }

   Example pom-migration.json file with dependencies only:

   {
     "dependencies":[
   
       {"groupId":"junit", "artifactId":"junit", "version":"4.12", "scope":"test"},
       {"groupId":"com.thoughtworks.xstream", "artifactId":"xstream", "version":"4.12", "scope":"test"}
   
     ],
     "repositories-add":[],
     "repositories-remove":[],
     "repositories-update-urls":[],
     "pluginRepositories-add":[],
     "pluginRepositories-remove":[],
     "pluginRepositories-update-urls":[]
   }

5. Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:

   • Product: Process Automation Manager
   • Version: 7.0
6. Download Red Hat Process Automation Manager 7.0.0 Add-Ons and extract the downloaded rhpam-7.0.0-add-ons.zip file to a temporary directory.
7. In the extracted rhpam-7.0.0-add-ons folder, extract the rhpam-7.0-migration-tool.zip sub-folder. The migration tool is in the bin directory.

8. In your command terminal, navigate to the temporary directory where you extracted the rhpam-7.0-migration-tool folder and run the migration tool. The $GIT_REPO_PATH portion is the path to the cloned Git repository.

   On Linux or UNIX-based systems:

   $ cd $INSTALL_DIR/rhpam-7.0-migration-tool/bin
   $ ./migration-tool.sh -t $GIT_REPO_PATH

   On Windows:

   $ cd $INSTALL_DIR\rhpam-7.0-migration-tool\bin
   $ migration-tool.bat -t $GIT_REPO_PATH

9. In the command prompt that appears, enter the path to the output directory where the migrated copy of the repository will be placed. The migration tool operates on a copy of the cloned repository and will place the new repository or repositories in the output location that you specify.

   After you enter the output location, the migration tool prepares the repository copy and restructures all project directories to be compatible with Red Hat Process Automation Manager 7.0.

   In the command prompt, the following additional migration options are displayed:

   • Forms migration: Migrates forms created in the Red Hat JBoss BPM Suite 6.4 forms designer to the new forms designer.
   • POMs migration: Updates pom.xml files with dependencies required for Red Hat Process Automation Manager 7.0. This migration option requires the forms migration to be executed first.
   • All: Runs all remaining migration options in sequence.
   • Exit: Exits the migration tool.
   Note

   The Project structure migration option is not displayed because that option was run automatically when you entered the output location to initiate the migration tool.

10. Select the option to run ALL migrations in sequence.

    Note

    If you prefer to run one migration option at a time, select and run the first individual migration option. After the tool runs, re-run the Business Central migration tool and select the next individual migration option in the sequence.

11. Enter yes each time you are prompted to run a specific migration option.

    For the POMs migration option, if you want to include a path to an external pom-migration.json file that you created previously, enter yes when prompted and enter the path.

12. After the tool finishes running, enter the option to Exit the migration tool.

    The project directories in the specified output location are now separated into individual repositories compatible with Business Central in Red Hat Process Automation Manager 7.0. The new project repositories are bare repositories with no working directory, and therefore do not show any content files. You can clone each repository to create non-bare repositories and inspect directory contents.

13. Log in to Business Central for Red Hat Process Automation Manager 7.0.
14. For each project, create or select the space for the project and click Import Project.

15. Enter the Repository URL for the newly structured project repository. This URL may be the local file path to the output location if you are importing directly from the workstation where you ran the migration tool, or a GitHub URL or other file hosting location where you have uploaded the repository.

    Example: Local file location

    file:///$OUTPUT_DIR/loan-application.git

    Example: GitHub repository location

    https://github.com/$REPO/loan-application.git

    Note

    If you use Git hooks with your project data, you may need to update your hooks scripts to accommodate the migration.