In this step, you add the schema extensions to the database.
To add schema extensions in the Schema Extension
Confirm the security prompt with Yes.
The schema extensions are added to the database and the necessary extensions are made to the One Identity Manager system data model. This make take some time.
On the Compilation page, click Next.
The compilation process can take some time.
After completing the schema extensions, you can access them with One Identity Manager tools and make further changes.
Once you have added custom tables or columns to the One Identity Manager schema, some additional steps are necessary to display the extensions in the Manager user interface.
The Designer contains a variety of consistency checks. Run these consistency checks and apply the repair methods after carrying out a schema extension and after making changes to table and column definitions. For detailed information on checking data consistency, see the One Identity Manager Operational Guide.
The properties include, for example, display names, descriptions, display templates for tables and columns, value templates, formatting, required field definitions. For more information, see One Identity Manager schema basics.
||NOTE: You do not need to enter a display template for many-to-many tables. For these tables, the viDB.DLL forms the display template from the foreign keys.|
Flag columns containing an email address with the value Email address in the Designer in the Table lookup support property.
When you extend a schema using the Schema Extension program, you already assign permissions to permissions groups. You can carry on editing permissions in the Designer Permissions Editor and also create permissions groups with the User & Permissions Group Editor. Permissions groups can be linked to application roles. The users are assigned to application roles and therefore receive the permissions they require. For more detailed information, see the One Identity Manager Authorization and Authentication Guide.
The data in the user interfaces is represented by means of objects. A generally applicable object definition without any limiting selection criteria is already created with the Schema Extension program. You can create other object definition constraints in addition. You create object definitions in the Designer. For more information, see Object definitions for the user interface.
Expand the menu to display the data in the Manager. Use Designer's User Interface Editor to create menu items for navigation and result lists. For detailed information, see User interface navigation and Recommendations for editing menu navigation.
Create or extend the forms for editing and displaying in Manager. For more detailed information, see Recommendations for editing forms, Editing user interface forms, Forms for custom extensions and Working with overview forms.
If you want to offer particular tasks for the objects in theManager, you need to create task definitions in the Designer. For more information, see Task definitions for the user interface.
For data analysis purposes, you need to create statistics definitions and reports and incorporate these in the user interface. For more information, see Statistics in One Identity Manager and Reports in One Identity Manager.
For language-dependent display of texts in the Manager such as column names, comments, menu items, and form names, translate the texts using the DesignerLanguage Editor. For more information, see Language-dependent data representation.
To create transport packages with the Database Transporter program and to create reports about the system configuration, information about database objects such as customized database tables and database columns, database procedures, features, triggers, indexes or view definitions is stored in the database. The DBQueue Processor checks and updates this data.
NOTE: It is not usually necessary to edit the data manually although you might edit the comment for use in reports.
To customize database objects
The processing status is used for creating custom configuration packages.
|Remarks||Additional comments, for example, for using in system configuration reports.|
|Name||Database object name.|
|Modified||Specifies whether the database object has been changed.|
Order in which the data is presented.
|Type||Type of database object, for example, procedure, function, trigger, index, view, custom table, custom column.|
For detailed information about creating transport packages, see the One Identity Manager Operational Guide.
The One Identity Manager offers you the option to integrate web services. For example, you can use web services to write data to applications, which cannot be connection to One Identity Manager as a default target system.
Data for external applications can be originate from any of the One Identity Manager schema's tables. They can, for example, be mapped as custom target systems.
The general data for a telephone system should be found from personnel data in One Identity Manager. The telephone system is mapped in One Identity Manager as a custom target system. One extension in the telephone corresponds a user account in One Identity Manager.
Once a new employee has been added in One Identity Manager, a new extension should become available in the telephone system. A new user account is added for each account definition. A web service passes the user account''s master data onto the telephone system. where a new participant and telephone number is added. The web service passes this telephone number to the One Identity Manager as the return value. The telephone number should be transferred to the employee's master data.
Proceed as follows
The web service integration wizard helps you to create scripts for provisioning data for the default events Insert, Update and Delete. The provisioning processes are supplied by default through One Identity Manager.
TIP: When you insert, change or delete containers, user accounts, and groups in a custom target system, the return values are saved by default as GUID objects in the database.
Create a process to add the telephone number from the object GUID to the employee master data.
For detailed information about setting up a custom target system, about account definitions, IT operating data and setting up a server, see the One Identity Manager Administration Guide for Connecting to Custom Target Systems.