Notes DB (Magic xpi 4.7)
The Notes DB connector lets you access the IBM Lotus Notes database.
|
To be able to use the Notes DB connector with local access (when remote access is set to No), you should make sure that you have Lotus Notes Client VR5, or above, is installed on your machine. You should also know this information:
Before you locally access the Notes DB connector, you need to do the following:
-
Enter the full path of the Notes.jar file (for example, D:\lotus\notes\Notes.jar) in the Windows Environment Variables CLASSPATH or place it in Magic xpi's java/lib directory. Notes.jar file is located in the Lotus Notes clients installation folder.
-
Enter the full path to the Lotus Notes DLLs folder in the Windows Environment Variables PATH.
Before you remotely access the Notes DB Server, you need to do the following:
-
Copy the NCSO.jar to the Magic xpi machine from the Lotus Notes server and add it to the [MAGIC_JAVA]CLASSPATH (in the magic.ini) or place it in Magic xpi's java/lib directory.
-
This jar is found on Notes DB server machine at: c:\lotus\notes\data\notes\java\NCSO.jar
-
Configure the Notes DB server using SSL for remote access, as per IBM specifications.
|
The connector lets you view the available databases and perform Query, Add, Update, and Delete operations through forms and views. Global Queries can also be executed.
|
-
The Notes DB connector lets you work with Lotus Notes custom databases. To work with the standard Lotus Notes database, we recommend that you use the Domino component.
-
The Notes DB connector is not supported on all platforms. See here for more information.
-
Before accessing the Notes DB connector locally, make sure that Magic xpi's java/lib directory does not have the NCSO.jar file in it. Likewise, before accessing the Notes DB server remotely, make sure that Magic xpi's java/lib directory does not have the Notes.jar file in it. Having both the .jar files in the directory at the same time can cause a run time issue.
|
Notes DB - Configuration
Notes DB - Error Handling
Notes DB Troubleshooting