Multi-User Configuration

MetriQ allows for a number of different configurations, and the type you choose will depend on your organization's internal structure, size and preferences. Each installation type has its own advantages (see also Installing MetriQ, for information about administrator rights and using MetriQ).

Standalone: MetriQ can be installed as a standalone software package. In this arrangement, the MetriQ installation program installs both the MetriQ Timing Engine and the Database Server onto the same computer. MetriQ is then able to connect to the database (default IBMetriQ.fdb or IBMetriQ.gdb). In the standalone installation, no data can be shared with other users except by exporting data through reports (see also Reports).

Client/Server: For the Client/Server installation there are in effect three different installs types:

1. The MetriQ Timing Engine is installed onto the client computer.
2. The database client software (to allow MetriQ to communicate with the database server) is installed onto the client computer.
3. The database server (Firebird - Recommended or Interbase) software is installed onto a different networked computer which is nominated as the server.

The client machine is then configured to communicate with the remote database server with the aid of the following settings:

1. The name or dotted IP address of the database server.
2. The location of the .fdb/.gdb database file stored on the database server. Note: This must not be a shared directory!

Terminal Server: MetriQ can also be configured to run on in terminal server, such as Citrix and Windows 2003 Server. When installing to run with terminal server, it is important to make sure that you have the Terminal Sever version of MetriQ.

Connection types: MetriQ facilitates a whole range of connection possibilities - from clustered standalone machines to a fully centralized network. Each connection type has its own advantages.

e.g. consider:

Figure 1. One to Many

In the example above, computers SA1, SA2 and SA3 each have their own MetriQ timing engine and database server software installed as if they were standalone. Billing has only the MetriQ timing engine and a client database installation. Such a configuration allows Billing to connect to computers SA1, SA2 and SA3 in turn to obtain their timing data.

Figure 2. Grouped

Extending the connection model in Figure 1, Figure 2 shows how computer SA3 is itself acting as a database server for computers C1 and C2. Again billing has access to these computers through the database on SA3.

See also MetriQ Applet, Database Security, Connection Issues,Installing MetriQ, Firewalls, System Requirements, Troubleshooting, Multi-User Environment

Next: License Agreement

©Copyright 2004-2007 MetriQ Limited All Rights Reserved. MetriQ Software is Patent Pending

site map