The NamingService MBean is easily deployed into a JMX Agent. The following code snippet shows how to deploy it into a JMX Agent.

                  
MBeanServer server = MBeanServerFactory.createMBeanServer();
ObjectName naming = new ObjectName("Naming:type=registry");
server.createMBean("mx4j.tools.naming.NamingService", naming, null);
               
               

To use the NamingService MBean as rmiregistry, it must be started; the NamingService MBean can be started and stopped at wish, simply by invoking the start() and stop() methods of the management interface.

                  
Object proxy = MBeanServerInvocationHandler.newProxyInstance(server, naming, NamingServiceMBean.class, false);
NamingServiceMBean mbean = (NamingServiceMBean)proxy;
mbean.start();
...
mbean.stop();


or using the MBeanServer:


server.invoke(naming, "start", new Object[0], new String[0]);
...
server.invoke(naming, "stop", new Object[0], new String[0]);
            
               

It is also possible to specify the port on which the rmiregistry will run. Simply pass this parameter to the constructor of the NamingService MBean. By default the rmiregistry runs on port 1099.

                  
MBeanServer server = MBeanServerFactory.createMBeanServer();
ObjectName naming = new ObjectName("Naming:type=registry");

server.createMBean("mx4j.tools.naming.NamingService", naming, null, new Object[] {new Integer(2099)}, new String[] {"int"});


or


NamingService mbean = new NamingService(3099);
server.registerMBean(mbean, naming);


or via MLet file (specify the suitable codebase)


<MLET CODE="mx4j.tools.naming.NamingService"
      ARCHIVE="mx4j-tools.jar"
      CODEBASE="../lib/">
   <ARG TYPE="int" VALUE="4099">
</MLET>
               
               

It is also possible to change the rmiregistry port at runtime. Just start the NamingService MBean, stop it after a while, change the port it runs on, and restarting it, so that it will accept requests on the new port.
Below you can see the steps needed to perform this change.

                  
MBeanServer server = MBeanServerFactory.createMBeanServer();
ObjectName naming = new ObjectName("Naming:type=registry");
server.createMBean("mx4j.tools.naming.NamingService", naming, null);
Object proxy = MBeanServerInvocationHandler.newProxyInstance(server, naming, NamingServiceMBean.class, false);
NamingServiceMBean mbean = (NamingServiceMBean)proxy;

mbean.start();
...
mbean.stop();
mbean.setPort(5099);
mbean.start();
            
               

The CosNamingService MBean is easily deployed into a JMX Agent, in a way very similar to the NamingService MBean.

Exactly like the NamingService MBean, the CosNamingService MBean must be first registered in the MBeanServer and then started using the management interface it exposes.
There is the possibility to set the port on which the service will listen for incoming connections, exactly like the NamingService MBean.

One difference between the CosNamingService and the NamingService MBeans is that the latter provides and easy API to be implemented, so that creating, starting and stopping it can be implemented easily by the MX4J team, while the former does not.

A consequence of this is that tnameserv is started using Runtime.exec() and stopped by killing the process created when starting the MBean.

Since starting and stopping an external process may result in the start (); and stop (); returning before the process is really started (or stopped), it is recommended to sleep some time after start() and stop() in order to let tnameserv to start and stop completely.
A suggested value for this delay may be few seconds (1000-5000 milliseconds), but the value strongly depends on the hardware and operative system.