iDNA Applications 3.5.0 comes with a rebuilt configuration interface. This article describes its pages and the new Config Manager, a wizard that sets up the data collection for a Domino domain in four steps.

Overview

The configuration interface is where you tell iDNA what to collect and from where: the license, the Notes ID iDNA uses to access your Domino servers, the list of Domino servers, and the content packages that define which data iDNA collects from which servers.

• Address: https://<your iDNA host>/idna/config. https://<your iDNA host>/idna/ opens it as well, and the previous address /idna/cfgc redirects to it.
• Login: an iDNA account with the administrator role. On a new installation, log in with the default credentials (see Web Interface) and change the password right away (see Change Password).
• Sidebar: the pages [License], [User ID], [Server List] and [Config Manager], followed by the content packages under [Core Config] and [Optional Config]. At the bottom, [Portal] opens the iDNA Portal and [Advanced Settings] opens iDNA's system pages, each in a new browser tab; below them is the iDNA version.

The Sidebar Follows the Setup

The sidebar shows only the pages that make sense at the current stage of the setup, and the interface opens on the next page to work on:

First Setup in Short

1. Upload the license (see License).
2. Upload the Notes ID iDNA uses for the collection (see User ID).
3. Run the Config Manager: discover the servers of each Domino domain, choose the address book servers and the servers to analyze, apply (see Config Manager).
4. Check that iDNA can access every server and fix missing access rights (see Server List).
5. Set up the optional content packages you need, for example Domino Event Log or Mail Routing Activity (see Content Packages).

License

The page shows whether your license is valid and until when ([Valid thru]). If servers in your server list are not covered by the license, they are listed as [Unlicensed servers].

To upload a new license file:

1. Tick [I have read and agree to the General Terms and Conditions].
2. Choose the license file at [Upload new license file].
3. Click [Upload].

After a successful upload, [Continue to User ID] takes you to the next page.

User ID

iDNA reads the Domino Directory, the server databases and the usage data with a Notes ID that you provide. The ID needs access to all servers in scope; see System Requirements, Access and Permissions.

The page shows the ID in use ([Current ID]) and when it was uploaded ([Uploaded]). To upload an ID:

1. Click [Browse…] and select the ID file.
2. Enter the ID's password in [Password].
3. Click [Upload].

After a successful upload, [Continue to Server Discovery] takes you to the Config Manager.

Config Manager

The Config Manager sets up the data collection for one or more Domino domains: it finds the servers of a domain, lets you choose the server whose Domino Directory iDNA reads and the servers iDNA analyzes, and writes these selections to the content packages under [Core Config]:

The content packages under [Optional Config] are not changed.

Move between the steps with [Next] and [Back], or click a step in the step bar. Nothing is saved before you click [Apply Settings] in step 4. Your selections are kept while you move between the steps, but they are discarded when you leave the Config Manager without applying them.

Step 1: Server Discovery

Discovery finds the servers of a Domino domain and adds them to the server list.

1. Enter the host name or IP address of one server of the domain in [Entry server host name/IP]. An administration or hub server is recommended.
2. Click [Start Discovery].

iDNA connects to the entry server with the User ID, reads the server documents in its Domino Directory, checks its access to each server it found and adds them to the server list. The progress is shown in the log below the field; until discovery has finished, you cannot leave the step. When the message "Discovery finished." appears, continue with [Next].

• For several domains, run discovery once per domain, each time with an entry server of that domain.
• If your servers are already in the server list, you can skip discovery and click [Next].
• Servers that are not in the Domino Directory of the entry server can be added on the server list (see Server List).

Step 2: Address Book Servers

Select one server per domain whose Domino Directory iDNA analyzes; users, groups and mail-in databases are collected from this server. Select several servers of a domain only if they hold different address books.

Both this step and the next use two lists:

• [Available Servers] lists the servers of the server list that are not selected, [Active Servers] the selected ones. Move servers with the arrow buttons between the lists or by double-clicking them. [Add all →] adds every server the left list shows; [← Remove all] clears the selection.
• The filter fields above the lists narrow them by server name. [Only show accessible servers] hides the servers iDNA cannot access; these are marked with ⚠ in red.
• [Copy settings from another content package]: choose a content package as [Source] and click [Copy Settings] to take over its server selection.

