HCL Verse and Apache Reverse Proxy Integration

HCL Verse
and Apache
Reverse
Proxy
Integration
Copyright 2020 HCL Technologies Ltd.

Contents
Introduction ................................................................................................................................ 3
Installing and Configuring HCL Verse ...................................................................................... 4
Before you begin .............................................................................................................................. 4
Procedure ......................................................................................................................................... 4
Multi-Server Session bases authentication (Single Signon) ..................................................... 14
Before you begin ............................................................................................................................ 14
Procedure ....................................................................................................................................... 14
Apache Reverse Proxy.............................................................................................................. 16
Apache Reverse Proxy General Diagram ................................................................................. 17
Installing Apache Web Server .................................................................................................. 18
Installing and Configuring SSL on Apache .............................................................................. 21
Configuring Third party SSL certificates in Apache ................................................................ 30
Generate a Certificate Signing Request (CSR) using OpenSSL ................................................... 30
Acquire an SSL/TLS certificate from a third-party CA.................................................................... 33
Configuring Apache to use with HCL Verse: .......................................................................... 35
Summary ................................................................................................................................... 37
Legal statements ....................................................................................................................... 38
Disclaimers ............................................................................................................................... 39
©2020 HCL Technologies Ltd. 2

Introduction
HCL Verse™ is an email and business messaging experience that is based on an
innovative user-centric design, including social analytics and advanced search
capabilities. Verse helps users quickly find and focus on what content is most
important, empowering them to build stronger working relationships while optimizing
business results.
HCL Verse™ brings Verse to the user desktop in the on-premises HCL
Domino® environment. To set up HCL Verse, you complete simple steps on
a Domino server to prepare to begin using mail and calendar features. Offline
capability is available by default and does not require Domino Offline Services (DOLS)
configuration.
In this document, you will learn more about HCL Verse capabilities and how to integrate
HCL Verse with Apache Reverse Proxy Server. It will also cover what Apache Reverse
Proxy Server is and how to install and configure Apache Reverse Proxy Server with
HCL Verse. You will learn how to install self-signed and third-party SSL certificates to
make your Apache Reverse Proxy Server secure, and the configuration required to
integrate HCL Verse with Apache Reverse Proxy Server.

Installing and Configuring HCL Verse
To install and configure HCL Verse™ on a Domino® mail server, complete the
following steps.
Before you begin
Ensure that your Domino server meets the system requirements.
Note: As of release 1.0.8, VOPDesign.nsf has been removed from the kit. Ensure
your user's mail files are on the mail template from Domino 9.0.1 FP9 or later.
Procedure
1. Enable HCL iNotes on the Domino server. Make sure that you run the HTTP
server task and that you configure iNotes® settings. See the topic Configuring
iNotes in the Domino documentation.
2. Register users as iNotes users. See the topic Registering iNotes users in the
Domino documentation.
3. To ensure that international characters are displayed correctly, configure the

Web server to use UTF-8 for output:
a. In the Domino Directory, open the Server document in edit mode.
b. Click the Internet Protocols tab and then the Domino Web Engine tab.
c. In the Character Set section for Use UTF-8 for output, select Yes.
Or, if you use a Web Site document, see the topic Specifying the character set to use
when retrieving Web pages in the Domino documentation.
4. Create full-text indexes on mail files, if they don't already have them. For
information, see the topic Full-text indexes for single databases in the Domino
documentation.
5. Configure the following notes.ini settings on the Domino server:
6. HTTPJVMMaxHeapSize=2048M
HTTPJVMMaxHeapSizeSet=1
If the settings don't exist, add them. If they exist, make sure that they have these
values.
7. Enable SSL on the Domino server. HCL Verse requires HTTPS and a valid
certificate. Follow the instructions in the article Generating a keyring file with a
third party CA SHA-2 cert using OpenSSL and KYRTool on a Windows™
workstation.

