by Robert Perron, Steve Nikopoulos, and Kevin Smith

Level: Advanced Works with: Notes/Domino Updated: 01-Jul-2003

• lotus.domino.local to service the call from Notes/Domino software on the same computer
• lotus.domino.cso to service the call from a Domino server accessed through a remote connection

• The client obtains the server's initial object as an IOR (Interoperable Object Reference) using the HTTP protocol.
• The client obtains further objects over an IIOP connection.

• Execute threads through inheritance
• Execute threads through the Runnable interface
• Execute threads through the static methods

public static void main(String argv[])
{
myClass t = new myClass();
t.start();
}
public void runNotes() // entry point for Notes thread
{
try
{
Session s = NotesFactory.createSession();
// Operational code goes here
}
catch (Exception e)
{
e.printStackTrace();
}
}
}

public static void main(String argv[])
{
myClass t = new myClass();
NotesThread nt = new NotesThread((Runnable)t);
nt.start();
}
public void run() // entry point for thread
{
try
{
Session s = NotesFactory.createSession();
// Operational code goes here
}
catch (Exception e)
{
e.printStackTrace();
}
}
}

public static void main(String argv[])
{
try
{
NotesThread.sinitThread(); // start thread
Session s = NotesFactory.createSession();
// Operational code goes here
}
catch(Exception e)
{
e.printStackTrace();
}
finally
{
NotesThread.stermThread(); // must terminate every thread
}
}
}

• Within a session, Domino Objects are shared, synchronized, and recycled across threads. Using a different session on each thread loses these capabilities; you must explicitly manage synchronization and recycle on a per-thread basis.
• Do not use DbDirectory across threads.
• Accessing an existing document on multiple threads is permissible, but accessing it on just one thread simplifies memory management. Restricting access to one thread allows you to recycle without checking the other threads. Creating documents across threads is always safe, and these objects can be recycled without reference to the other threads.
• Profile documents are cached on a per-thread basis. In the event of an update contention, the last thread updating takes precedence.
• Take care not to delete a document needed for navigation by a view or by a collection on another thread.
• When child objects are used on threads other than the parent, keep the parent thread alive until all child threads terminate. This is particularly important when using Domino Objects in AWT event handlers.

public static void main(String argv[])
{
try
{
String host = "myhost.east.acme.com:63148";
Session s = NotesFactory.createSession(host);
// Operational code goes here
}
catch(Exception e)
{
e.printStackTrace();
}
}
}

public static void main(String argv[])
{
myClass t = new myClass();
Thread nt = new Thread((Runnable)t);
nt.start();
}
public void run()
{
try
{
String host = "myhost.east.acme.com:63148";
Session s = NotesFactory.createSession(host);
// Operational code goes here
}
catch(Exception e)
{
e.printStackTrace();
}
}
}

public static void main(String argv[])
{
try
{
FileInputStream fin = new FileInputStream(
"c:\\Lotus\\NotesR6\\diiop_ior.txt");
InputStreamReader fisr = new InputStreamReader(fin);
BufferedReader br = new BufferedReader(fisr);
String ior = br.readLine();
fin.close();
Session s = NotesFactory.createSessionWithIOR(ior);
//Operational code goes here
}
catch(Exception e)
{
e.printStackTrace();
}
}
}

• Changing a DIIOP port number
• Enabling or disabling a DIIOP port
• Changing the TCP/IP address

• A name and the associated Internet password in a Domino Directory
  This works for local or remote access. For local access, the computer running the code must be configured as a Domino server.
• The current Notes ID (as specified by the KeyFilename variable in Notes.ini)
  This works only for local access. The computer running the code can contain either a Notes client or a Domino server.

Access through a Notes ID
For access through the current Notes ID, specify no parameters:

Session s = NotesFactory.createSession()

In this case, a dialog box requests the password for the Notes ID when authentication (for example, access to a database) is required. The Notes ID chosen is that specified by the KeyFileName variable in the first Notes.ini file on the search path. The user must enter the correct password or click Cancel to continue.

Instead of specifying no parameters, you can specify the second parameter as null (cast to a String) and the third as the password for the Notes ID:

Session s = NotesFactory.createSession((String)null, (String)null, "tops3cr3t")

On servers, the above methods restrict access according to Readers fields. For full access, use the following methods:

Session s = NotesFactory.createSessionWithFullAccess()

or

Session s = NotesFactory.createSessionWithFullAccess("tops3cr3t")

Conclusion
You now know the basics of using the Domino Objects from a Java application locally and remotely. In the next article, you will learn about SSL encryption, servlets, connection pooling, single sign-on, firewalls, timeouts, recycling, and troubleshooting.


ABOUT THE AUTHORS
Robert Perron is a documentation architect with Lotus in Westford, Massachusetts. He has developed documentation for Lotus Notes and Domino since the early 1990's with a primary concentration on programmability. He developed the documentation for the LotusScript and Java Notes classes and coauthored the book 60 Minute Guide to LotusScript 3 - Programming for Notes 4. He has authored several LDD Today articles. Last year he authored "A Comprehensive Tour of Programming Enhancements in Notes/Domino 6" for The View.

Steve Nikopoulos is a Senior Software Engineer with the Domino Server Programmability team. His most recent work includes the remoted Domino Objects, Domino/Websphere integration, and single sign-on. In his spare time, he enjoys bike riding with his family.

Kevin Smith is an Advisory Software Engineer in the IBM Messaging & Collaboration Development organization in Westford, currently responsible for programmability features of the Domino server. He joined Lotus in 1990 as a technical support engineer for Lotus 1-2-3/M, the famous PC spreadsheet ported to the famous IBM mainframe, one of the earliest IBM-Lotus engineering ventures.