Add data to your config development environment

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

First, update the DEPLOYMENT_PATTERN variable in your <config_name>/utils/variables.conf file to your intended deployment pattern.
For example, to deploy with the i2 Connect gateway and the Information Store set the following value:

DEPLOYMENT_PATTERN="i2c_istore"

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

• To develop the process for ingesting data into the Information Store, refer to Ingesting data into the Information Store.
• To develop connections to external data sources, refer to Connecting to external data sources.
• 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. If you need to make destructive changes, change the DEPLOYMENT_PATTERN variable in your <config_name>/utils/variables.conf file to schema_dev and redeploy. Then complete the process of developing schemas.

After you add data to your environment, you can configure the rest of the configuration.

When you are happy with your schemas and you have populated your Information Store database with any required data, you can create a release of your schemas and a backup of your database. For more information, see Back up and restore a development database and config.