Note:
• If you are using a proxy server in front of the Domino server, it is the proxy
server that needs to support HTTPS and have a valid certificate.
• Ensure the SSL key file name field matches the file name that you created.
For more information see the description of the Key Ring File Name field in
the topic Creating a server key ring file in the Domino documentation.
• Domino 11 ships a version of KYRTool. For other versions of Domino, you

can get a version of the tool from here on the HCL Support site.
8. Ensure the SSL port status is enabled. For more information, see the
topic Modifying Web server Internet port and protocol settings in the Domino
documentation.
9. Ensure that you configure the ID vault on the Domino server and that you
assign Verse users to the vault. An ID vault is required so users can read and
send signed or encrypted messages. For information, see the topic Notes ID
vault in the Domino documentation
Note: In the ID vault tab of the Security Settings document that you use to assign
users to the vault, select the option Allow Notes-based programs to use the Notes
ID vault.
10. Ensure that users have valid Internet addresses in their Domino directory
Person documents:
a. Open the Person document.
b. On the Basics tab, verify that the Internet Address field contains a valid
address for example, sdaryn@acme.com.
11. Extract the files from the HCL Verse package. The package contains the
following files:
HCL_Verse.zip
iwaredir.ntf
readme.zip
12. Stop the Domino Web server. From the server console, enter:
tell http quit
13. If a previous version of HCL Verse is installed, delete the existing HCL
Verse jar files from one of the following directories, depending on how product
was installed:

<Domino program directory>/osgi/shared/eclipse/plugins
or
<Domino data directory>/domino/workspace/applications/eclipse/plugins
Use the wildcard syntax "*-1.0.*-0.0-*.jar", core-1.0.*.*.jar and servlet-1.0.*.*.jar to

ensure that only the HCL Verse jar files are removed.
14. Extract the contents of the HCL_Verse.zip file to the following directory:
<Domino data directory>/domino/workspace/applications

<Domino data directory> is typically:
HCL\Domino\Data (Windows)
/local/notesdata (Linux)
Note: Extract with the directory structure intact. After extraction, the Verse On-
Premises .jar files should be in the following directory:
<Domino data directory>/domino/workspace/applications/eclipse/plugins
Note: As of Verse On-Premises 1.0.6, there are just four .jar files, fewer than in
previous versions.
15. Copy iwaredir.ntf to the Domino data directory.
16. If there isn't a redirector database, create one using the iwaredir.ntf template
that you copied to the data directory. For more information, see Using iNotes
Redirect to access mail in iNotes in the Domino documentation. Otherwise,
replace the design of the existing redirector database using the
new iwaredir.ntf template that you copied to the data directory:
Note: This version of the redirector template includes translations for English,
Chinese (China), Chinese (Taiwan), French, German, Italian, Japanese, Korean,
Portuguese (Brazil), and Spanish.
a. From HCL Notes®, open the redirector database on the server. The
default file name is iwaredir.nsf.
b. Click File > Application > Replace Design.
c. Select the new iwaredir.ntf template that you copied to the data
directory.
d. Click Replace and click Yes.
e. On the redirector database UI Setup page, select the following options

which enable users to log on to Verse:
• Enable Personal Options? No.

• Enable Login Options? Yes.
• Enable HCL Verse? Yes.
Figure 1. Screenshot of Redirector database UI Setup Page
f. Set your server's home URL to either /verse or /iwaredir.nsf?open. For

more information, see the topic Configuring HTML, CGI, icon, and Java
files for Web Site documents in the Domino documentation.
17. If you are upgrading from the previous release, simply start the Domino Web
server. From the server console, enter:
load http
If you are setting up Domino for the first time, you may need to stop and
restart the server:
restart server
18. If there is not a credential store application on the server, run the following
commands at the Domino console to create one. The first command creates a
document encryption key to be used for authentication that is called credstore.
The second command creates the application credstore.nsf to store the
encryption key.
19. keymgmt create nek credstore
keymgmt create credstore credstore

