Using the Default Connectivity Applications

This chapter describes the default Connectivity applications available in the Connectivity view group and how to configure and customize them.For information about the default request workflows, see the DirX Identity Provisioning Administration Guide.The sections in this chapter

  • Describe how to work with the default Connectivity applications as a whole

  • Provide an understanding of the default Connectivity applications

  • Describe how to configure a custom Connectivity scenario

The chapters that follow describe the default Connectivity applications and are subdivided into the following:

  • Source workflows

  • Maintenance workflows

  • Target system workflows

Working with Default Connectivity Application Objects

All default Connectivity application objects are located in Default folders. We strongly recommend that you do not work directly in the default Connectivity scenario or any of its folders. Instead, you should create your own scenarios and create your own connected directories and workflows within your own scenarios. The "Getting Started" chapter in the DirX Identity Tutorial provides detailed instructions on how to perform these tasks. When you follow this recommended procedure, all of your objects are created in folders within your own scenario; for example, workflows are created in the Workflows folder, connected directories are created in the Connected Directory folder and so on. DirX Identity automatically uses folders that have the name of your scenario.

Important note: The objects you create from default application objects will not be affected by DirX Identity upgrades for two reasons: each object has a unique identifier (and your created objects have these identifiers, too) and DirX Identity preserves all central objects from the previous release by copying them to a version-specific folder (but only if there were changes in these objects).

You should also be aware that some default Connectivity applications use central objects like Tcl scripts in the folder ConfigurationTcl. If you change these central objects, all of your copied default applications will be affected by your change. DirX Identity surrounds all property sheets that belong to this central area with a red border that contains the text This object might be shared because it belongs to the Configuration folder. If you do not want this behavior, you should make your copies independent from the central objects by creating local ones. See the section "Linking Objects" in the "Managing Provisioning Workflows" chapter in the DirX Identity Connectivity Administration Guide to learn more about thi concept.s

Working with the Default Connectivity Scenario

The default Connectivity applications consist of:

  • Source Workflows - comprise the Source Real-time and Source Scheduled scenarios. These scenarios consist of Java-based / Tcl-based Identity creation workflows, which assist with importing and joining organizational and user information from various sources to create identities within the Identity Store. Update workflows can import attributes back to these source systems.

  • Maintenance Workflows - comprise the Identity Store scenario. This scenario contains Identity maintenance workflows, which help to manage the created identities. Consistency checks, policy execution, privilege resolution and password expiration are examples of this workflow group.

  • Target System Workflows - comprise the Target Real-time and Target Scheduled scenarios. These scenarios contain all Java-based / Tcl-based Identity Provisioning workflows, which offer initial load and validation from connected systems as well as regular synchronization. These scenarios also offer password synchronization and other useful capabilities.

These workflows are part of the default Connectivity scenario, which you can view with Identity Manager’s ConnectivityGlobal view. The following figure illustrates the default Connectivity scenarios and its workflows.

DirX Identity Default Connectivity Scenario
Figure 1. DirX Identity Default Connectivity Scenario