Updating the i2 Analyze application configuration
This section describes an example of the process to update the configuration of a deployment in a Docker environment. After you update the configuration, rebuild the configured Liberty image. You must rebuild the image, because the configuration is part of the image.
Updating the configuration includes the following high-level steps:
- Removing the Liberty containers
- Updating configuration
- Rebuilding the configured Liberty image with the modified configuration
- Running the Liberty containers
- When you start Liberty, the schema that it caches from the database is updated
Note: Before you complete this walkthrough, reset your environment to the base configuration. For more information, see Resetting your environment.
Removing the Liberty containers
Before you update the application configuration, you remove the Liberty containers. To remove the containers, run the following docker commands:
docker stop liberty1 liberty2
docker rm liberty1 liberty2
See the Removing the Liberty containers
section of the walkthrough script.
Updating your configuration
In the examples/pre-prod/walkthroughs/change-management/updateConfigurationWalkthrough.sh
script, a modified geospatial-configuration.xml
is being copied from the walkthroughs/configuration-changes
directory to the configuration/live
directory.
For information about modifying the configuration, see Configuring the i2 Analyze application.
See the Updating the configuration
section of the walkthrough script.
After you modify the configuration, build a new configured liberty image with the updated configuration.
The build_liberty_configured_image_for_pre_prod
server function builds the configured Liberty image. For more information, see Building a configured Liberty image.
Running the Liberty containers
The run_liberty
server function runs a Liberty container. For more information about running a Liberty container, see Liberty.
See the Running the Liberty containers
section of the walkthrough script.
Note: You must run both Liberty containers.
The wait_for_i2_analyze_service_to_be_live
common function ensures that Liberty is running.