Home  Administration > Monitor Administration > SiteScope Data Collector Configuration > Managing SiteScope > SiteScope Preferences > UNIX Remote Preferences > Technical Notes on Remote UNIX Monitoring



Technical Notes on Remote UNIX Monitoring

The following is additional information relating to the setup of remote UNIX servers in SiteScope and the monitoring of remote UNIX server performance.

Connection Methods for Remote UNIX

You can choose one of several methods that SiteScope should use to connect to remote UNIX servers. These include the following:

telnet

Along with SSH, telnet is another popular method for connecting to remote UNIX servers. You can set up your remote servers to require a password for telnet, or to allow access without a password (like "rsh"). SiteScope will handle either case.

SSH

For Solaris, using the SSH access method requires that an SSH client is installed on the SiteScope machine and the SSH server installed on the servers you are monitoring. See the document on Secure Shell in the Advanced SiteScope Topics section for more information on SSH requirements. The path to the SSH client on the machine where SiteScope is running should be:
/usr/local/bin/ssh or /usr/bin/ssh

For Windows NT or 2000, an SSH client is included in the package. For debugging, the Windows SSH client can be run from the command line, replacing the values for the username, host name, and password:\SiteScope\tools\plink.exe -ssh myUser@myServer.myCompany.com -pw myPassword

Using SSH requires that digital certificates be installed on each of the servers you will be connecting to.

rlogin

You can set up your remote servers to require a password for rlogin, or to allow access without a password (like "rsh"). SiteScope will handle either case.

HTTP

There are some cases where it may be useful to use a Common Gateway Interface program over HTTP to access performance data or application data from a UNIX server. Two simple CGI scripts are included with SiteScope to allow access over HTTP: <SiteScope root directory>/WEB-INF/classes/CustomRemote/examples/remote.pl and <SiteScope root directory>/WEB-INF/classes/CustomRemote/examples/remote.sh

The remote.pl CGI is a Perl (version 4 and above) script that executes a command on the server; the remote.sh script does the same, except as a UNIX sh script. CGI commands are passed in via the COMMAND CGI variable. If you are using the CGI connection method and you want to use remote actions, remember that the permissions for both the directory containing the CGI script and the /script directory need to allow the Web server (probably running as a user with few permissions) to execute in those directories. Additionally, the scripts need to have execute permission.

If you wish to use a CGI script that puts more restrictive limits on the commands that can be run, you can use a different CGI script. All that matters is that the CGI returns the output of the command passed in via the COMMAND variable. For greater security, you can set up your Web server to require a login/password authorization to run the script (this is recommended). Also, if you have a secure Web Server on that server, you can set up the script to run using the Secure Sockets Layer (SSL, used in https requests), so that the request and output is encrypted.

We are open to requests for additional connection modes and the API for writing connectors is available. We have also included information on how to create an adapter file to remotely monitor versions of UNIX that are not currently supported as one of the SiteScope defaults. In either case, contact SiteScope support at http://support.mercuryinteractive.com/ and we can discuss adding a connector that fits your specific needs. A sample connector Java class, which outlines the structure of a connector, can be found in the following directory: <SiteScope install path>/SiteScope/classes/CustomRemote/examples

If you choose to write one yourself, let us know - we'd like to hear about your experience. 




Copyright 2006 Mercury Interactive Corporation