Figure 2. Sample output from the Domino Console.
If the mail servers are in a cluster, complete the following steps to configure the
credential store on each additional server:
From the server console of the server on which you created credstore.nsf, enter the
following command to export the encryption key to a file in the Domino data directory:
KEYMGMT export nek credstore <keyname>.key <password>
For example:
KEYMGMT export nek credstore NameVerseKey.key Password
Figure 3. Sample output from the Domino Console.
a. Copy the key file to the data directory of each Domino cluster member.
Figure 4. Screenshot of /local/notesdata where the KEY file is located
b. From the server console of each Domino cluster member, enter the
following command to import the encryption key:
KEYMGMT import nek <keyname>.key <password>
For example:
KEYMGMT import nek NameVerseKey.key Password
You see this response:
NEK credstore - Fingerprint XXXX XXXX XXXX XXXX XXXX XXXX
NEK credstore imported successfully
c. Create a replica of credstore.nsf from the initial server to all Domino

cluster members.

Figure 5. Screenshot showing the location of credstore.nsf
20. To see both iNotes and Verse on login page, you can create domino web
configuration database and map your redirection database:
a. From the File menu go to Application > New
Figure 6. Screenshot of Domino Administrator
b. In new window, Select the server name and give the database title for
example Domino Web Configuration database and choose the template
as Domino Web Server Configuration as shown in Figure 7 below.
Click OK button to proceed with database creation.

Figure 7. New Application window
c. Click Add Mapping option.
Figure 8. Screenshot of Web Server Configuration database
d. In Target Database field, input the redirect database name, for

example, redirect.nsf.

Figure 9. Screenshot of Form Mapping
e. In Target Form field, remove the word “Custom” and replace it with
“DWA” to map the redirect database with DWALoginForm.
Figure 10. Screenshot of Form Mapping
f. Close the database.
g. Open the server document and go to tab Internet Protocol > HTTP >
Home URL and type the redirect database name as shown in Figure
11.

Figure 11. Server Configuration Document
h. Restart the HTTP task.
21. To confirm that Verse On-Premises works, have a user with a mail file on the
server complete these steps:
a. From a browser, go to https://domino_hostname/verse.
b. Log in.
c. Verify that you see the Verse user interface
Figure 12. Sample Verse login page

Multi-Server Session bases authentication (Single Signon)
The Web SSO configuration document is a domain-wide configuration document
stored in the HCL® Domino® Directory. This document, which should be replicated to
all Domino servers participating in the single sign-on domain, is encrypted for
participating servers and administrators, and contains a shared secret key used by
servers for verifying user credentials.
Before you begin
Make sure you have created a Web Site document and enabled the use of Internet Site
documents in the Server document.
Also make sure that your client location document has the home/mail server set to a server in
the same domain as the servers participating in SSO. This ensures that all public keys for
participating server can be found when the SSO document is encrypted.
Procedure
1. In the Domino Administrator, click Files, and open the server's Domino
Directory (usually NAMES.NSF).
2. Select the Internet Sites view.
3. Click Create Web SSO Configuration.
4. In the document, click Keys.
5. Initialize the Web SSO Configuration with the shared secret key in one of two
ways:
o Choose Domino only (no IBM WebSphere® servers participating in single

sign-on), and then select Create Domino SSO Key. If you choose this
option, do not complete Step 6, instead go to Step 7.
o Choose Domino and WebSphere (single sign-on with WebSphere), and

then continue to Step 6.
6. Save the Web SSO Configuration document. A message on the status bar
indicates the number of servers/people for whom the document was
encrypted. The document(s) will appear in the Internet Sites view.
Below is an example of WEB SSO configuration document:

Figure 13. Example of a WEB SSO Configuration document
Figure 14. Example of a Web Site document
For more details on how to create SSO document please refer below link:
https://help.hcltechsw.com/domino/11.0.1/admin/conf_creatingawebssoconfiguration
document_t.html

