HCL Domino · Notes · API-Engine · seit den 1990er Jahren
Domino/Notes/API-Engine Development
I develop, maintain and modernize HCL Domino and Notes applications — with deep platform knowledge, long-term project experience and a dedicated API-Engine that I have designed and developed myself.
My work with Domino and Notes goes back to the 1990s. Since then, I have implemented business applications, interfaces, data migrations, automation processes and high-volume data processing solutions for productive Domino environments.
This combination of long-standing Domino expertise and my own Engine technology makes it possible to solve problems that are often difficult, slow or risky to handle with standard tools or classic LotusScript alone.
Domino expertise and Engine development
Domino/Notes development based on decades of real project experience
I have been working with Lotus Notes, IBM Domino and HCL Domino since the 1990s. During that time, I have developed and maintained business-critical applications, data workflows, interfaces, migration tools and automated processing systems for productive Domino environments.
This is not limited to surface-level application maintenance. My work covers Domino database architecture, formula language, LotusScript, C/C++ add-ins, Notes/Domino APIs, MIME processing, data conversion, replication scenarios and integration with external systems.
The API-Engine is the result of this long-term experience: a Domino server add-in and runtime environment that I developed to automate, integrate and process Domino data in a controlled and high-performance way.
Automation and integration directly on Domino
API-Engine – automation and integrations for Domino
The API-Engine is a powerful Domino server add-in developed for complex automation and integration processes. It can run directly on the Domino server and execute tasks time-based, event-driven or manually.
Scripts are stored in Domino databases and executed by the Engine. The scripting language is inspired by Notes @Functions, but extends the concept into a much broader runtime environment for data processing, logic, calculations, file handling, integrations and controlled operations on Domino documents.
Typical use cases
- Imports and exports using MySQL, SQL, XML, CSV, EDIFACT and other formats
- Automated processing of Domino databases and documents
- Selective replication using Notes-compatible selection formulas —
even between Domino databases that do not share the same Replica ID. - Exclusion or preservation of specific fields during replication
- Mass operations and batch processing on large data sets
- Data conversion between Domino and external systems
- Scheduled, event-driven and background processing on Domino servers
Technical depth
More than scripting: a dedicated runtime for Domino data processing
Many Domino automation tasks start as LotusScript agents. Over time, however, they often grow into complex processes involving large document counts, external interfaces, transformations, error handling, logging and scheduled execution.
The API-Engine was developed to handle exactly these situations. It provides a structured runtime for recurring processes and makes it possible to execute complex operations in a controlled, traceable and performant way.
Areas of expertise
Domino application logic
Development and modernization of Notes/Domino applications, including forms, views, agents, formulas, workflows and business logic.
Server add-ins and APIs
Low-level Domino development with C/C++, Notes APIs and server-side processing where standard application techniques are not sufficient.
Data integration
Interfaces between Domino and SQL databases, web services, files, mail systems and structured exchange formats.
Migration and conversion
Controlled conversion of grown Domino data structures, legacy formats, attachments, MIME content and document metadata.
High-volume processing
Processing of large NSF databases and high document counts with logging, statistics and reliable error handling.
Replication scenarios
Selective replication, synchronization and field exceptions — also between Domino databases without a shared Replica ID.
Integration, use cases and projects
For organizations that continue to rely on Domino
Many companies still operate Domino as a central and reliable backend for workflows, document management, archiving, business processes or specialized applications. Replacing these systems is often expensive, risky and not always necessary.
With the API-Engine, existing Domino environments can be extended, automated and connected to modern system landscapes without immediately replacing working business-critical applications.
Who this is designed for
- Organizations that continue to use Domino productively
- Companies with mature or highly customized Notes applications
- Businesses with heterogeneous system landscapes
- Customers using Domino as a backend for workflows, archiving or ERP integrations
- Organizations that need stable integrations instead of a risky full migration
Licensing and project work
The API-Engine is distributed and licensed through SL Net-Solutions GbR. In customer projects, I use it to design and implement scripts, data workflows, integrations and processing logic tailored to the specific Domino environment.
Summary
My Domino/Notes development experience and the API-Engine complement each other: long-standing platform expertise, deep technical understanding and a dedicated automation platform for demanding Domino environments.
This allows existing systems to be modernized, integrated and extended — without media disruptions, without unnecessary migration pressure and without losing the strengths of Domino.