Introduction

This document explains the client-server architecture on which Metrix is based. It's intended for those who want to conceptually understand the components that make up Metrix. Understanding the Metrix architecture can help to diagnose common installation problems.

Metrix is a desktop-based application; it's not a web-based solution. See Connecting to Metrix Remotely from Different Locations for a work around to get Metrix to work on the Web. Please read the "Cautions" section.

Understanding Key Terms

The key to understanding Metrix's structure lies in knowing some basic concepts and terminology.

Client
A client is any application that sends requests to and receives responses from another program. For example, a Microsoft Outlook client is used to retrieve messages from an e-mail server. So, in the context of Metrix, individual users use the "client" program to connect to the shared database on the server (see below).

Server
A server is the application that receives the requests, processes the request and responds to the client. It is designed to be accessible by multiple users. For example, an email server processes requests and sends messages to an Outlook client. In the context of Metrix, the server hosts the database that stores all of your organization's Metrix data and certain customizations you may make to Metrix.

SQL Server and Microsoft Desktop Engine (MSDE)
SQL Server is a relational database management system (RDBMS) produced by Microsoft. You can use it to manage data in Metrix like deleting users, backing up the database, etc. MSDE, also known as "SQL Server 2000 Desktop Edition," is the free version of SQL Server. It is based on command line operation; no graphical user interface is provided.

Peer to Peer (P2P) network
Unlike a traditional centralized server network, a P2P network doesn't have a central server. It consists of a series of similar computers linked to each other and sharing resources. Smaller organizations use peer-to-peer networks when they have not purchased a more powerful, centralized server.

Back To Top

Installers and Installation Files

There are four Metrix installers. In most cases, you will need only two of them.

Client installer
The client installer installs and configures the Metrix Client (Metrix.adp) .

Client upgrader
The client upgrader is intended for organizations already using Metrix. It updates your version of the Metrix Client to the latest version. In doing so, it maintains any custom forms and reports you have made.

Server installer
The server installer installs and configures the database, as well as two server files (reportsql.adp and interactsql.adp, ) which contain certain customizations you may make to Metrix. The server installer can also install MSDE (see above) if you need it.

Server upgrader
The server upgrader is intended for organizations already using Metrix. It updates your database and copies any customizations you have made to the upgraded server files.

Back To Top

Installation and Configuration

When the Metrix Server is installed, the server files, interactsql.adp and reportsql.adp, are installed and the database is created. Connections are made from the server files to the database.

When the Metrix Client is installed, Metrix.adp is installed and configured to connect to the database and to have references to the server files, interactsql.adp and reportsql.adp.

After the Metrix Server (which consists of the database and the server files) is installed on a computer (known as the Metrix server), the server files will need to be shared with other users on your network. See http://support.microsoft.com/kb/304040 for more information about sharing Files in Windows.

The Metrix Client will be installed on users' computers. The configuration that happens upon installation allows the client, server files, and the database to exchange information.

The following image will help you to conceptualize the relationships among the components:

Figure: Conceptual Metrix installation setup

Back To Top

Alternative Setups

The terms client and server are also used in defining components of a computer network. A client is any computer that sends requests to and receives responses from a server. A server, in this case, is a computer dedicated solely to handle requests from multiple clients and run multiple applications for a large audience. Metrix can be deployed in other environments besides this traditional client-server setup.

For instance, your organization may have only one computer, or you may just want to try out Metrix for evaluation purposes. In these cases, that computer will act as both the Metrix server and the Metrix client. Or your organization may have multiple computers, but no servers, i.e., computers running a server operating system like Windows Server 2003. In this case, you can use Metrix in your "peer-to-peer" network. (See below for details on these alternative setups.)

Back To Top

When One Computer Functions as the Client and Server

For evaluation purposes, users may want to install both the server and client files on one computer. All the files, Metrix.adp, reportsql.adp, interactsql.adp, and the Metrix database are installed, configured, and connected on one machine during installation.

Back To Top

Metrix on a Peer-to-Peer (P2P) Network

Users can install Metrix in a P2P network, where one computer will act as the server and the others will act as the clients. Make sure that the folder in which the two library server files reside, interactsql.adp and reportsql.adp, is a shared folder that other users can access. Part of the installation process for the client file, Metrix.adp, consists of locating these files to set references. See http://support.microsoft.com/kb/304040 for details about sharing files.

Users on the other computers will need to install the client file.

Back To Top

Contacting Us

If you have any questions, comments, or suggestions please contact the Metrix development team at metrix@fcny.org or call the Metrix hotline at 212-590-9400.

Back To Top