Defining the mapping solution
In a deployment of i2® Analyze, you can define the mapping tiles that can be accessed, and the coordinate systems that are used to plot locations on them. By default, analysts can select from a list of publicly available maps and common coordinate systems.
- Modify the geospatial-configuration.json file:
Update the deployment with your changes.
The following method deploys your changes without stopping the server by using a POST request to a REST endpoint.
To redeploy your changes by using the deployment toolkit only, see Redeploying Liberty. You must deploy your changes by using the deployment toolkit if you are in a deployment with high availability or you are deploying in your production environment.
- Update the configuration on the
setup -t updateLiveConfiguration
- Update the running application by using
To reload the server by using the reload endpoint, ensure that you can use the admin endpoints. For more information about using the admin endpoints, see Using the admin endpoints.
curl -i --cookie-jar cookie.txt -d j_username=user_name -d j_password=password http://host_name/conext_root/j_security_check curl -i --cookie cookie.txt -X POST http://host_name/conext_root/api/v1/admin/config/reloadWarning: The
reloadmethod updates the configuration without requiring a server restart, but any logged-in users are logged out from i2 Analyze when you run it.
Where deployed_war can be:
IS_DATAtables that contain geographical data. For more information on creating indexes manually in the Information Store, see Creating indexes in the Information Store database. In addition, for database specific information about the use of spatial indexes:
- For Db2 databases, see the IBM Integrated Analytics System documentation: Using indexes and views to access spatial data.
- For SQL Server databases, see the Microsoft SQL Server Spatial Indexing documentation: https://docs.microsoft.com/en-us/sql/relational-databases/spatial/spatial-indexes-overview?view=sql-server-ver15.