Developing schemas in your configuration development environment

To reduce the time that it takes to update the environment with your schema changes, use the schema_dev deployment pattern.

Note:

  • In the analyze-deployment-tooling repository, the structure of the configuration directory is modified. The configuration files are in the top level configs/<config_name>/configuration directory.
  • You cannot run any toolkit tasks described in the linked documentation in this environment.

Ensure that the DEPLOYMENT_PATTERN variable in the <config_name>/utils/variables.conf file is set to schema_dev.
For example: 

DEPLOYMENT_PATTERN="schema_dev"

Developing the data model

  1. In i2 Analyze Schema Designer, modify the schema.xml and schema-charting-scheme.xml files in the <config_name>/configuration directory with your changes. For more information about developing your schema, see i2 Analyze Schema Designer.
    On Windows, open the file from your mapped network drive.
    On MacOS, use Schema Designer in a Windows VM that has access to your analyze-deployment-tooling directory.
  2. After you make your changes, run the deploy command.
  3. Test your changes in Analyst's Notebook.
    Note: You might need to log out of Analyst's Notebook and log back in to see your changes.

Developing security model

  1. Update the security-schema.xml file in the <config_name>/configuration directory with your changes. For more information about developing your security schema, see Configuring the security schema.

    1. After you make your changes, run the deploy command.

  2. Update the user.registry.xml file to align to your security schema changes. For more information about updating the user registry, see Configuring the Liberty user registry.
    Note: In this release, you must ensure that your user registry file contains the user Jenny in the Administrator group.

    1. After you make your changes, run the deploy command.

  3. Update the command-access-control.xml file to align to your users and groups. For more information about controlling access to features, see The command access control file.

    1. After you make your changes, run the deploy command.

  4. Test your changes in Analyst's Notebook.
    Note: You might need to log out of Analyst's Notebook and log back in to see your changes.

After you develop your schemas, Add data to your config development environment.