Conversation: [Boss vs. JBoss Geek ]
Boss: Hey buddy, you know that guy BOB at onsite… he installed the JBoss server on production box. I need some info on that. Can you grab some for me?
JBoss Geek: What sort of info you need boss?
Boss: Well, not much. Can you just check for me which JBoss Version BOB has installed on production server? On which path? Hey, also check me on which Ports Set it is installed on? And yea, configuration name too if you don’t mind. Also, don’t forget the Bind Address along with the UDP Group Address. And oh yea, I know you won’t forget to check which Java Version it is running on along with the OS Version. That’s it buddy!
JBoss Geek: Ok ya sure boss. Not much. I can check these things for you. Please share me the production server credentials to access the JBoss Server for getting details you’ve asked for.
Boss: Oh man, you’re kidding me, right? Why do you think they’d give us the production server access!! We don’t have production server access buddy. All we have is just the access to our application via browser. But, You’re a JBoss Geek, an important asset of organization. Use your Magic Wand. I’m sure you’ll grab the info for me, right buddy? Inform me once done, alright… see ya !!!
JBoss Geek: Ohkk, Boss!!!
Oops, the geek is stuck… literally I mean!!! He was always used to make his hands dirty on the ground for grabbing such info by accessing the physical location of JBoss Installation, Configurations, Logs etc. He ain’t got no access to either of these now. Just the browser by which he can access the deployed application. What to do??? Well, its time for the geek to air the Magic Wand!!! Let’s help the geek!!!
Well, its not always that you’ve got to make your hands dirty to get these info. JBoss publishes all the meta info. on the management console called ‘jmx-console‘. The JMX Console is accessible via browser using the IP Address and HTTP Port Number of JBoss where your web application is running. The JMX Console is accessible as following URL Pattern:
All the meta information about JBoss Server is available on JMX Console under ‘jboss.system’ domain.
Once you click on the ‘jboss.system‘ domain, you’ll see the management services under this domain.
Now, let’s sum up all the information the Boss wanted:
- JBoss Version
- JBoss Path
- Ports Set
- Configuration Name
- Bind Address
- UDP Group Address
- Java Version
- OS Version
So, this is all information the Boss wanted. Yes, ‘not much‘!!!
Let’s get all the things one by one by using either of the Management Services shown in above screen.
PS: I have pixelated some private info which I don’t want to disclose for my JBoss server in screenshots as following.
1. JBoss Version:
Access Path: jmx-console -> type=Server -> VersionNumber
Oh yeah, enjoying!! Let’s hit another.
2. JBoss Path:
Access Path: jmx-console -> type=ServerConfig -> JBossHome
3. Ports Set
Access Path: jmx-console -> service=ServiceBindingManager -> ServerName
4. Configuration Name:
Access Path: jmx-console -> type=ServerConfig -> ServerName
5. Bind Address:
Access Path: jmx-console -> type=ServerConfig -> BindAddress
6. UDP Group Address:
Access Path: jmx-console -> type=ServerConfig -> UdpGroup
7. Java Version:
Access Path: jmx-console -> type=ServerInfo -> JavaVersion
8. OS Version:
Access Path: jmx-console -> type=ServerInfo -> OSVersion (also OSName for OS Name)
Yeahh, that’s cool… isn’t it!!!
So, not only those info. asked by Boss can be found, but also there’s a plenty of other meta info. you can find under the hood on jmx-console. Quite powerful… yes we aired the Magic Wand and spared some time for checking out the social network!!!
Boss: Hey buddy, got the info??
JBoss Geek: Hmm.. yes, boss… the info. is blah blah blah @#%#$^#%$^.
Boss: Okay, cool… hope you didn’t have much problem to grab this info man!
JBoss Geek: Nah, ‘not much‘!!!