Deploying i2 Analyze with the exported iBase schema

After you've installed i2 Analyze and created the schema, the next step is to deploy i2 Analyze with the i2 Connect gateway that enables the use of connectors. You also need to configure i2 Analyze so that your iBase users can log in.

You started the process of deploying i2 Analyze for use with iBase when you created the toolkit/configuration directory in Preparing iBase and generating an i2 Analyze schema. To complete the deployment:

  1. Follow the instructions in the documentation to create a schema development environment for i2 Analyze.

    A "schema development environment" of i2 Analyze provides only the i2 Connect gateway, which is what you need here.

    Important: In the procedure, you can ignore the second part of Step 1 (installing the Analyst's Notebook Premium desktop client) for now, and you have already completed the copy in Step 2. In Step 5, instead of creating a schema, use the schema and the charting schema that you created from iBase.

  2. Configure Liberty so that iBase users can log in to the i2 Analyze server and run external searches.

    iBase and i2 Analyze manage their users independently. However, it's easier to use the Analyst's Notebook Premium desktop client with iBase and i2 Analyze when both environments use the same user registry type.

    For example, if iBase uses a local user registry, then configuring the same user registry in i2 Analyze means that there is only one set of users and groups to manage. See the documentation about configuring the Liberty user registry in i2 Analyze.

    Alternatively, if iBase is configured to use Active Directory, then configuring i2 Analyze to use the same directory will give a similar result.

    See the Open Liberty documentation for information about configuring LDAP as a user registry.

  3. Optionally, use i2 Analyze's command access control feature to permit or deny access to specific connectors on a per-user or per-group basis. For more information, see the documentation about controlling access to features.

For troubleshooting assistance, see the reference information.