Error rendering macro 'rw-search'

null

Downloads

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

panagenda is proud to announce this new release of iDNA Applications. Whether you’re in a Notes/Domino modernization or migration project, iDNA gives you the knowledge to deliver the most difficult projects efficiently, on time and on budget.

This new version is a significant milestone release, as it introduces a ton of new features in the application itself and opens a new chapter when it comes to setting up iDNA Applications. In addition, this release packs a significant number of updates in underlying components along with lots of new features, improvements and bug fixes.

No More Virtual Appliance Images

As of version 3.5.0, panagenda no longer supplies virtual appliance images for VMware or Hyper-V. iDNA Applications now runs on a Linux host that you provide, installed with the panagenda installer. This gives you more flexibility in choosing your virtualization platform and makes it easier to keep the operating system iDNA runs on up to date.

Existing appliances keep running and are upgraded with the same installer. See Running iDNA Applications on Your Own Linux Host for the details.



New Features

Application Lifecycle

The new [App Lifecycle] menu answers four questions about every application in your Notes/Domino estate, in this order: keep it or sunset it? Which route leads to ready? How ready is the estate? What is the plan?

iDNA classifies each application with a lifecycle vector (for example Keep/Modernize, Sunset/Archive or Sunset/Delete) and a modernization vector, shows how ready the whole estate is, and turns the remaining work into a ranked modernization plan of work sessions, down to the individual code blocks. Template lineage shows which standard template a customized design comes from and what was changed in it. The modernization topics are Notes 64-bit and Nomad.

Read more in Application Lifecycle in iDNA Applications and its pages on the Lifecycle Vector, the Modernization Vector, Modernization Readiness and Modernization Planning.

MCP Server

iDNA Applications now includes an MCP server. MCP (Model Context Protocol) is the open standard through which AI assistants access external data. With the MCP server enabled, AI clients such as Claude, GitHub Copilot or OpenAI Codex answer questions about your Notes/Domino estate from your live iDNA data.

The MCP server is read-only and disabled by default. It runs on your iDNA host and is reached through the existing HTTPS port. Every user authenticates with their own token, and administrators see and revoke all tokens in one place. Your license sets the mode, restricted or permissive, and iDNA enforces it regardless of the AI client or model.

MCP is free of charge and requires a double opt-in: your organization requests an MCP license from panagenda, and your iDNA administrator enables the service. See Setting up the MCP Server in iDNA Applications.

iDNA Applications Companion

The iDNA Applications Companion is an AI-assistant plugin for Notes/Domino estate analysis: usage, modernization, source-code remediation and application lifecycle. It adds a curated knowledge wiki and analysis guidance to your AI client and, once connected to the MCP server, answers from your live iDNA data. Without the connection it answers from the wiki only and tells you so.

The Companion is installed from panagenda’s plugin marketplace on GitHub and supports Claude (Cowork and Claude Code), GitHub Copilot (App and CLI) and OpenAI ChatGPT/Codex (app and Codex CLI). See Setting up the iDNA Applications Companion.

Run iDNA Applications on Your Own Linux Host

Starting with version 3.5.0, iDNA Applications runs on a Linux host that you provide. You prepare the host with a Linux distribution and Docker; the panagenda installer sets up iDNA Applications on it as a set of Docker containers, online or from an offline package. The same installer upgrades existing installations, including the existing VMware and Hyper-V appliances.

Read more in Running iDNA Applications on Your Own Linux Host (requirements, recommended distributions, sizing and partitioning), Installing iDNA Applications on Linux and Upgrading iDNA Applications.

New Configuration Interface and Config Manager

iDNA’s configuration interface has been rebuilt. It opens at https://<your iDNA host>/idna/config and has pages for the [License], the [User ID] iDNA uses for collection, the [Server List] and the [Content Packages] that define what iDNA collects. The previous address /idna/cfgc redirects to it.

The new [Config Manager] wizard sets up the collection for a Domino domain in four steps:

  1. [Server Discovery]: connect to one entry server of the domain (recommended: an administration or hub server); iDNA reads its Domino Directory and lists all servers of the domain.
  2. [Address Book Servers]: choose the servers whose address books iDNA reads.
  3. [Application/Mail Servers]: choose the servers whose applications and mail databases iDNA analyzes.
  4. [Review]: check the selection and apply it.

