Configuring the context parameters

Some context parameters must be specified in the Servlet Manager in order for SECollab to work properly. The procedure for specifying a context parameter depends on the selected application server. See the corresponding section for Apache Tomcat or IBM Application Server Liberty.

Valid attributes for each Parameter are the following.

Attribute Description
description Optional. The literary description of the context parameter.
name Mandatory. The name of the context parameter to be created.
value Mandatory. The value of the parameter that will be specified in the application. The values shown below are examples and must be modified to match your configuration

List of context parameters

Attribute Description
description When purchasing SECollab, two options are available for managing licenses. You will have either been given a license file, installed locally on the server, or an application to install to play the role of License server. In the first case, you will enter the absolute path (the file must be located on the application server hosting SECollab). In the second case, you will indicate the address of the server.
name mdw.license

Two values are possible:

  • License Server
    Specify the license server address with the syntax port@nameOfServer. The port is optional and usually does not need to be filled in.
    Example: @LicenceServer
  • Local license file
    Specify the absolute path of the license file installed on the same server as the machine hosting SECollab.
    Example: c:\licences\secollab.lic
Attribute Description
description Absolute path to the folder where SECollab will store the files it needs. This folder must be set to the machine hosting the SECollab server and exist before the application is deployed to the application server.
name mdw.server.workspace
value Example: c:\secollab\workspace

List of context parameters for the Neo4j database

Attribute Description
description Hostname of the Neo4j server(s)
name mdw.server.neo4j.uri
value Example: bolt+s:// for a single server, bolt+s://|bolt+s:// for a cluster of servers. Refer to the official documentation for the protocol
Attribute Description
description Name of the Neo4j user used by SECollab
name mdw.server.neo4j.user
value Example: secollab
Attribute Description
description Password of the Neo4j user used by SECollab
name mdw.server.neo4j.password
value Example: anyPasswordOfYourChoiceWillBeBetterThanThisOne...
Attribute Description
description (optional parameter) Indicates if users are authenticated against an LDAP host.
name mdw.server.platform.ldap.enabled
value Default: false
Attribute Description
description URL to LDAP host, an absolute path to users or group cannot be use.
value Example: ldap://example.domain:port/
Attribute Description
description (optional parameter) The LDAP domain to use. If not set or empty, the domain will be inferred from the host.
name mdw.server.platform.ldap.domain
value Example: example.domain
Attribute Description
description The path within the LDAP host where users will be searched for during the authentication process.
name mdw.server.platform.ldap.path
value Example: CN=dev,OU=Group,DC=example,DC=domain
Attribute Description
description (optional parameter) Indicates the provided path points to a group, hence to users references (value "true"). By default, considers the provided path points to users.
name mdw.server.platform.ldap.useGroup
value Default: false
Attribute Description
description LDAP user to call LDAP authentication.
name mdw.server.platform.ldap.user
value Example: ldap
Attribute Description
description LDAP user's password to call LDAP authentication.
name mdw.server.platform.ldap.password
value Example: password
Attribute Description
description LDAP Property to match to a user's property
name mdw.server.platform.ldap.mapping.X

Two values must be provided:

  • login
    The user's login
    Example: sAMAccountName
  • name
    The user's name
    Example: name

One additional value can be provided:

  • email
    The user's email address
    Example: mail

Note: It is necessary to restart your application server after changing its context parameters.