JMap application users can generate certain data that will be stored in the JMap Server environment.

This can include various types of data, including user preferences (choice of units, print settings, etc.), map contexts (JMap Pro, JMap Web and JMap NG) and customized print layouts.

Map context data is stored in JSON format in the JMAP_CONTEXTS table of the System database.

Non-context data is stored in separate folders for each user. The parent folder of these user folders is

JMAP_HOME\workspaces<username>

Note that this folder can have a different location if you indicate a different folder in the server.workspaces.path line of the jmapserver.properties file and manually copy the files and subfolders.

In some cases, the administrator may have to copy certain files when a migration occurs or when these files need to be shared with other users. The following sections describe each of these situations in detail.

Contexts

Map contexts are comprised of all the parameters that allow a JMap Pro, JMap Web or JMap NG user to recreate a geographic map. Contexts can be used to save maps and even share them between users. Existing contexts can be recalled easily to recreate a map environment. All layer parameters, annotations, thematics, selections, etc. are part of the context and are recreated when the context is opened.

Personal Layers

The Personal Layers section provides more information on managing personal layers and how to make them public. The data from personal layers is not stored in the workspaces folder; instead, it is saved directly in JMap Server’s System database (one table per personal layer).

JMap Spatial Tables

As with personal layers, the data from editable layers of JMap projects is stored directly in JMap Server’s System database, in tables that are called JMap Spatial tables.

Print Layouts

The users of JMap Pro applications can create their own print layouts. The files are stored in the folder

JMAP_HOME\workspaces<username>\printLayouts

The print layouts created by users can be made public. To do this, you must copy the files in the following directory:

JMAP_HOME\workspaces\public\printLayouts.

This section contains tools that allow you to import and export JMap Server configuration, user data as well as make backup copies of JMap Server.

Exporting and importing the JMap configuration

Your JMap Server configuration (spatial data sources, databases, projects, layers, etc.) is stored on a disk in binary format. This configuration is only accessible by JMap Server and is only compatible with your current version (main version, e.g. Lima).

Using the export tool, a text version of this configuration can be produced. This exported configuration can then be imported back into JMap Server, with the same settings or different ones. The configuration can even be exported to a newer version.

Here are a few examples where exporting and importing your configuration can be useful:

• You installed a new version of JMap with major changes and you want to reuse your existing configuration. You can export the configuration from your older JMap version and then import it in the newer version.

• You manage many instances of JMap Server and you need to move a project from one instance to another. You can do a partial export to move only the project you need and then import it in the other instance.

• You need to replicate your development environment to the production environment. You can do a full export from your development server and then import it in the production server.

To access export and import tools, select Import / Export in the Tools section.

Exporting

When exporting a configuration, you must choose whether you want to export the complete configuration or some specific resources (partial exportation).

If you choose to export specific resources, you must select if you want to export databases, spatial data sources, projects, style templates or metadata templates.

There is a dependency relationship between these different resources: projects depend on spatial data sources and style templates while spatial data sources may depend on databases. Consequently, if you export a project, then spatial data sources, style templates, and possibly databases will also be exported.

The exportation process creates up to 4 files: the .properties file is the main exportation file and contains the configuration information. All files are necessary for the importation. You can determine the destination directory and file name.

Importing

When importing a configuration, you have the choice to import a complete configuration (complete importation) or only a portion of it (partial importation). You can only do a complete importation if the exportation files contain a complete exportation.

When a full importation is completed, you will automatically be sent back to the JMap Admin login page.

When doing a partial importation, there may be situations where the imported resources already exist (identical names). In these cases, you have to tell JMap Admin which action to take: replace the existing resource or create a new one with a different name. The file type data sources that you import are not ready to use and must be updated after the importation.

Exporting and importing JMap user data

If you change JMap Server instances and you wish to keep all existing user data, you must export it from the previous server and import it into the new server.

The configuration file for the export and import of user data is a .properties file.

Exporting

When you export user data, you must decide whether to export all data, only the editable layers stored in JMap (including personal layers) or only the workspaces (including contexts, user preferences, etc.).

Importing

When you import user data, there may be situations where imported resources already existed (identical names). In these cases, you must indicate which action JMap Admin must take: replace the existing resource or create a new one under a different name.

.mapping File

During exports and imports of JMap configurations the project IDs change and this has a considerable impact on user data such as contexts which are associated with a particular project.

To resolve the problem you can create a .mapping file that maps the old and new IDs of each project. The following text details the procedure to follow.

From the old JMap Server:

1. Export the JMap Server configuration.

2. Export user data configuration.

On the new JMap Server:

1. Import the JMap Server configuration.

2. Take note of the ID of each project on the old server.

3. Take note of the ID of each project on the new server.

4. Create one (1) .mapping file with the mapping for each project between the old and new IDs.
5. Import the user data configuration by specifying the .mapping file created in the previous step.

Backups

If the JMap Server System database was moved to another RDBMS, it must be included in the backup strategy. It contains very sensitive information like personal layers data.

The simpler backup strategy is to make copies of the JMap directory and all sub-directories.

If you wish to make smaller backups, you can make copies of the specific directories listed below, which contain important information.

JMap Admin provides a generic SQL console that can be used to view database structures, execute SQL queries, inspect the content of tables, test for query execution speed, etc.

When performing an SQL query, the query execution is subject to security permissions granted to the user connected to the database. See Creating Databases section for more information about specifying the user for database connections.

Query results are displayed in a new window. The results of the INSERT, UPDATE, and DELETE requests are grouped in the same tab. The results of SELECT type queries appear in separate tabs.

This section presents tools that allow you to perform different tasks in JMap Server.

As the administrator, you can send messages to JMap users from JMap Admin.

Users who already have an active session will see the messages immediately. The other users will see the message the next time they log on.

Messages can be used to inform users of service interruptions, for example.

Messages will be displayed each time a user starts a new session, during the validity period of the message.

Sending messages

To create a new message to be sent to all users, press Create from the Messaging section in Tools.

Deleting messages

To delete a message before it expires, select it in the table and press Delete.

This section contains a table that shows all the scheduled tasks of JMap Server, either updates of spatial data sources or tasks executed for JMap extensions that require it.

The table shows each task with its details. Click on the name of a task to edit it.

Select one or more tasks to delete them.

This section presents debugging tools available in JMap Admin. These tools help identify JMap Server operating and performance problems.

Layer configuration troubleshooting

This section allows JMap Server administrators to identify the source of an application performance problems caused by layer configuration.

The section displays a table of vector layers on a project. To populate the table, select the project and press Load to display the project layers. By default, layers in the table are sorted in descending order based on the number of map elements in the spatial data source.

You can display the configuration interface of a layer by clicking on its name.

For each layer the table displays the following data:

You can select layers in the table and bulk edit the Published, Visible, Selectable and Request mode settings.