Installation checklist

When setting up a new DME installation, follow the procedure below. First select the OS you are installing DME on, the collaboration system you are integrating with, and the DME database type. The view below is updated to show a checklist of 17 items with links to the relevant documentation.

1 Hardware and software requirements

Make sure that your server hardware is sufficiently sized, and that it runs the required software. This applies to

  • The DME server
  • The DME connector server(s)
  • The database server

Also make sure that the server operating systems and the collaboration software versions are supported by DME, see System requirements.

Updated: May 16 2017

2 Security and firewall setup

Now you need to set up the firewall for operating DME with other elements in your setup - such as client access, collaboration system, database, and connectors.

Please be aware that for stability reasons, network equipment should not have speed auto-negotiation enabled, but should be set to speed of the slowest network component.

HTML reference:
Updated: Jul 07 2015

3 Integration with backend collaboration system

Now you need to set up the backend collaboration system to allow DME access to mail files/databases etc.

PDF reference:
HTML reference:
Updated: May 16 2017

4 Preparing for Apple Mobile Device Management

*If you are going to use the Apple MDM feature, there is a number of things that must be in place first. Follow the procedure described in the DME online documentation.
Please note that if you are integrating with SOTI MobiControl, enrollment of Apple devices is done through MobiControl.

HTML reference:
Updated: Jul 08 2015

5 Getting the DME software

To get the DME software, you first need to obtain access credentials for the DME support site. Contact your DME partner or DME support for more information.
Then download the following:

  • Download the file from the DME installation server, and run it on Linux. You can use the following wget command:
  • This installer is also used for installing DME connectors.
  • The Domino Unread mark database
  • The Domino ID storage database (if you cannot use Notes ID for encrypted e-mail - see the Integration with Domino doc)
  • The database creation and update scripts (only for MS SQL Server or MySQL Remote)
  • Download or obtain your DME license file. To order the license, you need the MAC address of the DME server machine (or multiple MAC addresses when installing DME as a cluster).
  • DME clients

All of the above files, except the license, can be downloaded from this site.

HTML reference:
Updated: Jul 07 2015

6 Database setup

You must also set up a database for working with DME. Running Linux, you have the following choice of databases:

  • MySQL, installed locally on the DME server.
  • MySQL, installed remotely
  • MS SQL Server
HTML reference:
Updated: May 16 2017

7 Install the DME server and the G/On (AppBox) server

You are now ready to install the DME server for Linux.

If you are running DME 4.x, you also need to install the G/On server in order to use the AppBox functionality.

HTML reference:
Updated: May 16 2017

8 SSL certificate

After installing, you should request and install an SSL certificate on the server. The installer will create a temporary self-signed certificate, which can be used while testing and configuring connectors, but which does not support actual client connections.

For client connections, DME supports using the self-signed certificate, but we warmly recommend using a certificate from a trusted certificate authority for the reasons stated here: SSL certificates (Server Reference).

If you want to use a self-signed certificate from Excitor, you can either:

  1. Send the file signrequest.csr to Excitor Support. The Excitor support team will sign the certificate, and send a file named signed.cer it back to your e-mail address.
  2. Easier: Go to the Excitor DME Certificate Signing page, upload the sign request, and download the Excitor-signed certificate immediately.

Rename the file signed.cer to sslcertificate.pem, and install it on the server. You can find more details in the references below.

PDF reference:
HTML reference:
Updated: May 16 2017

9 Install Nginx

Nginx is an open source SSL proxy server, that provides higher security for SSL connections. Nginx can be used with any version of the DME Server, and is placed in front of the Apache web server.
Nginx can also be used as a Load balancer in a DME cluster setup. As default, port 443 is configured to accept incoming connections from devices, in addition to the port used previously.
PDF reference:
HTML reference:
Updated: May 16 2017

10 Install SMS gateway

Many DME features rely on the DME server having access to an SMS gateway. DME ships with the open source Kannel SMS Gateway software for Linux and Windows. See also the Kannel website.

HTML reference:
Updated: Dec 16 2015

11 Connect to the DME server, install license

Now you are ready to connect to the DME server for the first time.

  1. Open a supported browser, and enter the URL for the DME server, like this:
  2. Log in to DME, using the following credentials:
    Username: SYSADM
    Password: HeraterSol55
  3. Upload the DME licence file you have received from Excitor
  4. Change the password for SYSADM

This last step is VERY IMPORTANT. To change the SYSADM password, do the following:

  1. Click the Devices tab
  2. Click the SYSADM user
  3. Click the User panel in the user setup page
  4. Click Edit password
  5. Enter a new, strong password
  6. Click Accept
HTML reference:
Updated: May 16 2017

11 Install a DME connector

When running Lotus Domino, be sure to configure Domino according to whether you install the connector using Notes session*), Domino session*), or remotely using DIIOP.
The connector OS does not depend on the DME server OS.
)* Please note that on Linux you cannot configure a connector to run using Notes session or Domino session, as those two modes require Windows software.

HTML reference:
Updated: May 16 2017

13 Configure the DME server

In the DME web interface you need to configure the following (minimum):

  • Server: Click the Server tab to configure the server. You need to configure or verify options on the following setup panels (minimum):
    • Authentication
    • Collaboration
    • SMS modem
    • Web
  • Default client settings: Click the Server tab, and then Default settings in the page menu to configure or verify the following options (minimum):
    • Server path
    • Network push path
    • All options in the Security section
  • Notification framework: Click the Server tab, and then Notifications in the page menu. Click Schedule to configure the notification framework.
  • Provisioning: Click the Provisioning tab, and upload DME clients and other software to the DME server - OR: Prepare enrollment and DME provisioning from external MDM provider.
HTML reference:
Updated: May 16 2017

14 Configure the connector

In the DME web interface, click the Connector tab to configure the connector. The configuration options depend on the collaboration system to which the connector connects.

HTML reference:
Updated: Dec 16 2015

15 Deployment

You now need to distribute the DME client to your users. This is mainly done from the Provisioning tab.
If you plan to integrate with an external MDM system, provisioning will be carried out from there. See Appendix B in the server reference.

HTML reference:
Updated: Dec 16 2015

16 Test

Test the DME server thoroughly using a few, assorted test clients, and celebrate the fact that you're done!

Updated: Dec 16 2015

17 Follow DME

Follow DME and Soliton Systems on social media, and sign up for the DME Service Bulletin. The Service Bulletin is sent by e-mail whenever Soliton Systems Europe has important announcements.

Become fan on Facebook  Join LinkedIn  Follow on Twitter  Sign up for Service Bulletins

Updated: Jan 13 2017