The Domino plug-in provides end-users with SSO access to all applications on Domino servers, creating convenience and saving login time. The Domino plug-in now offers two methods for SSO capabilities: Kerberos or proprietary cookies, both of which optionally allow authentication utilizing a Personless NAB.

Enabling SSO to Domino HTTP servers via Kerberos requires connectivity to a central Key Distribution Center (KDC). In Windows, each Active Directory domain controller acts as a KDC. Users authenticate themselves to services (e.g. Domino servers) by first authenticating to their Windows machine using a domain account, then requesting encrypted service tickets from the KDC for the specific services they wish to use. This last step is performed automatically by the user's web browser. Only the service (and the KDC) can decrypt the service ticket to get the user's information. Because only the KDC could have created the service ticket, the service knows that the user must have also authenticated to the KDC so it can trust the user credentials in that ticket.

Alternatively, to enable SSO to Domino HTTP servers, a web browser toolbar creates client-side cookies with encrypted credentials for each of the Domino servers listed in the Password Power configuration file. Accessing a Domino server through a web browser automatically sends the corresponding cookie with the request. These same cookies can also be used to grant SSO to IBM Lotus QuickPlace and Sametime, IBM WebSphere and WebSphere Portal and SAP Netweaver. These in-memory session cookies have a configurable expiration interval that defaults to 12 hours. When the end-user closes the browser, logs out or shuts down Windows, the cookies are automatically destroyed.

The Domino plug-in also supports a Personless NAB allowing the end-user to logon to Domino HTTP with their network directory (e.g. Microsoft Active Directory) credentials to access all Domino HTTP solutions, including Lotus iNotes, Sametime, QuickPlace, and Domino Web applications. Browser-only end-users no longer need a duplicate set of Person documents as the Domino plug-in requires that the end-user be defined only once in Active Directory (users of the stand-alone Notes client would still need Person documents to support encryption and signatures). The Personless NAB approach also leverages Domino's Directory Assistance, which allows an end-user access token to contain their Active Directory name and any Active Directory groups to which they belong. The central role in this approach is performed by a DSAPI filter which can give SSO and overrides the normal authentication process, which checks the username and password against the Domino Directory.

This functionality solves many of the username mapping issues associated with authenticating against remote directories without requiring changes to the LDAP server accounts or Domino Directory. Redirecting web authentication requests from the Domino Directory to a different LDAP directory also eliminates the need to maintain or synchronize the Domino Internet password, as its presence and upkeep are no longer required. This functionality extends to affect all Domino HTTP authentication including QuickPlace and Sametime.

PistolStar's Password Power Notes ID plug-in removes the need for separate passwords and repositories for the Notes ID file by configuring the Active Directory as the central password authentication point for accessing the Lotus Notes Client, thus eliminating the need to separately maintain the Notes ID password.

The Notes ID plug-in provides synchronization between Active Directory and the Notes ID File and allows forgotten Notes ID file passwords to be automatically recovered and resynchronized with the Active Directory.

With PistolStar's Password Power Notes Id plug-in, a successful authentication to Microsoft Active Directory, Novell eDirectory, Lotus Domino LDAP, Tivoli Directory Server or Sun ONE LDAP grants access to the Lotus Notes client. This effectively eliminates the manual Notes ID password recovery by allowing a reset of the LDAP password to restore access to Lotus Notes. Password synchronization between LDAP and the Notes ID file is always performed for times when the LDAP server is unreachable.

This plug-in synchronizes multiple passwords via a web browser. This allows end-users to synchronize Windows, HTTP, LDAP passwords and Notes ID File. This increases security because having only one password to commit to memory decreases the likelihood end-users will write it down and become a target for internal intruders.

For more information about PistolStar and Password Power 8 plug-ins please visit our websitewww.pistolstar.com. Or you may contact:

PistolStar, Inc.

PO Box 1226

Amherst, NH 03031 US

(603) 546-2300

