When you first start the RTI Console, you should see the following:
If you have installed the RTI Browser collectors on Windows, then you will see IE and maybe Chrome and Firefox under the localhost node at the upper left in the Collectors view. The localhost node 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.
If you want to work with a JBoss ON host (platform) you will use Connect to JBoss Managed platforms as described in Section 3.4, “Connecting the RTI Console to JBoss Operations Network”.
If your remote hosts are in the cloud, such as Red Hat OpenShift or Amazon EC2 VPC, you can access multiple hosts through a single remote cloud server by choosing Connect to RTI in the Cloud. This allows you to choose among multiple RTI-enabled hosts accessible through a single remote server. For OpenShift, the available hosts are discovered from the gear registry; on other platforms such as EC2, simply list the hosts, one-per-line, in the file $HOME/.ocs-rti-hosts. Click the Help icon () at the lower left of the "New Cloud Platform Connection" dialog for more information.
For other connections to Linux or Windows Connect to RTI Performance Collectors, which brings up this dialog:
RTI supports accessing remote performance collectors using several protocols:
Select one and click Next. This displays a new dialog for entering the connection details. The most general is that shown below for connecting via SSH to a Linus server:
Enter your remote host login information:
  • Remote Host MUST allow SSH access, or RSH if Windows.
  • Login and Password is your user account on the remote machine.
  • Optional private key exchange is supported.
  • Optional SSH tunneling through a firewall is supported.
Enter the required information and click Test the connection to verify. Once you are done, click Finish.
If you have a direct connection to the host, do not check the Create a tunnel through a firewall checkbox. Contact if you have any questions pertaining to advanced features, including private key exchange or SSH tunneling.
When you have established a connection to the remote host, that host's Description or Host name will be displayed immediately in the RTI Collectors view. The connection is saved internally and will automatically be made available at startup until you delete the connection from your RTI Console.
Some possible variations might be:
  • If you get an error about "No RTI License" and you don't see an RTI Installation node under a newly added platform, verify that you have installed or enabled RTI on that host platform.
  • If you see the host name, but don't see a Collector corresponding to your application, or the collector isn't marked as "[collecting]", verify that you have enabled RTI and restarted your application server, as described in Section 1.3.3, “Enabling Your Applications for Monitoring”.
  • To add a JBoss, Tomcat or Fuse collector accessible on localhost, install RTI Enterprise locally if you haven't already, then click on Configure an Application for Monitoring shortcut on the Welcome page and follow the wizard, as described in Section 1.3.3, “Enabling Your Applications for Monitoring”.


loading table of contents...