Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleSummary
  • Read-only towards Domino. iDNA creates, changes or deletes no documents, designs or ACLs in your databases and runs no agents. The only console command it sends is show config *, which lists the server's notes.ini settings.
  • Connections start at the appliance: Notes RPC (TCP 1352) to your Domino servers, and HTTP or HTTPS to a Domino web server if web logs are read as text files.
  • From system databases: the Domino Directory, server documents and notes.ini settings, log.nsf, catalog.nsf and domlog.nsf. With the optional packages, also the DLAU and MarvelClient Analyze databases.
  • From application databases: the design and source code of focus applications Focus Applications and templates, the database's record of user activity, profile documents Profile Documents in full, and document metadata. No other document content, and no attachment contents.
  • Personal data: Notes user names, directory data about people and groups, IP addresses and client details from web logs and MarvelClient, mail addresses from the router's log. Stored on the appliance and pseudonymized in the analyses by default.
  • Data stays on-prem: collected data is processed and stored on the appliance in your network. It only leaves when you choose: results for your AI assistant if you enable the MCP server, alerts and report subscriptions by email, and support bundles or license requests an administrator sends.

...

AccessWhereUsed for
Access to the serverEvery HCL Domino server in scopeAny collection from that server
ReaderThe Domino Directory (names.nsf) on one server per domain, and by default the directories configured in Directory AssistanceThe Domino Directory package
Readerlog.nsf and catalog.nsf of every server; domlog.nsf where web logging to it is enabledThe Server Basics, Database Catalog, Notes Client Activity and Web User Activity packages; the optional Domino Event Log and Mail Routing Activity packages
Full Remote Console AdministratorServer document of every server in scopeThe console command show config * and the console part of the server access check
Designer, or Full Access AdministrationDesigner in the ACL of every focus database Focus Database and template; or Full Access Administration in the server documentDesign analysis. Where the ID has Full Access Administration, iDNA uses it by default. Reader access is the minimum for a database to be opened at all.
ReaderThe DLAU result database; the MarvelClient Analyze databaseThe optional HCL DLAU and MarvelClient Analyze packages
Reader, or Full Access Administration where the ID has itEach database a content scan is started forContent analysis
  • Full Access Administration lets the ID open every database on that server whatever its ACL says, mail files included. iDNA uses it to read designs. Designer access per database is the narrower alternative.
  • Servers of other organisationsorganizations: iDNA collects only from servers certified by an organisation organization named in your license. Other servers it finds are listed as unlicensed and not collected. Multiple certifier names can be included in a license.
  • Server prerequisites (the Catalog and Statlog tasks, session logging, the web log format) are listed in System Requirements.
  • The ID file and its password are stored on the appliance, so that iDNA can collect without anyone logged in. See Data Flow in Detail, Storage on the Appliance.

...

  • Content packages, set up per server in the admin interface (see Admin Interface and Config Manager). Each package reads one kind of data from the servers it is active on.
  • Design analysis of focus databases Focus Databases and templates, with the activity record, profile documents Profile Documents and content age of each focus databaseFocus Database.
  • Content analysis, started by an iDNA user for a single database.

...

PackageRead fromWhat is readPersonal data
Domino Directorynames.nsf on one server per domain; directories in Directory AssistancePerson documents, group documents (with members and owners), mail-in database documentsNames, organisational organizational data and mail and internet addresses of people; group memberships
Server BasicsEvery server in scopeServer documents, connection documents, notes.ini settings (through show config *), server statistics (hourly)Administrator names in server documents
Database CatalogEvery server in scope; catalog.nsf, log.nsfThe list of databases with their properties (title, file path, replica ID, template, size, dates), catalog entries, the number of ACL entries per access level, database activity countsNone: ACL entries are counted, not stored by name
Notes Client Activitylog.nsfSession records: who opened which database on which server, when, with read and write counts (every 2 hours)Notes user names
Web User Activitydomlog.nsf, or text web logs over HTTP or HTTPSWeb requests: user name, client address and host name, user agent, requested URL, time. Cookies and referrers are not stored.User names, IP addresses, host names
MarvelClient Analyze
(optional)
The MarvelClient Analyze databaseClient records: Notes user name, home server, Notes and MarvelClient versions, operating system, operating system user name, IP addressAll of these
HCL DLAU
(optional)
The DLAU result databaseIts documents in full, rich text includedUser names and the licensing data DLAU recorded about them
Domino Event Log
(optional, licensed separately)
log.nsfEvents and security events: time, type, severity, server task and message textNames that appear in event messages
Mail Routing Activity
(optional, licensed separately)
log.nsfThe router's transfer and delivery events: sender, recipients, size, timeMail addresses

...

Design analysis covers the focus databases Focus Databases and one replica of each template. Focus databases Databases are the databases of type Application and Mail-in, as classified from the catalog. You can adjust the classification with recategorization rules. Design analysis runs one database at a time. It re-reads a design when it has changed, by default weekly on Saturday.

SourceRead fromWhat is readPersonal data
DesignFocus databases Databases and templatesThe full design, exported as DXL. It contains every design element and its code (LotusScript, Formula language, JavaScript, Java, XPages) with names, comments, signers, last modifiers and dates. It also contains the database properties and the ACL with its entries, roles and log. iDNA keeps the export on the appliance as a compressed file. No data documents.Names of signers, modifiers and ACL entries; anything developers wrote into the code, such as names, addresses or credentials
User activity recordFocus databases Databases and templatesThe activity that Notes records in each database: user names, dates, reads and writesNotes user names
Profile documentsDocumentsFocus databasesDatabasesEvery profile document Profile Document in full: all items and their values, its modifiers and revision datesWhatever the application stores in its profile documentsProfile Documents; modifier names
Content ageFocus databases Databases (content-age module)The number of documents and their creation and modification dates, stored as counts per month. No item values, no form names.None

...

  • Application documents: metadata only, except profile documentsProfile Documents, which are read in full.
  • Mail files: listed in the database inventory and seen in the session records. Design analysis, profile documents Profile Documents and content age do not open them, because mail files are not focus databasesFocus Databases.
  • Mail messages: Mail Routing Activity, which is not enabled by default and is licensed separately, reads the router's log entries and takes sender, recipients, size and time from them. It reads no subjects and no message bodies.
  • Rich text and attachments: not read, with two exceptions: DLAU documents are read in full, and content analysis reads attachment names, sizes and dates.
  • Source code: read and stored in full, including whatever developers wrote into it.

...

Personal dataRead from
Notes user namesSession records, web logs, events, the user activity records of databases, ACLs, design signers and modifiers, profile documentsProfile Documents, DLAU and MarvelClient records
Data about people and groupsPerson documents and group documents in the Domino Directory
IP addresses and client detailsWeb logs (client address, host name, user agent, requested URL); MarvelClient records (IP address, operating system user name)
Mail addressesThe router's log (Mail Routing Activity); the Domino Directory
Values written by applications or developersProfile documentsDocuments, event messages, source code

...

A trial license reads from the same sources, with the same access, as a full license. This includes the content packages and the design of every focus database Focus Database and template, which iDNA exports and keeps as described above. The differences:

  • Source code: depending on license options, source code from a subset of databases is analyzed.
  • Profile documents Documents and content age are read only for the trial sample.
  • The trial sample is a set of up to 50 focus database Focus Database instances that iDNA selects itself from the middle of the pack in usage and complexity. iDNA recomputes it every night, so it can change while usage data build builds up. You cannot choose it.
  • Content analysis works as on a full license.

...