Developing the i2 Analyze configuration

About this task

Developing the configuration is separated into two parts: enabling i2 Analyze to work with your data, and defining how analysts interact with your data.

The i2 Analyze deployment in the configuration development environment is not your final deployment. When you are configuring the deployment, use small amounts of data with a few users to ensure that the processes are functional.

Procedure

Depending on the composition of your deployment, there are three methods that you can use to get your data into i2 Analyze for analysis.

1. To develop the process for ingesting data into the Information Store, refer to Ingesting data into the Information Store.

2. To develop connections to external data sources, refer to Connecting to external data sources.

3. Ensure that analysts can import and create representative records in Analyst's Notebook. Then, if required, upload records to the Information Store. For more information, see Import data and Create i2 Analyze chart items.

When you develop the process to get your data into i2 Analyze, you might realize that your schema or security schema are not correct for your data. You can update the deployed schemas to better represent your data and security model. Some changes require you to remove and recreate the underlying database.

1. To update your deployed Information Store or Chart Store schema, refer to Changing the schema.

2. To update your deployed security schema, refer to Configuring the security schema.

After you develop the mechanisms for making data available to analysts, you can configure how analysts interact with the data when they use the system. The list of things that you can configure includes:

1. To configure which features or types of commands analysts can access, refer to Controlling access to features.

2. To configure how analysts search for information, and the options that are available to them, refer to Configuring search.

3. To configure how analysts can identify matching records, refer to Configuring matching.

4. To configure user security, refer to Configure user authentication and authorization.

   For more information about the configuration changes that you can make, see Configuring i2 Analyze.

What to do next

After you configure your deployment sufficiently in the single-server environment, you can move to another environment that is more representative of the production deployment. Keep your configuration development environment in place so that you can access the configuration directory in later phases of the production process, and return to it to make further configuration changes.

Next, create the Pre-production environment.