If your application server and other software is all local, running on the
same machine as the RTI Console, then you should already see the applications
there. If not, try refreshing localhost by selecting localhost, right-click,
Refresh or follow the directions in Section 1.3, “Installing RTI and Enabling Your Application for Monitoring”.
The remainder of this section addresses connecting to remote hosts where RTI
Enterprise has already been installed.
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 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), refer to Section 3.4, “Connecting the RTI Console to JBoss Operations Network”, otherwise click on Connect to RTI
Performance Collectors, which brings up this dialog:
RTI supports accessing remote performance collectors using several
protocols:
-
JBoss Operations Network (JON or RHQ) – Connect through the JBoss ON framework to a remote platform managed by JBoss ON or RHQ
-
Remote Shell (RSH) – Connect to a remote Windows server using Remote Shell (RSH). This option requires the Remote Shell Daemon to be installed as part of Section 1.3.1.2, “Installing RTI Enterprise Collectors on Windows”.
-
Secure Shell (SSH) – Connect to a remote Linux server using Secure Shell (SSH).
-
Cygwin Secure Shell (SSH) – Typically not used, connect to a remote Windows installation containing Cygwin with the Cygwin SSH daemon enabled.
Select one and click . This displays a new dialog
for entering the connection details, such as the one below for Linux SSH:
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 the
connection to verify. Once you are done, click
.
If you have a direct connection to the host, do not check the Create
a tunnel through a firewall checkbox. Contact
<rti_support@ocsystems.com> 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 or Tomcat 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”.
 |  |  |
| 1.6. Viewing and Analyzing RTI Performance Data |  | 1.6.2. Analyzing Application Performance Data |
