Importing group configuration

Before you begin

Any group configuration settings that you import from a file act as a foundation for the provisioning process. To avoid unexpected behavior, i2 recommends putting the file in place before provisioning runs for the first time. If the target deployment already contains users and groups, the following rules apply:

• If the file contains users and groups with identifiers that are not already in the deployment, those users and groups are created.

  Note: In a brand new deployment, this is the case for all imported users and groups.

• If the file contains users and groups with identifiers that (case insensitively) match identifiers that are already in the deployment, those users and groups from the file are ignored.

  Note: This and subsequent conditions can be true only if provisioning has already happened at least once.

• If the file contains users with user names that (case insensitively) match user names that are already in the deployment, those users from the file are also ignored.

• If the file contains system groups with display names that (case insensitively) match display names that are already in the deployment, those groups from the file are ignored. However, any custom groups with matching display names (but different identifiers) are created.

• At creation, imported groups have their membership lists filtered so that they only contain users and groups whose identifiers are (case sensitively) already in the system, or are also to be created during the import.

For the import to be a success, set up the source and target environments so that they're provisioned with matching users and system groups. If the result of an import followed by provisioning is different from what you expected, check the provisioning log.

About this task

Arranging for an exported group configuration to be imported into a new deployment of i2 Analyze just involves putting the file in the right place so that it's processed during system initialization.

Procedure

To import group configuration settings into a new deployment of i2 Analyze:

1. Locate the group-configuration-init.json file that you exported from an existing deployment.

2. As you create the new deployment, place the file in the fragments/common/WEB-INF/classes directory of the i2 Analyze deployment toolkit.

Provided that it's in the right place, the file is processed during initialization, the groups and their settings are created according to the rules above, and then provisioning runs as usual.

What to do next

After initialization and provisioning, if you want to inspect or change the group configuration, you can do so through the i2 Analyze Server Admin Console. If you ever need to, you can also export the settings again for the next deployment.