Changes

{{TOC right}}__NOEDITSECTION__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 networked 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.

{| class==Standalone=="wikitable"|+ Comparison of Stand-alone and Client/server Configuration Options ! Configuration! Advantages! Disadvantages|-| <b>Stand-alone</b>|* 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|-| <b>Client/server</b>|* Multiple concurrent data access* Redundancy|* Complicated to set up and maintain* Local Area Network infrastructure required* Multiple computers required|-|}

In a stand-alone systemclient/server configuration, one computer acts as a server and many other computers can connect to it simultaneously over a network, both enabling multiple people to access the IMSMA^NG client and server are installed on same data at the same computertime. The stand-alone configuration is the simpler type of A client/server installation: it requires no additional at least two computers and a network equipment or infrastructure and is easy to maintainconnecting the computers together. Using a client/server installation, a mine action programme can have multiple data entry clerks entering data at the same time.

==[[Image:Understanding Configuration Options - Networked Configuration=Config.png|center|300px|''Client/server Config'']]<div align="center">''Client/server configuration''</div>

In {{Note| Be aware of the following when running IMSMA in a networked client-/server configuration, one computer acts as a installation:* The server and many other computers can 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 it simultaneously over a network, enabling multiple people the server. * Maps only need to access be installed on the same data at server. * Data entered into the same time. A networked installation requires at least two computers and a network infrastructure connecting server or clients will be automatically rendered to all clients (as well as the computers togetherserver). Using a networked installationHowever, geospatial information (points, a mine action programme can have multiple data entry clerks entering data at 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 same timeserver, you must log out of IMSMA and then log back in.* Fonts will need to be installed on both the server and client(s)}}

IMSMANG is designed to support information management in a decentralized context involving many users and groups at various sites. These users can include implementing partners, mine action operators and regional or decentralized mine action authorities. Decentralizing information management within IMSMANG is easy and allows information managers to expand * the scope and impact of information on mine action activities. While IMSMANG supports nearly any conceivable patterns for decentralized information exchange including multilateral exchange, peer-to-peer exchange and one- and two-direction exchange, IMSMA^NG server* the most prevalent pattern is that of a central mine action authority (CMA) and subordinate regional mine action authorities (RMAs). Much of the discussion of maintaining a decentralized IMSMANG system refers to this typical example; however, many points apply to other information exchange patterns as well.IMSMA^NG client

The centralized pattern is characterized by one or more non-overlapping regional sites or authorities that conduct data entry and data quality control for their region. Regional sites also typically perform some regional data analysis designed to support regional operations management and planning. By contrast, figure below shows the parts of the central authority manages software; the overall data set for following sections then explain the entire country, collecting all regional information in order to perform national planning and produce national statisticsfunctions that each part performs.

Establishing IMSMANG with the correct configuration in this complicated context of multiple users and asynchronous data exchange is important to trouble|[[Image:Understanding Configuration Options-free operations and high-quality information management. The first step in ensuring the correct configuration is to document the information management flows.In the following example, mine action field reports are entered at each regional site for the ongoing operations in that region. Field reports are reconciled, linked and approved according to the regional operations needs. Using the export functionality, the regional sites export data on a regular basis (for example, monthly) and send it to the central authority. (Regional information managers can use the search functionality to export the field reports entered since the last data exchange.) The central authority then imports the maXML files from each site and resolves any issues with the imports as well as performs quality control. When the import is complete, the central authority compiles a set of national statistics and then distributes a complete dataset (in the form of a database backup) to each of the regional sites. The regional sites restore the dataset and then import any data entered since the last export was sent to the central authority. When the backup is restored, regular data entry and exchange can continue, based on a common datasetClient Server Architecture.png|center|600px|''Client/server architecture'']]

===Ensuring Correct Roles The IMSMA^NG server stores data and Permissions are Assigned===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.

Establishing correct roles and permissions is a key factor in managing and maintaining data exchange within IMSMANG. Using the permissions structure, {{warning|While the information manager can carefully control access database contains many relational database constraints designed to key functions that affect preserve data exchange including field report template creationintegrity, CDF creation, field report approvals and auxiliary data creation. When permissions are correctly established and roles and user accounts created, information managers can freely distribute the IMSMANG dataset to regional partners knowing that key all updates of data controls are in place.Using the example of the central authority and regional sites, the following principles for user account creation and permissions should be considered: Central Authority: Ensure central authority has exclusive control over user accounts and roles, field report templates, handled through the Data Inventory Manager and auxiliary databusiness layer rather than with direct SQL updates in order to maintain integrity. Regional Sites: Ensure that regional sites have Failure to do so will likely cause data entry, approval and import/export permissions. Remove permissions for user accounts and roles and auxiliary data.By establishing a set of limited permissions for the regional sites, information managers can prevent the accidental corruption or intentional creation of new data elements not available at the central authority that could affect the ability of the central authority to import field reports and cause the dataset to become fractured.loss}}

===Creating New Auxiliary Data at The business layer is where rules are implemented to ensure data quality and consistency. The business layer takes data from the Central Authority Level===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.

===Sending Backups The IMSMA^NG client is the interface through which users can connect to Reset 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 Common Dataset===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.

The easiest way to ensure that each site JasperSoft’s iReport tool is working from a common dataset is to distribute a full backup of the IMSMANG dataset to built into each site on a regular basis. This can occur weekly, monthly or quarterly, but the key is IMSMA^NG client and allows users to distribute an ―official‖ dataset to each site regularly to ensure that auxiliary access data is up to date and that any changes made to other parts of from the database via the dataset are distributedbusiness layer. In this wayWith iReport, organisations users can maintain a common set of national statistics and the dataset reflects the decisions made by the central authority to resolve errors or issues in importing and exchanging field generate reports.It is important to understandcontaining tabular data, however, that the restoration subreports and cross tabs as well as various types of a backup file overwrites the data at the regional site including any locally created searches charts and reportsgraphs. So, the recipient sites should consider the following recommendations: Make a complete backup prior to restoring the central authority’s backup. Export all field These reports can easily be localized into any language that have been entered since the last exchange with the central authority before restoring a backupIMSMA^NG supports. Restore only Additional reporting options include direct connections to the IMSMANG database and GIS IMSMA^NG databasevia ODBC. This preserves local customisations of peripheral elements functionality supports tools such as field report templates Crystal Reports, Microsoft® Access®, Microsoft Excel® and iReport templates, which can be reimported into IMSMANG. Request that any searches or other nonvarious open-exportable elements that are important for regional site use be created in the central authority’s dataset prior to distribution so they do not need to be recreated regionally each time a new backup is distributedsource reporting tools.

===Collecting Regular FeedbackMemory settings===__NOEDITSECTION__

In any information exchange activityBy reserving memory for {{IMSMANG}}, it less memory may be used by other applications. It also depends on how much memory the computer has if is important possible to have regular sessions or meetings to collect feedback and discuss issues or improvements reserve more memory for {{IMSMANG}}. [[Image:memory_settings.png|500px]] If you would like to reserve more memory for the information exchange IMSMA server '''process''', edit row 3 in ''C:\IMSMAng\trayLauncher\TrayLauncher. One recommendation is to establish a feedback forum where organisations can address data quality issues and make adjustments properties''.  If you would like to reserve more memory for the information exchange IMSMA client '''process''', edit row 12 in ''C:\IMSMAng\trayLauncher\TrayLauncher. Topics properties''. Start with increasing it to address in such a forum include:1024 and then evaluate.  {||- valign="top"| {| class="wikitable" ! Value !! Meaning |- align="right"| 512 || 0.5 GB |- align="right"| 1024 || 1 GB |- align="right"| 2048 || 2 GB |- align="right"| 3072 || 3 GB |- align="right"| 4096 || 4 GB |- align="right" frequency of data exchange|} standardization of reports The values should be increased step-by-step and searches included in the central datasetevaluated after each change. permissions and role changes creation or modification of auxiliary data{{Note |  form template changes* Since IMSMA NG is a 32-bit application there is no effect by reserving more than total 4 GB. By collecting feedback on these issues* On the physical server in a client/server configuration there is need to start the client, information managers can help ensure that decentralized information exchange works as expected take backup and restore so do not set up a quality assurance mechanism the client process memory to prevent data quality issues from affecting the programme’s information managementless than 512.}} {{NavBox Information Management}}[[Category:NAA]]