You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The SQL Provisioning Plugin provisions CO Person and CO Group records to a SQL database.

Operations

Registry CO Person Transaction

SQL Action

Add

Synchronize the CO Person and their CO Group Memberships

Edit

Synchronize the CO Person and their CO Group Memberships

Enter Grace Period

No changes (unless attributes change as part of grace period)

Expiration / Becomes Inactive

Synchronize the CO Person and their CO Group Memberships

Unexpire / Becomes Active

Synchronize the CO Person and their CO Group Memberships

Delete

Remove the CO Person

Manual Provision

Synchronize the CO Person and their CO Group Memberships

Registry CO Group Transaction

Changelog Action

Add

Synchronize the CO Group and its Memberships

Edit

Synchronize the CO Group and its Memberships

Delete

Remove the CO Group

Manual Provision

Synchronize the CO Group and its Memberships

Reference Data

In addition to the usual CO Person and CO Group data, the SQL Provisioning Plugin will write Reference Data to the target database. Reference Data can be used to understand foreign keys in the provisioned operational data. Reference Data is fully provisioned when the plugin is initially configured, and then updated whenever there are changes to the Reference Data.

The following models are provisioned as Reference Data:

  1. COU
  2. CoTermsAndConditions

Installation

This is a non-core plugin, see Installing and Enabling Registry Plugins for more information.

Configuration

  1. Create a new, empty database where the Provisioner will write. This database is the Target Database.
  2. Define a new Server in Registry.
    1. ServersAdd a New Server
    2. ServerType: SQL
    3. On the next page, enter the configuration information for the Target Database.
  3. Configure a new Provisioning Target in Registry.
    1. Configuration > Provisioning Targets > Add Provisioning Target
      1. Plugin: SqlProvisioner
      2. On the next page, select the Server created in the previous step.

The Target Database must be available when the configuration is saved. The Provisioner will instantiate the target database schema when the configuration is saved.

Target Database Schema

See Also

  • No labels