|
|
This chapter describes how to achieve connectivity to Lotus Domino with the WebLogic Portlets for Groupware Integration. This chapter describes the WebLogic Domino Service architecture, installation, and configuration.
| Note: | This chapter is applicable only if you are running Lotus Domino R5, R6, R6.5, or R7. |
The WebLogic Portlets for Groupware Integration leverage a native WebLogic Domino Service to expose Lotus Domino groupware functionality from the Domino mail database. The WebLogic Domino Service machine acts as an intermediary between the Java API and Lotus Domino, as shown in Figure 4-1. See the WebLogic Domino Service Setup Guide for more information on installing and configuring the WebLogic Domino Service.
The WebLogic Domino Service is implemented using a combination of Notes RPC and Notes DSAPI and runs within Lotus Domino as part of the HTTP task. The details of this do not need to be understood by the application programmer, but this is the reason the Lotus Domino install is a prerequisite of the installation. This is where Notes RPC and the Notes DSAPI filter for Domino are obtained.
The WebLogic Domino Service must be located on a machine running Lotus Domino that is part of the same “Notes Domain” as the Domino server to access. It is possible to put the Domino Service on an existing Domino server, but be aware of the additional processor and memory burden that will be placed on Domino.
HTTP traffic must be able to pass between the Java client and the WebLogic Domino Service. Traversing an HTTP proxy is OK as long as it is able to pass the POST requests used by the XML protocol. Although a high bandwidth, low-latency connection will improve performance, the protocol has been designed to reduce the number of round trips made on the network. Therefore, packet round trip times of 50-100ms should be tolerable for the application.
The amount of bandwidth required will depend on the number of users simultaneously using the application. Each user may consume roughly 1K/sec. on average, with this number increasingly dramatically if users do a lot of work with large file attachments.
Notes RPC traffic must be able to pass between the WebLogic Domino Service and Lotus Domino. Notes RPC requires TCP port 1352 to be open. The network connection for this Notes RPC traffic must have a low latency (less than 10 milliseconds, and preferably a 100 megabit LAN with less then one millisecond response times).
Round trips are made over the network for each Notes RPC, therefore the WebLogic Domino Service machine must be located as close as possible to Domino on the network.
A guideline is approximately 250 active Domino users on a CPU running the WebLogic Portlets (an active user defined not as a thread, but as a user using an application with typical user delays between each request). Adding additional CPUs to the hardware will increase the scalability of the application, with diminishing returns. A potential guideline is going from one to two CPUs increases the number of users that could be supported by about 75%. Going from two to four CPUs increased the two CPU number by about 50%. However, each application and environment may be different.
|