Pre-production example environment

Prerequisites

Before you create an example pre-production environment, you must configure the analyze-deployment-tooling repository.
For more information, see Getting started with the analyze-deployment-tooling repository.

Creating a containerized deployment

After you have all of the prerequisites in place, you can create the reference pre-production containerized deployment.

Install pre-prod example

Run the command:

install-analyze-deployment-tooling -e pre-prod

Creating the environment and configuration

The create-pre-prod-environment script performs a number of actions that ensure all of the artifacts for a deployment are created and in the correct locations. These actions include:

Extracting the i2 Analyze minimal toolkit to the pre-reqs/i2analyze directory.
Creating the i2 Analyze Liberty application
Creating and populating the configuration directory structure

For more information about the what the script does, see:

Create environment

To create the environment and configuration:

Navigate to the examples/pre-prod directory.
Run the following script:
```
./create-pre-prod-environment
```

The configuration directory is created in the examples/pre-prod directory.

By default, the environment is created for an Information Store and i2 Connect gateway deployment for SQL Server.

Accepting the licenses

Before you can use i2 Analyze and the tools, you must read and accept the license agreement and copyright notices. The license agreement and copyright notices can be found in the pre-reqs/i2analyze/license directory. To accept the license agreement, change the value of the LIC_AGREEMENT variable to ACCEPT. The variable is in the licenses.conf file in the root directory.
Before you can use Microsoft SQL Server, you must accept the license agreement and the EULA. For more information about using the MSSQL_PID and ACCEPT_EULA environment variables, see Configure SQL Server settings with environment variables on Linux To accept the license in this environment, change the value of the MSSQL_PID and ACCEPT_EULA environment variables. The variable is in the licenses.conf file in the root directory.

Running the containers and start i2 Analyze

To deploy and start i2 Analyze:

Navigate to the examples/pre-prod directory.
Run the following script:
```
./deploy-pre-prod
```

For more information about the actions that are completed, see Deploying i2 Analyze.

Installing Certificate

To access the system, the server that you are connecting from must trust the certificate that it receives from the deployment. To enable trust, install the /environment-secrets/generated-secrets/certificates/externalCA/CA.cer certificate as a trusted root certificate authority in your browser and operating system's certificate store.

For information about installing the certificate, see:

Accessing the system

To connect to the deployment, the URL to use is: https://i2analyze.eia:9046/opal/

What to do next

To understand how the environment is created, you can review the documentation that explains the images, containers, tools, and functions:

To learn how to configure and administer i2 Analyze in a containerized environment, you can complete the walkthroughs that are included in the repository:

Walkthroughs