How to move existing jBPM5 project and their artifacts stored in SVN to BPM Suite or BRMS 6 repository ?
Environment
- Red Hat JBoss BPM Suite (BPMS) 6.x
- Red Hat JBoss BRMS (BRMS) 6.x
Issue
There is an already existing jBPM5
project in SVN
. It is required to move the project and it's artifacts to JBDS 7.x
workspace and deploy that project into a new BPM suite 6
or BRMS 6
environment. No migration of process / data from Guvnor
is required as part of the process. What are the steps for that process?
Resolution
SVN
andGit
are two different version control systems and the internal repository maintained byBusiness Central
inBPMS 6
orBRMS 6
is done throughGit
notSVN
. If the source code maintained inSVN
is following aMaven
project structure then it is possible to import the project intoJBDS
or anyEclipse
basedIDE
as aMaven Project
.- Now, as per the BPM Suite - Administration and Configuration Guide , the below mentioned procedures can be followed to ensure that the source
SVN
artifacts are uploaded into theBPMS or BRMS
repository and accessible viaBusiness Central
:
- Log in to
Business Central
. - Create a new
Repository
which has similar naming convention (or whatever it is preferred to be named) . - Go to
Project Authoring
and create one or twoProjects
which has the same package structure so as to mock the project structure that the sourceSVN project
used to maintain. - Now, come back to
JBDS
and clone thatBPMS
repository which has just been created. - Visit the workspace in the local filesystem which just got created due to cloning of the
Business Central
project. - Since the
SVN
project was earlier downloaded into the local filesystem , now, start copying the artifacts (i.e.Source codes, rule assets, process definitions
etc.) from that previously downloadedSVN projects
and place them in the folder structure of the cloned repository in theworkspace
. - Once done, go back to
JBDS
to view your clonedBusiness Central
repository, and doCommit
andPush
to the changes which has just been made to the repository.
This might look tedious , but things would have been quite easy if the source project would have been maintained in a Git repository
as Business Central
provides a feature to Clone from an existing Git repository
to avoid this manual procedure.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments