2. Installing and Running the Hyperserver

You can obtain the installation program for the hyperserver from iTivity. In order to use the hyperserver, it must be licensed for the number of connections you will run. Refer to Section 2.4, Licensing the Hyperserver on Windows, or Section 2.10, Licensing the Hyperserver on Linux for more information.

See the iTivity Deployment Guide for more information and recommendations on hyperserver requirements.

2.1 Installing the Hyperserver on Windows

You can obtain the hyperserver distribution MSI via download from iTivity.net. Contact iTivity Corp for more information.

Other Installation Options:

-You can automate installation on Windows. See Appendix A in this guide.

-You can also create custom installers on the iTivity Support website. See Appendix B.

After installing the hyperserver component, it is recommended that you review the Readme file for the most current product information. You will find this file located at

C:\Program Files\iTivity\iServer\README.txt

1. Download the distribution EXE file the iTivity.net website. After saving this file to disk, open the file.

The following Welcome dialog is displayed:

2. Click Next.

The License Agreement page is displayed.

3. Scroll Down to view the entire agreement. Then click "I accept the terms in the license agreement" to indicate your acceptance. Click Next.

The following dialog is displayed.

4. Click the Custom option to select features if desired. Either way, click Next to continue.

The Destination Folder dialog is displayed.

5. Change the Folder if desired. Click Next to continue.

6. The Hyperserver Port Numbers dialog is displayed.

7. Change the port numbers if needed. Many customers use the default port numbers. The most common change is two switch the agent port to port number 443. If you are upgrading the hyperserver, the installer will display the current setting and there is no need for any change. Click Next.

The following dialog is displayed.

These choices define how a user of iTivity console must authenticate before being allowed to open a connection to the hyperserver. Choose one of the following authentication methods, then click Next to continue.

NTLM (Microsoft Authentication): iTivity console authenticates the username and password against a Microsoft Domain or local database, eliminating the need for a separate local password on every system. NTLM authentication can be used both in an NT domain environment as well as on a standalone Windows NT, 2000 or XP system.

Simple Password: Each hyperserver has its own password that must be entered by the console user trying to connect. Use this option if you want iTivity console authentication to use separate passwords from Microsoft (NTLM) authentication.

No Authentication Required: No login is required. This option is strongly discouraged.

8. After selecting the authentication method, click Next. The next step depends on which method you chose in Step 7.

The Access Permission Group dialog is displayed:

Console users must belong to this group to log in to the hyperserver. Provide a different permission group name or accept the default. Then click Next to continue.

9. The installer is now ready to begin copying the hyperserver files and configuring the hyperserver settings.

Click Install to continue.

10. Next the installer prompts for elevated privileges needed to perform the installation.

Click Continue to authorize the hyperserver installation.

The installer displays a progress bar depicting the status of the installation and configuration.

11. The following dialog is displayed when the installer finishes.

The installation is now complete. Click Finish to exit.

2.2 Licensing the Hyperserver on Windows

After installing, you must license the hyperserver to make it operable.

As explained in the Welcome to iTivity section of this guide, your iTivity license allows a given number of concurrent connections between consoles and agents through the hyperserver. The license you purchase determines the number of concurrent connections that your hyperserver allows.

Note: It is also possible to license agent software separately. When an agent is licensed separately, its connection to an hyperserver does not count as one of the connections allowed by the hyperserver license. Contact iTivity Corp for more information on this option.

2.2.1 Obtaining the License Key and Activation Key

When you purchase your license, iTivity Corp provides a TLA license key. The TLA license key is a series of numbers with hyphens:

Example: 533-0025-32-112012527

When you install the hyperserver, the install process generates an install code. This install code is displayed on the License Status dialog (see Section 2.4.4, below).

To activate your hyperserver, you use the install code to obtain an activation key. The activation key is generated based on the install code and is unique to your ihyperserver system.

To obtain your activation key:

1. After installing the hyperserver, choose Start > All Programs > iTivity > iTivity hyperserver > Tridia Licensing > License Information to display the License information dialog. Note the install code.

2. Contact iTivity Corp with the install code to obtain your activation key, or visit the iTivity Support Site at https://support.itivity.net/ and choose the Licensing option.

After obtaining both the license key and activation key, you can proceed with licensing the hyperserver.

2.2.2 Creating the License File

After obtaining your license key and activation key, follow these steps to license the hyperserver:

1. Select Start > All Programs > iTivity > Hyperserver > Tridia Licensing > Create or Locate Tridia License File.

The Create New Tridia Software License File dialog is displayed.

2. Click Open to create the file with the default name and location.

The license file is created and opened in Notepad.

3. Below the comment area, enter your license key and activation key, separated by a colon.

Example: 533-0025-32-112012527:DIBDRGS:AHWONGS:MMJYEAK

4. Save the file and exit Notepad.

The hyperserver is now licensed.

2.2.3 Editing the License File

You can use the Start > All Programs > iTivity > Hyperserver > Tridia Licensing > Edit Tridia License File option to add a new license key to a license file that you previously created.

This option is typically used to add licenses to allow the hyperserver to support additional connections.

2.2.4 Viewing License Information

You can use the Start > All Programs > iTivity > Hyperserver > Tridia Licensing > License Information option to view your current license status, including the allowed number of agent connections.

2.3 Hyperserver Windows Start Menu Options

After the hyperserver is installed, the following Window Start menu options are available.

2.3.1 Administrative Tools

Choosing Start > All Programs > iTivity > Hyperserver > Administrative Tools opens a menu with additional options.

Configure Automatic iTivity Hyperserver Start

Choose this option to set up the hyperserver to start automatically each time the system starts.

Configure Manual iTivity Hyperserver Start

Choose this option to set up the hyperserver to start on demand. You can then start the hyperserver by choosing Start > All Programs > iTivity > Hyperserver > Administrative Tools > Configure Manual Hyperserver Start.

License Snapshot to Activity Log

Choose this option to cause the hyperserver to write the current license status to the activity log. This allows you to obtain a snapshot of all hyperserver users and the number of licenses they are each using.

Refer to Section 2.12, Hyperserver Activity Log for more information on the activity log that receives this license snapshot.

Reload iTivity Hyperserver Changes

Choose this option to the reload hyperserver operating parameters without having to stop and restart the hyperserver. This allows you to change hyperserver settings without interrupting live connections.

For example, if a new license key is added to expand the number of licensed users, an administrator can use this option to load the new license data without interfering with current users.

Remove iTivity Hyperserver Configure

Choose this option to temporarily disable the hyperserver software. This option causes the hyperserver Windows services to be removed from the Services database.

To re-enable the hyperserver, choose Start > All Programs > iTivity > Hyperserver > Administrative Tools > Configure Automatic iServer Start or Start > All Programs > iTivity > Hyperserver > Administrative Tools > Configure Manual Hyperserver Start.

Rotate Hyperserver Activity Log

You can use this option to "rotate" or increment the numbering of the hyperserver activity log without stopping the hyperserver. This means that the current log file is renamed to "xxx.log.1" Any existing xxx.log.1 is renamed to xxx.log.2, and so on.

For information on the hyperserver activity log, see the iTivity Deployment Guide.

Rotate Hyperserver Error Log

You can use this option to "rotate" or increment the numbering of the hyperserver error log without stopping the hyperserver. This means that the current log file is renamed to "xxx.log.1" Any existing xxx.log.1 is renamed to xxx.log.2, and so on.

For information on the hyperserver error log, see the iTivity Deployment Guide.

Set Hyperserver Simple Password

You can use this option to change the password used by a remote user of iTivity console to connect to this hyperserver. This password applies only if Simple Password was chosen as the Authentication Method when the hyperserver was installed. If another Authentication Method was chosen, any entry in this dialog is ignored.

Enter the password twice, then click OK to reset the password.

2.3.2 Documentation

Choose Start > All Programs > iTivity > Hyperserver > Documentation > iTivity Online Help to display the iTivity online Help.

2.3.3 iTivity Licensing

Use this option to create or edit your license file for the hyperserver. See Section 2.4, Licensing the hyperserver on Windows, for instructions.

2.3.4 About iTivity Hyperserver

Choose Start > All Programs > iTivity > Hyperserver > About iTivity Hyperserver to display the About dialog containing version information.

2.3.5 Start iTivity Hyperserver

Choose Start > All Programs > iTivity > Hyperserver > Start Hyperserver to start the hyperserver software. You need to use this option only if the hyperserver is not configured to start on system startup.

2.3.6 Stop iTivity Hyperserver

You can use the Start > All Programs > iTivity > Hyperserver > Stop Hyperserver option to stop the hyperserverwhenever it is running.

Caution: All current connections to the hyperserver are immediately lost.

2.4 Hyperserver Windows System Tray Menu

When the hyperserver is started, the following icon is displayed in the Windows System tray:

Right-click on this icon to display the System Tray menu.

2.4.1 Show Active Sessions

This option displays a dialog showing active remote control sessions currently connected to the hyperserver. You can use the buttons to select and close any or all of the sessions. When NTLM authentication is used, the NTLM user name is shown for each session. The name of the hyperserver is shown in the remote host column.

2.4.2 Show Certificate Fingerprint

The hyperserver automatically generates a local default 2048-bit RSA encryption certificate the first time it runs. This unique certificate is presented to the iTivity console to ensure encryption of all data transmitted between the hyperserver and the console.

Selecting the Show Certificate Fingerprint option displays the Certificate Fingerprint.

The first time the console or agent attempts to connect to this hyperserver, the user is asked to confirm the certificate fingerprint. After the first connection, the console or agent computer retains the fingerprint in its cache for the next viewing session.

Note: On agent systems, the behavior to check the certificate fingerprint on the first connection can be configured using the varAutoAcceptAllCerts setting in the one-click HTML file. See Section 5.4.1, Global agent Settings.

iTivity also supports commercial SSL digital certificates purchased from Verisign or other Certificate Authorities. For more information on certificates, see the iTivity Deployment Guide.

2.4.3 About iTivity Hyperserver

Choose this option to display the About dialog containing version information.

2.4.4 Stop iTivity Hyperserver

You can click this option to immediately stop the hyperserver.

Caution: All current connections to the hyperserver are immediately lost.

2.5 Installing the Hyperserver on Linux

Note: For information on configuring the hyperserver after installation, see Section 2.9, Configuring the Hyperserver on Linux.

Downloading the Distribution File

1. Download the hyperserver Linux distribution from the iTivity website. The filename is linux-hyperserver.tar.

Note: Many popular Window's based ZIP file utilities do not properly extract the contents of our distribution file. Please do not attempt to use them with any of the distribution files.

2. Place the downloaded file in your home directory on the Linux server where you want to install the hyperserver.

Example: /home/username/ (where username is your actual user name)

CONTINUING YOUR INSTALLATION

1. Logon as the root user or issue the su command.

2. Change to the /tmp directory.

cd/tmp [Enter]

3. To verify the presence of the distribution file, list the directory contents of your home directory:

