Created date: 8.7.2024
Updated by: Emma Camacho
LICENSE
Note the expiration date and parallel executions and verify that it corresponds to the subscription period, if it doesn't, contact [email protected].
The renewal subscription email will be sent shortly before the expiration date. It will be sent by [email protected] to the previously defined email.
Verify that the emails sent by [email protected] don't land in the spam folder.
SERVER
Attention: Changes in this Menu will require a service restart.
Attention: Some of the items are not present in the M&D SaaS edition.
GENERAL
Authentication
The service account is displayed in this section. If necessary, the service account can be changed in this section.
Network
The Port numbers should be different.
Attention: IN M&D on-prem, when using the M&D Extensions for Qlik Sense and calling Qlik Sense with HTTPS a 3rd party certificates is mandatory and its THUMBPRINT should be added.
The 3rd party certificate should have the following attributes
- Certificates that are x509 version 3. More information including filename extensions under https://en.wikipedia.org/wiki/X.509
- Use signature algorithm sha256RSA
- Use signature hash algorithm sha256
- Signed by a valid, and OS/browser configured , CA
- Are valid according to date restrictions (valid from/valid to)
- Key in format CryptoAPI (not in CNG)
- The certificate itself has to contain private key
If Qlik Sense is used with HTTP, the calls to M&D API can be made with HTTP and the 3rd party certificate is not necessary.
Before handling certificates Enable HTTP, otherwise there's the risk to be locked out.
Debugging
Enable this option only when instructed by Mail & Deploy support team. And disable it as soon as the support ticket is close.
Attention: Debugging files are stored in c:\Mail & Deploy folder\Data\Dumps and can be deleted as soon as the support ticket is close.
SERVICE ENDPOINTS
Attention: in M&D SaaS edition a Heartbeat Service Endpoint is included (Heartbeat-do-not-delete). Do not delete.
Use the URL Folder to form the correct URL to gain access to the Management Console, Hub or API depending on the Authentication Method that is required. For example, using the above screenshot's settings:
http://server:14999/Management to gain access to the Management Console using Windows authentication.
http://server:14999/Management/custom to gain access to the Management Console using Custom credentials.
ADDITIONAL SETTINGS
Attention: During installation PARALLEL EXECUTIONS is set by default to 1. Increase it according to the license and the size of the server that is running Mail & Deploy server.
The rest of the settings can remain as they are set during installation.
DATA EXCHANGE
Attention: By default, during installation the DATABASE TYPE is set to (none). Please set it to one of the provided options. If you don't have a SQL Server, you can always use Local SQLite Database.
USER DIRECTORIES
The most common user directories are Active Directory and Azure AD.
The Active Directory configuration looks something like this:
The Azure AD looks like this:
For more information, see User Directory - Azure AD
Here as some examples for the USER GROUP QUERIES (apply to both Active Directory and Azure AD)
Attention: The group names (in this example Development and MD_Hub) should be present in the Active Directory / Azure AD.
Attention: The users will be synchronized when pressing the Sync icon in the LIST of User Directories.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article