Before you can configure the Groupware app, you have to install d.velop documents domino on the HCL Domino server. Run the d.velop documents domino setup program on the HCL Domino server to install d.velop documents domino (servlet) and the d.velop documents update site.
You can specify the installation path of the d.velop documents domino service when you select the components in the setup. The default installation path is: d3\d.3one\addons\DecsDomino
Let's assume you have completed all the preparatory steps and want to install d.velop documents domino.
This is how it works
In the Groupware app setup, select the d.ecs domino service setup component.
Open the folder d3\d.3one\addons\DecsDomino in the installation directory and copy the file decs_domino_windows_<version number>_setup from the folder.
Go to the HCL Domino server and paste the d.velop documents domino setup program into a directory.
Run the EXE file as an administrator and follow the installation steps in the installation wizard.
Enter the installation location.
Select which components you want to install.
Under IBM Domino server, enter the name and domain of the HCL Domino server on which the d.velop documents domino service will be installed.
Under IBM Domino administrator, enter the login name of the HCL Domino administrator account and the domain. Make sure that the user has permissions to create databases and start services.
Enter the base address under d.3one application server host. This is the name of the server on which d.velop documents is or will be installed.
Under d.3one application server port, enter the default port for d.ecs http gateway. The default value is 443.
Under Path for temporary files, enter a folder where temporary files that are needed when processing documents will be stored while d.velop documents domino is running. Make sure that the temporary folder is not scanned by any antivirus software; otherwise, access to temporarily stored files may be disrupted.
The next step is to specify the certificate to be used for communication between the d.velop documents application server and d.velop documents domino.
After you have specified the path for the temporary files during the setup with the installation wizard, you have to specify the certificate to be used for communication between the d.velop documents application server and d.velop documents domino. The further steps in the installation will differ depending on the option you select, and you will need to enter different information for each option. Three options are available to you:
Create self-signed certificate: This certificate is suitable for testing purposes only. You have to manually install the certificate as a valid certificate on the d.velop documents server. Creating a self-signed certificate creates only the certificate itself. It does not create a trust relationship via a valid certification authority.
Install trusted certificate: This option allows you to use a certificate for d.velop documents domino that already exists on the server. You may need to distribute the certificate to establish a trust relationship between the server running d.velop documents domino and the d.velop documents application server.
Use Keystore from previous installation: If you have already uninstalled d.velop documents domino on a server but the configuration and Keystore still exist, you can use this option to reuse the original Keystore.
You can create a self-signed certificate—for testing purposes, for example—by selecting the Create self-signed certificate option during the d.velop documents domino setup. You can use the Certify and import the PKCS #7 file option to send a certificate signing request (CSR) to your domain to have the self-signed certificate certified by a valid certificate authority in your domain. You can use the signed certificate in a production environment without having to distribute the certificate manually.
To use the certificate, follow the steps in the installation wizard.
Let's assume you also want to use the self-signed certificate in your production environment.
This is how it works
Enter the organization data in the wizard.
Enter the password for the Keystore.
Check that the host name is identical to the fully qualified domain name (FQDN) you entered in the d.3one in IBM Notes: d.ecs domino address installation step under d.ecs domino host.
Enter one or more organizational units under Organizational Unit. Separate multiple entries with a semicolon.
Under Country, enter the two-character ISO country code, e.g. DE for Germany or US for the United States of America.
Enable the Certify and import the PKCS #7 file option.
Define a password for the Keystore to be created.
Copy the entire contents of the Certificate request text box.
Select the Web server option for the certificate template.
Provide the contents of the certificate to your certification authority for signing.
Create a Base64-encoded certificate chain as a *.p7b file.
Enter the exported certificate chain in the input box.
If you have a trusted certificate, you can use the certificate for the d.velop documents domino setup. During setup, select the option Install trusted certificate.
To use the certificate, follow the steps in the installation wizard. Specify the certificate and enter the password for the Keystore. This certificate is a different certificate than the d.velop documents certificate. You need to issue the certificate for the server that is running the HCL Domino server with the d.velop documents domino service installed.
Alternatively, you can create a domain certificate for d.velop documents domino in the same way you create a web server certificate for d.ecs http gateway. Enter the fully qualified server domain name (FQDN) you entered in the d.3one in IBM Notes: d.ecs domino address installation step under d.ecs domino host.
If your certificate is encrypted, enter the password for the Keystore used by d.velop documents domino in the d.velop documents domino setup. The Keystore is automatically created with the PKCS12 Keystore certificate chain and the new password.
If you have already uninstalled d.velop documents domino on a server but you did not delete the configuration and the Keystore during the uninstall, you can use the Keystore for communication between the d.velop documents application server and d.velop documents domino.
To use the existing Keystore, follow the steps in the installation wizard. Enter the password and the key for the Keystore.
If you select Install d.ecs domino and Install update site when installing d.velop documents domino for the first time, you can fully configure the HCL Domino-based update site during the setup. During the setup you can also configure a widget catalog, a policy, a desktop setting and a group for distributing the d.velop documents sidebar plug-in in the mailbox.
You can make various settings for the update site and widget catalog in the setup dialog Create an IBM Notes/Domino UpdateSite and WidgetCatalog.
This is how it works
Select Create an IBM Notes/Domino UpdateSite to create an NSF-based update site on the HCL Domino server.
If necessary, select Use named server if you want to set up the update site on an alternate server, then enter the name of the alternate server under Server name. If you want to use the current HCL Domino server, leave the option unselected.
If necessary, enter the file name of the update site database, including the path relative to the Domino data directory, under File name. The default file name is: dvelop/d3ecm_updatesite.nsf
If necessary, enter the title of the database to be created under Title. The default title is d.3ecm UpdateSite.
Select Create an IBM Notes/Domino WidgetCatalog to create a widget catalog on the HCL Domino server. The widget catalog is based on toolbox.ntf.
If necessary, enter the file name of the widget catalog database, including the path relative to the Domino data directory, under File name. The default title is d.3ecm WidgetCatalog.
If necessary, enter the category of the widget under Category. The default category is d.3ecm.
If necessary, specify a protocol under Use NRPC or HTTP for distributing the d.velop documents sidebar plug-in in the mailbox. NRPC (Notes Remote Procedure Call) is used by default. For the HTTP option, you have to enable and configure the HTTP task for the HCL Domino server.
After you have performed the setup, you need to specify the host computer and the port for d.velop documents domino in the configuration of the Groupware app.
This is how it works
Open the Configuration feature from the start page and select the item IBM Domino under E-mail management in the Common settings area.
Click Enable IBM Domino services.
Under d.ecs domino service server, enter the host name of the HCL Domino server as a fully qualified domain name (FQDN).
If necessary, change the port for d.velop documents domino. The HCL Domino server uses the port to communicate with the d.velop documents application server. The default port is 8182. If you change the default port, enter the new port in the HCL Domino configuration database under SSL port. You also have to change the SSL port under d.ecs domino in the d3onecfg.nsf database on the HCL Domino server.
Save your entries.