Tihomir Surdilovic [https://community.jboss.org/people/tsurdilovic] created the discussion "Re: Problem in deploying Process from guvnor to JBPM Console" To view the discussion, visit: https://community.jboss.org/message/716790#716790 -------------------------------------------------------------- Designer is integrated with Guvnor currently. This means that  in standalone mode it is only able to view existing processes in your Guvnor packages but not save them. There is a number of people in the community asking for this feature to be added (check some of the latest posts on the forum) so it should be addressed in the future. Currently to save processes in your Guvnor package you would create a new BPMN2 process in Guvnor which will load it in Designer, edit/modify it there and then save it in Guvnor and build your package. Hope this helps. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/716790#716790] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Tihomir Surdilovic [https://community.jboss.org/people/tsurdilovic] created the discussion "Re: Problem in deploying Process from guvnor to JBPM Console" To view the discussion, visit: https://community.jboss.org/message/736800#736800 -------------------------------------------------------------- First you must build all your Guvnor packages. If you have any fact model jars in Guvnor, you have to put those in the $jbpm-installer/dependencies dir and then run "ant clean.demo" and "ant.install.demo" or "ant.install.demo.noeclipse" and then "ant start.demo" or "ant start.demo.noeclipse". We fixes some package detection issues in jBPM 5.3 which has just released, for example in 5.2 you pretty much have to build your packages before you access the jbpm console, if you access console before you build your packages, it will not be able to detect them after. With 5.3 you should be able to do that and also console should be able to detect new packages as well that include process definitions (and have been successfully built). With 5.3 another thing that we fixed is the issues if some of your packages are not build (they will simply be ignored instead of raising issues during the console kbase building). I would in your case give jBPM 5.3 a try as things are somewhat easier to work with and let us know what you run into. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/736800#736800] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]