0 Replies Latest reply on Dec 13, 2004 4:34 PM by Randy Xu

    Switching JMX-Console from JRMP to HTTP invoker

    Randy Xu Newbie

      Hi,

      I read in the admin/dev guide that it's possible to switch to the HTTP/RMI invoker from the pre-configured JRMP invoker. But I'm not entirely sure how to do this.

      Right now the JRMP invoker references are in conf/jboss-service.xml and jmx-invoker-adaptor-server.sar/META-INF/jboss-service.xml

      I have the following http-invoker.sar configuration. Any suggestions on how to do this or where to start?



      <!-- The HTTP invoker service configration
      -->

      https://
      /invoker/JMXInvokerServlet
      false


      <!-- The HTTP HA invoker service configration for EJB invocations
      -->

      https://
      /invoker/EJBInvokerHAServlet
      false



      <!-- Expose the Naming service interface via HTTP -->

      <!-- The Naming service we are proxying -->
      jboss:service=Naming
      <!-- Compose the invoker URL from the cluster node address -->
      https://
      /invoker/JMXInvokerServlet
      false
      org.jnp.interfaces.Naming



      org.jboss.proxy.ClientMethodInterceptor
      org.jboss.proxy.SecurityInterceptor
      org.jboss.naming.interceptors.ExceptionInterceptor
      org.jboss.invocation.InvokerInterceptor




      <!-- Expose the Naming service interface via clustered HTTP. This maps
      to the ReadOnlyJNDIFactory servlet URL
      -->

      jboss:service=Naming
      https://
      /invoker/readonly/JMXInvokerServlet
      false
      org.jnp.interfaces.Naming



      <!-- Config from: Sebastian -->
      <!-- Expose the HAJNDI service interface via clustered HTTP. This maps
      to the JMXInvokerHAServlet servlet URL
      -->

      jboss:service=HAJNDI
      jboss:service=HAJNDI
      https://
      /invoker/JMXInvokerHAServlet
      false
      org.jnp.interfaces.Naming

      org.jboss.ha.framework.interfaces.FirstAvailable
      <!-- ### Change PartitionName attribute ### -->
      yankee


      org.jboss.invocation.http.interfaces.ClientMethodInterceptorHA
      org.jboss.proxy.SecurityInterceptor
      org.jboss.naming.interceptors.ExceptionInterceptor
      org.jboss.invocation.InvokerInterceptor




      <!-- Config from: Examples: chap8/ex3b/http-invoker-service.xml -->
      <!-- Expose the HAJNDI service interface via clustered HTTP. This maps
      to the ReadOnlyJNDIFactoryHA servlet URL
      -->

      jboss:service=HAJNDI
      jboss:service=HAJNDI
      https://
      /invoker/readonly/JMXInvokerHAServlet
      false
      org.jnp.interfaces.Naming

      org.jboss.ha.framework.interfaces.FirstAvailable
      <!-- ### Change PartitionName attribute ### -->
      yankee


      org.jboss.invocation.http.interfaces.ClientMethodInterceptorHA
      org.jboss.proxy.SecurityInterceptor
      <!--
      org.jboss.naming.interceptors.ExceptionInterceptor
      -->
      org.jboss.invocation.InvokerInterceptor





      <!-- Config from: Examples: chap8/ex3b/http-invoker-service.xml -->
      <!-- Expose the HAJNDI service interface via clustered HTTP. This maps
      to the secured HAJNDIFactory servlet URL
      -->

      jboss:service=HAJNDI
      jboss:service=HAJNDI
      https://
      /invoker/restricted/JMXInvokerHAServlet
      false
      org.jnp.interfaces.Naming

      org.jboss.ha.framework.interfaces.FirstAvailable
      <!-- ### Change PartitionName attribute ### -->
      yankee


      org.jboss.invocation.http.interfaces.ClientMethodInterceptorHA
      org.jboss.proxy.SecurityInterceptor
      <!--
      org.jboss.naming.interceptors.ExceptionInterceptor
      -->
      org.jboss.invocation.InvokerInterceptor