OHD Administration Guide

Administration Guide OpenHand Server for Lotus Domino v4.0 Enabling the Mobile Network Administration Guide OpenHand Server for Lotus Domino v. 4.0 Hardware Requirements....................................................................................................................................2 Software Requirements......................................................................................................................................2 OpenHand Server for Lotus Domino structure....................................................................................................3 OpenHand Server for Lotus Domino Frontend.......................................................................................3 OpenHand Server for Lotus Domino Usermaster...................................................................................3 OpenHand Server for Lotus Domino Backend........................................................................................3 Connection/Communication scenario.....................................................................................................3 Installation..........................................................................................................................................................5 Lotus Domino preparation steps.........................................................................................................................6 Users using RSA SecurID® authentication.............................................................................................6 DIIOP service. ......................................................................................................................................6 Network and Firewalls............................................................................................................................6 The Primer Tool.....................................................................................................................................7 The OpenHand user database...........................................................................................................................9 User Database Tables........................................................................................................................................9 Mail server mapping..............................................................................................................................9 Groups..................................................................................................................................................9 Users...................................................................................................................................................11 Address book access...........................................................................................................................11 First time set-up...................................................................................................................................13 Configuration....................................................................................................................................................16 Manual configuration............................................................................................................................16 The Configuration Tool........................................................................................................................17 Configuration files, file sections and variables......................................................................................18 Installation Notes..............................................................................................................................................23 First connection from OpenHand server to Lotus Domino.....................................................................23 Installation methods.............................................................................................................................23 For Further Information and Support.................................................................................................................24 The OpenHand Team..........................................................................................................................24 Appendix A – Enabling DIIOP...........................................................................................................................25 HTTP service.......................................................................................................................................27 Interesting Lotus Documents................................................................................................................28 Appendix B – Creating an OpenHand user on the Domino server.....................................................................29 Appendix C – 1_ChangeLog.txt v4.0................................................................................................................35 Appendix C – 2_KnownIssues.txt v4.0..............................................................................................................36 OpenHand Software Ltd., UK office 2 Exmoor Street, London W10 6BD E-mail: Sales@OpenHand-Mobile.Com Tel: +44 (0)20 8962 3270 Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Hardware Requirements 100 concurrent users and below – IBM Compatible PC; 1GHz Intel Pentium 4 Processor or Equivalent; 512MB RAM; 500MB free disk space; 10/100MB Network Card 100+ concurrent users - IBM Compatible PC; 2GHz Intel Pentium 4 Processor or Equivalent (dual if possible); 1GB+ RAM; 1GB free disk space; 10/100MB Network Card 500+ concurrent users - IBM Compatible PC; 2GHz Intel Pentium Xeon Processor or Equivalent (dual if possible); 4GB+ RAM; 10GB free disk space; 10/100MB Network Card Minimum x86 hardware Requirements (concurrent users < 100) OpenHand Software recommends the following minimum dedicated server specification (100 concurrent users and below): — IBM Compatible PC — 1 GHz Intel Pentium 4 Processor or Equivalent — 512 MB RAM — 500 MB Free Disk Space — 10/100 Mb Network Card Recommended x86 hardware Requirements (100 < concurrent users < 500) For a high usage OpenHand Server for Lotus Domino, the suggested dedicated server specification should be (100+ concurrent users): — IBM Compatible PC — 2GHz Intel Pentium 4 Processor or Equivalent (Dual if possible) — 1GB+ MB RAM — 1GB MB Free Disk Space — 100/1000 Mb Network Card Recommended x86 hardware Requirements (concurrent users > 500) For a high usage OpenHand Server for Lotus Domino, the suggested dedicated server specification should be (100+ concurrent users): — IBM Compatible PC — 2GHz Intel Pentium 4 Processor or Equivalent (Dual if possible) — 4GB+ MB RAM — 10GB MB Free Disk Space — 1000 Mb Network Card Other hardware platforms OpenHand Server for Lotus Domino runs comfortably on any hardware platforms with Operating Systems that supports Java 2 SE 1.4 or later (JRE or JDK). It has been used on Windows, Unix, Linux and IBM iSeries. It should run on all common Unix systems and mainframes. Software Requirements Operating System OpenHand Server for Lotus Domino runs on any Operating System supporting Java 2 Platform Standard Edition version 1.4 or later. For example: • Any 32-bit Microsoft Windows desktop or server operating system. • • Most newer Unix and Linux systems Most newer IBM iSeries systems. Java runtime. • OpenHand Server for Lotus Domino runs on any Java 2 Platform Standard Edition version 1.4 or later. It does not use any GUI classes (AWT, Swing or other) so it can run on Java server runtimes. Using Java server runtimes makes OpenHand Server for Lotus Domino run faster and use fewer resources. The Sun Java 2 Windows JDK runtime includes a server runtime version, while the JRE one does not. Unix Java runtime usually includes a server version. The Sun Java runtime uses the server runtime version if it is given the -server flag on startup. Other Java runtimes found to work include the IBM Java Runtimes and the BEA WebLogic Jrockit(TM) Java Runtimes. All OpenHand Server for Lotus Domino startup options assume that -server is not supported, but the server runtime can easily be enabled. 2005/06/22 – v4.0 2/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Lotus Domino. • • • OpenHand Server for Lotus Domino supports Lotus Domino version 6.0.3 and 6.5.1 or newer. The Lotus Domino built-in DIIOP server task must be running. For OpenHand Server for Lotus Domino to work the NCSO.jar Java library found in the Domino/Data/domino/java directory on the Domio server must be copied to the jlib directory of the OpenHand Server for Lotus Domino installation. OpenHand Server for Lotus Domino structure. The OpenHand Server for Lotus Domino system contains tree types of components: 1. One Frontend. Receives connections from OpenHand clients. 2. One Usermaster. Maintains OpenHand user information in a Lotus Domino server. 3. One or more Backends. The Backends connect to the users mail, address book, calendar and to-do information in a Lotus Domino server. One common set-up is to have the OpenHand Server for Lotus Domino run all three parts in one Java runtime on one machine for installations that use only one Domino server and one Firewall, effectively working as one program. Another common setup is to have the Frontend running in the DMZ and the Usermaster and the single Backend running together inside the inner firewall along with the Domino server. NOTE: It is very important that the Usermaster and Backends are runing on the same LAN as the Domino servers they are connecting to, as the CORBA communication protocol used by the Lotus NCSO.jar library to talk to the Domino server is very ineffective compared to the LOUIS communication protocol used by OpenHand. We have seen severe slowdown in OpenHand when a router between the NCSO libaray and the Domino server was set by mistake to 10Mbs instead of 1000Mbs. The OpenHand Frontend and Backends can be in different continents without adversly affecting the speed. OpenHand Server for Lotus Domino Frontend. The OpenHand Server for Lotus Domino Frontend receives connection requests from OpenHand clients on IP-port 10622 (configurable). After the TCP-connection to the client has been established and the first client request has been received, the Frontend will contact the OpenHand Server for Lotus Domino Usermaster to get basic OpenHand user information and then use that information to connect to the correct OpenHand Backend, using the password received from the client to log into the Domino server on belhalf of the connecting user. OpenHand Server for Lotus Domino Usermaster. The OpenHand Server for Lotus Domino Usermaster receives connection requests from the Frontend either internally (when Usermaster and Frontend are then running on the same machine), or on IP-port 10624 (configurable) if the Frontend and Usermaster are running on different machines. For the Usermaster to function as an OpenHand User Database, OpenHandUsers.nsf (configurable), must be installed on a Domino server whose Domain Directory (names.nsf) contains information on all Domino users which will be using OpenHand. The Usermaster should be set up on the same Local Area Network as the Domino Server containing the Domain Directory and OpenHand User Database, and could even be located on the same machine. The Usermaster uses the Domino Domain Directory to find the real Domino user name and mailserver of the OpenHand client user. The users mailserver name is used to select which Backend the Frondend should connect to and which Domino server the Backend should connect to on behalf of the OpenHand client.. The Usermaster returns other user information from the OpenHand User Database to the Frontend, some of which is used by the Frontend, while the rest is forwarded on to the Backend. OpenHand Server for Lotus Domino Backend. The OpenHand Server for Lotus Domino Backend receives connection requests from the Frontend either internally or on IPport 10623 (configurable) if the Frontend and Backend are running on different machines. The Backend does all the real work of OpenHand Server for Lotus Domino, reading and updating the Domino users mail database and sending information back to the client. The Backend should be set up on the same Local Area Network as the Domino servers it connects to, and could even be located on the same machine. Connection/Communication scenario. The following is a general overview of a typical OpenHand client/server scenario. The initial challenge/response mechanism and the persistence mechanism are not described here 1. 2. 3. 4. 5. An OpenHand client connects to the OpenHand Server for Lotus Domino Frontend sending a message containing a Domino username or alias and an Internet Domino password. The whole message, excluding the username, is encrypted using the security key. The Frontend sends the unencrypted username to the Usermaster. The Usermaster looks in the Domino Domain Directory for the Domino user with the specified username or alias and which mailserver he uses. The Usermaster looks in the OpenHand User Database user table to see if the Domino user is also an OpenHand user. 2005/06/22 – v4.0 3/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 6. 7. 8. 9. 10. 11. 12. 13. The Usermaster looks in the OpenHand User Database user table (and sometimes the group table) for other user information including the users security key, permissions and to which Backend the user should connected to, and to which Domino server the Backend should connect to. The Usermaster sends the Security Key, Backend specification, Domino server specification and other user information back to the Frontend. The Frontend uses the Security Key received from the Usermaster to decrypt the rest of the client message, including the Domino password. The Frontend uses the Backend specification received from the Usermaster to connect to the correct Backend, forwarding the Usermaster supplied Domino server specification and the client supplied password and message. The Backend connects to the Domino server specified and logs into Domino using the client supplied username and password. The Backend performs the Domino server operations the client requested and sends the results back to the Frontend. The Frontend forwards the results from the Backend to the OpenHand client. The OpenHand client, Frontend and Backend exchange messages until the session is closed. 2005/06/22 – v4.0 4/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Installation. The following installation instructions are written with an administrator, or someone familiar with Domino in mind. If the person following these steps is not familiar to Domino, please consult someone that is, and/or refer to the “Domino Administrator Help” in Domino. Appendix A (Enabling DIIOP) and Appendix B (Creating an OpenHand user on the Domino server) could also come in handy as a further supplementing help. 1) 2) 3) 4) 5) 6) Install or ensure there is installed a 1.4 or newer Java Runtime on each server machine where OpenHand will run. Copy the OpenHand installation archive to any machine you want a part of OpenHand to run on. Create a directory for OpenHand (e.g. OpenHand). On Windows, please do not create this directory on a network drive if you want to run the server as a Windows NT Service. Unpack the archive into the new directory. Copy the provided OpenHandServerDomino.license file to the installation directory on the machine running the OpenHand Usermaster. Move the platform dependent files from the relevant sub-directory to the installation root. 1. On Windows go into the 0_Windows_Move_Here directory and run the prepare.bat command file. If you want to run the server from the command line also run the preptest.bat command file. 2. On Unix go to the 0_Unix_Move_Here directory and run the prepare.sh shell script. 3. On iSeries contact OpenHand Ltd. for more information. Copy OpenHand Server for Domino User Database template to the Domino server which the OpenHand Usermaster will connect to. Go into the 0_ToDominoServer directory and copy OpenHandUsers.ntf to the Domino server, in the data directory or some sub-directory there of . This will typically be .../Lotus/Domino/Data. Copy the NCSO.jar Java library from each Domino server OpenHand will connect to, to the jlib sub-directory of the corresponding Openhand installation directory, i.e. for each OpenHand Usermaster and Backend. The NCSO.jar Java libarary can be found in the .../Lotus/Domino/Data/domino/java directory of the Domino server. In the Lotus Domino Administrator create an OpenHand user with an Internet password on the Domino server the OpenHand Usermaster will connect to (See the appendix “Creating an OpenHand user on the Domino server”, and the Domino Administrator Help for guidance). This user needs read access to the names.nsf file but does not need to have a Notes ID file, but it needs to have a mail database, as the OpenHand server will on occation send problem reports by email to itself. This user does not even have to be in the Domino names.nsf file if Domino Directory Assistance is correctly set up. In the Lotus Domino Administrator create an OpenHand Server for Domino User Database on the Domino server the OpenHand Usermaster will connect to. Use the template you copied earlier from the OpenHand installation to this Domino server. The deafault OpenHand Usermaster configuration assumes the database file is named OpenHandUsers.nsf and is in the Domino data directory. The default ACL to this database should be 'no access' but the OpenHand user created above should have Manager access. See “Domino Administrator Help” for guidance. Fill in the new OpenHand User database. See “The OpenHand user database” chapter below. In the Lotus Domino Administrator enable the Lotus Domino DIIOP service. See “Domino Administrator Help” for guidance. The appendix “Enabling DIIOP” below has some pointers. In the OpenHand installation directory start the OpenHand Primer Tool, either by double-clicking the OHDPrimerTool.jar file or giving the command java -jar OHDPrimerTool.jar. See “The Primer Tool” chapter below. In the OpenHand installation directory start the OpenHand Configuration Tool, either by double-clicking the OHDConfigTool.jar file or giving the command java -jar OHDConfigTool.jar. See “The Configuration Tool” chapter below. To test the installation it is best to start the OpenHand server using OHDServer.bat or OHDServer.sh. If the JAVA_HOME environment variable is NOT set on the machine, edit the OHDJavaBin.bat or OHDJavaBin.sh file and change the line setting JAVABIN to point to the Java runtime directory you want to use. If you want to install the server on Windows as a NT Service go into the NTService directory. 1. If the JAVA_HOME environment variable is NOT set on the machine, edit the NTService.config file and change the line (~18): wrapper.java.command=%JAVA_HOME%/bin/java to point to the Java runtime you want to use. 2. Execute the InstallService.bat command file. This will install the OpenHand server as a NT service running as a “Local System Account”. The OpenHand server does not need any special priviledges so you can change this to a different account. 3. Go into the Windows Services Control Panel, find OpenHand Server for Lotus Domino and start the service. This will only have to be done once after installation, the service will be started automatically on system reboot. 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 2005/06/22 – v4.0 5/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Lotus Domino preparation steps Users using RSA SecurID® authentication Make sure to carry out the following additional steps when using RSA SecurId for authentication with OpenHand for Lotus Domino: 1. Copy a sdconf.rec obtained from the data directory of the RSA ACE server install directory to the config directory of your OpenHand server. Please verify that sdconf.rec file contains the correct address information for your RSA ACE Server. For information on how to edit sdconf.rec please refer to the RSA ACE server admin guide. 2. The OpenHand server acts as an agent against the RSA ACE server and thus the RSA server needs to be configured to allow agent connections from the host running the OpenHand server. In addition, one can set up a shared node secret between the agent (OpenHand server) and the RSA server, at which point you also need to copy the node secret file to the config directory of the OpenHand server. The secret file must be named securid. For information on how to make a node secret file and allowing agent connections, please refer to the RSA ACE server admin guide. 3. In the OpenHand user database, please set “User must use RSA SecurID authentication” to true either for individual users or the appropriate user group. 4. Note: Users must log into OpenHand using the user name registered as default login in the RSA ACE server, make sure this user name is registered in Lotus Domino. DIIOP service. The OpenHand Server for Lotus Domino uses the Lotus NCSO.jar library to communicate with the Domino server. 1 The NCSO.jar library, in turn, uses the industry standard CORBA mechanism to talk to the Domino servers DIIOP service (i.e. Domino IIOP service, IIOP is the protocol used by CORBA for remote object communication). For OpenHand Server for Lotus Domino to work, in fact any program that uses CORBA to communicate with the Domino server, the DIIOP service built into the Domino server must be enabled. For information on how to enable DIIOP see the Lotus Domino Administrator Help. For a rudimentary description of the process see the Appendix B: Enabling DIIOP. NOTE: Make sure you add the DIIOP service to the ServerTasks line in notes.ini file (located in the ...\Lotus\Domino directory on Windows), otherwise the DIIOP service won't be automatically enabled when the Domino server is restarted. Lotus Domino User Password. OpenHand Server for Lotus Domino uses the users Domino Internet password to log in, the same passwords Lotus iNotes uses.These can (and should) be different from the internal Domino one. Network and Firewalls. OpenHand clients connections. OpenHand clients connect to the OpenHand Server for Lotus Domino from the Internet on TCP port 10622 by default. The port number can be changed in OpenHandDominoServer.config using the Configuration Tool or a text editor (is.softis.openhand.domino.port variable). Potential firewalls between the Internet and the OpenHand server must allow connections from the Internet to this port on the machine running the OpenHand server. OpenHand server connections. The OpenHand Server for Lotus Domino (Backend, see below) connects to the Lotus Domino server DIIOP service on port 63148 by default. This port number can be changed in the Domino Administrator program and then needs to be changed too in OpenHandDominoServer.config using the Configuration Tool or a text editor (is.softis.openhand.domino.lotus.port variable). Note that this host and port is not used by OpenHand to talk to the Domino server on behalf of the user, but only by a Lotus CORBA remote library to get the real host and port to connect to (see HTTP service section above). Potential firewalls between the OpenHand server and the Lotus Domino server must allow connections from the OpenHand server to this port on the machine running the Lotus Domino server, see the next section for exceptions. OpenHand Front- and Back-end connections. The OpenHand Server for Lotus Domino can be run in two parts, the Frontend which clients connect to, and the Backend which connects to Lotus Domino. The Frontend connects to the Backend on port 10623 by default. The Backend host port number can be changed in OpenHandDominoServer.config using the Configuration Tool or a text editor (is.softis.openhand.domino.db.host/port variables). The most common reason for running the OpenHand server in two parts is to be able to run the Frontend on a DMZ but the Domino server is on a MZ and you don’t want to open connections to the DIIOP service from the DMZ. CORBA is the acronym for Common Object Request Broker Architecture, OMG's open, vendor-independent architecture and infrastructure that computer applications use to work together over networks. Using the standard protocol IIOP, a CORBA-based program from any vendor, on almost any computer, operating system, programming language, and network, can interoperate with a CORBA-based program from the same or another vendor, on almost any other computer, operating system, programming language, and network. (From the Object Management Groups website, OMG is the CORBA standardisation body. See http://www.omg.org) 2005/06/22 – v4.0 6/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com 1 Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Potential firewalls between the OpenHand Frontend and the OpenHand Backend must allow connections from the OpenHand Frontend to this port on the machine running the OpenHand Backend. The Primer Tool. OpenHand Server for Lotus Domino Primer Tool is used to check if the Domino server, and especially the DIIOP service, have been set up correctly for OpenHand to work. To start the tool either double-click the OHDPrimerTool.jar or run the OHDPrimerTool.bat on Windows or OHDPrimerTool.sh on Unix. You can also give the command java -jar OHDPrimerTool Here are some figures from a typical run of the Primer Tool. 2005/06/22 – v4.0 7/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 2005/06/22 – v4.0 8/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino The OpenHand user database The OpenHand server for Lotus Domino ships with a user database template. A OpenHand User database must be created from this template on the Lotus Domino server that is being used by the OpenHand Usermaster. This database is used by OpenHand for individual user settings and to manage who is allowed to use OpenHand. User Database Tables Mail server mapping Mail server mapping maps a Lotus Domino mail server to an OpenHand Backend. Fields Field Mail server: Description A Lotus Domino mail server. All users using the selected mail server will connect through the OpenHand backend configured below. The OpenHand Backend server DNS name or ip-number as seen from the OpenHand backend if set to “internal” the Backend runs within the OpenHand Frontend The OpenHand backend port. The Lotus Domino servers (selected in “Mail server”) DNS name or ip-number as seen from the OpenHandBackend above. The Lotus Domino servers port. Optional. The Lotus Domino servers IOR string. If specified overrides the Lotus Domino Host and Port settings. OpenHand Backend host: OpenHand Backend port: Lotus Domino host: Lotus Domino port: Lotus Domino IOR: Groups OpenHand users can be divided into groups. A group sets all the default settings for its users, each users settings can be set to override the group settings. Fields Field Group name: User is enabled: Users security key: Users must use challenge response login: User must use RSA SecurID authentication: User can save password: User can use attachments: User can save to local folders: User can use files services User can take snapshot of server contact directory: Reverse mail order: 2005/06/22 – v4.0 The name of the group. This enabled or disables the users in this group, disabled users can not log in to OpenHand and are not counted as a part of the license number. This sets the encryption key for the users in this group, the key must match the encryption key on the users client. This should always be used Set if users must use RSA SecurId to login Set if users can save their password on the clients. Set if users can send/receive attachments Set if users can save information to their local folders. Set if users can use the files services Set if users can take snapshots of the server contact/user directory. Warning: Enabling this can cause the server to run out of memory. Set to true if the oldest email appears at the top of the email list in the clients. 9/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Description Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Field Users timezone: Description The timezone the users are in. The default is the servers timezone. Note: Instead of selecting “Local time” you should check “Server timezone” 2005/06/22 – v4.0 10/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Field Users address books: Description The address books the users can access. Address book definitions must be of the form: database;access;view;sort_index where: database is the database containing the address book use ${mail} for the users mailfile access is the access right the user has to the address book view is the view to read the contact list from sort_index is the index of the contacts name column in the view (must be sorted). Example: names.nsf;R;People;1 gives the user read access to the global address book Enter a list of address books one on each line Note: If a entry for a custom address book is added then that address book must be on the same format as names.nsf, otherwise data integrity is not guaranteed. Special settings: Do not change this unless advised to do so by the OpenHand tech support. Users Every Lotus Domino user that should have access to OpenHand has to be added to the OpenHand user database. Fields Field User name Group Description The users name, imported from the Lotus Domino names directory The group the users inherits its default settings from. Other fields have the same meaning as for groups. Settings for users can override group settings by setting the explicitly. “Group” or empty settings mean that that setting is inherited from the group. Address book access OpenHand both access standard address books (address books that are on the same format as names.nsf) and custom address books. Accessing standard address books Standard address books like the Lotus Domino user directory and the private address book synced to the users mail file can be accessed simply by adding a definition “Users address books” field. Address book definitions must be of the form: database;access;view;sort_index where: database is the database containing the address book use ${mail} for the users mail file access is the access right the user has to the address book view is the view to read the contact list from sort_index is the index of the contacts name column in the view (must be sorted). Example: names.nsf;R;People;1 gives the user read access to the global address book Enter a list of address books one on each line Accessing custom address books Warning: For now this is experimental only. 2005/06/22 – v4.0 11/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino To access custom address books it is necessary to import the “(Contact list view)” view from the OpenHand user database into the address book database and implement the appropriate columns in it. The view can be renamed to any name but the name must end with _ohc (ex. openhand_ohc). Only the first column (name) is required to be implemented but all columns must return a value even though they are not used, an empty string for unused columns. The first and second column must be sorted. Note that the empty string can not be a constant, a function that returns the empty string must be use, the formula @if(name = “”; “”; “”) is the default (You might have to change that if “name” is not a field in your contact documents). Note: It is important that the order of columns is not changed and that no column is deleted. After the ohc view has been implemented an entry for it must be added in the “Users address books” field. The definition entry follows the same rule as for standard address books but the “sort_index” field is ignored and can be omitted. Example: contacts.nsf;R;contacts_ohc gives the user read access to contacts in the contacts.nsf database using the contacts_ohc view. Note: That for the time being only read access is supported for custom address books. 2005/06/22 – v4.0 12/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino First time set-up When the OpenHand user database is opened for the first time there is only one entry in it, a default group. The first thing you have to do is making a mail server mapping for your mail servers, one for each Lotus Domino mail server your users want to connect to or one for each OpenHand Backend, most small setups only need one mail server mapping. Next take a look at the DefaultGroup in the group list, most setups only need the DefaultGroup but you should add more groups if you intend to have different settings for different groups of users. Note that a group (or any other) document can be edited by double clicking on the documents background. Now you are ready to import users to the database. This can be done one at a time or multiple users at once. Note that if you change the advanced settings for a user it will override the group settings. The following figures show a typical session. 2005/06/22 – v4.0 13/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 2005/06/22 – v4.0 14/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 2005/06/22 – v4.0 15/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Configuration. OpenHand Server for Lotus Domino does not need any special priviledges to run, only to accept TCP connections from clients, connect to Lotus Domino over TCP and write log files in the installation directory. You can move the installation by just moving the installation directory (see NT service discussion below for an exception). For a typical simple installation only the Domino host DNS-name or IP-number needs to be changed. Manual configuration. Unix/Linux. If the JAVA_HOME environment variable is not set you must change the JAVABIN variable in the provided OHDServer.sh file to point to the required Java runtime. Windows. If you want to start the OpenHand server from the command line (a good idea when testing the installation) and JAVA_HOME environment variable is not set, then you must change the JAVABIN variable in the provided OHDJavaBin.bat file to point to the Java runtime to use. Windows NT/2000/XP/2003 Service. If you want to install the OpenHand server as an NT service and JAVA_HOME environment variable is not set you must change the wrapper.java.command variable in the NTService\NTService.config file to point to the required Java runtime. Run NTService\InstallService.bat to install OpenHand Server for Lotus Domino as an NT service. Run NTService\UninstallService.bat to uninstall OpenHand Server for Lotus Domino as an NT service. 2005/06/22 – v4.0 16/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino The Configuration Tool OpenHand Server for Lotus Domino version 4.0 comes with a configuration program “OHDConfigTool” for editing OpenHand configuration information. To start the Configuration Tool on Windows you can double-click the OHDConfigTool.jar file in the installation directory. You can also run the OHDConfigTool.bat command file from a command window. On most other platforms you must start the Configuration Tool by issuing ‘java –jar OHDConfigTool.jar’ from a command line. To familiarize yourself with the Configuration Tool click the Help button in the Configuration Tool or the question mark button by each configuration parameter. 2005/06/22 – v4.0 17/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino General description On the left hand side there is a menu which can be used to browse the configuration. Each menu item represents a configuration file, some of which are divided into sections (tabs) for easier editing. When any changes are made, a star appears at the end of the menu item name, indicating that there are unsaved changes. Selecting a sub level node displays the variables that can be edited. For the default value leave the field blank or enter "default" (without the quotes). The "Reset" button resets the variable to its default value. Clicking on the "?" button below gives a brief description of the variable. Editing the default configuration files The config tool is configured to read and write the config files located in the /config folder in the OpenHand for Domino install folder. To edit the default config files, just edit the variables as needed and hit the "Save all" button. If only one specific file should be saved, hit the "Save" button and the file section currently active (the one being editing) will be saved. Editing other configuration files To edit other files than the default ones, hit the "Load" button and browse for the file to edit. This automatically disables the "Save" and "Save all" buttons to prevent accidentally overwriting the default files. To save this loaded config file, make sure that the section being saved is the section currently being edited/viewed and hit the "Save as" button. Importing old configuration files This feature is used when the format of the configuration files has been changed. Just import config files in an older format, and the format is then updated to the latest config format. To import a file, just hit the "Import" button and browse for the old file. When the old settings are loaded hit the "Save all" button to save the configuration files at their default locations. Configuration files, file sections and variables This section is based on the on-line help in the configuration tool. It describes the config file contents, the variable names, description, and the default value. It also describes the pull down menu values, where appropriate. Menu item "Server Launcher", file path="config/OHDServer.config" An OpenHand server contains at least three parts, one Frontend, one Usermaster and one or more Backends. It can optionally contain one or more Files Servers and one Key Server Tab item "Active parts" variables Which OpenHand Server parts should be activated on server startup variable name="openhand.server.frontend" Run Frontend, default="true", [true, false] Should the OpenHand Launcher start the Frontend variable name="openhand.server.usermaster" Run Usermaster locally, default="false", [true, false] Should the OpenHand Launcher start the Usermaster locally variable name="openhand.server.backend" Run Backend locally, default="false", [true, false] Should the OpenHand Launcher start the Backend locally variable name="openhand.server.keyserver" Run Key Server locally,default="false", [true, false] Should the OpenHand Launcher start the Key Server locally. Key Service enables downloading of old security keys and generation of new security keys (encryption keys) variable name="openhand.server.files" Run Files Server locally, default="false", [true, false] Should the OpenHand Launcher start the Files Service locally. Files Services enables access from client devices to files stored on a public FTP server within the company or a company department Menu item “Usermaster”, file path="config/OHDUsermaster.config" The OpenHand Usermaster accepts connections from the OpenHand Frontend and handles all OpenHand client and Frontend requests for user information from the OpenHand User Domino database Tab item "Service" variables The Usermaster offers its Service to Frontend variable name="openhand.domino.usermaster.port" Usermaster TCP port, default="10624" The TCP-port the OpenHand Usermaster offers its services on. (The OpenHand Frontend connects to the OpenHand Usermaster on this port). This port is ignored if Usermaster runs internally in the OpenHand Frontend. The same TCP-port number MUST be set in the Frontend configuration too 2005/06/22 – v4.0 18/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino variable name="openhand.domino.usermaster.ssl" Use SSL, default="false", [true, false] Should the Usermaster only offer its services to the Frontend over SSL variable name="openhand.domino.usermaster.ssl.keystore" SSL Keystore, default="" The Keystore SSL should use. Blank means the default Java Keystore variable name="openhand.domino.usermaster.ssl.keystore.password" SSL Keystore Password, default="" The Keystore SSL password Tab item "OpenHand Administrator" variables The OpenHand User Administrator variable name="openhand.domino.usermaster.username" Domino Username, default="OpenHand" The Domino Username for the OpenHand Usermaster/Administrator. This Domino user must have read access to the domain directory (Vietnamese) and read/write access to the OpenHand User database. variable name="openhand.domino.usermaster.password" Domino Internet Password,default="usermasterpwd" The Domino Internet password for the OpenHand Usermaster/Administrator. variable name="openhand.domino.usermaster.email" E-mail address, default="" The e-mail address the OpenHand Usermaster/Administrator will send problem reports to. If blank, no e-mails will be sent variable name="openhand.domino.usermaster.database" Database Path,default="OpenHandUsers.nsf" The relative path of the OpenHand User Database from the Lotus Domino servers data directory Tab item "Domino server" variables The Domino server the UserMaster should connect to variable name="openhand.domino.usermaster.domino.version" Domino server version, default="6.5", [6.0, 6.5] Version of Domino server the Usermaster connects to. This variable affects amongst other things the way users extra mail folders are found, the version 6.5 is considerably faster. (Using the 6.5 method seems to work for 6.03 and newer even though the Lotus documentation says it shouldn't) variable name="openhand.domino.usermaster.ior.host" Domino Server host (for IOR), default="127.0.0.1" The DNS-name or IP-address of the HTTP service to get the Lotus Domino IOR from. The IOR contains amongst other things the location of the Domino DIIOP task the OpenHand Usermaster should connect to. The Lotus Domino version 6 server DIIOP service (port 63148 by default) contains a small HTTP server which can return the IOR. The standard Lotus Domino HTTP service (port 80 by default) can also be used but then it must allow anonymous access. variable name="openhand.domino.usermaster.ior.port" Domino Server TCP Port (for IOR), default="63148" The TCP port of the HTTP service to get the Lotus Domino server IOR from. The IOR contains amongst other things the location of the Domino DIIOP task the OpenHand Usermaster should connect to. The Lotus Domino version 6 server DIIOP service (port 63148 by default) contains a small HTTP server which can return the IOR. The standard Lotus Domino HTTP service (port 80 by default) can also be used but then it must allow anonymous access. variable name="openhand.domino.usermaster.ior.ssl" Use SSL, default="false", [false,true] Should the Usermaster only offer its services to the Frontend over SSL variable name="openhand.domino.usermaster.ior.ssl.keystore" SSL Keystore, default="" The keystore SSL should use. Blank means the default Java keystore name="openhand.domino.usermaster.ior.ssl.keystore.password" SSL Keystore Password,default="" The keystore SSL password variable name="openhand.domino.usermaster.ior" Domino Server IOR String, default="" You can set this variable to the Domino IOR contained in the file .../Lotus/Domino/Data/domino/html/diiop_ior.txt in your Domino server installation. This is a very long hexadecimal string. If you specify the IOR here the Domino Server Host and Port will be ignored. NOTE however that the above diiop_ior.txt file can change if you do one of the following on the Domino server: - change the IP-address or DNS-name the DIIOP service is offered on. - change a DIIOP port number. - enable or disable a DIIOP port%nl%in which case you must update this config variable 2005/06/22 – v4.0 19/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Menu item “Frontend”, file path="config/OHDFrontend.config" The OpenHand Frontend accepts connections from OpenHand clients and forwards user information requests to the (possibly remote) OpenHand Usermaster but forwards all other OpenHand client requests to a (possibly remote) OpenHand Backend Tab item "Service" variables name="openhand.client.port" TCP port for OpenHand clients, default="10622"variable The TCP port OpenHand clients should connect to variable name="openhand.client.ssl" Use SSL, default="false", [true, false] Should the Frontend only offer its services to the OpenHand clients over SSL variable name="openhand.client.ssl.keystore" SSL Keystore, default="" The keystore SSL should use. Blank means the default Java keystore variable name="openhand.client.ssl.keystore.password" SSL Keystore Password, default="" The keystore SSL password Tab item "Persistence" variables variable name="openhand.client.persist" Persistent session time-out, default="120" Minutes until unused persistent OpenHand sessions die Tab item "Usermaster" variables variable name="openhand.usermaster.host" Usermaster host, default="internal" The DNS-name or IP-address of the host Usermaster runs on. (The OpenHand Frontend connects to the OpenHand Usermaster for user information). "internal" means that the Usermaster runs internally in the OpenHand Frontend variable name="openhand.usermaster.port" Usermaster TCP port, default="10624" The TCP-port the Usermaster offers its services on. (The OpenHand Frontend connects to the OpenHand Usermaster on this port). This port is ignored if Usermaster runs internally in the OpenHand Frontend. The same TCP-port number MUST be set in the Usermaster configuration variable name="openhand.usermaster.ssl" Use SSL, default="false", [true, false] Connect to the Usermaster using SSL variable name="openhand.usermaster.ssl.keystore" SSL Keystore, default="" The keystore SSL should use. Blank means the default Java keystore variable name="openhand.usermaster.ssl.keystore.password" SSL Keystore Password, default="" The keystore SSL password Tab item "Client Versions Auto Update" variables variable name="openhand.client.autoupdate.versions" Fetch newest client versions file from Update Server, default="false", [true, false] Should the OpenHand server automatically download the latest client versions file at the given interval from the given URL variable name="openhand.client.autoupdate.interval" Update interval in hours, default="24" The interval in hours the OpenHand server should check for a new version of the client versions file at the given URL variable name="openhand.client.autoupdate.url" URL, default="http://www.openhand-mobile.com/updates/clients.xml" The URL to fetch the latest client versions file from Menu item “Backend”, file path="config/OHDBackend.config" The OpenHand Backend accepts connections from the OpenHand Frontend and handles all OpenHand client requests for information in the users Domino databases Tab item "Service" variables variable name="openhand.domino.backend.port" Backend TCP port, default="10623" 2005/06/22 – v4.0 20/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino The TCP-port the OpenHand Backend offers its services on. (The OpenHand Frontend connects to the OpenHand Backend on this port). This port is ignored if Backend runs internally in the OpenHand Frontend. The same TCP-port number MUST be set in the OpenHand Users database on the Domino server Usermaster connects to variable name="openhand.domino.backend.ssl" Use SSL, default="false" [true,false] Should the Backend only offer its services to the Frontend over SSL variable name="openhand.domino.backend.ssl.keystore" SSL Keystore, default="" The keystore SSL should use. Blank means the default Java keystore variable name="openhand.domino.backend.ssl.keystore.password" SSL Keystore Password, default="" The keystore SSL password Menu item “Key Server”, file path="config/OHKeyserver.config" The OpenHand Key Server accepts connections from OpenHand clients on a SSL socket and retrieves the users Security Key, it can also generate a new one Tab item "Service" variables variable name="openhand.keyserver.port" Keyserver TCP/SSL port, default="10624" The TCP-port the OpenHand Key Server offers its services on. (The OpenHand clints connect to the OpenHand Key Server on this port) variable name="openhand.keyserver.ssl.keystore" SSL Keystore, default="" The keystore SSL should use. Blank means the default Java keystore variable name="openhand.keyserver.ssl.keystore.password" SSL Keystore Password, default="" The keystore SSL password Menu item “Files”, file path="config/OHFiles.config" The OpenHand Files service accepts connections from OpenHand Backends and gives them access to file systems through FTP servers Tab item "Service" variables variable name="openhand.files.port" Files Service TCP port,default="10625" The TCP-port the OpenHand Service for Files offers its services on. (The OpenHand Backend connects to the OpenHand Files on this port). This port is ignored if Files runs internally in the OpenHand Backend. The same TCP-port number MUST be set in the OpenHand Users database on the Domino server Usermaster connects to variable name="openhand.files.ssl" Use SSL, default="false", [true, false] Should the Usermaster only offer its services to the Frontend over SSL variable name="openhand.files.ssl.keystore" SSL Keystore, default="" The keystore SSL should use. Blank means the default Java keystore variable name="openhand.files.ssl.keystore.password" SSL Keystore Password, default="" The keystore SSL password Menu item “Files User configuration”, file path="config/OHFilesUser.config" The OpenHand Files service accepts connections from OpenHand Backends and gives them access to file systems through FTP servers Tab item "Files Service" variables variable name="openhand.user.files.1" Files Service name, default="Default" The name of this Files Service point variable name="openhand.user.files.1.host" Files Service host, default="internal" The DNS-name or IP-address of the host the Files server runs on variable name="openhand.user.files.1.port" Files Service TCP port, default="10625" 2005/06/22 – v4.0 21/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino The TCP port the OpenHand Backends should connect to Tab item "FTP server" variables variable name="openhand.user.files.1.ftp.host" FTP Server Host, default="localhost"The FTP server DNS-name or IP-address the OpenHand Server for Files should connect to variable name="openhand.user.files.1.ftp.port" FTP Port, default="21" The FTP servers TCP-port number the OpenHand Server for Files should connect to variable name="openhand.user.files.1.ftp.username" FTP user name, default="openhand" The FTP username the Files service uses to log into the FTP server variable name="openhand.user.files.1.ftp.password" FTP user password, default="ftpPassword" The FTP password the Files service uses to log into the FTP server Menu item “Logging”, file path="config/OHDLogging.config" In this section you control the logging level of the OpenHand server. The log records generated by OpenHand are sent both to the console and to a file. You can control the logging level for each destination independantly Tab item "Logging Levels" variables Logging Levels control generation of log records variable name="openhand.level" Log record generation, default="INFO", [SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST] The OpenHand logging level. Controls the generation of log records in OpenHand. The finer the log level is set the more time is spent generating log records. Setting handler logging levels to a finer level has no effect variable name="java.util.logging.ConsoleHandler.level" Log to Console, default="INFO", [SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST] Logging level for the console log. Controls which log records generated by OpenHand are actually logged to the console variable name="java.util.logging.FileHandler.level" Log to File, default="FINE", [SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST] Logging level for the file log. Controls which log records generated by OpenHand are actually logged to the log file Tab item "Log Size" variables You can limit the size and count of the generated log files variable name="java.util.logging.FileHandler.limit" Log file size limit, default="50000" Maximimum size of individual log files variable name="java.util.logging.FileHandler.count" Log file count limit, default="20" Maximum number of log files to keep around, the oldest log will be thrown away to make room for new ones. The newest log file is always number 0 (zero) Tab item "Advanced" variables Server logging variable name="java.util.logging.ConsoleHandler.formatter" Console log formatter, default="openhand.OHFormatter", [openhand.OHFormatter, , java.util.logging.SimpleFormatter, java.util.logging.XMLFormatter] Log record formatter to use for Console logger variable name="java.util.logging.FileHandler.formatter" File log formatter, default="openhand.OHFormatter", [openhand.OHFormatter, java.util.logging.SimpleFormatter, java.util.logging.XMLFormatter] Log record formatter to use for File logger variable name="handlers" Active loggers, default="java.util.logging.FileHandler, java.util.logging.ConsoleHandler" Logs to activate. File and Console logs are the default variable name="java.util.logging.FileHandler.pattern" Name pattern for log files, default="LOGS/OpenHandDomino.%g.log" Pattern to generate log file names 2005/06/22 – v4.0 22/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Installation Notes First connection from OpenHand server to Lotus Domino The first time the connection is made from OpenHand server to Lotus Domino can take a long time (tens of minutes, depending on the number of users, size of global address lists etc.) During this first connection, the Domino server is creating index placeholders for speeding up the access to the information in the Lotus Domino server. The following connections will not take as long, as the index placeholders have been created. Installation methods The installation method described here does not fully support distributed mode of operation where the OpenHand server is split in two, a front end (talks LOUIS to clients) and back end (uses DIIOP and HTTPS to Lotus Domino Server). The back end can reside inside a firewall, and the front end resides either outside of the firewall or in a DMZ. Only one back end is supported in the current version. Installing the back end into Lotus Domino is not supported in the current version. 2005/06/22 – v4.0 23/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino For Further Information and Support Please contact: (UK office) OpenHand Software Limited Tel: +44 (0) 20 8962 3270 Email: support@openhand-mobile.com (Iceland office) Softis hf. Hafnarstaeti 19, 101 Reykajvik, Iceland Tel: + 354 511 5440 Email: support@softis.is The OpenHand Team Ólafur Bragason, Mobile: + 354 696 5441, EMail: olibraga@softis.is Fridrik Asmundsson, Mobile: +44 (0) 7733 111 698, Email: fridrik.asmundsson@openhand-mobile.com Tim Belfall, m: +44 (0) 7834 753944, e: tim.belfall@openhand-mobile.com 2005/06/22 – v4.0 24/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Appendix A – Enabling DIIOP The following figure shows what needs to be enabled for the NCSO.jar library being able to connect to Domino. Figure 4: Domino Administrator DIIOP Access 2005/06/22 – v4.0 25/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino The following figure shows where the DIIOP port is enabled and configured. Figure 5: Domino Administrator DIIOP Ports The following figure shows where to add an IIOP Internet Site. This is the best way, and sometimes the only way, to control which DNS-name or IP-address is returned in the IOR. Figure 6: Domino Administrator IIOP Internet Site creation 2005/06/22 – v4.0 26/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino The following figure shows where to configure an IIOP Internet Site to return the correct DNS-name or IP-address in the IOR. Figure 7: Domino Administrator IIOP Internet Site configuration The following figure shows some help text to explain the previous figure. Figure 8: Domino Administrator IIOP Internet Site help HTTP service. The HTTP service is not necessary for Lotus Domino 6 as the DIIOP service contains a simple HTTP server. The HTTP server is used by the NCSO.jar Lotus library OpenHand uses to get the information necessary to connect to the Domino CORBA ORB. The information returned from this initial HTTP GET request is called the IOR, it contains amongst other things the real DIIOP server host DNS-name or IP-number and the IP-port the OpenHand server should connect to. It is very important that the IOR information is correct, otherwise the OpenHand server will try to connect to the wrong machine and/or port. The DIIOP server generates this information in the Domino Web server root directory “.../Lotus/Domino/Data/domino/html/diiop_ior.txt” the first time it starts. The only way to regenerate this file seems to be to change the DIIOP host or port in Domino Administrator, restart the Domino DIIOP task (“restart task diiop”), change the host or port back to the correct value and restart the Domino DIIOP task again. To check if the IOR has been generated and is accessible you can point a web browser to “http://host:port/diiop_ior.txt” where host is the host-name/IP-number of the HTTP server and port is 63148 if you want to use the HTTP server built in to 2005/06/22 – v4.0 27/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino the DIIOP server (and you are using the default DIIOP port) or 80 if you want to use the Domino built-in HTTP server (and you are using the default HTTP port). If this test works you will get back a very long hexadecimal string (>350 characters) and the host and port can be used by the OpenHand server to get the IOR, if it does not work OpenHand will not be able to connect. We recommend using the built-in HTTP server in the DIIOP task if possible but it does not always work for some unknown reason. If that does not work you can use the standard Domino HTTP task, or you can insert the content of the diiop_ior.txt file directly into the IOR string field in the OpenHand Configuration Tool. If you use the IOR string from diiop_ior.txt you must update the OpenHand configuration each time the IOR file is regenerated. The OpenHand Primer Tool/Get IOR option does the same test, but in addition it will also try to decypher the IOR string to tell you which server and port is returned in the IOR string, i.e. the real IOOP host and port the NCSO library will use. If this information is not correct, you must change the DIOOP settings and regenerate the diiop_ior.txt file. Interesting Lotus Documents For general information on the DIIOP service configuration point your browser to ”Java access to the Domino Objects, Part 1” Administration section from the Notes Forum (URL: http://lwmreg.lotus.com/ldd/nd6forum.nsf/0/7f5bda9e1fcf28b085256dfa005bfd55?OpenDocument) Nore however that OpenHand Server for Lotus Domino special priviledges, i.e. Does not need to run any scripts or agents. 2005/06/22 – v4.0 28/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Appendix B – Creating an OpenHand user on the Domino server The pictures are here only for quick reference purposes. Please consult the Domino Administrator Help for further guidance. A certificate is created by Domino for each person created in Domino. 2005/06/22 – v4.0 29/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 2005/06/22 – v4.0 30/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 2005/06/22 – v4.0 31/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 2005/06/22 – v4.0 32/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 2005/06/22 – v4.0 33/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino 2005/06/22 – v4.0 34/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Appendix C – 1_ChangeLog.txt v4.0 -- OpenHand Server for Lotus Domino -Change log for version 4.0.0: == Changes since version 3.2.1 + Support for reading contacts in a costom database, writing not supported * Attachment names had " surounding them so they could not be saved on the client device, this has been fixed. + Support for copying whole folders or multiple selected records to the client. + Server for retreaving and generating encryption keys added * Config tool gui changed Sidebar instead of a tree and tabs for sections Change log for version 3.2.1: == Changes since version 3.2.0 2005.05.18 + Added update script in user database * Timezone field in user database fixed * Encryption key and addressbook field in user database made clearer * Starting standalone Backends was broken, fixed. * Failing to connect to Domino server was on rare occations not noticed, this would cause a sequence of error messages instead of just one. *Checking for attachments updated * PocketPC now shows days with calendar events correctly (i.e. bold). * PocketPC now shows repeating calendar events correctly. * Attachment names will now show correctly more often in badly generated emails (mostly spam). * Fixed Calendar/ToDo default folder confusion. * Files Services are now a part of OH Domino + Mail read in OpenHand is now marked as read in Notes. + Server can now access mail files on Domino servers other than the one it is connected to. This means that replicating mail files is no longer neccessary (except for speed reasons). + Attachment name will generated if none provided. (nonameNNNNN.dat). + Fewer eoNNNNtm temporary files left undeleted. + License signature no longer logged. + Security key no longer logged. == Changes since version 3.1.4 2005.05.01 + Individual OpenHand user configuration through a Lotus Notes GUI interface. + Supports persistent connections. + Supports OpenHand Central Server + Supports multiple Backends, i.e. you can have different OpenHand users connecting to different Backends, which in turn connect each to their own Domino server. The Backends do not need to be on the same LAN (or continent for that matter). + Vastly improved Configuration tool + New Primer Tool to assist with setup, and check if the Domino server is set up correctly for OpenHand to work. 2005/06/22 – v4.0 35/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com Pre-Install Document OpenHand Server v. 4.0 for Lotus Domino Appendix C – 2_KnownIssues.txt v4.0 Known Issues for OpenHand Server for Lotus Domino Version: 4.0 Date: 2005.07.21 ## ---- General ---- ### - Installer is not finished yet, so some things need to be done by hand. - Only versions 6.0.x where x >= 3 and 6.5.y where y >= 1 of Domino are supported. We know that version 6.0.1 does NOT work (use free update from IBM). - The first ever connection to the Domino server can take a VERY long time, a few minutes up to dozens of minutes. This is not the OpenHand Server that is working but the Domino server. ### ---- OpenHand server for Domino Issues ---- ### # - Usermaster - # - The Usermaster does not use the openhand.domino.usermaster.email variable, it always sends email to the OpenHand user. - The communication between the Frontend and Usermaster is not encrypted. # - Backend - # - The communication between the Frontend and Backend is not encrypted. # - EMail - # - All Emails are shown as read. This is a Lotus Domino issue which we are still looking for a solution for. This version marks the emails read in OpenHand as read in the Lotus Notes client. - Emails deleted in OpenHand clients are not moved to the Trash folder unless an Email has at some point been deleted in the Notes client. # - Calendar - # - Recurring Calendar events can not be created, but recurring events created in Notes are shown. # - Tasks (To Do) - # - All Tasks are shown together, In Progress, Overdue, Not Started, ... 2005/06/22 – v4.0 36/36 OpenHand Software Ltd. www.openhand-mobile.com - www.softis.com