Apache Reverse Proxy
A reverse proxy is a gateway for servers and enables one web server to provide
content from another transparently. As with a standard proxy, a reverse proxy may
serve to improve performance of the web by caching; this is a simple way to mirror a
website
Proxy servers provide security benefits on top of the privacy benefits. You can
configure your proxy server to encrypt your web requests to keep prying eyes from
reading your transactions. You can also prevent known malware sites from any access
through the proxy server
The reverse proxy becomes a single point of entry for the different web applications in
the organization. The web servers stay hidden and thus protected from the Internet.
Security monitoring such as log review can be performed from a single point. The
reverse proxy can act as a single SSL server.
A reverse proxy accepts a request from a client, forwards it to a server that can fulfil it,
and returns the server's response to the client. A load balancer distributes incoming
client requests among a group of servers, in each case returning the response from
the selected server to the appropriate client.

Apache Reverse Proxy General Diagram
Figure 15. A typical reverse proxy implementation

Installing Apache Web Server
You can install Apache Web Server in different linux operating systems like Linux,
CentOS, or in Ubuntu.
1. To install Apache HTTPD service in Linux, run the command as shown in

Figure 16 and verify the installation as shown in Figure 17.
yum install httpd* -y
Figure 16. Screenshot of Terminal in Linux

2. You can start Apache service using the command systemctl start httpd. To
enable the Apache as service use command systemctl enable httpd.
3. To add the service in firewall use below command.
4. Restart the firewall after making these changes using the command:
firewall -cmd –reload
5. To verify the installation, open a web browser and type the IP address of your
host machine or type localhost. If you see below screen, it means the
installation completed successfully.
Figure 21. Screenshot of testing in a web browser after installation

Installing and Configuring SSL on Apache
1. To install SSL on linux machine first we need to install SSL module. To install
SSL module, we need to use the command yum install mod_ssl* -y as
shown in below screen shot.
Figure 22. Running yum command
Once installation is complete, you should see the output as shown below.
Figure 23. Sample output from running yum command shown in Figure 22

2. To create SSL certificate, go to the path /etc/pki/tls/certs/ and then type make
command followed by name of the site for which you want to create SSL
certificate.
For example, acme.crt. It will ask you to enter password three times.
Figure 24. Creating SSL certificate using make command
Follow the rest of the instructions as shown below.
Figure 25. Sample inputs when creating an SSL certificate
3. To see the certificates, issue the ls command:
Figure 26. Sample output of ls command
4. The next step is to move the key file one folder back from, for example,
“private” folder. We will use mv command to move acme.key. Adding .. will
move the KEY file one directory above the “private” folder.
Figure 27. Using the mv command to move the KEY file
5. Open SSL configuration file using vim editor from below path.
vim/etc/httpd/conf.d/ssl.conf
6. Press : (colon) and the cursor will move at the bottom left corner of the screen.
Type set number or se nu and hit Enter.

Figure 28. Showing Line Number in vim editor
7. Press : (colon) again and type 56 to go to row number 56 as shown below:
Figure 29. Line 56 of ssl.conf file

8. Remove the characters _default_ and replace it with the host IP address.
Figure 30. Sample host IP address

9. Go to row number 60. Remove # and type the server name.
Figure 31a. Uncomment Line 60 then replace the server name
Figure 32. Sample server name to set in Line 60

10. Press : (colon) again and go to Line Number 100. Type the path of acme.crt
file we created in previous steps.
Figure 33. Updating Line 100 of the ssl.conf file
Similarly, change the path for acme.key file as well in Line Number 107.
Figure 34. Updating Line 107 of the ssl.conf file

11. Save the changes by typing :wq!
Figure 35. Saving changes in vim editor
12. To allow HTTPS port in firewall, issue the command below and reload the
firewall.
Figure 36. Allowing HTTPS port in firewall
When you start the HTTPD service, it will ask you to enter password of the
certificate file.
Figure 37. Password prompt when starting HTTPD service

13. To avoid entering password each time you start httpd service, we need to
follow these steps:
a. Go to the private folder where we placed acme.key file and create an

