Where ist the Websale Example Application?

[mdolphin]

I'm really new to jBPM and so I wanted to follow the Getting startet Guide which I found on this Site: http://www.jboss.org/community/wiki/jBPM3GettingStarted

I downloaded and installed jbpm-3.2.6.SP1 as well as JBOSS 5.0.0.GA. I managed to set up jBPM to use a MySQL Database instead of the Default Hypersonic DB, and I can Login to the jBPM Administration Console. But after loggin in I can't see the Websale Example Application in the Processes List. How can I eventually build and manually deploy this Process to JBOSS?

Regards
Michael

[mdolphin]

The Sources for all the Examples are in <jBPM_install_dir>\examples\ , but there are no build files, so - because I'm just starting with jBPM -I don't know how to build these examples. I used the Installer jar File to setup my jBPM Environment, and would have expected the Examples to be automatically built and deployed to JBOSS.

[swatis]

make use of GPD and deploy processes using web console(by creating par files) or from GPD itself

[mdolphin]

Thanks, but I think my Problem is that I simply don't geht it how to start at all.

There are several different Versions of jBPM 3.2.x available for Download, and they differ in Content, Structure and Filetype. The Version I installed first (jbpm-installer-3.2.6.SP1) comes with a jar installer, but obviously without the Examples. Only that I can follow the getting started Tutorial mentioned above, I downloaded jbpm-jpdl-suite-3.2.GA, which comes with the Examples, but it's only a ZIP File and in the Tutorial it says:

Next, you will need to install jBPM to your machine by opening a prompt and cd'ing to the download directory. Then running the following command:

java -jar jbpm-installer-3.<<x>>.<<y>>.GA.jar

I don't have no jbpm-installer-somewhat.jar File!

And anyway: Why are there two Versions jbpm-jpdl-3.2.GA.zip and jbpm-jpdl-suite-3.2.GA.zip ? Whats the difference?

Sorry, but after nearly two Days of try and error I'm a little bit frustrated now.

Currently I'm totally confused because of all these different Versions and installation concepts. Sometimes the JBOSS has to be installed standalone, sometimes it has to be inside the jBPM install Directory, sometimes there is a jbpm-jpdl.jar in the Root of my Installation, sometimes it isn't (jbpm-installer-3.2.6.SP1)


It would be really kind if someone could tell me which Files I need to startup, and where I can find the proper Documentation. I mean: Besides the Documentation for jBPM 4 BETA(!) I haven't found any official User Manual for the 3.2.x Versions yet.

Kind Regards

Michael

[kukeltje]

You have to differentiate between 3.2.6 and <3.2.6. The latter (mainly) has the suite which contains everything, including a JBoss AS, can be just unzipped and used.

The 3.2.6 has an installer. But again *nothing* has to be installed in the jbpm install dir. If you have a standalone JBoss AS, you can point the installer to it. If not, the installer downloads a JBoss AS for you (afaik, never tried it).

If you do not havea jbpm-installer*.*.*.jar, you probably used the pre 3.2.6 version. Most of the documentation is still valid, just not the install procedure. Regarding the *usernmanual* : http://docs.jboss.com/jbpm/v3.2/userguide/html/

[swatis]

But Ronald, I tried many times to install different former versions > 3.2.6 using installer. Even though I selected install jboss server, still asked to give existing jboss application server directory path.

[kukeltje]

>3.2.6 is *not supported* 3.3.x was dropped for several reasons (search the forum for the specifics)

I just gave 3.2.6SP1, freshly downloaded from sourceforge a try and it does not download JBoss AS if the optional component is not selected

But indeed, if you select download JBoss AS 5.0.0, it does ask for a folder, and does not continue. Now if someone would have stated exactely that (and only that). it would have saved everybody a lot of trouble. So the workaround is: Download JBoss AS separately and install it separately. And if someone wants to file a Jira issue for this, it might get fixed in the next release.