ls l /home/username/*.tar [Enter] where username is your actual user name

4. Extract the distribution (*.tar) file:

tar xvf /home/username/linux-hyperserver.tar

NOTE: You may install the hyperserver using RPM by issuing this command:

rpm -ivh linux-hyperserver.rpm

Several files are extracted into the /tmp folder. One of these is the install script.

5. Run the install-hyperserver script.

./install-hyperserver

6. The a variety of messages will display as the installation completes.

NOTE: Once the installation completes, the hyperserver will start automatically, and will restart each time the system is rebooted.

2.6 Configuring the Hyperserver on Linux

2.6.1 Editing the iServer.conf File

For the Linux version of hyperserver, all configuration settings are controlled by an ASCII text file called iServer.conf, which is placed in the installation directory on the Linux computer.

You can change the settings by opening the file in any text editor. The following table describes the settings in the file.

COMMON OPTIONS

Programdir

Specifies the directory in which the hyperserver is installed. This setting is automatically configured by the Installation program.

Default: /usr/lib/iTivity/iServer

dataDir

Specifies the directory where the hyperserver stores information between program invocations. This information includes encryption keys and other data used internally.

Default: /usr/lib/iTivity/iServer/itivity_data

FilePath

Specifies the license file for use by the hyperserver.

Default: FilePath=/usr/lib/iTivity/iServer/LicenseData.txt

vnchostname

vnchostdesc

The server name and Description as listed in iTivity console for this hyperserver.

The default vnchostname is the Linux machine name. The vnchostdesc can be entered during the Installation procedure.

CONNECTOR OPTIONS

randomFile

keyFile

caFile

These settings specify the filenames and location of three files used for encryption. The hyperserver automatically generates default versions of these files the first time it runs. There is no need to change these settings unless the default files in the dataDir directory are not acceptable.

Defaults:

randomFile=/usr/lib/iTivity/iServer/itivity_data/random.dat

keyFile=/usr/lib/iTivity/iServer/itivity_data/keys.pem

caFile=/usr/lib/iTivity/iServer/itivity_data/root.pem

Log File Flags

The following options control which events are written to the Syslog. A value of 1 (one) enables logging and a value of 0 (zero) disables logging.

Syslog facility and priority: iTivity.daemon

connectSysLogMask

Arrival of an encrypted connection. Default = 0.

disconnSysLogMask

Closing of an encrypted connection. Default = 0.

startSysLogMask

hyperserver startup. Default = 1.

stopSysLogMask

hyperserver shutdown. Default = 1.

proxyServiceSysLog Mask

A remote control session is forwarded via the hyperserver. Default = 0

Ports

These settings control the TCP listening ports and interface of the hyperserver.

transportPort

The port for iTivity console connections. Default = 25800

transportHost

Normally, the hyperserver listens on all interfaces (Default=0.0.0.0). However, if you have a multi-homed system, you can have the hyperserver listen on any network interface by changing the default setting.

iasServerPort

The port for agent connections. Default = 23800.

transportTimeout

serviceTimeout

These two settings control the timeout behavior of hyperserver data connections.

transportTimeout - Timeout in milliseconds set for end-to-end or host to host network connections. Keep this value high if using the Internet or other high-latency network transport (such as satellite connections).

serviceTimeout - Timeout in milliseconds for internal or local connections between hyperserver daemons.

Defaults:

transportTimeout=90000

serviceTimeout=45000

Keep-Alive Settings

These three settings control the keep-alive behavior of hyperserver data connections.

endToEndKeepAlive

Determines whether the ihyperserver sends keep alive packets. Not supported on all transports. Values are:

1 (one) - send packets

0 (zero) - no packets.

Default = 1.

iasVerifySessionFlag

In addition, the hyperserver can send application messages to guarantee the connections are viable and detect lost connections more reliably. Set this flag to 1 (enabled) to have the hyperserver verify session status when there is otherwise no network traffic. Values are 1, enabled, and 0, disabled.

Default = 1.

iasVerifySessionTimeout

If the iasVerifySessionFlag is set to 1, this value controls how often, in seconds, the verification packets are sent.

Default = 240.

disableSessionDNSLookup

Prevents DNS lookups for new connections to query the host name of the foreign system. This can be useful to improve performance in environments with slow DNS service. Values are:

1 (one) - prevent DNS lookup

0 (zero) - allow lookup

Default = 0.

cipherList

Specifies the list of cipher algorithms to be allowed for incoming connections. If you add other ciphers to the list, it is highly recommended that you keep the default setting as an option. If an iTivity console or agent system connects to the hyperserver and there is no mutually acceptable cipher algorithm, the connection will fail.

In order for a different cipher to be used, it must also be allowed by the cipherList of the console or agent system. The recommended best practice is to set the same cipherList in all iTivity systems.

Supported OpenSSL ciphers:

DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA AES256-SHA EDH-RSA-DES-CBC3-SHA:EDH-DSS-DES-CBC3-SHA DES-CBC3-SHA:DES-CBC3-MD5 DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA AES128-SHA IDEA-CBC-SHA:IDEA-CBC-MD5 RC2-CBC-MD5

DHE-DSS-RC4-SHA RC4-SHA:RC4-MD5:RC4-MD5:RC4-64-MD5 EXP1024-DHE-DSS-DES-CBC-SHA:EXP1024-DES-CBC-SHA:EXP1024-RC2-CBC-MD5 EDH-RSA-DES-CBC-SHA:EDH-DSS-DES-CBC-SHA DES-CBC-SHA:DES-CBC-MD5 EXP1024-DHE-DSS-RC4-SHA:EXP1024-RC4-SHA:EXP1024-RC4-MD5 EXP-EDH-RSA-DES-CBC-SHA:EXP-EDH-DSS-DES-CBC-SHA EXP-DES-CBC-SHA:EXP-RC2-CBC-MD5:EXP-RC2-CBC-MD5:EXP-RC4-MD5:EXP-RC4-MD5

Default: cipherList= AES128-SHA:DES-CBC3-SHA

Connector_debugMode

Enables debugging output in the connector daemons. The debugging mode of 0 (zero) disables output. As the mode number increases from 1 to 12, more and more information is written to the log file.

This option should be disabled unless instructed otherwise by iTivity Corp staff.

Default: 0 (disabled)

PROCESSOR OPTIONS

permissionGroup

Specifies the name of the user group granting permission to use the hyperserver to view and access agent systems. To grant a user access to the hyperserver, simply add the user to this group. To block a user from using the hyperserver, remove their user id from the group.

A user in this group needs to log in with a username and password when connecting to the hyperserver through iTivity console.

Default: isrvauth

logonSysLogMask

logoffSysLogMask

These flags control whether it is recorded in the syslog each time a user of iTivity console logs on and logs off of the hyperserver. Setting the flags to 1 (one) enables logging and provides an audit log of authentication. Setting the flags to 0 (zero) disables logging.

Syslog facility and priority: iTivity.authpriv

logonSysLogMask - Log iTivity console user logon (succeed or fail). Default = 1.

logoffSysLogMask - Log console user logoff (disconnect). Default = 1.

connectPort

connectHost

connectTimeout

These settings specify the TCP network interface and port on which the processor daemon listens for new hyperserver authentication connections. These connections are internal to the hyperserver and generally use localhost.

The connectTimeout value specifies the socket timeout for processor connections in milliseconds.

Caution: iTivity Corp strongly recommends that you do not change these settings.

Defaults: connectPort=7800 connectHost=127.0.0.1 connectTimeout=45000

Processor_debugMode

Enables debugging output in the processor daemon. The default setting of 0 (zero) disables output. As the number increases from 1 to 12, more and more information is written to the log file. This option should be disabled unless instructed otherwise by iTivity Corp staff.

Default: 0 (disabled)

Hyperserver OPTIONS

proxyViewSysLogMask

Controls whether hyperserver requests to view an agent are written to the syslog. A value of 1 (one) enables logging and a value of 0 (zero) disables logging.

Syslog facility and priority: iTivity.daemon

Default: 1

hostSessionTimeout

remoteClientTimeout

These values specify how long in milliseconds the IASDB process should wait for responses from iTivity console (remoteClientTimeout) and agents (hostSessionTimeout).

The settings determine how long an unresponsive console or agent connection will be allowed before being removed from the tracking database in the IASDB.

Caution: iTivity Corp recommends leaving these values at the default setting unless instructed otherwise by iTivity Corp staff.

Defaults:

hostSessionTimeout=30000

remoteClientTimeout=90000

clientPort

clientHost

Controls the TCP network interface and port on which the IASDB daemon listens for internal console connections from the processor_ia daemon.

Caution: iTivity Corp strongly recommends that you do not change these settings.

Defaults: clientPort=6900 clientHost=127.0.0.1

IASDB_debugMode

Enables debugging output in the IASDB daemon. The default debugging mode of 0 (zero) disables output. As the mode number increases from 1 to 12, more and more information is written to the log file.

This option should be disabled unless instructed otherwise by iTivity Corp staff.

Default: 0 (disabled)

sessionRefresh

The maximum length of time (in seconds) the hyperserver will wait before checking that existing connections are still valid. Note that new connections from agent systems are handled immediately. This setting controls the time interval of cleanup operations on existing connections that are lost due to network outages.

Default: 20

authUsername=

authPassword=

Generally, the reverse connection established from an agent system to the hyperserver is unauthenticated. This initial connection is generally required to traverse a local firewall or simply to notify the hyperserver of the agent's availability.

Since the initial reverse connection only provides access to the standard remote control daemon, authentication of the remote hyperserver is normally not required. However, if the agent system is configured to require authentication from the ihyperserver, the username and password needs to be stored in these settings.

Default: (blank)

2.6.2 Changing a Configuration

You can change configuration options without stopping and restarting the hyperserver software. The options can be changed without losing current connections.

To reload the settings of a running hyperserver, run the following script:

/usr/lib/iTivity/iServer/iServer_config_reload

2.6.3 Running Multiple Hyperservers on One Linux Server

With the Linux version, you can run multiple instances of hyperserver on a single Linux machine. This allows you to configure different groups of agent computers (for example, from different departments or organizations) to connect to different hyperservers. By allowing support users to log in to only certain hyperservers, you can control who can connect to the different groups of agents.

When running multiple copies of hyperserver on a single machine, each hyperserver has its own iServer.conf file. Within each iServer.conf file, you need to configure the following settings.

COMMON OPTIONS

dataDir

Each hyperserver needs its own unique dataDir

FilePath

This variable points to the unique License File for each hyperserver.

vnchostname

vnchostdesc

The name and description should be unique for each hyperserver to make them distinguishable in iTivity console.

CONNECTOR OPTIONS

transportPort

iasServerPort

The listening ports for iTivity console and agent connections must be unique for each hyperserver. For example, you might make the following settings if running two hyperservers on one Linux server:

hyperserver#1 (default ports) transportPort=25800 iasServerPort=23800

hyperserver #2 transportPort=25802 iasServerPort=23802

PROCESSOR OPTIONS

permissionGroup

Each hyperserver is typically given its own user group.

connectPort

Set to a unique port number for each hyperserver.

commandSvcPort

Specifies the internal port number used by the connector daemons to find the listening port of the processor daemon. This setting is only for use with multiple hyperserver configurations. It should not be used when only one hyperserver is running on the system.

When this setting is used, it should always match the connectPort setting of the processor.

HYPERSERVER OPTIONS

clientPort

Set to a unique port number for each hyperserver.

2.7 Licensing the Hyperserver on Linux

After installing, you must license the hyperserver to make it operable.

As explained in the Welcome to iTivity section of this guide, your iTivity license allows a given number of concurrent connections between consoles and agents through the hyperserver. The license you purchase determines the number of concurrent connections that your hyperserver allows.

Note: It is also possible to license agent software separately. When an agent is licensed separately, its connection to an hyperserver does not count as one of the connections allowed by the hyperserver license. Contact iTivity Corp for more information on this option.

2.7.1 Obtaining the License Key

When you purchase your license, iTivity Corp provides a license key. The license key is a series of numbers with hyphens:

Example: 533-0025-32-112012527

When you install the hyperserver, the install process generates an install code. You can display this install code by running the License Status command (see Section 2.11.2, below).

To activate your hyperserver, you use the install code to obtain an activation key. The activation key is generated based on the install code and is unique to your hyperserver system.

To obtain your activation key:

1. After installing the hyperserver, type the license_status command to display your License information. Note the install code.

2. Contact iTivity Corp with the install code to obtain your activation key, or visit the iTivity Support Site at https://support.itivity.net/ and choose the Licensing option.

After obtaining both the license key and activation key, you can proceed with licensing the hyperserver.

2.7.2 Entering the License Information

You enter the License Key in the LicenseData.txt file. This file is automatically created in the hyperserver installation directory when you install.

You can edit the LicenseData.txt file with any text editor. Follow the instructions in the comment area of the file to enter your License Key and Activation Key.

Example: 533-0025-32-112012527: DIBDRGS:AHWONGS:MMJYEAK

2.8 Linux Hyperserver Components and Commands

2.8.1 Component Files and Subfolders

The following table lists and describes the files and subfolders that make up an hyperserver implementation.

Folder or File

Description

bin

Directory holding binaries and programs.

BUILD

Link to BUILD_#

BUILD_1

Build# of this release

connector_ia

Starter script to one of the hyperserver programs. No user interaction is required.

docs

HTML documentation files.

init_iserver_daemons

Used to start hyperserver at boot time.

install_daemon

Hyperserver installation script. Used to install the hyperserver to run at boot time.

iServer

Starts one of the hyperserver programs.

iServer_downall

Shuts down all runninghyperserver programs.

Caution: The stop_iServer command is the preferred method of stopping the hyperserver. Run iServer_downall only if stop_iServer fails. You must be the root user to issue this command.

iServer_perms

Holds inventory and permissions settings to all hyperserver files.

iServer_version

See Section 2.11.2 Hyperserver Commands.

itivity_data

Directory that holds all of the data files used by the hyperserver. The directory can be configured via the iServer.conf file.

iTivitySupportModule

Directory containing all of the files for one-click installation of the Unattended and Attended agents. Refer to Section 5.3, Installing the Support Module, for more information.

iTivityUserGuide.pdf

PDF version of this User Guide.

LICENSE_30DAY.txt

Text file containing the 30-day license agreement.

LicenseData.txt

Text file used to enter the license keys. See Section2.10, Licensing the hyperserver on Linux.

LICENSE_FULL.txt

Text file containing the full license agreement.

license_status

See Section 2.11.2 Hyperserver Commands.

licmgr

License Manager program. No user interaction is required.

PLATFORM

Description of the platform supported by this release of the hyperserver.

processor_ia

One of the hyperserver programs.

rc_iserver_daemon

Script used by the startup programs under some operating systems when the hyperserver is to be started at boot time. Normally does not require user intervention.

README

Text file containing updated release information.

remove-iServer

Program used to remove the hyperserver from the system.

sample_iServer.conf

Copy of the original hyperserver configuration file. System administrators can copy this file and use it to create more than one instance of the hyperserver to run on their systems.

start_iServer

See Section 2.11.2 Hyperserver Commands.

stop_iServer

See Section 2.11.2 Hyperserver Commands.

VERSION

ASCII file containing the version number of the installed product.

2.8.2 Hyperserver Commands

Administrators can use the programs explained in this section to display information about the hyperserver and control its operation.

iServer_version

This program displays the exact version of the hyperserver currently in use, as shown in the following example.

license_status

This program displays the current license information for the hyperserver, including the Installation Code and the number of allowed connections.

start_iServer

You can use this command to start the hyperserver. You must be the root user to issue this command.

stop_iServer

You can use this command to stop thehyperserver. You must be the root user to issue this command.

2.9 Hyperserver Activity Log

On both Windows and Linux systems, the hyperserver maintains an audit log of activity. The central audit log records information each time an agent system connects to the hyperserver or disconnects.

The information includes the authenticated username at the hyperserver as well as the username (if any) used to authenticate to the agent system.

The activity log is a CSV text file stored at one of the following locations:

Hyperserver OS

Central Audit Log Location

Windows

/Program Files/iTivity/itivity_data/activity.log

Linux

/usr/lib/iTivity/iServer/itivity_data/activity.log

The following listing shows an example section of the activity log.

101,,agent_connect,2005-05-06 15:42:17,-1,-1,,,209.168.166.227,209.168.166.227,,,,,,,,,, 102,,agent_disconnect,2005-05-06 15:42:25,-1,-1,,,209.168.166.227,209.168.166.227,,,,,,,,,, 101,,agent_connect,2005-05-06 15:42:41,-1,-1,,,209.168.166.227,209.168.166.227,,,,,,,,,, 102,,agent_disconnect,2005-05-06 15:43:03,-1,-1,,,209.168.166.227,209.168.166.227,,,,,,,,,,

More Information: For more information on the activity log, see the iTivity Deployment Guide, Section 4, Troubleshooting.

2.10 iTivity Product Support

Product support is available from iTivity by web site or email:

Copyright © 2004 - 2019, iTivity Corporation Copyright and License Information