Manually creating the Information Store database

You can create the Information Store database manually before running deploy, as an alternative to supplying Administrator user credentials at deploy time.

You can create the Information Store database, logins, users, and roles manually before running deploy as an alternative to supplying Administrator user credentials at deploy time. This option applies to new deployments only and is not applicable during upgrade. For a description of the database objects created, see Database Permissions Summary.

The Information Store database must use the same collation as your iBase database. Before generating the database scripts, you must determine that collation and set the required configuration properties. You can do this using the i2 Explore Administration Console or the command line tools.

Generating database scripts using the i2 Explore Administration Console

Before you can generate the scripts, the following configuration properties must be set in the Configuration tab of the i2 Explore Administration Console:

  • IBASE_DB_NАME — the name of your iBase data database as it appears in SQL Server

  • IBASE_SEC_DB_NАME — the name of your iBase security database as it appears in SQL Server

  • DB_INSTALL_DIR — the file path of the SQL Server installation or client tools on this machine

  • DB_LOCATION_DIR — the file path where SQL Server stores database files

  • DB_COLLATION — the collation of your iBase data database

The recommended way to populate IBASE_DB_NАME, IBASE_SEC_DB_NАME, DB_LOCATION_DIR, and DB_COLLATION is to use the Load iBase details button on the Configuration tab, which discovers and populates those values automatically. You must set DB_INSTALL_DIR manually. For more information, see Administration Console: Configuration.

After the required properties are set, generate the scripts:

  1. Open the i2 Explore Administration Console and select the Admin tab.

  2. Under Database Scripts, click Generate Database Scripts.

  3. When generation succeeds, the console displays the path where the scripts were written. Note this path for use in the next stage.

Generating database scripts using the command line tools

  1. Run the following query on your SQL Server instance to determine the collation of the iBase database:

    USE master;
    SELECT collation_NАME
    FROM sys.databases
    WHERE name = '<IBASE_DB_NАME>'

    Replace <IBASE_DB_NАME> with the name of your iBase database as it appears in SQL Server.

  2. Open <installation_location>/analyze-deployment-tooling/configs/explore-for-ibase/utils/variables.conf and set the following properties, surrounding each value with double quotes:

    • IBASE_DB_NАME — set to the iBase data database name as it appears in SQL Server

    • IBASE_SEC_DB_NАME — set to the iBase security database name as it appears in SQL Server

    • DB_INSTALL_DIR — set to the file path of the SQL Server installation or client tools on this machine

    • DB_LOCATION_DIR — set to the file path where SQL Server stores database files

    • DB_COLLATION — set to the collation value returned by the query above

  3. Navigate to the <installation_location>/analyze-deployment-tooling directory in a terminal and run:

    setup -t createDatabaseScripts

Executing the manual database creation scripts

Whichever method you used to generate the scripts, they are located in <installation_location>/analyze-deployment-tooling/configs/explore-for-ibase/database-scripts.

  1. Open SQL Server Management Studio and connect as an Administrator user with sysadmin permission.

  2. Execute all scripts prefixed with D in order, starting with D001-create-database-storage.

  3. Once all scripts have been executed successfully, run deploy from either the command line or the i2 Explore Administration Console. The deployment detects that the database, logins, users, and roles are already present and completes without requesting Administrator user credentials.

Note: The scripts prefixed with C can be used to drop the Information Store database and all associated logins and users. They must be run in order as an Administrator user with sysadmin permission.

Completing the deployment

To complete the deployment, deploy i2 Explore for iBase using either the i2 Explore Administration Console or the command line tools. For more information, see Deploying the Application.