Notes professionals often prefer to create and manage their reports programmatically using Lotus Script. This approach ensures that data security and integrity are preserved, the business context is inherited, and the Notes application workflow is kept intact. While it overcomes many limitations set by non-native reporting tools, reporting using Lotus Script does have a few limitations:

This approach is time consuming, expensive and end-user unfriendly. In most situations, user request for reports cannot be met due to the effort involved in producing the report and the poor presentation quality of the reports.

There are a wide variety of report creation tools with extensive functionality that are available for use with Notes and Domino. However, most of these are not native to the Notes and Domino framework. These tools connect to Notes data by using ODBC drivers or by exporting Notes data to other formats such as spreadsheets. Limitations posed by these approaches include:

IntelliPRINT started as a printing solution for Notes and Domino and has matured to become one of the best reporting solutions in its current release, which was launched at Lotusphere 2007. It has also been extended to natively support Notes/ Domino 8 while continuing support for Notes versions 6 and 7.

IntelliPRINT Reporting is to Notes and Domino what Crystal Reports was to Visual Basic. It is a native reporting component that is tightly integrated with the Notes and Domino application framework. It is a logical extension to Notes and Domino and lets you use its APIs to tightly integrate the reports within the workflow of your Notes and Domino applications.

As the report format is stored as a Notes document, security settings for report access as well as row level access are automatically inherited from the Notes ACL. The report is then presented as a Notes tab making the reporting workflow integral to your application workflow.

The key features that make it a logical extension of Notes and Domino are listed below and include details of the steps involved in creating a simple report and a complex report.

To sum up, here's why IntelliPRINT Reporting can help you improve the productivity of your reporting system:

All of these make IntelliPRINT Reporting the product of choice for reporting and printing with Lotus Notes and Domino applications.

For more information on IntelliPRINT, please visithttp://www.synaptris.com/go/intelliprint.

To make it easier to administer, the Archiver installation is automated as much as possible. The setup process below is followed for each database included in the Archive:

Sub Initialize
Dim s As New NotesSession
Dim db As NotesDatabase
Dim agent As NotesAgent
Dim doc As NotesDocument
Set db = s.CurrentDatabase
Set doc = ... Set the document object containing the Database Replica ID
Set agent = db.GetAgent("BuildIndex")
Call agent.RunOnServer(doc.NoteID)
End Sub

Sub Initialize
Dim s As New NotesSession
Dim db As NotesDatabase
Dim targetDB As New NotesDatabase("", "")
Dim agent As NotesAgent
Dim doc As NotesDocument
Set db = s.CurrentDatabase
Set agent = s.CurrentAgent
Set doc = db.GetDocumentByID(agent.ParameterDocID)
If Not (doc Is Nothing) Then
replicaID$ = doc.DBReplicaID(0)
If targetDB.OpenByReplicaID("", replicaID$) Then
Call targetDB.CreateFTIndex(23, False)
End If
End If
End Sub

During setup, we created a replica on the Archive Server (the Archive Replica) and a copy of that replica (the Archive Store), for each production database.

A scheduled agent in the Archiver checks each Production database for any changes made to eligible documents (i.e. those matching the Archive @formula for the Database) since the last time replication occurred, using the Search method of the NotesDatabase class - the Search method allows reasonable search performance using time/date criteria within databases that may or may not be Full Text Indexed.

For any document that has been modified, the corresponding document is located in the Archive Replica (where it contains the previous content). This document is copied to the Archive Store database. Because we're copying data on the same file system and not traversing a network, this is a reasonably fast process.

During the copy process, the user has the choice to automatically ZIP attachments. This is done by calling a Java agent that uses the java.util.zip package. Briefly, the steps are:

Set doc = ... Set the document object containing information on the files to ZIP
Call session.SetEnvironmentVar("ZipAgentStatus","")
Set agent = db.GetAgent("(ZipFiles)")
Call agent.RunOnServer(doc.NoteID)
chkFinished$ = session.GetEnvironmentString("ZipAgentStatus")
While chkFinished$ = ""
chkFinished$ = session.GetEnvironmentString("ZipAgentStatus")
Sleep 1
Wend

