The archive folder is hard-coded to the base Uptime Infrastructure Monitor installation directory on the server hosting the up.time Data Collector or uptime_core service.

To change this location, you have the option of creating a logical link to another folder on the same server or a different server.

For example, using the ln command for Linux or Solaris environments: 

1. cd /usr/local/uptime/archives
2. # mv archives archives_old
3. ln -s </new/archive/location> archives

The URL in this monitor is based on the httpContext value in the uptime.conf file. You may find that the httpContext value is set to localhost as shown below:

1. The context of the Uptime HTTP server http://<hostname>:<port> httpContext=http://localhost:9999
   To ensure that the link back URL works correctly, update this field to the proper hostname of the Uptime Infrastructure Monitor monitoring station.
   If this hostname is not resolvable from other networks, some users may not be able to resolve the URL in the email alert.
   A restart of the uptime_core or "up.time Data Collector" service is required after applying this change.
   

   Linux and UNIX Agents

   
   The Linux and UNIX agents do not run until they are polled by the Monitoring Station. To simulate a polling and verify that the agent is active, telnet to the agent server using the agent port (default 9998). The agent is running correctly if you enter sysinfo and the agent returns plain text information about the configuration of your server.
   
   

   Windows Agent

   
   The Windows agent runs as the uptmagnt.exe process and is controlled via the Uptime Infrastructure Monitor agent Windows service. The agent is running if these services are running and you can verify that it is accepting connections using the simulation steps listed above. Enter the "sysinfo" command (including the quotes) to verify connectivity.
   Uptime Infrastructure Monitor uses action profiles to perform recovery steps when a service monitor returns a critical status. Action Profiles are templates that define an action to perform when a monitor encounters a problem and can be applied to one or more service monitors.
   An Action Profile allows you to specify:
   When to start and stop performing the action (escalations).
   The name of the log file to which Uptime Infrastructure Monitor writes error information.
   The name and location of a recovery script that can reboot a server or restart an application, process or service. The name of a Windows host and service, as well as whether to start, stop or restart the host or service.
   An SNMP trap to be sent to a specific traphost and trap community.
   Use the following steps to create an action profile:
2. Click on the Services tab.
3. Click the Add Action Profile link on the left tree menu.
4. Set up the action profile to perform the desired steps (e.g. log to file, run a script, start / stop Windows service, send an SNMP trap, etc.) and click Save.

Next, attach the action profile to an existing service monitor with the following steps:

1. Click on the Services tab.
2. Locate the service monitor in the list and click its name (or click the View icon).
3. Scroll to the bottom of the page and click the Edit Action Profiles button.
4. Add the appropriate Action Profile to the right list and click the Save button.

Related Documentation: For a more in depth understanding please review the documentation Alerts and Actions
How the User Authentication Configuration page works.

1. Take LDAP Query, replace %s in the query with the name under LDAP Username
2. Connect to LDAP using the distinguished name pointing to that user. If authentication fails (or user is not found), it will return "Invalid Credentials"
3. On success, it takes LDAP Group Distinguished Name, and reads the object.
4. If it can not find the object at all, it will output "No Group exists under that Distinguished Name."
5. If it finds the object but the Group object is not under a domain name, it will not be able to read it and returns "Could not get members listing for Group Distinguished Name."
6. If object is read, and the distinguished name in the object exists, the users are inserted into the local Uptime Infrastructure Monitor database
7. If object is read, but it contains entries that do not link to a user, that particular user is skipped and not inserted into Uptime Infrastructure Monitor.

Example:
======================================================================
LDAP URL ldap://ldaphostname:389
LDAP Query uid=%s,ou=usersgroup,dc=subdomain,dc=domain,dc=tld
======================================================================
Synchronization enabled Yes Synchronize every 1h
Group Distinguished Name cn=uptime.group,ou=usersgroup,dc=subdomain,dc=domain,dc=tld
======================================================================
LDAP Username asmith Password ******
======================================================================
Using Oracle LDAP server, there are two methods of creating groups, "groupOfNames" and "groupOfUniqueNames". Uptime Infrastructure Monitor uses "groupOfNames" method.
The following articles will help with setting up Oracle LDAP users under "groupOfNames"
http://docs.oracle.com/cd/E19623-01/820-6169/defining-static-groups.html http://docs.oracle.com/cd/E19316-01/820-2763/bcajq/index.html
If unsure of the paths use software like 'Active Directory Explorer' or 'Wireshark' to connect to the AD/LDAP server to determine the path.

Active Directory Explorer

http://technet.microsoft.com/en-ca/sysinternals/bb963907.aspx

Wireshark

http://www.wireshark.org/download.html