JMap Server Settings
<< Click to Display Table of Contents >> Navigation: JMap Server Management > JMap Server Settings |
These parameters have an impact on the behaviour and performances of a JMap Server system. Press Save to save all modifications. Click on to reread parameters from configuration files if they have changed. The configuration files are located in JMAP_HOME/conf.
General |
|
JMap Server name |
You can give a name to this JMap Server instance. This name will be displayed in the authentication screen and in the JMap Admin header. |
Default language |
You can select the default language that will be selected automatically when creating new projects. |
Available languages |
You can select the available languages that will be automatically selected when creating new projects. |
Ports |
|
Server port |
TCP/IP port used by JMap Server for connections with JMap Pro and other JMap Server instances. |
Web server port |
TCP/IP port that JMap Server embedded web server listens to for HTTP requests. Used for JMap Admin and for local application deployments. |
Web server port (https) |
TCP/IP port that JMap Server embedded web server listens to for HTTPS requests. |
Network |
|
Preferred external service address |
The proxy address used to deploy the applications. When configuring a new deployment, you can change the local address to this external address. |
Preferred JMap Server address |
The local address of JMap Server used to deploy the applications. When configuring a new deployment, you can change the external address to this local address. |
Server port |
TCP/IP port used by JMap Server for connections with JMap Pro and other instances of JMap Server. |
Web server port |
TCP/IP port used by the integrated JMap Server web server for HTTP requests. Used for JMap Admin and local application deployments. |
Web server port (https) |
TCP/IP port used by the integrated JMap Server web server for HTTPS requests. |
Caching |
|
Memory size |
Size of memory cache. Holds previously loaded vector data tiles to minimize data source queries. This helps improve JMap Server performances. Cache statistics can be viewed in JMap Server Status section. |
Disk size |
Size of disk cache. Its operation is similar to the memory cache. Unlimited size is recommended. |
Imaging size |
Size of memory cache dedicated to imaging operations. This cache is used by JMap Server when processing image files (raster data sources that read image files). It dramatically helps improve JMap Server performances when working with high volume images. |
HTTPS |
|
Redirect |
Automatically redirects JMap Admin users to a secure connection (https). This option is only available if there is a security certificate. For more information, refer to Using HTTPS with JMap. |
HTTP Proxy |
|
Host |
Host name or address of HTTP proxy server. Is used if JMap Server must go through an HTTP proxy to access systems outside of the local network. |
Port |
TCP/IP port used to connect to the HTTP proxy server. |
Username |
Username used to connect to the HTTP proxy server. |
Password |
Password used to connect to the HTTP proxy server. |
SMTP (Mail server) |
|
Host |
Host name or address of SMTP server. JMap Server requires an SMTP server to send emails. |
Port |
TCP/IP port used to connect to SMTP server. |
Username |
Username used to connect to the SMTP server (if needed). |
Password |
Password used to connect to the SMTP server (if needed). |
Encryption |
Select an encryption method if required by the SMTP server. |
GeoWebCache |
|
URL (1-4) |
Enter one or more URLs to connect to the GeoWebCache server. Only one URL is necessary, but entering several URLs that point to the same server will optimize the use of this type of server. Configuring settings for GeoWebCache is optional but offers better performance for JMap Web and JMap Mobile applications. Refer to the Using a GeoWebCache Server section for more information. |
Username |
User name used to connect to the GeoWebCache server. |
Password |
Password used to connect to the GeoWebCache server. |
Route Logistics Service |
|
URL |
Enter the URL of the RLS service to use (e.g. https://rls.jmaponline.net/rls/rest/v1.0). This service allows you to geocode addresses and calculate optimal routes. |
Client ID |
Enter your organization's unique key that allows you to use the RLS services. |
API Keys |
|
Enter the API key of your organization that allows you to use Google services. For more details, visit the following page: https://developers.google.com/maps/documentation/javascript/get-api-key?hl=Fr |
|
Bing |
Enter the API key of your organization that allows you to use Bing services. For more details, visit the following page: https://msdn.microsoft.com/fr-fr/library/ff428642.aspx |
File browser |
|
Allow upload |
Select this option if you allow uploading files to JMap Server directly from JMap Admin. |
Max. upload file size |
Specify the maximum size of a file to upload. Select the Unlimited option if you do not set a limit on file size. |
Upload root folder |
Specify the directory where the uploaded files will be copied. Each administrator account in JMap has a subdirectory automatically created in the JMAP_HOME/Data/Uploads directory. Uploaded files are accessible to all JMap Admin users. The Uploads directory is also available when creating spatial data sources. |
Loaded parameters |
|
Database drivers |
List of loaded database drivers. New drivers can be added by creating new configuration files in the directory JMAP_HOME/conf/db on the server. |
Custom spatial data sources |
Spatial data sources related to certain specific applications. |
Projections |
List of loaded projections. New projections can be created by adding entries in the file JMAP_HOME/conf/projections.properties on the server. |
Element factories |
Map element generation modules related to certain specific applications. |
User managers |
List of loaded user manager modules. User managers are used to manage users and groups and they provide the authentication service used in JMap Server. |