The wizard applies the matching content packages in one go, which replaces setting up each package by hand for a first setup. Run it again to add another domain. The content packages themselves now carry clearer names and descriptions.


Improvements

  • Metabase 62: The embedded dashboarding and reporting solution Metabase has been upgraded to one of the latest versions. Read more about the new capabilities of Metabase 62 in their official announcement blog post. The embedded dashboards have been restyled to match, and clicking through from an embedded dashboard now opens the full Metabase dashboard or question in a new browser tab, with the current filters kept.

  • Metabase Site URL and AI Features: Metabase’s site URL is now set from the iDNA host name. If users reach iDNA through an alias, a reverse proxy or another port, set PANAGENDA_METABASE_SITE_URL in the configuration file. Metabase’s own AI features are disabled by default and can be enabled only through the configuration file (PANAGENDA_METABASE_AI_FEATURES_ENABLED).

  • Domino 12.0.2 FP8: iDNA’s backend utilizes a greatly reduced subset of a Domino server’s data and binary directories for Notes-native communication. This server never starts and cannot start, but when iDNA communicates with Domino servers for collection, it appears like a Notes Client for those Domino servers, carrying the version this stub Domino server inside iDNA is set up with. Since the previously used Domino 9 server was long outdated, this change was made with security and stability in mind.

  • Code Insights Detection Patterns: 22 detection patterns of the shipped rule sets were corrected. Counts rise for Definite and Possible dependencies on other databases, External C Calls, Addressbook related code, Calendar related code, What’s new in Notes 10.0.1 and Paper Printing, and a little for Mail Send, Working with files and Working with other programs; Calendar related code and What’s new in Notes 10.0.1 find code for the first time. Hardcoded IP Addresses (version strings no longer match) and Pro: Javascript and HTML tags drop slightly; External C Calls can also drop on some estates (forward declarations no longer match). Insights scores and ranks of the affected databases change with the first nightly run after the update.

  • Notes 64-bit and Nomad Insights: New insights detect Windows/32 platform literals, LS2J, Java EE and CORBA classes removed from current Java, NotesHTTPRequest web methods and GetAllEntriesByKey, and several existing detections are more precise. Findings now show their severity, and findings in code that HCL itself ships in its current standard templates count as notes rather than as work for you.

  • Standard Templates: The catalog of HCL standard templates used for template comparison now covers releases up to Notes/Domino 14.5, including HCL DART and the DLAU template, as well as older Notes 5–7 templates.

  • Code Element Details: Findings name the code element more precisely, for example Script Library → Code instead of Script Library → Script Library, Java code by its file name, and formulas such as hide-when formulas by their position and event (for example pardef[4] > hidewhen).

  • Insights Overview Exclude: A database whose custom property [Insights Overview Exclude] is set to Exclude is now left out of every insights result (scores, ranks and summaries), not only out of the overview.

  • Content Age per Replica Set: The replica set data now include a content age summary: scan status, retention configuration, cutoff date and the number of documents within the retention period.

  • Insights per Replica Set: New views in cqx_data summarize Code Insights per replica set, overall and for Notes 64-bit and Nomad, which makes them easier to query in Metabase or SQL.

  • View Usage: The new cqx_data view dbviews_used lists the views of each database that have a built index, that is, views that have actually been used.

  • Activity History: Weekly activity per application, by department and by location, is now available in cqx_data.

  • Unique Titles: Unique replica set titles now carry the replica ID instead of a hash, which makes them readable and searchable.

  • Log Download: Administrators download the system logs as a zip file directly in iDNA ([Download Logs], https://<your iDNA host>/idna/sys/logs). The separate PAC container that offered the log download before has been removed; the old address /pac/logs redirects to the new page.

  • Installer: The installer shows the installed and the target version and waits 10 seconds before it starts, so you can still cancel. If an upgrade fails, it prints the exact rollback commands, and it recovers from an interrupted container teardown. New commands: ifa recreate, ifa diagnose-network and ifa uninstall (see The ifa Command).

  • User Names: User names at login are no longer case-sensitive, and leading or trailing spaces are ignored; users are signed in under their stored name. A login through the LDAP fallback updates the existing account instead of creating a second one.

  • Security: Request-forgery protection now covers all administration pages, role permissions are enforced on the server, query handling has been hardened, disabled accounts can no longer sign in, error pages no longer echo request details and session IDs no longer appear in URLs. Numerous third-party libraries were updated, and unused ones removed.

  • Pseudonymization: With user-name pseudonymization enabled, each person now has one pseudonym across all user-related data.


Bug Fixes

  • Complexity Overview: Templates of the new server versions were added, and an issue with the navigation drop-down was fixed.

  • Insights Scores: Insights with several topics were counted three times and weighted nine times in scores and summaries; this affected the 2017 mail insights. Scores and ranks of the affected databases change with the first nightly run after the update.

  • Missing V14 Java Classes: The insight no longer reports com.sun.net.httpserver, which still exists in Java 17.

  • Last Write Access: The last write access of a replica set showed the last access instead. Replica sets without write activity now show no write date.

  • Content Age: After a failed content age scan, the results and the scan time of an earlier scan were still shown.

  • Usage Dashboards: Filtering from one usage dashboard to another failed for some applications because their titles were formatted inconsistently.

  • Container Health: A hung DDA container now restarts on its own instead of staying unhealthy, and the cron container restarts when its scheduler stops.

  • Configuration File: The installer no longer corrupts a hand-edited configuration file that lacks a final line break.

  • Fresh Installation: A timing issue could leave the iDNA database partly initialized after a fresh installation.


Structural Changes / Upgrade Path

Component Upgrades inside Containers

Virtually all Docker images/containers have undergone significant updates in outward-facing components and underlying libraries. This provides a significant improvement in performance, stability and security.

Component3.3.x3.5.0
Metabase0.50.360.62.19.5
Domino (Notes-native communication)912.0.2 FP8
Tomcat9.0.1159.0.123
PostgreSQL15.1615.19
Data Miner2.1.02.5.0
MCP server container–new (disabled by default)
PAC containerincludedremoved

What Changes for Administrators

  • Configuration address: The configuration interface moved from /idna/cfgc to /idna/config. The old address redirects; update your bookmarks.

  • Log download: Logs are downloaded in iDNA under [Download Logs] (administrator login required). The PAC container and its Tomcat manager are gone.

  • User names: User names are no longer case-sensitive. If two accounts differ only in upper and lower case, only one of them can sign in; merge such accounts.

  • Disabled accounts are now refused at login, including through the LDAP fallback and the external API.

  • Role permissions: Role permissions are now enforced on the server. The log download, the ETL refresh and the notification settings require the Administrator role; changes to Custom Insights require the Administrator or Editor role. Give users who need these functions the matching role.

  • Metabase content: The upgrade replaces the dashboards and questions panagenda ships. Make your own changes in copies, not in the originals.

  • Metabase site URL: Set PANAGENDA_METABASE_SITE_URL in the configuration file if users reach iDNA through an alias, a reverse proxy or another port.

  • Docker: Docker Compose v2 (docker compose) is required. ifa customize no longer changes Docker’s storage location and now does the same as ifa recreate; the configuration keys PANAGENDA_DOCKER_BRIDGE and PANAGENDA_DOCKER_GRAPH are deprecated.

  • Custom queries on cqx_data: Code element names in findings have changed (see Code Element Details above), [Insights Overview Exclude] removes a database from every insights result, and with user-name pseudonymization enabled the pseudonyms change once with the first nightly run. Check saved questions and filters that rely on them.

Data Warehouse Rebuild Required

DWH Rebuild Required

After installing the update, parts of the application may not be available until the data warehouse is rebuilt. This process runs automatically at night, but can be triggered manually after the update. On the first login after the installation, more information on this topic will be displayed, along with the option to trigger the rebuild.

With 3.5.0, the rebuild also recalculates the Code Insights findings, so insights scores and ranks change in that run. From then on, the nightly processing takes a few minutes longer because of the new modernization and template lineage steps.

Upgrade Procedure: Container Installer

Details on how to update to this new version can be found in the knowledge base article Upgrading iDNA Applications. Back up the database before you upgrade, as described there. The upgrade from 3.3.x to 3.5.0 has been tested.


Visit our site to start your evaluation right now!