Tuesday, October 6, 2026

Setting Up Directory Assistance for LDAP in HCL Domino

Setting Up Directory Assistance for LDAP in HCL Domino

Integrating remote LDAP directories into your HCL Domino environment can streamline authentication and directory lookups. Here's a step-by-step guide to setting up directory assistance for an LDAP directory.

Prerequisites

Before diving in, ensure you have:

  • Network Connectivity: Verify that your Domino servers can reach the remote LDAP server. A simple ping test can confirm this.
  • Directory Assistance Database: Create a directory assistance database (da.nsf) from the da.ntf template and replicate it across servers that will utilize it. Each server must have a local replica to use directory assistance. (ibm.com)

Creating a Directory Assistance Document

  1. Access the Domino Administrator:

- Open Domino Administrator. - Navigate to the server that will use the directory assistance database.

  1. Open the Directory Assistance Database:

- Go to the Configuration tab. - Expand Directory > Directory Assistance. - If prompted with Server Error: File does not exist, ensure the server is set up to use the directory assistance database.

  1. Add a New Directory Assistance Document:

- Click Add Directory Assistance.

  1. Configure the Basics Tab:

- Domain Type: Select LDAP. - Domain Name: Assign a unique name different from other Directory Assistance documents. - Company Name: Enter the associated company's name. - Search Order: Define the order in which servers search this directory relative to others. - Make this domain available to: - Notes clients and Internet Authentication/Authorization: For mail addressing and client authentication. - LDAP Clients: To enable LDAP service referrals. - Group Authorization: Choose Yes if you want to search group memberships in this LDAP directory for database access control. - Enabled: Set to Yes.

  1. Configure the LDAP Tab:

- Host Name: Enter the LDAP server's hostname or IP address. - Port: Default is 389 for standard LDAP or 636 for LDAPS. - Optional Authentication Credential for Search: Provide credentials if the LDAP server requires authentication for searches. - Base DN for Search: Specify the base distinguished name (e.g., dc=example,dc=com). - Channel Encryption: Choose Yes if using SSL/TLS. - LDAP Vendor: Select the appropriate vendor (e.g., Active Directory).

  1. Save and Close the document.

Testing the Configuration

After setting up, it's crucial to test the configuration:

  • Verify Connectivity: Use the Verify button in the LDAP configuration section to test the connection. If you encounter errors like LDAP Server is NOT available, ensure the LDAP server is accessible and that network configurations are correct. (developer.ds.hcl-software.com)
  • Monitor the Domino Console: Restart the Domino server or the LDAP task and monitor the console for any error messages related to directory assistance.

Troubleshooting Tips

  • SSL/TLS Issues: If connecting over LDAPS (port 636), ensure that the Domino server trusts the LDAP server's SSL certificate. This might involve importing the certificate into Domino's key ring.
  • Authentication Failures: Double-check the credentials provided in the Optional Authentication Credential for Search field. Ensure they have the necessary permissions to search the LDAP directory.
  • Group Authorization: If group lookups aren't functioning, verify that the Group Authorization setting is enabled and that the LDAP directory contains the expected group structures.

The Outcome

By integrating a remote LDAP directory through directory assistance, your Domino environment can authenticate users and perform directory lookups seamlessly across multiple directories. This setup enhances flexibility and centralizes user management, especially in environments with diverse directory services.

Tuesday, September 22, 2026

Setting Up Domino's Native Backup: A Hands-On Guide

Why Native Backup Matters

If you've been juggling third-party backup solutions for your Domino servers, you know the drill: compatibility issues, complex configurations, and sometimes, less-than-ideal integration. With Domino 12, HCL introduced a native backup and restore feature that simplifies the process, offering a seamless way to protect your data without external tools. Let's dive into setting it up.

Prerequisites

Before we get our hands dirty, ensure:

  • Domino Version: You're running Domino 12 or later. This feature isn't available in earlier versions.
  • Operating System: Your server is on Windows or Linux. The native backup doesn't support other Operating Systems.

Step 1: Initialize the Backup Database

First things first, we need to create the dominobackup.nsf database, which will house our backup configurations and logs.

  • Run the Backup Task: Open your Domino console and execute:

`` load backup ``

This command initializes the backup database. If it's the first run, Domino will create dominobackup.nsf in the data directory.

  • Verify Creation: Navigate to your Domino data directory and confirm the presence of dominobackup.nsf.

Step 2: Configure Backup Settings

With the backup database in place, let's set up the backup configurations.

  1. Open dominobackup.nsf: Using the Domino Administrator client, access the backup database.
  2. Create a New Configuration:

- Platform Selection: Choose between 'Default' (applies to multiple servers) or 'Server' (specific to one server). For most setups, 'Default' suffices.

- Backup Paths: Specify directories for storing backup files. Ensure these paths have adequate storage and permissions.

- Excluded Databases: If there are databases you don't want to back up, list them here.

- Schedule: Define when backups should run. Regular scheduling ensures consistent data protection.

For a detailed breakdown of each configuration field, refer to the official documentation.

  1. Save and Close: Once configured, save your settings.

Step 3: Schedule the Backup Task

To automate backups:

  1. Create a Program Document:

- Program Name: backup

- Command Line: Leave this blank.

- Server to Run On: Specify your server.

- Schedule: Set the desired frequency and time for backups.

  1. Save the Document: This schedules the backup task as per your configuration.

Step 4: Test the Backup

Before relying on the setup:

  • Manually Run the Backup: In the Domino console, execute:

`` load backup ``

  • Monitor the Process: Check the console for any errors. Also, verify that backup files are created in the specified directories.

Step 5: Restore a Database

Testing the restore process ensures your backups are reliable.

  1. Open dominobackup.nsf: Navigate to the 'Restore' view.
  2. Select a Database: Choose a database to restore.
  3. Restore Options: Decide whether to restore to the original location or an alternate one. You can also choose to restore deleted documents.
  4. Initiate Restore: Click 'Restore' and monitor the process.

For more insights on the restore process, check out the Domino Backup Introduction.

To Review

Setting up Domino's native backup isn't just about ticking boxes; it's about ensuring your data's safety without unnecessary complexity. By following these steps, you integrate a robust backup solution directly into your Domino environment. Remember, regular testing of both backup and restore processes is crucial. After all, a backup is only as good as its restore.

For a visual walkthrough, consider watching this HCL Domino Backup/Restore Function video.