As IBM sold the Notes and Domino assets to HCL in 2019, the previous method (we’ve kept the details below) of using an ODBC Connector to Domino is not available from IBM or HCL.
The new way is to enable REST and Domino Access Services, available since Domino 9.0, to pull data from NSF databases and expose the data as an entity within OutSystems.
Our partner T4S has built a Forge component (with documentation!) to allow any OutSystems developer to use Domino as a data source for an OutSystems application. This could be for using the Domino data in another application or could be for migration purposes.
An overview of what T4S has created is here
Find all the documentation and the connector here
An example of an OutSystems application that connects to Domino is here
A detailed webinar/walkthrough of the components is here.
<The below method is no longer supported or available>
Recently I've come across a few customers that were looking into ways to integrate new OutSystems applications with existing data from legacy Lotus Notes / Domino applications that were still being used.
Two options came up as the most promising ones
This How To focuses on the second option, specifically abstracting the Platform from the ODBC connection details by creating a Linked Server in MS SQL Server (an alternative here would be to perform the ODBC work inside an extension). I've researched a number of instructions available on the web and I've tested the steps to created a linked server but none of tutorials we I found seemed explain well enough what you need to do. Below you can find the steps I've learned through these experiments. I've actually tested them from start to finish in clean environment to make sure they worked just fine.
One more thing... For the OutSystems applications to be able to access the data of the linked server in runtime you need to change the permissions of the OSRuntime database user. This user is the one used to access data by the running applications.
Hi Peter,
Actually if I recall correctly you can use the exact same mechanism to connect to remote databases.
The key difference should be in step 6 to configure a remote datasource instead of a local file.
Cheers,
Pedro
Hi Pedro,
do you know about solution how to connect to domino database that is not local?
Is there any way how to use this solution to connect non local database?
Thanks
Hello Pedro,
Thanks for this useful article. Now I have nsf file on my local machine and lotus notes. I installed API notessql, SQL server and management studio on my local machine. when I configured ODBC administrator for pointing to nsf file, it crashed and the below error appear :
Problem signature: Problem Event Name: BEX Application Name: odbcad32.exe Application Version: 6.1.7600.16385 Application Timestamp: 4a5bcd4c Fault Module Name: NLNVP.DLL_unloaded Fault Module Version: 0.0.0.0 Fault Module Timestamp: 57d36c1f Exception Offset: 51b82f4f Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789Can you assist me in solving this issue?
Hi all,
Is it possible to implement option 2 (Linked Server) on a cloud environment (enterprise, not the personal) ?
Thanks in advance,
Pedro Moita
Option 2 should be possible but does imply an additional redirection as you cannot manipulate the database which is managed by OutSystems.
The steps should be something in the line of
That should do it!
Thanks Pedro!
Pedro,
Great piece of information...!
I have worked through this solution on my end and have everything in place to extract data in MS Excel using a 32 bit ODBC driver as a bridge.
I have a requirement to pull some legacy data from Lotus Notes and at the moment I am working through a 32 bit Lotus Notes Client.
From my local machine I have been able to read NSF file using 32bit Lotus Notes ODBC driver.
I have been unsuccessful to link the 32bit ODBC driver reference from SSMS based on the working 32bit ODBC references or the sample NSF file you provided.
Can you share any information on the 32bit side and if it is possible.
Many thanks in advance.