import lotus.domino.*;
import java.io.*;
import java.util.*;
import java.util.zip.*;
import java.text.*;
public class JavaAgent extends AgentBase {
private ZipInputStream inZipFile;
private String aDBServer;
private String aDBFileName;
private String aDBNoteID;
private String zipFileNameInput;
private String zipFileNameOutput;
public void NotesMain() {
try {
Session session = getSession(); //Instantiate NotesSession
AgentContext agentContext = session.getAgentContext(); //Instantiate AgentContext
Database db = agentContext.getCurrentDatabase(); //Instantiate CurrentDatabase
Agent agent = agentContext.getCurrentAgent(); //Instantiate CurrentAgent
Document callingDoc = db.getDocumentByID(agent.getParameterDocID()); //Get the doc calling this agent
String aDBServer = callingDoc.getItemValueString ("IOZipDBServer"); //Get the server of the target database
String aDBFileName = callingDoc.getItemValueString ("IOZipDBFileName"); //Get the filename of the target database
String aDBNoteID = callingDoc.getItemValueString ("IOZipNoteID"); //Get the Note ID of the target document
Database aDB = session.getDatabase(aDBServer, aDBFileName); //Open the target database
Document doc = aDB.getDocumentByID(aDBNoteID); //Get the target document
Vector zipFileInput = doc.getItemValue("IOZipInput"); //Source uncompressed files
Vector zipFileOutput = doc.getItemValue("IOZipOutput"); //Target compressed files
byte[] buffer = new byte[18024];
for (int i = 0; i < zipFileInput.size(); i++) {
// Associate a file input stream for the current file
String zipFileNameOutput = (String)zipFileOutput. elementAt(i);
ZipOutputStream out = new ZipOutputStream(new FileOutputStream(zipFileNameOutput));
out.setLevel(Deflater.DEFAULT_COMPRESSION);
String zipFileNameInput = (String)zipFileInput.elementAt(i);
FileInputStream in = new FileInputStream(zipFileNameInput);
// Add ZIP entry to output stream.
out.putNextEntry(new ZipEntry(zipFileNameInput));
int len;
while ((len = in.read(buffer)) > 0) {
out.write(buffer, 0, len);
}
// Close the current entry
out.closeEntry();
// Close the current file input stream
in.close();
out.close();
}
session.setEnvironmentVar("ZipAgentStatus", "Completed", false);
session.recycle();
agentContext.recycle();
db.recycle();
agent.recycle();
doc.recycle();
}
catch (IllegalArgumentException iae) {
iae.printStackTrace();
}
catch (FileNotFoundException fnfe) {
fnfe.printStackTrace();
}
catch (IOException ioe) {
ioe.printStackTrace();
}
catch(Exception e) {
e.printStackTrace();
}
}
}

During the setup process, a Dialogbox Form and a 'Restore Document' Agent are automatically added to the Production database. When a user wants to restore a document, they run this agent. They are prompted for the date and it is retrieved from either the Archive Replica or Archive Store (depending on the required date), and opened.

The following graphics show the Restore operation. Note the handy use of the R8 function to modify the right-hand menu.

The user then has to select the type of Restore:

If the user wants to restore a deleted document, they instead automatically open the Archive Replica (where deletions are not removed), locate the document they want, set the date and repeat the restore process, retrieving the document from either the Archive Replica or Archive Store depending on the required date. Users can then restore deleted documents to the Production database.

The user is also able to search the Archive Replica and Archive Store databases for the data they want.

This allows a 'back through time' search facility that includes the date archived. This functionality is provided via our FT Search Manager, which allows simultaneous searching of multiple Full Text Indices.

Housekeeping agents optionally clear out Archived data after a configurable period.

A separate database option allows the restore process to use a separate directory, so that if a restore of data from 5 years ago is required, the Archive Replica and Archive Store tape backups can be restored into this directory and the process works from there instead of the normal location. This is so that 'normal' full backups to tape can be performed if required (i.e. for Disaster Recovery, reducing disk space usage etc.)

