6 Replies Latest reply on Sep 14, 2004 5:19 PM by jxtang

    How to disable MEJB access?

    jxtang Newbie

      I want to control admin access to the JBoss from control. I know that I could disable JMX access via making RMIAdaptor unaccessible. Now I am wondering how to disable the MEJB which could also get the management information in JBoss server.

        • 1. Re: How to disable MEJB access?
          Scott Stark Master

          Remove the ejb-management.jar. This is no longer deployed by default in jboss 3.2.4 and latter.

          • 2. Re: How to disable MEJB access?
            jxtang Newbie

             

            "jxtang" wrote:
            I want to control admin access to the JBoss from control. I know that I could disable JMX access via making RMIAdaptor unaccessible. Now I am wondering how to disable the MEJB which could also get the management information in JBoss server.


            A typo for the first statement. The second "control" should be "console". So the correct statement is:

            I want to control admin access to the JBoss from console.

            • 3. Re: How to disable MEJB access?
              jxtang Newbie

               

              "scott.stark@jboss.org" wrote:
              Remove the ejb-management.jar. This is no longer deployed by default in jboss 3.2.4 and latter.


              Very appreciated your reply!

              But what if I still want to access the MEJB locally inside the JBoss server? My scenario is that I am implementing a CLI like Twiddle but not using JMX. A facade is developed to wrapper the MEJB. When the client call invokes the facade, the facade will do the authorization of the caller and then delegate the call to the MEJB if it is authorized. Otherwise, the facade will reject the call.

              • 4. Re: How to disable MEJB access?
                Scott Stark Master

                They why not use the MBeanServer directly? There is not much point in having a wrapper on top of the MEJB if the only component that should access it is in the same vm as the JMX MBeanServer.

                • 5. Re: How to disable MEJB access?
                  jxtang Newbie

                   

                  "scott.stark@jboss.org" wrote:
                  They why not use the MBeanServer directly? There is not much point in having a wrapper on top of the MEJB if the only component that should access it is in the same vm as the JMX MBeanServer.


                  Honestly, I have been struggling for this design issue from the very beginning. The main consideration not using use the MBeanServer is that I want to adhere to the JSR 77 which must be compilied by all J2EE vendors. So it is the portable issue. I assume that no all the J2EE product support the MeanServer and JMX and even they do, there are some differences among them. I have been awared that MEJB is not that powerful in management as MBeanServer in JBoss. The state management for almost all managed objects are not support in MEJB and start/stop operation can not be invoked through MEJB.

                  Frankly, I could be totally wrong for these reasons and assumptions. If you could correct me and help me to avoid a wrong approach, I would be very appreciated!

                  • 6. Re: How to disable MEJB access?
                    jxtang Newbie

                    Hi Scott,

                    Can you some comments on my latest response?

                    Thanks a lot!

                    John