When you open the step, [Active Servers] already holds the servers currently configured for Domino Directory.

Step 3: Application/Mail Servers

Select all servers iDNA should analyze. From these servers, iDNA collects basic server information, the database inventory and the Notes usage. Web usage is collected only from servers whose domlog iDNA can access; for the others, Web User Activity is not set.

When you open the step, [Active Servers] already holds the servers currently configured for these content packages.

Step 4: Review

The last step summarizes what will be applied:

• [Address Book Servers] and [Application/Mail Servers]: the selected servers and the content packages they are applied to.
• [Removed from Collection]: servers that are configured today but no longer selected, and the content packages that will stop collecting from them.
• [Not modified]: the content packages under [Optional Config], which the Config Manager leaves unchanged.

Click [Apply Settings] to save. The button then reads "Settings applied successfully".

What applying does:

• The content packages under [Core Config] are replaced with your selections.
• Servers that were already configured for a content package keep their settings there, for example a Web User Activity source set up by hand. Newly selected servers get the default settings.
• For a server you removed, collection stops. The data collected so far is kept, but it may no longer be visible in iDNA.

Adding Another Domain

1. Open [Config Manager] and run discovery with an entry server of the new domain.
2. In step 2, add the address book server of the new domain to the servers already selected.
3. In step 3, add the servers of the new domain.
4. In step 4, check that [Removed from Collection] lists no server you want to keep, and click [Apply Settings].

Server List

The server list holds every Domino server iDNA knows, whether found by discovery or added by hand. For each server, it shows whether iDNA can access it with the User ID:

• [Access]: the server itself.
• [Nab], [Log], [Catalog], [Stats], [Domlog], [Console]: the Domino Directory, the log database, the catalog, the statistics, the domlog and the server console. These columns are filled only when the server itself is accessible.

✓ means access is fine, ✗ that it is not; hover over a ✗ to see the status code. Fix missing access before you rely on the collected data.

• [Filter] narrows the list by server name or host name. Click [Domino Name], [Hostname] or [Access] to sort.
• [Manually add a server]: enter the server's host name and click [Add]. Use this for servers that discovery does not find.
• [Delete] removes a server from the list after a confirmation, for example a decommissioned server that is still in the Domino Directory.
• [Check Server Access] opens the access check in the system pages in a new browser tab. There you repeat the access check after fixing access rights, and run the extended check of the server configuration (see Content Packages - Basic Configuration, Check Server Access).

Content Packages

Content packages define what iDNA collects and from which servers. The sidebar lists them in two groups: [Core Config], the content packages the Config Manager sets, and [Optional Config]. The number next to each content package is the number of servers it is configured for. Only the content packages your license includes are listed.

Click a content package in the sidebar to open it. The page shows its description, the same server lists as the Config Manager (including [Copy settings from another content package]) and its settings. Settings that apply per server, such as [Database Path] or the Web User Activity [Type], belong to the server selected in [Active Servers]: select a server to see or change its values. A required field that is empty is marked red, and [Save] stays disabled until it is filled. [Cancel] discards your changes; Message Trace also has [Reset Configuration], which removes its configuration.

For Web User Activity with an HTTP resolver, the page asks for [Scheme], [Port], [File Path], [Username], [Password] and [Log Fields]; with form authentication also for [Action URL], [Username Field] and [Password Field].

The content packages under [Core Config] are usually set by the Config Manager. Open them directly for settings per server, such as a Web User Activity source, or to change a single content package without running the wizard.

What Changed for Existing Installations

• The configuration interface moved from /idna/cfgc to /idna/config. The old address redirects; update your bookmarks.
• Server discovery is now step 1 of the Config Manager, and the Config Manager sets the Core Config content packages in one go instead of one content package at a time.
• Your existing configuration is kept. Some content packages have new names:

Related Topics

• Installing iDNA Applications on Linux: from a prepared Linux host to the first login.
• Upgrading iDNA Applications: upgrading an existing installation to 3.5.0.
• System Requirements: what the User ID and the Domino servers need.
• Release Notes v3.5.0: everything new in iDNA Applications 3.5.0.