Web UI

Longitude provides a self-signed certificate when it is installed for basic site encryption. Since this certificate is not signed by a trusted certificate authority, Firefox 3.x may not allow you to view the Longitude Management Console in SSL using the default certificate, and other browsers may display security warnings.

There can be a problem viewing the detail page for a down SLA in IE - when you try to get the details, the status bar will display "Downloading data http://0.0.0.0/...", and then the display an incorrect detail report.

The work around for the "Downloading data http://0.0.0.0/..." message in IE for SLA details is:

1) Hit Ctrl-F5 - you should see "Done" in the status bar
2) Click the "Back" button in the browser
3) Now you should either see the correct page, or a "Webpage has expired" page
4) If you see "Webpage has expired": click "Back" button on the browser, and re-run the report.

Running Heroix Longitude 6.1.2 (build 337)

This inconsistency in the webui leaves me confused as well as making it difficult to /delete/ Monitored computers though I can easily /add/ Computers to be Monitored:

Where Computers are to be selected for Monitoring, the comma-delimited field is blank though Computers are being monitored, and in the Monitored Computers drop-down, the monitored computers are not checked according to the "Gears" view where I do see all monitored Computers by Application. See Home | Monitoring | Manage Monitoring | Monitor Application

In 6.2 by default the drop down menu items have been disabled. If you would like to enable them so they appear as they did in previous versions you can go to Administration > Component Management > Manage Longitude Properties and click on Web UI. Then select advanced, scroll to the bottom of the page, change showmenubaritems to yes and proceed to save changes.

You may see exclamation points appear on the manage monitoring screen. This means that the consolidator has not gotten its status yet and should fix itself next time it refreshes. If it seems as though it is taking a very long time, verify that your Statistics Service (on Both Agent and Management Console) is running.

The Web UI can slow down if the database fills up. The Longitude Upgrade Manager automatically allocates more storage space to a database that is over 80% full or has less than 100Mb of free space, but if the database fills up despite this, the Web UI will be very slow. To check how much space is left in the database and allocate more, if necessary:

1. Start up SAP DB WWW
   On Windows, this process is started by starting the SAP DB WWW service.
   On Linux, this process is started by switching to the Longitude/bin directory and executing:
   ./firenze_sapdbWebAdm start

When installing Longitude and creating new Longitude users, you create a internal Longitude accounts associated with a valid email address.

If you forget the password for a Longitude user account, select "Forgot password" after supplying the Longitude account name.

You will receive an email at the email address used to setup Longitude with a new password.

In rare cases the sliders used to set numeric values in the Web UI may not finish loading within the allowed timeout period. This is a timing issue that may affect some client browsers.

If the sliders are not fully initialized the pointers for the sliders will be all the way to the left and the line that normally runs down the center of the slider will not appear. Clicking on the slider will finish initializing it and make it operational.

Computer names including underscores may cause problems selecting groups of computers, including the Enterprise group, from the computer tree in the Web UI. If you encounter this problem, select the computers in the group individually. You may wish to create a view that restricts all computer names including an underscore to a particular group.

When a variable is inserted into the Full Text generated event field of a Correlated Event using Internet Explorer, the variable will always be appended to the end of the existing text, no matter where the cursor was positioned prior to the insert. This is not a problem with Firefox. Heroix is investigating how to resolve this issue for a future release.