This is a little step by step guide on how to create and register custom service with JMX interface on WebSphere: 1. Create class, which implements two interfaces: [java] com.ibm.websphere.runtime.CustomService com.ibm.websphere.management.JMXManageable [/java] 2. Implement "initialize" method (inherited from CustomService) This method has a parameter, Properties, which will contain properties defined via WS Administration console. We are interested in one property: externalConfigURLKey. This property contains path to external configuration file (if any is needed). This is how to get the path: [java] public void initialize(Properties configProperties) throws Exception { readConfig(configProperties.getProperty(externalConfigURLKey)); } [/java] 3. shutdown() method may be left blank. 4. implement getType() method (inherited from JMXManageable): [java] public String getType() { return "MyMBean"; } [/java] Remember the name you returned here! 5. implement getMBeanProperties: [java] public Properties getMBeanProperties() { Properties props = new Properties(); props.put("SpecialProperty", "value"); return props; } [/java] I think this will return a list of properties, not declared in MBean descriptor. Read only, of course, since there is no setMBeanProperties() method. 6. implement getters and setters for properties you want to expose: [java] public String getUserName() { return this.userName; } public void setUserName(String param) { this.userName = param; } [/java] 7. Create MBean descriptor file, for example myTest.xml. [xml] [/xml] IMPORTANT: Make sure that type matches the value you remembered on the step 4! 8. Compile and package. Create .jar, having descriptor in the root. Place .jar somewhere accesible for WebSphere. 9. Start WebSphere and open Administration console. 10. Go to Servers - Application Servers - yourserver - Server Infrastructure - Administration - Administration Services 11. Click on "Extension MBean providers" 12. Click on "New" 13. In the "Classpath" entry type the full path and name of your jar (created on step 8) 14. Type something memorable in two other fields and click Apply. 15. Click on "Extension MBeans" (on the left) 16. Click on "New" 17. Enter the name of MBean descriptor file (see step 7.) for example: myTest.xml 18. Enter the type name of your MBean. IMPORTANT: must be the same name as it was on steps 4 and 7. 19. Click Apply. 20. Go to Servers - Application Servers - yourserver - Server Infrastructure - Administration - Custom Services 21. Click New 22. Place check on "Enable service at server startup". 23. Enter full class name (with package) of your MBean class (the one we created on step 1) into "Classname" field. 24. Enter something memorable in "Display Name" 25. Enter fill path and file name of the jar file (step 8) into "Classpath". 26. If your service requires configuration file (step 2) enter full path to it into " External Configuration URL" 27. Click on Apply. 28. Click on Save (on top) 29. Click Save. 30. Restart the server. Here are the commands, used to verify MBean from admin console: To run console: wsadmin.bat -conntype SOAP -port 8881 To make sure that MBean started: $AdminControl queryNames *:*,type=> Store MBean in Tcl variable: set mybean [$AdminControl queryNames *:*,type=MBeanName] See MBean description: $Help all $mybean See MBean attributes and values: $AdminControl getAttributes $mybean Set specific attribute: $AdminControl setAttribute $mybean UserName mike