encrypted file using cp command as shown in Figure 38 below.
Figure 38. Creating an encrypted file using cp command
b. At this point, if we restart HTTPD service it will no longer ask for a password.
Figure 39. Restarting HTTPD service
c. We can delete the acme.key-encrypt file as it is no longer needed.
Figure 40. Deleting the .key-encrypt file using rm command

Configuring Third party SSL certificates in Apache
Note from the Author: While I have used Windows computer to create a certificate
and take these screenshots using OpenSSL, the steps and commands used are
same for Linux operating system.
Generate a Certificate Signing Request (CSR) using OpenSSL
1. openssl req –new –nodes –newkey rsa:2048 –keyout server.key –out

server.csr
Note: Give actual server name instead of server.key. For example, see the screen
shot.
Figure 41. Sample command to create CSR

Figure 42. Sample output when creating CSR
The resulting keypair should not be password protected. This isn't a good security
practice, so only perform these steps for production systems on a restricted access
system believed to be secure.
2. type apache.key
type apache.csr

Figure 43. Sample output when using the type command
Figure 44. Sample output when using the type command

Acquire an SSL/TLS certificate from a third-party CA
Provide both the certificates to your vendor and get them stamped from your SSL
provider.
You will receive a certificate just like the one created in the self-signed steps. This
can be displayed by using the "type" command from a command prompt or by
opening the file in Notepad.
type apache.pem
-----BEGIN CERTIFICATE REQUEST-----

MIIC1DCCAbwCAQAwgY4xCzAJBgNVBAYTAkluMQ4wDAYDVQQIDAVEZWxoaTEOMAwG
A1UEBwwFRGVsaGkxGzAZBgNVBAoMEkFjbWUgSW5kaWEgUFZUIGx0ZDELMAkGA1UE
CwwCSVQxFjAUBgNVBAMMDW1haWwuYWNtZS5jb20xHTAbBgkqhkiG9w0BCQEWDmFk
bWluQGFjbWUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz26M
+nleOQvghFZkcSBasWAqu+DP2ylS1r8zjLcl0YcURWGnjxLxtla6H26a7/nOW0py
+jTO6Gv4MnIigAWudqRDjbUDCBY/lyU7/leG5XRmAUEfPDahWbNsps0qGe2pSCsh
6e8L5JS2PBO8TOdA5EGP/0lx6st0G1aQ5denlStrB12WfnzZ3e9vNsCOxF3gUQWk
d+iijT1HUAcqthinU9HiDa/YRfHIRntbyT9yTyboavlQoijjlky1np09RzOq9dF1
Vj07D3wB5ZTuCFkMUPw3vcpKgKLOKHzSnCc2c1YR01iIQoCtNFnN15bmkKRQIZJN
D8EgWB7ReBIWMB9t+wIDAQABoAAwDQYJKoZIhvcNAQELBQADggEBAIMfcFWsjqPr
rmHchiRGPyOZ5/5RVDO1nfxNxXkEg6Ket+odIwzKWtmGgu3SetupwzquOoIcaEIW
PSH/j/zf/LG6oO5fEvYup1z2J7Oie+LTr8RlQaFgv2sQPrsD1L3yJYS/jA2HXY76
q5QZ6MPx8egC7c9Ks/rLHP0YB11pIDDT8kTWhZu9plPa0DblJl3t6xT+CUo0LLPk
yYdX9Y+6MgN8ZLSoJ65aokbd+BAISH80SdYjLNcbDCZ/ew+Wz0V3f/D4cZ4aJA5t
0eqH4At2kkulpdUElsfd2sI5WDE6wwG/DZLox/qbiJjI5tDwI6J+hd8HZm/lrGte
rt31vLxRbyY=
-----END CERTIFICATE REQUEST-----

