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.


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.


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.


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.


Improvements


Bug Fixes


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
Data Miner2.1.02.5.0
Domino (Notes-native communication)912.0.2 FP8
MCP server container–new (disabled by default)
Metabase0.50.360.62.19.5
PAC containerincludedremoved
PostgreSQL15.1615.19
Tomcat9.0.1159.0.123

What Changes for Administrators

Data Warehouse 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!