This enables configuration of geocoding for several countries, via different UGC functions and/or via the HERE web service. The choice of country is made via the countryCode parameter, cf. Geocoding service.
- Name: name by which the country is called (for example, France). the default value must be added if at least one country is listed, this determines the country used if the countryCode parameter is empty, or if it is not found under Name and Possible Names.
- Possible Names: country call alias separated by | (ex: FR|FRA). Not to be filled in if the Name parameter has default as value.
- provider UGC or HERE. The different parameters for access and utilisation of the HERE web service are to be filled in under Administration / Parameters / geocoder / here.
- Datasource: name of the UGC datasource (for example, Loire-Atlantique). Leave empty for HERE.
Tip | |
---|---|
This function can also be used for using separate repositories within a single country (towns, public amenities, …) |
Allows you to configure graphs for several countries and/or several vehicle profiles, via different SITI files.
- Name: Name of the configuration, this is used by the Routing widget.
- Description: Description of the configuration.
- Image: to select in the list. Geoconcept Web has, by default, several images that will vary according to the different vehicle profiles being used: they will have a prefix of “Transport_”.
- Provider: At the current time, SITI is the only provider available.
-
Graph name: Name of the graph to use, for example: “Graphe_France_2014.siti”. The graphs or networks must be stored in the filepath
defined by the “GraphsDirectory” variable in the
server.xml
file. For more details, consult the chapter entitled Configuration SmartRouting JEE. -
Type of profile: By default, the road networks and graphs designed and set up by GEOCONCEPT utilise the following values for profiles:
- Automobiles (default value if value not assigned) = car
- Bus = bus or coach
- Taxis = taxi
- Carpool = car share
- Pedestrians = pedestrian
- Trucks = truck or HGV, …
- Deliveries = Delivery vehicles (van, truck, small lorry, …)
- EmergencyVehicles = Emergency vehicles
Editing the server.xml file
In the case of a manual installation, it will be necessary to indicate to the application server where the SmartRouting JEE
application can be found. Using a text editor, edit the server.xml
file present in the directory: “<TOMCAT_HOME>”\conf\,
In the GlobalNamingResources tag, add the following lines:
<!-- SMARTROUTING --> <Resource ConnectionMode="LocalDll" name="geoconcept/smartrouting/default" RootDirectory="``<SMARTROUTING_HOME>''\server\SRJEE\smartrouting" auth="Container" type="com.geoconcept.smartrouting.connect.tomcat.ConnectionFactory" factory="com.geoconcept.smartrouting.connect.tomcat.ConnectionFactory" scope="Shareable" description="SmartRouting connection factory - local dll" />
The character string SMARTROUTING_HOME
must be replaced by the file path for the directory containing your SmartRouting Server application.
As an option, it is also possible to add the filepath to a directory storing the reference tables:
GraphsDirectory="D:\Data\graphs"
- Type of profile:
This section allows the super administrator to choose the level of strength required for user passwords.
Tip | |
---|---|
Password strength is not applied, by default, to accounts linked to the "Super Administrator" group. To change this behaviour, simply set the authentification.changePassword.excludeSuperAdmin parameter to false (cf. parameters section), so that these accounts are obliged to change their password regularly (if the option is activated) in the same way as for any other user. |
Warning | |
---|---|
When performing a migration from an earlier version to version 5.2 of Geoconcept Web, or a later version, users for whom the passwords do not match the strength criteria will be returned to a form requesting they change the passwords concerned. To maintain the old mechanism (without verification of robustness), even if this is not recommended, it may be disabled by unchecking "Activate password strength handling". |
Good practice measures to ensure password security correspond to the values defined by default in the table below. They can be strengthened or reduced according to the security policy applied.
Option | By default | Parameter |
---|---|---|
Change password regularly |
Yes |
60 days |
Force the change of password at the first login |
Yes |
|
Activate password strength handling |
Yes |
|
Force the presence of an integer |
Yes |
|
Force the presence of a lower case character |
Yes |
|
Force the presence of an upper case character |
Yes |
|
Force the presence of a special character (%,$, …) |
No |
|
Authorise the presence of spaces |
No |
|
Minimum number of characters for the password |
8 |
The 'List of processes' function permits real time tracking of one or several cache generation processes, as these are being executed.
It enables consultation, for example, of all programmed cache calculations:
- the Process Identifier,
- the Type;
- the Terminated status for each process. This status is signaled by a cross "X",
- the Result,
- the Progress status for the process, expressed as a percentage,
- the Execution time that has run since the start of the process,
- the Time remaining for each process in the course of execution,
- the number of Errors encountered since the process was run.
Allows you to activate the following protocols:
- Protection with an application key: provides, for all REST and SOAP services, two parameters (app_id with the application identifier, and token with the key of an identifier) to place in the header of queries sent to the web services.
For API Javascript, the identification information needs to be supplied in the following way:
GCUI.Settings = {app_id:"REPLACE_WITH_YOUR_APP_ID", token:"REPLACE_WITH_YOUR_TOKEN"};
- SOAP,
- WMS
- WMTS.
Monthly usage statistics for the various web services.
The
button allows you to retrieve statistics in a .xls format file.This allows you to reload a license file or to manually update it as a function of new user rights authorised by Geoconcept.
This allows you to provide information about:
- the server operating system,
- the parameters used,
- the correct functioning of GCIS,
- the parameters of the JVM;
- the memory,
- tracking of threads in the stack,
- the datasource;
- parameters used for geocoding;
- access to the geocoder,
- web services testing.