I would unpack JBoss to /usr/local - you should get a JBoss directory under this. It depends on your preferences - some people prefer the old Solaris configuration under /opt. YMMV.
You will need to set JAVA_HOME to point to your Java JDK root directory. Your JBoss distribution will have a bin/run.sh that will start JBoss.
Ensure that there is nothing in your Java classpath before you execute run.sh.
JBoss 3.2.1 is the latest stable, production release.
Thanks Jon, the installation went smooth....
I just have one problem (I think) I installed version 3.2.2RC4.
Do you think I should remove it and install the 3.2.1 version ?
And if so, what's the best way to un-install....
PS : Thanks a lot for your response :)
In essence, there is not a great deal to uninstall - you should be able to delete the existing JBoss directory.
JBoss 3.2.2 RC4 has a few run-time bugs that will probably be fixed this week. They aren't huge, but may make it difficult for the new J2EE developer who has not worked with JBoss before - it might make it difficult to determine if it is an own fault or a JBoss fault.
Has Jboss updated this version yeat ?
Is there a way to restrict access to Jboss (restrict accounts, enable and disable) ?
3.2.2 released? Not AFAIK. Watch the JBoss SourceForge announcements.
I'm not quite sure what you mean by restrict access to JBoss. Physical access to files and directories will be dependent on your Linux system security configuration.
Access to connect to JBoss ports (perimeter defences) will also be set up by your Linux iptables/ipchains configuration.
Roles and authentication to connect to EJB resources and to web application pages are a combination of standard J2EE security mechanisms - defined within the security constraints sections of web.xml and ejb-jar.xml, and as implemented by the JBoss security sub-system (the paid for documentation is the authorative guide) but you will be able to glean information from the free documentation, tutorials and various free pages on the Internet covering JBoss J2EE-related security.
Hope this answers your questions.
I guess you didn't understand me, I mean to resell JBoss on the server but only enable some accounts to have access to it our all accounts on the servers get jboss automatic ?
Thanks for the help :)
No. I'm still not quite understanding. Maybe try and explain how people are going to access JBoss and how accounts relate to this question?
Are these people who have Linux accounts? And do you mean access like start and stop JBoss? Add and delete web applications?
Explain step-by-step exactly how you see someone accessing JBoss and then we can answer.