JBossESB Install

[haydockg]

I've just installed JBossESB in order to evaluate it. I installed it using the jbossesb-server-4.2GA.zip binary, and unzipped it.

I've been trying to follow the Getting Started guide, but many of the files and folders referred to do not exist. For example, the jbossesb-server-4.2GA/install/ folder does not exist.

Supposing that this was because the jbossesb-server-4.2GA.zip includes a JBoss app server and the folders were only necessary if installing into an existing JBoss app server, I tried to carry on by running the HelloWorld QuickStart to test the installation.

This failed too - the ant script failed to compile with the following:

[javac] D:\JBossESB\jbossesb-server-4.2GA\samples\quickstarts\conf\anttasks\
src\org\jboss\ant\QuickstartJava.java:42: cannot find symbol
[javac] symbol : method getCommandLine()
[javac] location: class org.jboss.ant.QuickstartJava
[javac] CommandlineJava cmdl = getCommandLine();
[javac] ^
[javac] 1 error

Can anyone tell me what I've done wrong!

Thanks

[burrsutter]

Hello,

If you are using the ESB Server (which I do recommend) then all you have to do is
- use "run" in the bin directory to start the server.
- Then start a new command window and CD over to quickstarts\helloworld
- use "ant deploy-jms-dests" in the quickstarts\helloworld directory.
- use "ant run" in that same directory.
- start another command window, CD over to quickstarts\helloworld and use "ant runtest"

It might be that you have the wrong version of Ant in your PATH. I'm using 1.7.0

Burr

[kconner]

"haydockg" wrote:
For example, the jbossesb-server-4.2GA/install/ folder does not exist.

The install scripts exist in the jbossesb artifact so that it can be installed into an existing application server. The jbossesb-server artifact is a pre configured server containing the ESB.

"haydockg" wrote:

 [javac] symbol : method getCommandLine()
 [javac] location: class org.jboss.ant.QuickstartJava
 [javac] CommandlineJava cmdl = getCommandLine();

This is a method from a core ant class, looks like it may have changed in your version. Which version of ant are you using?

We test with 1.6.5 and Burr uses 1.7.0.

Thanks.

[phicouek]

how about jbpm "pre"configuration in jbossesb-server-4.2GA.zip?

I supposed that it is full proconfigured Jboss server with esb, jbpm ect.
but when I tried to login to jbpm-console I got 'login failed'.
server.log contains 'No properties file: users.properties [...]' error.
There was no jbpm application policy in login-config.xml.
I found /data/hypersonic/jbpmDB files but local-tx (hsqldb-ds.xml) pointed to DefaultDS only.
I hadn't configured anything - unzip and run only, so - is jbossesb-server-4.2GA.zip not-quite-preconfigured server?


regards
jarek

[phicouek]

how about jbpm "pre"configuration in jbossesb-server-4.2GA.zip?

I supposed that it is full proconfigured Jboss server with esb, jbpm ect.
but when I tried to login to jbpm-console I got 'login failed'.
server.log contains 'No properties file: users.properties [...]' error.
There was no jbpm application policy in login-config.xml.
I found /data/hypersonic/jbpmDB files but local-tx (hsqldb-ds.xml) pointed to DefaultDS only.
I hadn't configured anything - unzip and run only, so - is jbossesb-server-4.2GA.zip not-quite-preconfigured server?


regards
jarek

[burrsutter]

The jBPM Admin Console has some known issues. We are working to correct them now. However, it can be made to work with a little bit of effort. Check out this forum posting: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118843

And these jira tasks:
http://jira.jboss.com/jira/browse/JBESB-972
http://jira.jboss.com/jira/browse/JBESB-735

Some of the keys are getting the login-config.xml correct.
Plus getting the user ids and passwords into the database.
Note: there is also the fact that the jbpm-console.war has 2 jBPM jars that need to be removed from its lib folder. Otherwise it will create recreating the database every time you restart the server.

I've used the console a lot just in the last 24 hours so it works if you patient enough to configure it correctly. I'm hoping we'll get this nailed down in the ESB 4.2.1 release (Oct 2007) so it just works out of the box.

Burr