지금 지원 담당자와 채팅
지원 담당자와 채팅

Identity Manager 8.2.1 - Administration Guide for Connecting to HCL Domino

Managing HCL Domino environments Synchronizing a Domino environment
Setting up initial synchronization of a Domino environment Domino server configuration Setting up a gateway server Creating a synchronization project for initial synchronization of a Notes domain Adjusting the synchronization configuration for Domino environments Running synchronization Tasks following synchronization Troubleshooting Ignoring data error in synchronization
Managing Notes user accounts and employees Managing memberships in Notes groups Login information for Notes user accounts Using AdminP requests for handling Domino processes Mapping of Notes objects in One Identity Manager
Notes domains Notes user accounts Notes groups Notes certificates Notes templates Notes policies Notes mail-in databases Notes server Reports about Notes objects
Handling of Notes objects in the Web Portal Basic data for managing a Domino environment Configuration parameters for managing a Domino environment Default project template for Domino Processing methods of Domino system objects Domino connector settings

Creating custom INI files

When you configure the Notes client, a Notes.ini file is created. This file contains configuration information that the Domino connector needs to access the target system. Create a copy of this INI file and make it available to the Domino connector as a custom INI file. The custom INI file must contain the path to the synchronization user's ID file. Enter this INI file and the user ID file's password when you configure the system connection with the Synchronization Editor.

To add a custom INI file

  1. Create a copy of the file Notes.ini. Use the synchronization user's ID file for this.

  2. Check the following values in the copy.

    Table 4: Parameters required in the custom INI file
    Parameters Description
    Directory Path to Notes data directory (local directory)
    KeyFileName Path to the ID file of the synchronization user (local directory).
    KitType Notes type: 1 = Client, 2 = Server.

Installing the One Identity Manager Service on the gateway server

The One Identity Manager Service must be installed on the gateway server with the Domino connector. The gateway server must be declared as a Job server in One Identity Manager.

Table 5: Properties of the Job server
Property Value
Server function Domino connector
Machine role Server | Job server | Domino

NOTE: If several target system environments of the same type are synchronized under the same synchronization server, it is recommended that you set up a Job server for each target system for performance reasons. This avoids unnecessary swapping of connections to target systems because a Job server only has to process tasks of the same type (re-use of existing connections).

Use the One Identity Manager Service to install the Server Installer. The program runs the following steps:

  • Sets up a Job server.

  • Specifies machine roles and server function for the Job server.

  • Remotely installs One Identity Manager Service components corresponding to the machine roles.

  • Configures the One Identity Manager Service.

  • Starts the One Identity Manager Service.

NOTE: The program performs a remote installation of the One Identity Manager Service. Local installation of the service is not possible with this program.

To remotely install the One Identity Manager Service, you must have an administrative workstation on which the One Identity Manager components are installed. For detailed information about installing a workstation, see the One Identity Manager Installation Guide.

NOTE: To generate processes for the Job server, you need the provider, connection parameters, and the authentication data. By default, this information is determined from the database connection data. If the Job server runs through an application server, you must configure extra connection data in the Designer. For detailed information about setting up Job servers, see the One Identity Manager Configuration Guide.

To remotely install and configure One Identity Manager Service on a server

  1. Start the Server Installer program on your administrative workstation.

  1. On the Database connection page, enter the valid connection credentials for the One Identity Manager database.

  2. On the Server properties page, specify the server on which you want to install the One Identity Manager Service.

    1. Select a Job server from the Server menu.

      - OR -

      To create a new Job server, click Add.

    2. Enter the following data for the Job server.

      • Server: Name of the Job server.

      • Queue: Name of the queue to handle the process steps. Each Job server within the network must have a unique queue identifier. The process steps are requested by the Job queue using this exact queue name. The queue identifier is entered in the One Identity Manager Service configuration file.

      • Full server name: Full server name in accordance with DNS syntax.

        Syntax:

        <Name of servers>.<Fully qualified domain name>

      NOTE: You can use the Extended option to make changes to other properties for the Job server. You can also edit the properties later with the Designer.

  1. On the Machine roles page, select Domino.

  2. On the Server functions page, select Domino connector.

  3. On the Service Settings page, enter the connection data and check the One Identity Manager Service configuration.

    NOTE: The initial service configuration is predefined. If further changes need to be made to the configuration, you can do this later with the Designer. For detailed information about configuring the service, see the One Identity Manager Configuration Guide.

    • For a direct connection to the database:

      1. Select Process collection > sqlprovider.

      2. Click the Connection parameter entry, then click the Edit button.

      3. Enter the connection data for the One Identity Manager database.

    • For a connection to the application server:

      1. Select Process collection, click the Insert button and select AppServerJobProvider.

      2. Click the Connection parameter entry, then click the Edit button.

      3. Enter the connection data for the application server.

      4. Click the Authentication data entry and click the Edit button.

      5. Select the authentication module. Depending on the authentication module, other data may be required, such as user and password. For detailed information about One Identity Manager authentication modules, see the One Identity Manager Authorization and Authentication Guide.

  4. To configure remote installations, click Next.

  1. Confirm the security prompt with Yes.

  2. On the Select installation source page, select the directory with the install files. Change the directory if necessary.

  3. If the database is encrypted, on the Select private key file page, select the file with the private key.

  4. On the Service access page, enter the service's installation data.

    • Computer: Enter the name or IP address of the server that the service is installed and started on.

    • Service account: Enter the details of the user account that the One Identity Manager Service is running under. Enter the user account, the user account's password and password confirmation.

    The service is installed using the user account with which you are logged in to the administrative workstation. If you want to use another user account for installing the service, you can enter it in the advanced options. You can also change the One Identity Manager Service details, such as the installation directory, name, display name, and the One Identity Manager Service description, using the advanced options.

  5. Click Next to start installing the service.

    Installation of the service occurs automatically and may take some time.

  6. Click Finish on the last page of the Server Installer.

    NOTE: In a default installation, the service is entered in the server’s service management with the name One Identity Manager Service.

Setting up an archive database for backing up employee documents

You can add an archive database for backing up ID files in order to restore user ID files using the ID restore method. When you add a new user account in the One Identity Manager, a copy of the initial employee document is copied to an archive database on the gateway server. This archive database must initially added and should be part of a daily back up.

Information: The archive database is only required if the ID vault enabled option is disabled for the domain and if user ID files are supposed to be restored by One Identity Manager. For more information, see Restoring user ID files through ID restore.

The fastest method of adding an archive database is to create an empty copy of the local address book on the gateway server.

Table 6: Data required for the copy
Property Value
Server Local
Title Any name
File Name Archive.nsf
Database design only Enabled

By default, the copy of the local address is encrypted for the current user. Therefore, the copy of the synchronization user's local address book must be encrypted in order for the Domino connector to access the archive database.

For more information about adding the address book copy, see your Domino documentation.

Creating a synchronization project for initial synchronization of a Notes domain

Use the Synchronization Editor to configure synchronization between the One Identity Manager database and Domino environment. The following describes the steps for initial configuration of a synchronization project. For more information about setting up synchronization, see the One Identity Manager Target System Synchronization Reference Guide.

After the initial configuration, you can customize and configure workflows within the synchronization project. Use the workflow wizard in the Synchronization Editor for this. The Synchronization Editor also provides different configuration options for a synchronization project.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택