Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Colleague review: wording

...

The configuration interface is where you tell iDNA what to collect and from where: the license, the Notes ID that 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.

...

StageSidebar showsOpens with
No license uploaded[License][License]
License uploaded, no User ID[License], [User ID][License]
User ID uploaded, no servers yetalso [Server List] and [Config Manager][Config Manager]
Servers in the server listalso the content packages under [Core Config] and [Optional Config][Server List]

First Setup

...

at a Glance

  1. Upload the license (see License).
  2. Upload the Notes ID that iDNA uses for the collection (see User ID).
  3. Run the Config Manager: discover the servers of in each Domino domain, choose the address book servers and the servers to analyze, apply then click [Apply Settings] (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).

...

To upload a new license file:

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

...

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

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

...

Server List

The server list holds shows every Domino server iDNA knows about, whether found by discovery or added by handmanually. 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 in only when if the server itself is accessible.

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

...