I know about the jmx-console it's horrible...
Am talking about something in the lines of JMC for JRun. A place where I add new JMS topics/queues, datasources etc... Idont want to vae to figure out how to use 10 different xml config files on top of having to remember all the J2EE xml deployment descriptrs etc....
What can I say? With that attitude, you've got yourself between a rock and a hard place. Good luck !!
It's not the attitude... But if you ask me for a management console it's not much. I have better things to do then to try to figure out what link to click on or what tags a I have to use within the XML config files etc... I rather spend it on coding. You know it's things like that that can turn people away from a great product. I want to be able to install the app server right away and not have to figure out a bout a dozen thing before getting started...
Have you tried the swing console? It is quite good.
Swing concole? Nope see I know the docs are a bit out dated but how would I have known about a swing console...
Where is it?
By the way I dont know much about jmx-console either but should it not be password protected? I mean if some one knows I have a JBoss server, they just go to the jmx-concole and modifying evrything... And then if you just disable the jmx console, there is no way to remotly administer the server any more? Same thing with clustering should be done through a clean console.
The whole point of having a console of JRuns, BEA, Pramati etc... caliber is for ease of use and not to have to walk into the data center to configure a text file. What if the server is half around the world? Or if the production server is in the same bilding, but seperate network for security reasons and is only accessible through a terminal.
I think Pramati is on par with there deployment tools and there administration consoles though some tweaking needs to be done... I was able to download JRun and Pramati and recreate a few of my applications within 1 1/2 hours with pramati and about 2-3 hours with JRun a few difficulties...
This is what will make JBoss an even better product. You can have the nicest and fastest car! But if the driver can't find the ignition to put the key in! Then the car becomes useless!
Ok sorry I saw the link for the Swing console, I will check it out. But what I said still applies!
> What if the server is half around the world?
You do know what SSH is, don't you?
<You can have the nicest and fastest car! But if the driver can't find the ignition to put the key in!>
True. But some drivers are so full of attitude, full of themselves, that they could not find the ignition switch if it was 2 inches in front of their face.
The jmx-console is avvaile on the web through port 8181... Now if you disable it no one has access to it correct?
Now your saying to SSH to the JBoss machine and play around with the config files? Well depending on the platform... We have Windows 2000 here, so I can use SSH if we wish, there is also terminal services though not secure...
Or the smatter way would be...
A J2EE app running in it's own JVM server enviroment that allows you to start stop servers, create clusters, add resources(datasources etc...), create message queues/topics, loging, remote deploy etc... All through SSL and HTTP. Every server I have looked at has this and it makes it alot easier to get up and started. It makes peoples life easier. So you can't argue that just because every one else did doesn't mean we have to do it to.
Simply put the JMX Console needs a major face lift for it be even usefull to anyone... It's a bit difficult if you ask me to search through all those nodes to find what you are looking for and even if you know what section to look in it's not that obvious. Same thing with the swing version... So big deal you have a tree structure, now you can expand and colapse the nodes... How exciting!
JBoss is suposed to be the server of the future so make it the server of the future. Configuring servers and applications straight from a text file is something that was done 20 years ago, time to move forward!
> JBoss is suposed to be the server of the future so
> make it the server of the future.
I don't see a single code contribution coming from you.
Some people, if you gave them a gold plated Rolls Royce, they would STILL find something to complain about !!
1- There enough contributors to the project, I dont have the time to contribute to JBoss and server programming is not what I like to do...
2- Unfortunantly until for example the issue of having a so called "admin" console and other issues that might exist, JBoss can not be considered a "Gold Plated Roll Royce"
> 1- There enough contributors to the project, I dont
> have the time to contribute to JBoss and server
> programming is not what I like to do...
then you either a) buy the product you need or b) pay someone to write it for you
hope this helps