Provisioning Reference Guide › Program Exits › Program Exits Overview

Program Exits Overview

Program exits let you write software that executes during certain Provisioning Server actions. Program exits let you reference custom code from in the Provisioning Server process flow, extending the framework of the Provisioning Server to allow additional functionality that changes or augments standard behavior. Numerous exit points are available where custom code can be referenced, depending on the type of object. For example, you may want to install some files on a system every time a UNIX account is created. You could write a program exit that performs the file creations, and specify that it be run whenever a UNIX account is created.

There are two types of program exits:

• Common Exits are executed from the Provisioning Server core infrastructure.
• Native Exits are executed from the managed endpoint types.

The type of program exit is determined by where it is handled, not where it is referenced.

Note: For information about native exits, see the endpoint type-specific Connector Guide.

Program exits are implemented as separate objects, allowing you to define the necessary exits and associate them at the points where they need to be referenced. The following objects reference program exits:

• Common Configuration Objects
• Provisioning Roles
• Account Templates
• Endpoints

Each of these objects can reference multiple program exits, including multiple exits of the same type. For example, a directory can reference two exits that handle routines to be executed before creating an account.