Show Table of Contents
Chapter 4. Migration Examples
4.1. Hello World Project Migration
Let's start with the simplest migration example, a simple Hello World kind of process. This is just to get you started and make you comfortable with the migration process.
Data Migration
Start JBoss BRMS 5 with a clean repository and install the built-in samples. To make it more interesting, add one BPMN process with following structure:
START->SCRIPT_Task->Human_Task->End.
Save the process and build the package. This is what it looks like in JBoss BRMS 5:
As discussed earlier, in order to automatically migrate assets from JBoss BRMS 5 to JBoss BPM Suite 6, you need to convert the JCR repository, storage for business assets in 5, to a GIT repository - storage for business assets in 6. Run the migration tool:
$ ./runMigration.sh -i /home/osiris/jboss-playground/jboss-eap-6.0-brms/bin/repository -o /home/osiris/Downloads/myGitRepo -r MyMigratedRepo
This example assumes that the JBoss BRMS 5 instance was started from the
bin directory, using ./standalone.sh, so by default, the repository directory and repository.xml will be created in this directory.
The destination (specified by the
-o option) can be whatever dir you want it to be. The GIT repository is created under myGitRepo folder once the migration tool finishes its work.
Note
The destination folder must not exist when you run this command otherwise you will get an error.
Once done, clone this repository into JBoss BPM Suite 6.x via perspective and clicking on and then links. Point it to
file:///home/osiris/Downloads/myGitRepo/MyMigratedRepo.git to start the import.
It is now possible to build and deploy project in JBoss BPM Suite 6 and easily instantiate the process. This is what it should look like once successfully imported.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.