On all documentation pages, the applications refer to the .war files present on the DigDash Enterprise server:

  • Server: ddenterpriseapi.war
  • Dashboard: digdash_dashboard.war
  • Web Studio: studio.war
  • Home page and Desktop Studio: adminconsole.war

This set of applications constitutes a domain. Depending on the needs, this set can be duplicated, for example to have a development context and another for production.

Domain concept

  • A domain is an instance of DigDash, it means that you can have different environment (Development, testing and production) or you can split DigDash in business units (RH, Sales, etc.).
  • Every configuration files will be different in each environment (color scheme, translating files, hierarchies)

There are two use cases for domains :

  • Keep all instances of environments on the same server
  • Split in different instances for your business unit. Having one domain already permits to split your data and graphs into several roles, but having several domains will help you partition more securely.

Domain settings

Note: in this case, we suppose that LDAP server is shared between every domain. If you don’t want this, you will have to configure the LDAP by changing port.

Creating a domain

  1. Stop the Tomcat server
  2. Go the directory <DigDash installation path>\apache-tomcat\webapps
  3. Copy/paste the following files:
    • ddenterpriseapi.war
    • adminconsole.war
    • digdash_dashboard.war
    • studio.war

Warning: do not copy/paste the adswrapper.war file (LDAP)

  1. Rename these files with the wanted domain name liked. For instance: 
    • ddenterpriseapi_new.war
    • adminconsole_new.war
    • digdash_dashboard_new.war
    • studio_new.war
  2. Restart the Tomcat server and wait for the complete deployment. 

Settings for 2021R1 versions and more recent

  • Open the following file : <DigDash installation path>/digdash.properties.
  • From the 2021R1 version, settings of all applications and domains are included in this file. 
  • Delete the 3 following parameters :
  • adminconsole.adminconsole_domain=adminconsole
  • adminconsole.server_domain_list=ddenterpriseapi
  • adminconsole.dashboard_domain=digdash_dashboard
  • And add the 3 following ones :
  • adminconsole_new.adminconsole_domain=adminconsole_new
  • adminconsole_new.server_domain_list=ddenterpriseapi_new
  • adminconsole_new.dashboard_domain=digdash_dashboard_new

Settings for 2020R2 versions and older

  1. Open the file apache-tomcat\webapps\adminconsole_new\WEB-INF\web.xml and edit it as below :
     <param-name>server_domain_list</param-name> <!-- separate domain name by comma -->
  1. Open the file apache-tomcat\webapps\digdash_dashboard_new\WEB-INF\web.xml and edit it as below :
  1. Connect to the new domain through the URL: http://localhost:8080/adminconsole_new

LDAP Management

It is possible to use a distinct LDAP (and so a specific user, role, and/or rights) for each domain.

In Apache Directory Studio:

  • Create a new connection to LDAP DigDash:
  • You will need the following information:
    • DigDash server’s IP,
    • Port : 11389
    • User : uid=admin,or=system
    • Password : admin


  • Right click on the domain dc=digdash,dc=com,
  • Then cklick on New and then on New Entry
  • Select the option Create the entry from scratch


  • Add the organizationalUnit class


  • Then click on Next >
  • In the RDN field, put ou = domain_name


  • Then click on Next > and then on Finish

In DigDash Enterprise server settings :

  • From the DigDash Enterprise server home page, go to the Configuration section
  • Then, go to the Server settings part
  • In the left-vertical menu, select the LDAP... element


  • Click on the LDAP Queries button


  • On the first field, change the value to set  "ou=domain_name,dc=digdash,dc=com"


  • Click on Save to save the changes.
Copyright ©2006-2023 DigDash SAS