How to deploy project created in eclipse to the JBPM server in 7.7?

691 views
Skip to first unread message

mike....@gmail.com

unread,
Jun 5, 2018, 5:37:20 PM6/5/18
to jBPM Development
Hi everyone, I am just starting with JBPM, I have been able to import sample projects that are already bundled with 7.7 and play with those.  But I tried creating a new "helloworld" example using Eclipse, and now I want to deploy that to the server.  I've gone through the documentation and a number of articles on line, but I am thoroughly confused over this process.   I've seen some documentation that indicates we need to use GIT, but those all seem to deal with projects created in Workbench that are then pulled into Eclipse.  In my case I'd like to work in the other direction.

Is the correct process I should follow:

1.  Clone the JBPM repository locally using GIT
2.  Create a new project underneath that local clone folder using ecplise
3.  Merge the clone repository back into JBPM repository using GIT

I have tried to follow instructions at this link to clone the existing JBPM repository, with no luck:


It doesn't look like my install has the jbpm-playground repository.  Even command line, when I try this it does not work:

[oracle@localhost repo_test]$ git clone ssh://krisv@localhost:8001/jbpm-playground
Cloning into 'jbpm-playground'...
Password authentication
Password:
Can't resolve repository name.fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

So from the error message, how do I make sure the repository exists? It seems like the "Repository" link is gone in 7.7 workbench UI, and I haven't found a good source for how to find/configure Repository in 7.7?  Or is there a simpler way to deploy a new project to the server that I am missing? 

thanks


Maciej Swiderski

unread,
Jun 6, 2018, 2:58:25 AM6/6/18
to mike....@gmail.com, jBPM Development
in general it’s all maven based - do once you have the project you can just mvn clean install (deploy if you have remote execution) and then deploy the project to server via workbench - execution server perspective.

when it comes to cloning the url has changed and is:

check the team and project name to be valid for your scenario

Maciej

--
You received this message because you are subscribed to the Google Groups "jBPM Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-developme...@googlegroups.com.
To post to this group, send email to jbpm-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-development/5df6c6a6-2bde-4b83-8942-7f03bae5b1ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

mike....@gmail.com

unread,
Jun 6, 2018, 11:21:23 AM6/6/18
to jBPM Development
Thanks again for the help Maciej.   I think I am getting closer to understanding the process.   I had a little trouble figuring out what you meant by the Execution Server perspective.  In 7.7 "Execution Server" is only listed in the dropdown menu, on the main home page it is just listed as "Servers".  Normally I might have figured that out on my own, but I was thrown off because I couldn't find any place to upload anything on that Servers screen.   But since you mentioned it was maven based, I was able to track down the link to the maven repository under Admin->Artifacts, and I was able to upload my jar file there.   Then, I went back to Execution Servers and created a new "container" where I was able to select my helloworld artifact that I uploaded.    So I think my process is now "deployed", correct?  This is essentially the equivalent of what I did to get the eval demo working:

Eval Demo:  Create Project in Workbench.  Build and Deploy it using workbench, which puts the jar in the JBPM maven repository and creates the container for me.
My Helloworld:   Create project in eclipse, build using eclipse, and manually upload to JBPM maven repository and manually create container.

So, now that it is deployed, should I expect to see helloworld under Process Definitions, and kick off new instances?     I was hoping that would be the case, but I don't see it there now.

Maciej Swiderski

unread,
Jun 6, 2018, 11:23:11 AM6/6/18
to mike....@gmail.com, jBPM Development

On 6 Jun 2018, at 16:21, mike....@gmail.com wrote:

Thanks again for the help Maciej.   I think I am getting closer to understanding the process.   I had a little trouble figuring out what you meant by the Execution Server perspective.  In 7.7 "Execution Server" is only listed in the dropdown menu, on the main home page it is just listed as "Servers".  Normally I might have figured that out on my own, but I was thrown off because I couldn't find any place to upload anything on that Servers screen.   But since you mentioned it was maven based, I was able to track down the link to the maven repository under Admin->Artifacts, and I was able to upload my jar file there.   Then, I went back to Execution Servers and created a new "container" where I was able to select my helloworld artifact that I uploaded.    So I think my process is now "deployed", correct?  This is essentially the equivalent of what I did to get the eval demo working:

Eval Demo:  Create Project in Workbench.  Build and Deploy it using workbench, which puts the jar in the JBPM maven repository and creates the container for me.
My Helloworld:   Create project in eclipse, build using eclipse, and manually upload to JBPM maven repository and manually create container.

So, now that it is deployed, should I expect to see helloworld under Process Definitions, and kick off new instances?     I was hoping that would be the case, but I don't see it there now.
yes, make sure the container is started and kie server is running

Maciej
Reply all
Reply to author
Forward
0 new messages