You may also receive some of the CA's intermediate root certificates. Also note that
the file received may be a CRT file instead of a PEM file. The CRT file will the same
as a PEM file when you display it.
Once you receive the certificates from vendors, you need to copy these certificates
onto the Apache server, for example, on path /etc/httpd/conf/ and define the path in
your apache configuration file.
Next, you will need to define SSL certificate file path in virtual host configuration as
shown below:
Figure 45. Updating the virtual host configuration file
Most the steps are similar for all SSL certificate providers. For example, you may
refer to the below link to see the steps for digicert.
https://www.digicert.com/kb/csr-ssl-installation/apache-openssl.htm

Configuring Apache to use with HCL Verse:
We can define HCl Verse configuration in apche HTTPD.conf file. It is important to create re-
write rule for each cluster mate so that Apache can redirect request to user’s home mail server
on the basic of cookie value. Below is the sample configuration where we have 4 servers in
domino environment (2 servers in each cluster).
Make sure that below code is defined in AutoLogin form in redirection database. You
need to create a field, for example, Apache and need to define this code in AutoLogin
form. This is necessary as Apache redirect requests on the basis of cookies value.
nodecookievalue:= @Name([CN];@NameLookup([NoUpdate];@UserName;"MailServer"));
clustercookievalue:=@DbLookup("":"";@Subset(@DbName;1):"names.nsf";"($ServersLook
up)";nodecookievalue;"clustername");
nodecookie:=@SetHTTPHeader("Set-
Cookie";"inotesses="+@LowerCase(nodecookievalue));
@Success
Figure 46. Adding the code to the AutoLogin form of the redirection database using Domino Designer.

Figure 47. Sample virtual host configuration.
Figure 48. Sample virtual host configuration.
Please refer below article for more details.
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0080495

Summary
In this document, you have learned how to configure HCL Verse. You also learned how to
install Apache Reverse Proxy Server. You should also be able to create and configure self-
signed and third-party SSL certificates on Apache Reverse Proxy Server, as well as
understand the configuration required in Apache configuration file for HCL Verse.
You can check these documents as reference:
Installing and configuring HCL Verse
https://help.hcltechsw.com/verse_onprem/2.0.0/admin/vop_configuring_server.html
Configuring Apache Reverse Proxy Server to use with HCL Verse
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0080495

Legal statements
This edition applies to version 2.0.1 of HCL Verse, 11.0.1 of HCL Domino and to all
subsequent releases and modifications until otherwise indicated in new editions.
When you send information to HCL Technologies Ltd., you grant HCL Technologies
Ltd. a nonexclusive right to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.
©2020 Copyright HCL Technologies Ltd and others. All rights reserved.
Note to U.S. Government Users — Documentation related to restricted rights — Use,

duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule
Contract with HCL Technologies Ltd.

Disclaimers
This document is subject to the HCL Terms of Use (https://www.hcl.com/terms-
of-use) and the following disclaimers:
The information contained in this whitepaper is provided for informational purposes

only. While efforts were made to verify the completeness and accuracy of the
information contained in this publication, it is provided AS IS without warranty of any
kind, express or implied, including but not limited to the implied warranties of
merchantability, non-infringement, and fitness for a particular purpose. In addition, this
information is based on HCL’s current product plans and strategy, which are subject to
change by HCL without notice. HCL shall not be responsible for any direct, indirect,
incidental, consequential, special or other damages arising out of the use of, or
otherwise related to, this whitepaper or any other materials. Nothing contained in this
publication is intended to, nor shall have the effect of, creating any warranties or
representations from HCL or its suppliers or licensors, or altering the terms and
conditions of the applicable license agreement governing the use of HCL software.
References in this whitepaper to HCL products, programs, or services do not imply that
they will be available in all countries in which HCL operates. Product release dates
and/or capabilities referenced in this presentation may change at any time at HCL’s
sole discretion based on market opportunities or other factors, and are not intended to
be a commitment to future product or feature availability in any way. The underlying
database used to support these whitepapers is refreshed on a weekly basis.
Discrepancies found between whitepapers generated using this web tool and other
HCL documentation sources may or may not be attributed to different publish and
refresh cycles for this tool and other sources. Nothing contained in this whitepaper is
intended to, nor shall have the effect of, stating or implying that any activities
undertaken by you will result in any specific sales, revenue growth, savings or other
results. You assume sole responsibility for any results you obtain or decisions you
make as a result of this whitepaper.
Notwithstanding the HCL Terms of Use (https://www.hcl.com/terms-of-use), users of

this site are permitted to copy and save the whitepaper generated from this tool for
such users own internal business purpose. No other use shall be permitted.

HCL Verse and Apache Reverse Proxy Integration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HCL Verse and Apache Reverse Proxy Integration

Uploaded by

Copyright:

Available Formats

HCL Verse

Copyright 2020 HCL Technologies Ltd.

Installing and Configuring HCL Verse ...................................................................................... 4

Before you begin .............................................................................................................................. 4

Multi-Server Session bases authentication (Single Signon) ..................................................... 14

Before you begin ............................................................................................................................ 14

Apache Reverse Proxy.............................................................................................................. 16

Apache Reverse Proxy General Diagram ................................................................................. 17

Installing Apache Web Server .................................................................................................. 18

Installing and Configuring SSL on Apache .............................................................................. 21

Configuring Third party SSL certificates in Apache ................................................................ 30

Generate a Certificate Signing Request (CSR) using OpenSSL ................................................... 30

Acquire an SSL/TLS certificate from a third-party CA.................................................................... 33

Configuring Apache to use with HCL Verse: .......................................................................... 35

Legal statements ....................................................................................................................... 38

©2020 HCL Technologies Ltd. 2

©2020 HCL Technologies Ltd. 3

Before you begin

Ensure that your Domino server meets the system requirements.

3. To ensure that international characters are displayed correctly, configure the

a. In the Domino Directory, open the Server document in edit mode.

5. Configure the following notes.ini settings on the Domino server:

©2020 HCL Technologies Ltd. 4

• Domino 11 ships a version of KYRTool. For other versions of Domino, you

a. Open the Person document.

tell http quit

©2020 HCL Technologies Ltd. 5

<Domino data directory>/domino/workspace/applications/eclipse/plugins

Use the wildcard syntax "*-1.0.*-0.0-*.jar", core-1.0.*.*.jar and servlet-1.0.*.*.jar to

<Domino data directory>/domino/workspace/applications

<Domino data directory>/domino/workspace/applications/eclipse/plugins

15. Copy iwaredir.ntf to the Domino data directory.

b. Click File > Application > Replace Design.

d. Click Replace and click Yes.

e. On the redirector database UI Setup page, select the following options

• Enable Personal Options? No.

©2020 HCL Technologies Ltd. 6

• Enable HCL Verse? Yes.

Figure 1. Screenshot of Redirector database UI Setup Page

f. Set your server's home URL to either /verse or /iwaredir.nsf?open. For

19. keymgmt create nek credstore

keymgmt create credstore credstore

©2020 HCL Technologies Ltd. 7

KEYMGMT export nek credstore <keyname>.key <password>

KEYMGMT export nek credstore NameVerseKey.key Password

Figure 3. Sample output from the Domino Console.

KEYMGMT import nek <keyname>.key <password>

KEYMGMT import nek NameVerseKey.key Password

You see this response:

NEK credstore - Fingerprint XXXX XXXX XXXX XXXX XXXX XXXX

NEK credstore imported successfully

c. Create a replica of credstore.nsf from the initial server to all Domino

©2020 HCL Technologies Ltd. 9

a. From the File menu go to Application > New

Figure 6. Screenshot of Domino Administrator

©2020 HCL Technologies Ltd. 10

c. Click Add Mapping option.

Figure 8. Screenshot of Web Server Configuration database

d. In Target Database field, input the redirect database name, for

©2020 HCL Technologies Ltd. 11

Figure 10. Screenshot of Form Mapping

f. Close the database.

©2020 HCL Technologies Ltd. 12

h. Restart the HTTP task.

Use the wildcard syntax "-1.0.-0.0-.jar", core-1.0..*.jar and servlet-1.0...jar to