3.3. Migrating from 6.0.x to 6.2

3.3.1. Migrating Client Application APIs from 6.0.x to 6.2

To migrate client applictions from JBoss BPM Suite 6.0.x to 6.2 the applications must incorporate all of the changes mentioned in both Section 3.2.1, “Migrating Client Application APIs from 6.0.x to 6.1” and Section 3.1.1, “Migrating Client Application APIs from 6.1.x to 6.2”.

3.3.2. Migrating Business Central Project, Repository, and Artifacts from 6.0.x to 6.2

Use the following procedure to move your existing Red Hat JBoss BPM Suite 6.0.x git projects (.niogit folder) and maven local dependencies (bin/repositories) to a new JBoss BPM Suite 6.2 installation.
Note, the example commands used in the following procedures are based on migrating from JBoss BPM Suite 6.0.3 to 6.2.

Procedure 3.7. Migrate a Single Project

  1. Turn off JBoss BPM Suite 6.0.x and JBoss BPM Suite 6.2 instances.
  2. Navigate to .niogit folder of JBoss BPM Suite 6.0.x installation.
  3. Clone the repository where desired project is located. 
    $ git clone repository603.git
  4. Navigate to the JBoss BPM Suite 6.2.0 niogit folder.
  5. Clone the repository where you want to migrate the 6.0.x project. 
    $ git clone repository620.git
  6. Copy the project from 6.0.x cloned repository to 6.2.x cloned repository. 
    $ cp -R /path/to/6.0.3/project /path/to/6.2.0/repository
  7. Navigate to the 6.2.0 cloned repository. 
    $ cd /path/to/6.2.0/repository
  8. Commit the newly added 6.0.x project to your new 6.2.0 repository. 
    $ git add ./copied-6.0.3-project/*
$ git commit -m "migrating 6.0.3 project to 6.2.0 repository"
$ git push
  9. Start JBoss BPM Suite 6.2.0. The 6.0.3 project should be successfully migrated and visible under the specified repository.

Note

The outcome of the above procedure may also be achieved by using the eGit plugin for Red Hat JBoss Developer Studio. See the relevant section in the Red Hat JBoss BPM Suite Development Guide.
Migrating a Repository

The following procedure demonstrates how to migrate a selected JBoss BPM Suite 6.0.x repository to JBoss BPM Suite 6.2.0 installation.

Procedure 3.8. Clone and Migrate a Repository

  1. Turn on JBoss BPM Suite 6.2.0.
  2. Log in to Business Central and navigate to Authoring → Administration → Repositories → Clone Repository.
  3. Fill in the form. For example: 
    Repository Name - MyOld603Repo
Organizational Unit - example
Git URL - file:///path/to/old/603/.niogit/repository.git
    and press Confirm.
  4. The repository should be now available for Authoring.
For more information about cloning repositories, see the Red Hat JBoss BPM Suite Administration and Configuration Guide.
Migrating a Maven Artifact

The Artifact Repository is an internal maven repository for JBoss BPM Suite. The default internal maven repository is created in a working directory of JBoss BPM Suite 6.2.0 installation, with the folder name repositories/kie.

Maven artifacts can be migrated using the GUI.

Procedure 3.9. Migrating Maven Artifacts using the GUI

  1. Turn on JBoss BPM Suite 6.2.
  2. Navigate to Authoring → Artifact Repository.
  3. Upload the Artifact from your old 6.0.3 installation.
Alternatively, following procedure demonstrates how to migrate selected maven artifact from JBoss BPM Suite 6.0.x Artifact Repository to a JBoss BPM Suite 6.2.0 Artifact Repository, and assumes that the two Artifact Repositories are located on the same physical system.

Procedure 3.10. Migrating a Particular Artifact

  1. Consider following KJAR, which was installed into JBoss BPM Suite 6.0.x Artifact Repository by Business Central.
    KJAR installed

    Figure 3.4. Installed KJAR

  2. Copy this artifact to the JBoss BPM Suite 6.2.0 Artifact Repository. For example: 
    $ cp -R --parents /path/to/603/kjar/kie/org/redhat/gss/TimerProject/
/path/to/bpms-610-psql/bin/repositories/
    The --parents argument will ensure that all the necessary folders (if missing) will be created in 6.2.0 too. In this case, it will honor the /org/redhat/gss/TimerProject path.
  3. Start the JBoss BPM Suite 6.2.0 installation and navigate to Artifact Repository. The copied artifact should be present as shown.
    Artifact repository

    Figure 3.5. Artifact Repository

Migrating the .niogit Folder

In order to migrate the whole .niogit from 6.0.x to 6.2.0, set the org.uberfire.nio.git.dir property in 6.2.0 as follows. 

$ ./standalone.sh -Dorg.uberfire.nio.git.dir=/path/to/6.0.3/.niogit

3.3.3. Upgrading the Database from 6.0.x to 6.2

Ensure that the database has been upgraded as documented in Section 3.4, “Database Migration for 6.x Instances”.