Versions Compared

Old Version 27

changes.mady.by.user Unknown User (georg_dembowski)

Saved on

compared with

New Version Current

changes.mady.by.user Gregor B. Rosenauer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

No Format
org.apache.servicemix.jbi.jmx.JaasAuthenticator.authenticate(JaasAuthenticator.java:73) 

you may need to deactivate credentials or use have not provided the required username and password (default: smx / smx (default values for suer and password) to log in. The configuration is in the . These credentials are configurated in /conf/jmx.xml, and the default one delegates and can be deactivated (search in jmx.xml for Comment the following lines to disable JAAS authentication for jmx) which of course poses the usual security issues (no protection at all). The default setting is to delegate the credentials to JAAS, which is configured in conf/login.properties. The first module uses useing the two properties file at /conf/groups.properties and conf/users-credentials.properties and conf/users-passwords.properties. 

Using JConsole

The Java-2 Platform, Standard Edition (J2SE) 5.0 release includes a JMX monitoring tool, JConsole. JConsole monitors applications running on the Java platform and provides information on their performance and resource consumption. Please see Sun's JConsole documentation for more information on using this tool. Please see the following sections for instructions on configuring and using JConsole with ServiceMix.

...

  1. ServiceMix should be running first. Please see the Getting Started guide for instructions on running ServiceMix.
  2. Start JConsole from a command shell. The JConsole executable can be found in the bin directory of the J2SE installation directory.
    Code Block
    cd [J2SE_install_dir]\bin
jconsole
    The JConsole window will appear.

  3. Click on the "Advanced" tab. The following URL must be entered in the "JMX URL" box: service:jmx:rmi:///jndi/rmi://hostname:port/app_to_monitor. Where the hostname is name of the host on which the application to be monitored is running, the port is the port number to connect to the application, and the app_to_monitor is the JMX enabled application to monitor. For example, if none of the defaults for ServiceMix have been modified and ServiceMix is running on localhost, enter the following: service:jmx:rmi:///jndi/rmi://localhost:1099/defaultJBIJMX.



  4. Click the Connect box to connect to the ServiceMix container. org.servicemix will be visible in the console. Click on org.servicemix to see its MBeans.


...

  1. ServiceMix should be running first. Please see the Getting Started guide for instructions on running ServiceMix.
  2. Click on the MC4J executable MC4J Console 1.2b9.exe (for Windows) to start MC4J. The executable can be found in the top-level directory of the MC4J installation. The MC4J window will appear.
  3. Select "Management>Create Server Connection..." from the menu. This will start "My Wizard". The connection to ServiceMix can be created using the wizard.



  4. Enter the following into the text boxes/pull-down menus:
    Select your server connection type: JSR160
    Name: This can any name, for example, ServiceMix
    Server URL: service:jmx:rmi:///jndi/rmi://localhost:1099/defaultJBIJMX
    The Server URL is service:jmx:rmi:///jndi/rmi://hostname:port/app_to_monitor. Where the hostname is name of the host on which the application to be monitored is running, the port is the port number to connect to the application, and the app_to_monitor is the JMX-enabled application to monitor. For example, if none of the defaults for ServiceMix have been modified and ServiceMix is running on localhost, enter the following: service:jmx:rmi:///jndi/rmi://localhost:1099/defaultJBIJMX.
  5. Accept the defaults for the rest of the fields in the Wizard.
  6. Click "Next."
  7. Click "Finish" in the next window.
    A connection to ServiceMix has been added to MC4J!


...

  1. To see MC4J in action, start one of the ServiceMix examples running, for instance, the file binding Example:
    Code Block
    cd [servicemix_install_dir]\examples\file-binding
..\..\bin\servicemix servicemix.xml
    where servicemix_install_dir is the directory in which ServiceMix was installed.
  2. Run MC4J (see the previous section) and click on org.servicemix.
  3. Click on org.servicemix.jbi.framework.ComponentMBeanImpl. The components of the File Binding example will be shown. Right-click on a component and select "Available dashboards...>Basic MBean View" to see the information shown in the diagram below. For more details on using MC4J, please see the MC4J documentation.

ServiceMix JMX Console

...

  1. Download and build the ServiceMix source code. Please see the Getting Started guide for instructions.
  2. Create the WAR file:
    Code Block
    cd [servicemix_install_dir]\tooling\servicemix-web
maven war
    where servicemix_install_dir is the directory to which ServiceMix was downloaded.
  3. Deploy the WAR file into any servlet engine. Instructions for deploying ServiceMix on Tomcat, JBoss, and Geronimo can be found at the following links:
  4. Run the ServiceMix JMX Console. To do this enter the following URL in a web browser: http://localhost:8080/servicemix-web. You will see the following:

...

For examples of how to use the ServiceMix JMX Console, please see War Deployment.

Related Documentation