The next step is to connect the RTI Console to the JBoss ON management server and identify the hosts (platforms) that you want to work with.
When you first start the RTI Console, you should see the following:
Initial Console Welcome View
If you have installed the RTI Browser collectors on Windows, then you will see "IE" and "Firefox" under the "localhost" node at the upper left in the Collectors view. localhost represents the machine you're running the console on and is added automatically. In the Welcome to RTI view are several shortcuts to help you get started. We'll assume you want to work with a JBoss ON host (platform) on which you have already installed and enabled RTI, so you should click on Connect to JBoss Managed Platforms, which brings up this dialog:
New Managed Platform Connection Dialog
Enter the required information and click Test the connection to verify. Once you are done, click Next.

Note

In this page, provide the connection information for RTI to communicate with the JBoss ON Server. This is in essence the same information used to login to the JBoss ON Web Interface. We will choose one or more Managed Platforms next.
Once you have established a connection to the RHQ Server, RTI will find and list the available Platforms currently managed by RHQ. Select one or more platforms to work with and click Finish.
By clicking Finish, RTI will establish a connection to each of the selected Platforms. RTI will also determine if an RTI installation exists on the managed Platform and if there are applications being monitored by RTI.
Once you have successfully configured a connection to an RHQ Managed Platform, it will be displayed immediately in the RTI Collectors view. The connection is also saved internally and will automatically be made available at startup until you remove the connection from RTI.
RTI Connections
Some possible variations might be:
  • If you can't connect to your JBoss ON server, or don't see the host you're looking for once you do, use your web browser to connect to the JBoss ON management console directly. The login information and platform list there should be the same as from the RTI Console.
  • If you get an error about "Cannot connect to remote host..." or "No RTI License" and you don't see an RTI Installation node under a newly added platform on the JBoss ON console, verify that you have installed or enabled RTI on that host platform.
  • If you know RTI is installed, but you don't see it among the resources of your platform within the JBoss ON console, you may want to manually discover it, then check again in the Discovery Queue until it appears, as described in Section 3.2.2, “Discovering the RTI Installation”.
  • If you see an RTI Installation node, but don't see a Collector corresponding to your application, or it isn't marked as "[collecting]", verify that you have enabled RTI and restarted your app server. The application's startup script (JBoss run.sh/bat, Tomcat's catalina.sh/bat or Fuse's karaf/karaf.bat) should contain a block of text in it delimited with the string OCS.
  • If you want to connect to a remote host which is not managed by JBoss ON, click on Connect to RTI Performance Collectors and choose the appropriate connection in the "Remote Access Selection" wizard.
  • To add a JBoss or Tomcat collector accessible on localhost, install RTI Enterprise locally if you haven't already, then click on the Configure an Application for Monitoring shortcut on the welcome page and follow the wizard.


loading table of contents...