Identity Manager 8.0 - Configuration Guide

Reloading Changes Dynamically

Cached system data can be dynamically reloaded if it has changed. The changes are reloaded automatically in background. An exception to this are changes that effect the character of the user interface. These changes are only reloaded after requesting confirmation from the user. The semaphore is incremented when changes are made. The semaphore is calculated when the DBQueue Processor is run.

Which columns are reloaded is defined in the data model . You can find an overview of the semaphore in the category Base data | Advanced | Semaphore in the Designer.

• To reload data after changes to a column, the column must be assigned to the semaphore.
• To reload data after inserting or deleting in a table, the primary column key must be assigned to the semaphore.

TimeTrace Databases

The history databases must be declared in the One Identity Manager database if archive data is to be included in the One Identity Manager TimeTrace function. Historical data is displayed in the TimeTrace view in the Manager.

To link a History Database into a TimeTrace

1. Select the category Base Data | General | TimeTrace databases in the Designer.
2. Select the menu item Object | New.
3. Enter the One Identity Manager History Database's name.
4. Declare the Connection parameter .
   1. Open the connection data dialog box using the [...] button next to the text box.
   2. Enter the database connection data for the One Identity Manager History Database.

      Table 70: SQL Server Database Connection Data

      Data	Description
      Server	Database server.
      Windows authentication	Specifies whether Windows authentication is used. This type of authentication is not recommended. If you decide to use it anyway, ensure that your environment supports Windows authentication.
      User	Database user.
      Password	Database user password.
      Database	Database.

      Table 71: Oracle Database Connection Data

      Data	Description
      Direct access (without Oracle client)	Set this option for direct access. Deactivate this option for access via Oracle Clients. Which connection data is required, depends on how this option is set.
      Server	Database server.
      Port	Oracle instance port.
      Service name	Service name.
      User	Oracle database user.
      Password	Database user password.
      Data source	TNS alias name from TNSNames.ora.

   3. Click OK.
5. Save the changes.

Machine Roles and Server Functions

A machine role describes the role a computer or server assumes in a One Identity Manager system. You can give each computer or server several roles. This means, one or more machine roles can be assigned. You select machine roles when One Identity Manager components are installed.

Machine roles are structured hierarchically. If you select a machine role at installation, all parent machine are also assigned.

An example of machine role structure

Server

If you select the machine role "Active Directory" at installation, the additional machine roles "Job Server" and "Server" are assigned.

Some machine roles, for example, "Web" cannot be actively selected during installation. These machine roles are automatically assigned when different web applications are installed with the Web Installer.

Machine roles for installing the One Identity Manager Service are linked with server functions. The server function defines the functionality of a server in One Identity Manager. One Identity Manager processes are handled depending on the server function. The server functions available are predefined when a server installed, based on the selected machine role.

Example for the connection between machine roles and server functions.

The machine "Active Directory" is linked to the server function "Active Directory connector". Therefore, when you set up a Active Directory synchronization project after the machine role is installed, the server is available as synchronization server in One Identity Manager.

The installation packages and files to be installed on the computer or server are specified in a machine role. The information about the machine role, the installation package and the files is saved in the file InstallState.config during installation and are thus available for automatic software update.

If you import new files into the One Identity Manager database with the Software Loader, you should assign the files to a machine role. This ensures that the file are distributed by automatic software update.

To display information about machine roles

• Select the category Base Data | Installation | Machine roles in the Designer.

To display information about server functions

• Select the category Base Data | Installation | Server functions in the Designer.

Related Topics

• Files for Software Update
• Editing a Job Server

Files for Software Update

All the files included in an installation of the One Identity Manager are stored in the One Identity Manager database with name, repository and executable code. The One Identity Manager tool to which each file belongs, for example the Manager or the One Identity Manager Service, is entered in the database. In order to distribute new or changed custom files, such as custom form archives, through automatic software updating, the files are loaded into the Software Loader database with the program "One Identity Manager".

Detailed information about this topic

• Importing New Files into a One Identity Manager Database
• Exporting Files from a One Identity Manager Database
• Configuring Files