Another benefit of the Archiver is that no other form of archiving is required (i.e. no custom data archives need be done by the IT Department), documents can be simply deleted from the Production database and they will remain available in the Archive Replica for restore.

CMT Inspector contains an extensive Rules Filtering Engine with hundreds of rules that can be leveraged to find out if your applications will work when you upgrade. These rules can be modified and updated based on your environment. Furthermore, unlike simple searching that is performed by other products, CMT Inspector Rules can be tied to code snippets which can be executed to give you an even better understanding of the code in your Notes environment. This figure shows the Code Inspector at work:

All code can be flowcharted and exported to Visio for much better analysis.

CMT Inspector comes with an extensive collection of reports that can be automatically generated. Furthermore, all data can be exported to Microsoft Access for further reporting and querying. This means that almost any report can be generated on the fly.

You have business-critical information stored in Exchange Public Folders. You have to migrate to Lotus Notes, but, how do you migrate the data in the Public Folders?

Making your mail migrations from Microsoft Exchange to Lotus Domino easier is a snap with Binary Tree's CMT for Public Folders. This solution provides a simple and user-friendly means of migrating a public folder hierarchy to a single database.

The data in a Microsoft Exchange Public Folder often has significant value that has been protected with permissions, based on the identity stores in Exchange's Directory. CMT for Exchange Public folders was created to help companies recover the intellectual capital often found in Public Folders. CMT not only takes data from the Public Folders, but can also mimic the permissions that existed on the Exchange servers in brand new Domino databases. CMT migrates the standard Exchange document types, including mail messages, calendar events, journal items, tasks and notes. If your Public Folders contain forms that have been modified to include additional fields and data types, the CMT tool can be customized to migrate this data, as well.

The Binary Tree Common Migration Tool (CMT) migrates data from one email system to another. The tool can be used to migrate from numerous email systems to Lotus Notes, and like the DUS tool, CMT has the ability to migrate both Server-Based data and end-user based data.

Binary Tree's Common Migration Tool for Notes builds on 14 years of outstanding email and calendar/schedule migration solutions from Binary Tree. To date, millions of users world-wide have been migrated to Lotus Notes with Binary Tree's CMT for Notes tool.

CMT for Notes offers several business benefits:

By off-loading most of the traffic from the Microsoft Exchange Notes Connector, Binary Tree's CMT for Coexistence yields a more stable and reliable connection between Lotus Notes and Microsoft Exchange.

The most popular and highly functional connectivity solution between Microsoft Exchange and Lotus Notes environments is the Notes Connector for Microsoft Exchange. This solution addresses e-mail, calendar, scheduling and task data exchange, automated directory synchronization and free/busy lookup between Microsoft Exchange and Lotus Notes environments.

To overcome issues reported by many customers using the Microsoft Notes Connector, Binary Tree's solution greatly enhances fidelity of mail exchange and improves connectivity reliability. This is accomplished by a series of configuration and programmatic changes in the environment.

iCal is supported with the advent of Exchange 2000 and Notes 6. iCal is the standard for the encoding of a calendar messages in SMTP format. This allows email and calendaring to be sent via SMTP, which greatly decreases the stress on the Microsoft Connector, improving data fidelity.

Your Domain infrastructure is a vital asset, and one that should be protected. Your IT environment is unique, which means that you need something designed with adaptability in mind.

Enter Binary Tree's CMT for Domains, Users, Servers and Desktops, a solution which expedites the conversion between platforms, while diminishing the impact on your IT resources. A user-friendly administrator tool requiring virtually no end-user interaction, CMT for Domains, Servers, Users and Desktops will enable you to automate the entire migration lifecycle in minutes.

Utilizing CMT for Domains, Servers, Users and Desktops, the following processes can be accomplished with the click of a button:

Additionally, you can:

Never before has a consolidation of multiple Lotus Notes Domains been more straight-forward. CMT for Domains, Users, Servers and Desktops consists of everything a Lotus Notes Administrator needs to move users from an existing domain to a new one. Furthermore, as a result of the migration using CMT, users will appear to have always lived on the new domain.