Understanding Configuration Options

To determine the initial configuration of the IMSMA^NG system, it is important to understand the two ways in which IMSMA^NG can be set up and the basic architecture of the system. IMSMA^NG is a client/server software application designed to run in stand-alone or client/server mode. In a stand-alone system, both the IMSMA^NG client and server are installed on the same computer. The stand-alone configuration is the simpler type of installation: it requires no additional network equipment or infrastructure and is easy to maintain.

Comparison of Stand-alone and Client/server Configuration Options

Configuration	Advantages	Disadvantages
Stand-alone	Simple to set up and maintain Limited IT knowledge required Can be upgraded to a client/server configuration later	One-at-a-time data access
Client/server	Multiple concurrent data access Redundancy	Complicated to set up and maintain Local Area Network infrastructure required Multiple computers required

In a client/server configuration, one computer acts as a server and many other computers can connect to it simultaneously over a network, enabling multiple people to access the same data at the same time. A client/server installation requires at least two computers and a network infrastructure connecting the computers together. Using a client/server installation, a mine action programme can have multiple data entry clerks entering data at the same time.

Client/server configuration

Be aware of the following when running IMSMA in a client/server installation: The server and client(s) must be running the exact same version of IMSMA. The gisServer.properties file on the server must be configured. The client(s) must be configured to connect to the server. Maps only need to be installed on the server. Data entered into the server or clients will be automatically rendered to all clients (as well as the server). However, geospatial information (points, polygons) will NOT be immediately rendered to all clients. To either post your geospatial updates to the server (thus making them available to other clients) or to receive updates from the server, you must log out of IMSMA and then log back in. Fonts will need to be installed on both the server and client(s)

Contents

Client/server Architecture

Whether a programme uses a stand-alone installation or a client/server installation, the IMSMA^NG software has two main components:

• the IMSMA^NG server
• the IMSMA^NG client

The figure below shows the parts of the software; the following sections then explain the functions that each part performs.

Server

The IMSMA^NG server stores data and manages much of the data processing. The server has two main parts, the datastore and the business layer. The datastore is where data is stored for retrieval by the IMSMA^NG client. IMSMA^NG uses a PostgreSQL relational database to store data on the server. Additionally, IMSMA^NG stores other data including attachments and some configuration files on the server in file format. The PostgreSQL database is accessible via a variety of database access tools designed for browsing relational databases.

While the database contains many relational database constraints designed to preserve data integrity, all updates of data should be handled through the business layer rather than with direct SQL updates in order to maintain integrity. Failure to do so will likely cause data corruption or loss

The business layer is where rules are implemented to ensure data quality and consistency. The business layer takes data from the datastore and transforms it for display in the IMSMA^NG client. All data interaction between the client and server database is handled through the business layer, which allows for multiple clients to be connected to the database while preserving data integrity in cases of multiple requests. This includes access from the IMSMA^NG client and from the reporting tool.

Client

The IMSMA^NG client is the interface through which users can connect to the server and browse the system, enter data and generate outputs. The client includes an integrated GIS component and reporting tools. Based on ESRI’s ArcGIS Engine, the GIS component performs all geospatial calculations including distance/bearing calculation, coordinate conversion and reprojection. The GIS component also allows each client to load and manage its own maps and geographic data which the client receives from the IMSMA^NG server. As a result, each client receives and locally stores a complete copy of geographic data from the IMSMA^NG server when it is connected to the server. This synchronized data is stored in a client ―sandbox‖ separate from the server and can always be updated by connecting to the server.

JasperSoft’s iReport tool is built into each IMSMA^NG client and allows users to access data from the database via the business layer. With iReport, users can generate reports containing tabular data, subreports and cross tabs as well as various types of charts and graphs. These reports can easily be localized into any language that IMSMA^NG supports. Additional reporting options include direct connections to the IMSMA^NG database via ODBC. This functionality supports tools such as Crystal Reports, Microsoft® Access®, Microsoft Excel® and various open-source reporting tools.

Memory settings

By reserving memory for IMSMA^NG, less memory may be used by other applications. It also depends on how much memory the computer has if is possible to reserve more memory for IMSMA^NG.

If you would like to reserve more memory for the IMSMA server process, edit row 3 in C:\IMSMAng\trayLauncher\TrayLauncher.properties.

If you would like to reserve more memory for the IMSMA client process, edit row 12 in C:\IMSMAng\trayLauncher\TrayLauncher.properties. Start with increasing it to 1024 and then evaluate.

Value Meaning 512 0.5 GB 1024 1 GB 2048 2 GB 3072 3 GB 4096 4 GB The values should be increased step-by-step and evaluated after each change. Since IMSMA NG is a 32-bit application there is no effect by reserving more than total 4 GB. On the physical server in a client/server configuration there is need to start the client, take backup and restore so do not set the client process memory to less than 512.