Creating the production environment

To deploy i2 Analyze in production, you use the i2 Analyze configuration that you developed previously. Before you deploy i2 Analyze, update the configuration to reflect any environment changes.

Ensure that you have access to the following files and directories so that you can copy them to the production environment:
  • The toolkit\configuration directory from the test environment
  • Liberty user configuration, for example the server.xml file
  • Any configuration that you completed in the Information Store database. For example, your merged property values definition views.
  • Any certificates and certificate stores that are required
If you are planning to deploy with high availability, complete the instructions in i2 Analyze with high availability rather than the steps on this page.
  1. Install any prerequisite software to prepare your servers for the production environment.
    For the production environment, use the same deployment topology as in your test environment. For more information, see Deployment topologies.
  2. Copy the toolkit\configuration directory from the test environment to the toolkit directory at the root of the deployment toolkit on the Liberty server in the production environment.
  3. Update the values for any configuration settings that are specific to the environment.,, and topology.xml contain settings that you might need to update. For more information, see Configuration files reference.
  4. If your deployment uses a proxy server or load balancer to route requests from clients, ensure that it is configured for use with i2 Analyze. Specify the URI that clients use to connect to i2 Analyze.
  5. Deploy and start i2 Analyze:
After you deploy i2 Analyze, you can replicate any configuration changes that are not stored in the configuration of i2 Analyze.
  1. Configure Liberty security for your environment. To do this, repeat any changes that you made to the Liberty configuration in the previous environment.
    This might involve copying the user registry file, or updating the server.xml file.
  2. Complete any configuration changes in the Information Store database.
    1. If you created any rules or schedules to delete records by rule, replicate the rules and schedules in the current environment.
    2. If you created any merged property values definition views for your ingestion process, replicate the view definitions in the current environment.
Complete testing of the deployment to ensure that it is working in the production environment before you make i2 Analyze available to users.