HipCheck Installation and User Guide
2 Getting started
This chapter covers installing and configuring the HipCheck mobility service components.
To get started with HipCheck, complete these steps, in the following order:
- "Installing the HipCheck agent"
- "Setting up systems, user privileges, and alert recipients on the HipCheck Mobility Server"
- "Installing the HipCheck client"
- "Activating the HipCheck mobility service"
After you complete the steps described in this chapter, you are ready to monitor your systems with the HipCheck mobility service. See Chapter 3, "Using the HipCheck client" for more information.
Note: To update your current agents and clients, see Appendix A, "Upgrading HipCheck agents and clients" (page 103).Installing the HipCheck agent
The HipCheck mobility service uses special agent software to monitor the behavior and performance of SCO UNIX and Microsoft Windows systems. This section describes how to install the HipCheck agent on the following supported operating systems:
- "Install the HipCheck agent on SCO OpenServer Release 5.0.7 systems"
- "Install the HipCheck agent on SCO OpenServer Release 6 systems"
- "Install the HipCheck agent on SCO UnixWare 7.1.4 systems"
- "Install the HipCheck agent on Windows systems"
To verify that a system's configuration supports being monitored by the HipCheck agent, see "Before you begin".
Note: To update your existing agents, see Appendix A, "Upgrading HipCheck agents and clients" (page 103).Before you begin
HipCheck requires that a monitored system uses either a Fully-Qualified Domain Name (FQDN) or a static IP address. A system that obtains its IP address from a DHCP server can also be monitored by HipCheck, provided the system's IP address does not change. This can be accomplished in a variety of ways, including: NAT (Network Address Translation), firewall port-forwarding, or configuring a reserved IP address that is always assigned to the system by the DHCP server.
If your system uses NAT, or is located behind an ADSL router or firewall, you must configure your router to use port-forwarding and a static IP address provided by your Internet Service Provider. After you install the HipCheck agent on a system that falls into one of these categories, follow the instructions in the "Setting up port forwarding for NAT systems" section.
Install the HipCheck agent on SCO OpenServer Release 5.0.7 systems
The HipCheck agent for SCO UNIX systems is written in Java and works as a SOAP/XML-based web service. It uses the Apache Axis Java SOAP implementation and the Tomcat Java application server. It is not necessary to have the Apache web server installed or running.
Prerequisites for installing the HipCheck agent
Before installing the HipCheck agent, verify that your SCO OpenServer Release 5.0.7 system satisfies the following prerequisites:
- Using customquery(ADM), verify that the system contains the following required software products:
- SCO OpenServer Release 5.0.7 Maintenance Pack 5 or later
- Apache Tomcat Servlet Container, version 4.1.31 or later
- Java 2 Standard Edition (J2SE), version 1.4.2
- Provided on the SCO OpenServer Release 5.0.7 Supplement CD Version 5. To check that this software is installed, run:
# customquery ListPackages | grep Java2- Verify that the required Java 2 Runtime Environment (Java2_JRE_142::1.4.2La) and Java 2 Software Development Kit (Java2_SDK_142::1.4.2La) packages are listed.
- gSOAP 2.3.3 and JavaSOAP (including Xerces for Java), version 1.0.0Bb
- You must install the soap-1.0.0Bb_vol.tar version of this product, which is provided at the HipCheck Portal. Note that the 1.0.0Ba version of gSOAP is incompatible with the HipCheck agent and must be removed prior to installing the required 1.0.0Bb version.
- The system's domain name must be defined in the /etc/resolv.conf file. If you need to add a domain entry for your system to /etc/resolv.conf file, see "Configuring the Domain Name Service" in the SCO OpenServer Networking Guide or the resolver(SFF) manual page for help.
- Now verify that Apache Axis is working properly on the system. To do this:
Installing the HipCheck agent
To install the HipCheck agent on an SCO OpenServer Release 5.0.7 system:
- Log in to the SCO OpenServer system as root.
- Create the following directory:
# mkdir -p /HcSCOUA- Download the HipCheck agent for SCO UNIX systems.
Access the HipCheck Portal:- Change to the /HcSCOUA directory and extract the contents of the tar archive by running the following commands:
# bunzip2 HcSCOUA-1.0.2.OSR507.tar.bz2# tar xvf HcSCOUA-1.0.2.OSR507.tar- Run the following command to install the HipCheck agent:
# custom -p SCO:HipcheckSCOUnixAgent -i -z `pwd`/archives/TAPEThe HipCheck agent for SCO UNIX systems starts automatically upon installation, and whenever the system is rebooted.
Note: If this system uses NAT, or sits behind an ADSL router/firewall, see "Setting up port forwarding for NAT systems" to make the agent service accessible from the Internet.Verifying the HipCheck agent installation
To confirm that the HipCheck agent is running and able to communicate with the HipCheck Mobility Server:
- Review the custom logs in /var/adm/install/logs/custom/HcSCOUA to verify that the installation completed without errors.
- Confirm that Tomcat is running:
# ps -aef | grep tomcat- Verify that the SCOUnixAgentService service is listed on the Axis Services web page, at:
For information on troubleshooting, administering, and extending the HipCheck agent, see Chapter 5, "Managing HipCheck agents".
Next steps:
- When the HipCheck agent is running and able to communicate over the Internet, proceed to the "Setting up systems, user privileges, and alert recipients on the HipCheck Mobility Server" section.
Install the HipCheck agent on SCO OpenServer Release 6 systems
The HipCheck agent for SCO UNIX systems is written in Java and works as a SOAP/XML-based web service. It uses the Apache Axis Java SOAP implementation and the Tomcat Java application server. It is not necessary to have the Apache web server installed or running.
Prerequisites for installing the HipCheck agent
Before installing the HipCheck agent, verify that your SCO OpenServer Release 6.0.0 system satisfies the following prerequisites:
- Using customquery(ADM), verify that the system contains the following required software products:
- SCO OpenServer Release 6.0.0 Maintenance Pack 2 or later
- Java 2 Standard Edition (J2SE), version 1.4.2 or 1.5.0
- Apache Tomcat Servlet Container, version 4.1.31 or later
- A separately installable component that is included on the SCO OpenServer Release 6.0.0 MP2 Supplement CD. To check that this software is installed, run:
# customquery ListComponents | grep tomcat
- If Tomcat is installed, you see SCO:tomcat::4.1.31Sa.
- The system's domain name must be defined in the /etc/resolv.conf file. If you need to add a domain entry for your system to /etc/resolv.conf file, see "Configuring the Domain Name Service" in Administering TCP/IP (in the DocView Networking topic) or the resolver(SFF) manual page for help.
- Now verify that Apache Axis is working properly on the system. To do this:
Installing the HipCheck agent
To install the HipCheck agent on an SCO OpenServer Release 6 system:
- Log in to the SCO OpenServer system as root.
- Create the following directory:
# mkdir -p /HcSCOUA- Download the HipCheck agent for SCO UNIX systems:
Access the HipCheck Portal:- Change to the /HcSCOUA directory and extract the contents of the tar archive by running the following commands:
# bunzip2 HcSCOUA-1.0.2.OSR600.tar.bz2# tar xvf HcSCOUA-1.0.2.OSR600.tar- Run the following command to install the HipCheck agent:
# custom -p SCO:HipcheckSCOUnixAgent -i -z `pwd`/archives/TAPEThe HipCheck agent for SCO UNIX systems starts automatically upon installation, and whenever the system is rebooted.
Note: If this system uses NAT, or sits behind an ADSL router/firewall, see "Setting up port forwarding for NAT systems" to make the agent service accessible from the Internet.Verifying the HipCheck agent installation
To confirm that the HipCheck agent is running and able to communicate with the HipCheck Mobility Server:
- Review the custom logs in /var/adm/install/logs/custom/HcSCOUA to verify that the installation completed without errors.
- Confirm that Tomcat is running:
# ps -aef | grep tomcat- Verify that the SCOUnixAgentService service is listed on the Axis Services web page, at:
For information on troubleshooting, administering and extending the HipCheck agent, see Chapter 5, "Managing HipCheck agents"
Next steps:
- When the HipCheck agent is running and able to communicate over the Internet, proceed to the "Setting up systems, user privileges, and alert recipients on the HipCheck Mobility Server" section.
Install the HipCheck agent on SCO UnixWare 7.1.4 systems
The HipCheck agent for SCO UNIX systems is written in Java and works as a SOAP/XML-based web service. It uses the Apache Axis Java SOAP implementation and the Tomcat Java application server. It is not necessary to have the Apache web server installed or running.
Prerequisites for installing the HipCheck agent
Before installing the HipCheck agent, verify that your SCO UnixWare Release 7.1.4 system satisfies the following prerequisites:
- Using pkginfo(1), verify that the system contains the following required software:
- SCO UnixWare Release 7.1.4 Maintenance Pack 3 or later
- Java 2 Standard Edition (J2SE), version 1.4.2 or 1.5.0
- Apache Tomcat Servlet Container, version 4.1.31 or later
- javasoap - Apache Axis 1.2 and Apache Xerces-J 1.4.4, version 1.2 or later
- You must download and install the javasoap-1.2.a.pkg file that is available at the HipCheck Portal. Note that older versions of the javasoap package are incompatible with the HipCheck agent and must be removed prior to installing this required product.
- The system's domain name must be defined in the /etc/resolv.conf file. If you need to add a domain entry for your system to /etc/resolv.conf file, see "Configuring Domain Name System (DNS) servers" in Administering TCP/IP and Internet services (in the DocView Networking topic) or the resolv.conf(4tcp) manual page for help.
- Now verify that Apache Axis is working properly on the system. To do this:
Installing the HipCheck agent
To install the HipCheck agent on an SCO UnixWare Release 7.1.4 system:
- Log in to the SCO UnixWare system as root.
- Create the following directory:
# mkdir -p /HcSCOUA- Download the HipCheck agent for SCO UNIX systems:
Access the HipCheck Portal:- Change to the /HcSCOUA directory and uncompress the downloaded file:
# uncompress HcSCOUA-1.0.2.UW714.pkg.ds.Z- Run the following command to install the HipCheck agent:
# pkgadd -d `pwd`/HcSCOUA-1.0.2.UW714.pkg.ds
The HipCheck agent for SCO UNIX systems starts automatically upon installation, and whenever the system is rebooted.
Note: If this system uses NAT, or sits behind an ADSL router/firewall, see "Setting up port forwarding for NAT systems" to make the agent service accessible from the Internet.Verifying the HipCheck agent installation
To confirm that the HipCheck agent is running and able to communicate with the HipCheck Mobility Server:
- Review the pkgadd logs in /var/sadm/install/logs/HcSCOUA to verify that the installation completed without errors.
- Confirm that Tomcat is running:
# ps -aef | grep tomcat- Verify that the SCOUnixAgentService service is listed on the Axis Services web page, at:
For information on troubleshooting, administering, and extending the HipCheck agent, see Chapter 5, "Managing HipCheck agents".
Next steps:
- When the HipCheck agent is running and able to communicate over the Internet, proceed to the "Setting up systems, user privileges, and alert recipients on the HipCheck Mobility Server" section.
Install the HipCheck agent on Windows systems
You can install the HipCheck agent on the following Microsoft Windows systems:
To install the HipCheck agent on a supported Windows system:
- Install Microsoft .NET Framework Version 2.0, if it is not already on the system.
Download the installer file:
Install .NET Framework Version 2.0:- Download and install the HipCheck agent for Windows systems:
Download the installer file:- If Windows Firewall is running on the system, do one of the following so the HipCheck agent can communicate with the HipCheck Mobility Server:
The HipCheck agent is a standard Windows service that starts automatically when the installation is complete and whenever the system is restarted.
Note: If this system uses NAT, or sits behind an ADSL router/firewall, see "Setting up port forwarding for NAT systems" to make the agent service accessible from the Internet.To confirm that the HipCheck agent is running and able to communicate with the HipCheck Mobility Server:
- Run the Windows Services utility (Control Panel > Administrative Tools > Services) and verify that there is an entry for HipCheck Agent and that the "Status" column shows that the service is Started.
- Run the Windows Event Viewer utility (Control Panel > Administrative Tools > Event Viewer) and double-click on the HipcheckLog entry. Then double-click on the latest message in the log and verify that it says the agent is Ready to receive HipCheck requests.
- Finally, access the HipCheck agent service web page at:
For information on troubleshooting and administering the HipCheck agent, see Chapter 5, "Managing HipCheck agents".
Next steps:
- When the HipCheck agent is running and able to communicate over the Internet, proceed to the "Setting up systems, user privileges, and alert recipients on the HipCheck Mobility Server" section.
Setting up port forwarding for NAT systems
If the system that you want to monitor uses NAT, or is located behind an ADSL router or firewall, you must configure your router to use port-forwarding and a static IP address from your Internet Service Provider.
After you install the HipCheck agent on the desired system, perform these steps:
- Make your ADSL router your default route. Use the command that is appropriate for your operating system.
- Verify that the HipCheck agent is running. Open a web browser and enter the URL that is appropriate for your operating system.
- Replace <Agent-IPaddress> with the IP address for the system on which you installed the HipCheck agent (for example, 192.168.1.242).
Note: If you cannot see these services, there is a problem with your agent installation. See Chapter 5, "Managing HipCheck agents" for troubleshooting information.- Log in to your ADSL router/firewall and select the router's port redirection option.
- Create a service called "HipCheck".
- If you installed an agent on an SCO UNIX system, redirect TCP/IP port 8080 to the IP address for the system where you installed the UNIX HipCheck agent, on port 8080. In this example, that would be 192.168.1.242 on port 8080.
- If you installed an agent on a Windows system, redirect TCP/IP port 8081 (or the port number that you selected when you installed the agent) to the IP address for the system where you installed the Windows HipCheck agent, on port 8081. For example, 192.168.1.242 on port 8081.
- Activate the new "HipCheck" service that you set up on the router.
- Determine your ADSL router's Internet (or WAN) IP address, so you can verify that you can access the HipCheck agent service from the Internet. Open a web browser and enter the URL that is appropriate to your operating system:
- Replace <WAN-IPaddress> with your router's Internet IP address (for example, 83.217.55.123).
- You should see the same list of services that you see when you use the web address specified in Step 2.
Note: If you cannot see these services, there is a problem with your router configuration. Consult your router documentation for further assistance.Setting up systems, user privileges, and alert recipients on the HipCheck Mobility Server
Now you need to access the HipCheck Mobility Server and set up the systems that you want monitored by the HipCheck mobility service. You also need to configure permissions and responsibilities for the subscribers who will be running HipCheck clients.
You do these tasks at the HipCheck Portal, a set of administration web pages available on the HipCheck Mobility Server.
To log in to the HipCheck Portal:
- Open a web browser and enter the following web address:
- Enter your Me Inc. account user name and password and click OK.
Complete the tasks described in these sections, in the following order:
After you complete these steps, proceed to the "Installing the HipCheck client" section.
Set up systems to be monitored
You need to provide information about the systems that you want to monitor on the HipCheck Mobility Server.
To set up the systems that you want monitored by HipCheck:
- Log in to the HipCheck Portal at:
- Click Create/Delete Systems.
- Click Create in the management toolbar.
- On the "Create New System" page, supply the following information for the system that you are setting up:
Field Enter the following... System Name The Fully-Qualified Domain Name (FQDN) of the system. For example: system1.xyz.com.Alternately, you can enter the system's IP address. System OS Type Select the appropriate operating system from the pop-up list. System Description Descriptive text to help identify the system. This field is optional. System Admin User Administrator information is required to ensure that only authorized users can set up systems for monitoring. This field is automatically populated, based on the type of operating system selected in the "System OS Type" field. SCO UNIX systems require the root account; Windows systems require the default Administrator account. Localized versions of Administrator can be used. System Admin Password Enter the password that corresponds to the administrator account specified in the "System Admin User" field.
- Note: For Windows systems, you must supply the password for the default Administrator account. The password for a regular user account with administrative authority will not work.
- Note: If you are working within a Windows Domain group, use the password for the Administrator account for the system you are setting up. Do not use the domain-wide Administrator password.
HipCheck sends the system admin user name and password to the HipCheck agent for authentication. The agent must be installed and running on the target system in order for this to work. If HipCheck cannot authenticate the user name and password, or if the authentication check fails, you cannot add the system. System URL Specify the web address for connecting to the system's HipCheck agent. Click Default to automatically enter the URL for a default agent installation. If you specified a non-default TCP/IP port when you installed the agent, enter the correct port number instead of the one supplied by the Default button.The default protocol is http, which is recommended for development and testing only. For production servers and agents, specify https instead of http if you want a secure connection. Passwords are sent over this connection so https is recommended if an insecure network, such as the Internet, is used. Agent Connection Type Specifies how the connection between the HipCheck Mobility Server and the HipCheck agent is configured. Must be one of the following choices:
- Direct through http
- The server communicates directly with the agent using http or https. Recommended for development, evaluation, and test only.
- For more information, see "Direct through http" in Chapter 5, "Managing HipCheck agents".
- Through proxy
- The server communicates with a proxy server, which then relays the message to the agent. The proxy can be located on the same system as the agent, or another system behind the firewall. Choosing this option displays the Proxy Server URL field. Enter the URL of the proxy. You can specify either the http or https protocol. The http protocol is recommended for development and test only. If https is chosen, a self-signed certificate is used.
- For more information, see "Through proxy" in Chapter 5, "Managing HipCheck agents".
- Direct through https, default certificate
- The server communicates directly with the agent using https and a self-signed certificate (no proxy).
- For more information, see "Direct through https; default certificate" in Chapter 5, "Managing HipCheck agents".
- Direct through https, user certificate
- Click Add to complete the setup process.
When a system is successfully set up, it is included in the HipCheck system monitoring list that is displayed on the "Create/Delete Systems" page. This list shows all of the systems that are set up to be monitored for which you have owner privileges.
Note: When you set up a system for monitoring at the HipCheck Portal, you are automatically assigned Owner privileges for the system. See "Set up user privileges and alert recipients" for more information on the Owner privilege and associated permissions.Me Inc. account owners and account managers have Owner privileges for every system that is set up at the HipCheck Portal.Next steps:
- If you have other systems that you need to set up, repeat the steps in this section.
- When you are finished setting up systems to be monitored by HipCheck, proceed to the "Set up user privileges and alert recipients" section, below.
Set up user privileges and alert recipients
When you set up a system for HipCheck monitoring on the HipCheck Mobility Server, you are automatically assigned HipCheck Owner privileges, and also set up to receive alerts for problems that are detected on the system.
For each system that you own, you can authorize other subscribers or public groups in your Me Inc. account to have HipCheck monitoring or management privileges. You can also set up subscribers and public groups to receive alerts if problems are detected.
The HipCheck privilege levels that can be assigned to users and groups are:
- Owner
- HipCheck Portal management permissions -- the user can modify the system's privilege list, change the system's password, and remove the system from the HipCheck system monitoring list.
- HipCheck client management permissions -- the user can look at the various system views, turn alerts on and off, and perform maintenance or corrective actions.
- Admin
- HipCheck Portal monitoring permissions -- the user can see who is on the system's privilege and alert lists and can check on the system's status.
- HipCheck client management permissions -- the user can look at the various system views, turns alerts on and off, and perform maintenance or corrective actions.
- View
Use the following table to determine the configuration steps needed to set up subscribers and groups with the desired combination of privilege levels and alert responsibilities.
HipCheck Portal permissions HipCheck client permissions Receive alerts? Configuration steps Management Management Yes Management Management No
- Set privilege level to Owner
Monitoring Management Yes Monitoring Management No
- Set privilege level to Admin
Monitoring Monitoring Yes Monitoring Monitoring NoThese configurations steps are described in the following procedure.
To assign user privileges and/or alert recipients for a system that you own:
- Log in to the HipCheck Portal at:
- Click Manage/View System Privileges and Attributes. You see the "Manage/View Privileges and Attributes" page.
- This page displays all of the systems in the HipCheck system monitoring list for which you have privileges. The "Your Privs" column indicates the level of privilege that you have for each system in the list. Note that account owners and account managers see the complete HipCheck system monitoring list; that is, every system that has been set up at the HipCheck Portal.
Assign HipCheck privileges to subscribers and groups
- Click Modify in the "Privileges" column for the desired system. The "Manage Privileges" page displays the current privilege list for the specified system.
Configure users and groups to receive HipCheck alerts
- Click Modify in the "Alerts" column for the desired system.
- The "Manage Alerts" page shows the current alert list for the specified system. All of the HipCheck users displayed here, as well as every member of any public groups listed, receive alerts if the HipCheck agent detects problems with the system.
To assign alerts to HipCheck users:
To assign alerts to HipCheck groups:
- Click Add Group in the management toolbar.
- Select the checkbox next to the desired HipCheck group(s).
Next steps:
- When you are finished setting up user privileges and assigning alert recipients for the systems that you want monitored by HipCheck, proceed to the "Installing the HipCheck client" section, next.
- Chapter 4, "Managing HipCheck systems and users" for information on additional management tasks that you can perform at the HipCheck Portal.
Installing the HipCheck client
The HipCheck client is the interface for monitoring system performance, performing administration actions, and responding to alerts to correct problems. There are two client versions available: a mobile client that runs on Windows Pocket PCs and a PC client that runs on Windows computers.
The HipCheck client can be used on the following platforms:
Note: At this time, the HipCheck mobile client cannot be used on mobile devices that run Windows Mobile 5.0 Smartphone or Windows CE 5.0.See "Before you begin" to confirm that your system configuration supports the use of the HipCheck client.
To install the HipCheck client, use the appropriate installation procedure:
- "Install the HipCheck client on Windows Mobile Pocket PCs".
- "Install the HipCheck client on Windows computers".
Note: To update already-installed clients, see Appendix A, "Upgrading HipCheck agents and clients" (page 103).Before you begin
The following resources must be configured on all systems running HipCheck clients:
- DNS Server: The DNS server where the HipCheck Mobility Server is defined must be configured to route all requests of the form "https:*.server", where server is the IP address or Fully Qualified Domain Name (FQDN) of the HipCheck Mobility Server running the HipCheck service. For example, on UNIX systems, this involves placing an entry like the following in the resolv.conf file on the DNS server:
169.254.155.24 *.system1.domain.com- Certificates: When a HipCheck client connects to the HipCheck Mobility Server for the first time, the server offers a certificate that you must accept to continue. The certificate may be self-signed (the default) or it may be a third-party signed certificate, depending on the configuration of the HipCheck Mobility Server. While most mobile phones and browsers are pre-loaded with root certificates from many Certificate Authorities (CAs), it may be necessary to load a root certificate onto your mobile phone. Your system administrator should provide you with these details, if necessary.
- In any case, when using the HipCheck client, you should examine the contents of the certificate before accepting it, to determine the authenticity of the system sending the certificate. If the certificate does not contain the content that you expect, you should refuse to accept the certificate and contact your system administrator.
Install the HipCheck client on Windows Mobile Pocket PCs
Installing the HipCheck mobile client requires the use of a Windows desktop or laptop computer, as well as your Pocket PC device. Prior to installing the HipCheck mobile client, verify that the Windows computer you will be using contains the following software:
- Microsoft ActiveSync 4.1
- Microsoft .NET Framework Version 2.0
- See "Install the HipCheck agent on Windows systems", earlier in this chapter, for help downloading and installing this software, if necessary.
To install the HipCheck mobile client on a supported Windows Mobile device:
- Connect your Windows Mobile Pocket PC to your Windows desktop or laptop, using the synchronization cable or cradle provided with your mobile device.
- Install Microsoft .NET Compact Framework Version 2.0 on your mobile device, if it is not already on the phone.
Download the installer file:
Install .NET Compact Framework Version 2.0:- Install the HipCheck mobile client on your Windows Mobile Pocket PC.
Download the installer file:The HipCheck mobile client is now available from the Programs screen on your Windows Mobile Pocket PC.
Next steps:
- Repeat the steps in this section to install the HipCheck mobile client on other Pocket PCs.
- To install the HipCheck PC client, see "Install the HipCheck client on Windows computers".
- When you are finished installing HipCheck clients, proceed to the "Activating the HipCheck mobility service" section.
Install the HipCheck client on Windows computers
If you want to monitor systems from a Windows computer instead of from a Pocket PC, you can use the HipCheck PC client.
To install the HipCheck PC client on a supported Windows system:
- Install Microsoft .NET Framework Version 2.0, if it is not already on the system.
Download the installer file:
Install .NET Framework Version 2.0:- Download and install the HipCheck PC client.
Download the installer file:The HipCheck PC client is now available from the Me Inc folder in your Start menu.
Next steps:
- Repeat the steps in this section to install the HipCheck PC client on other Windows computers.
- To install the HipCheck mobile client on supported mobile devices, see the previous section, "Install the HipCheck client on Windows Mobile Pocket PCs".
- When you are finished installing HipCheck clients, proceed to the "Activating the HipCheck mobility service" section.
Activating the HipCheck mobility service
You now need to authenticate the HipCheck client that you installed so it is authorized to connect to the HipCheck Mobility Server. Doing this activates your subscription to use the HipCheck mobility service, at which point you can begin monitoring configured systems.
To authenticate your HipCheck client:
- Run the HipCheck client for the first time.
- Complete the fields on the "Account Edit" screen:
- Select the Set as current checkbox.
- Click Save.
- While the HipCheck client contacts the HipCheck Mobility Server, you see an "Authenticating" dialog.
Note: If you have not yet accepted the Subscriber License Agreement at the HipCheck Portal, you will be prompted to do so now. Read the contents of the Agreement and then click Accept.- Once you successfully authenticate with the HipCheck Mobility Server, the HipCheck client is launched. The list of systems that you can monitor or manage -- based on the settings made earlier in the "Setting up systems, user privileges, and alert recipients on the HipCheck Mobility Server" section -- is retrieved from the HipCheck Mobility Server. This operation may take a few seconds.
- See Chapter 3, "Using the HipCheck client" for help monitoring and managing systems using HipCheck views, alerts, and actions.