Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Disable web service using JMX

 
Rajesh Seth
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I like to have the following features in JMX. Web Services deployed on Tomcat instance with Axis2.

1. All the functionality provided by axis2 web admin should be there
2. It should be able to change global handler chain
3. It should be able to disable and enable service
4 it should be able to turn off an opeartion of a service
5. it provide a way to edit parameters in each level (Global , service ,
opearation , module , handlers , Transport sender and recivers)
6. Engaging and disengaging module (s)

Point number 3 is important to me.
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't think Axis-2 makes any of that available out of the box. I would imagine that you can implement quite a few of these by filtering org.apache.axis2.webapp.AxisAdminServlet and org.apache.axis2.transport.http.AxisServlet (and possibly org.apache.axis2.webapp.AdminAgent).
 
Rajesh Seth
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the reply.
Actually we have the Axis2 admin page disabled intentionally but there should be some way to do it through JMX or REST
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
By filtering org.apache.axis2.transport.http.AxisServlet you should still be able to accomplish most of what you ask for. Start by studying the source code of org.apache.axis2.webapp.AxisAdminServlet. You may have to adapt some of the Axis-2 classes, though.

I would expect the Axis-2 developer mailing list to be a more direct approach to get input from the people familiar with the Axis-2 innards.
 
Rajesh Seth
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Half way through. Placed some methods in JMX Object model making sure they are not starting with set. This will create buttons in JConsole to control services. Below is the query configured in Tomcat to authenticate from LDAP server.

Tomcat { /* should match to the com.sun.management.jmxremote.login.config property */

com.sun.security.auth.module.LdapLoginModule REQUIRED
userProvider="ldap://172.16.10.160:389/dc=mulesoft,dc=com"
userFilter="(&(uid={USERNAME})(objectClass=inetOrgPerson))"
authzIdentity="{departmentNumber}"
useSSL=false
debug=true;
};

But it doesn't work if direct DN is not provided. With direct DN (From root to bottom path) provided in "userFilter=", it authenticates fine. A wild guess to the problem is that it is not searching the subtree. I need some parameter here which tells the Server to search inside the subtree's as well for the user. Right now it is only looking into the head tree and not navigating inside.
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please ask unrelated questions in a new thread. People will not expect LDAP stuff in a topic about JMX.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic