Open Documentation Menu

d.3one application server (configuration options)

Either before or after finishing installation, you can optionally set which document types can be downloaded. This can be configured by using the user rights in d.3 admin.

After successfully finishing installation, you can add additional d.3 repositories or remove existing repositories and adjust the log level for single apps.

You can also set an additional reverse proxy. For additional information see Using an additional reverse proxy.

See also:

Managing d.3 repositories

You can add, edit or remove d.3 repositories for your users in the feature d.3 Repositories. In addition, you can, for example, assign a single d.3 repository to a dedicated user group so that only this user group can access the d.3 repository.

You can find the feature on the start page https://<Baseaddress>/home. You can also view the feature on any client PC in a browser using https://<Baseaddress>/repo/repositories/.

Note

JavaScript must be enabled in the browser in order to manage d.3 repositories.

In this chapter you can learn how to add, edit and remove a d.3 repository. You can also define a d.3 repository as default repository for your users in order to always have the definite repository selected in the features. If you users already selected a different repository, the user-specific d.3 repository is displayed as default in the features.

Note

To configure a connection to a d.3 repository, you need to log in using a user account of the administrator group (Admin Group in d.ecs identity provider). For more information, see the Configuration guidelines for d.velop infrastructure components in the d.ecs identity provider articles.

Options and actions in the start section

If you have already added d.3 repositories, these repositories are displayed in the start section of the feature. Per each entry for a repository, you can view the d.3 repository name (e.g. Production system) and the d.3 repository ID (e.g. P). If you have set a repository as default, this repository is displayed on the top of the list and is indicated as default repository. As soon as you have defined a repository as default, you can change the definition only, if you define a different repository as default.

Use the actions on the toolbar , for example, to edit or remove the selected d.3 repository connections, and define a d.3 repository as default. The actions are only displayed, if you logged in as administrator. The Define as default action is not displayed to you, only if a repository is already defined as default.

If you select an existing d.3 repository, the properties for this repository are displayed.

Information in the section "Details"

This information is specified when you establish a connection to a d.3 repository. The same information and connection data to a d.3 repository is then displayed in this section once it is created:

  • Repository ID: Specifies the connection ID. The ID matches the ID which is generated automatically by d.3 server for identifying a repository

  • Repository display name: Specifies the display name of the d.3 repository. You can specify any name. The name is used as a guidance for the user. You can change the display name at any time.

  • d.3 repository ID: Specifies the ID of the d.3 repository to be connected.

  • Host: Specifies the name of the computer hosting the d.3 repository.

  • Port: Specifies the port number used to access a d.3 repository.

  • d.3 gateway encryption: Specifies, whether to encrypt the communication with the d.3 repository (D3FC encryption). When adding a connection to a repository, select the d.3 gateway public.key file to enable the encryption. If you do not select a public.key file, there is no encrypted communication. You can change the d.3 gateway encryption at any time.

  • Visible for: Specifies the ID of a d.ecs identity provider user group for which this d.3 repository should be available. The value is a GUID or empty. If you do not specify an ID, then this d.3 repository is visible to all users. You can also assign a d.3 repository to a dedicated user group. If you have specified an ID, then this d.3 repository is only visible for users in this user group. You can edit a user group or remove an existing user group at any time.

Note

The available repositories are cached for some times in d.3one so that changes in the repository configuration are not instantly applied, provided the data are cached previously.

Note

When opening the feature d.3 Repositories, you may need to enter your credentials again, although the authentication was correctly set.

Cause: The fully qualified domain name (FQDN) for the server is not added to the security zone Local Intranet for the browser. For additional information see, e.g. KB303650 on the Microsoft support website.

Make sure that you logged in using a user account of the administrator group (Admin Group) and that the page is added to the security zone Local Intranet.

Using an additional reverse proxy

You can use functionality that uses the base address with an additional reverse proxy which is used in front of the d.ecs http gateway app. In order to use the OpenSearch functionality, for example, you need to use the URL of the reverse proxy in the DMSApp.

If you want to specify the URL of the reverse proxy, you can modify the web.config file in the installation directoryc:\d3\d.3one\dms.

This is how it works

  1. Open the web.config file in the installation directory \dms\.

  2. In the file, go to the following section and change the value:

    <!-- This parameter defines the base address of the client. -->
    <!-- Must be set when you use an additional reverse proxy. -->
    <add key="Client.BaseUri" value="" />
Adjusting the log level in the d.3one apps

You can individually configure the log level for each app (microservice) in d.3one. By default, the log level for each app is set to INFO.

Adjusting the log levels for the Apps DMSApp, InboxApp, ImageApp and HomeApp

For adjusting the log level, do the following:

  1. On the d.3one application server, go to the installation directory for the apps you want to adjust. The default name for the installation directory is c:\d3\d3one\<app name>.

  2. Open the Web.config configuration file and go to the section <log4net>.

  3. Go to the <level value="INFO"/> entry and set the value for the log level for the value property. The possible values are DEBUG, INFO, WARN and ERROR.

  4. Once the log level is changed, restart the Internet Information Services (IIS) Manager.

<log4net>
        [...]
        <root>
                <level value="INFO"/>
                <appender-ref ref="DvelopAppender"/>
        </root>
</log4net>

Adjusting the log level for the apps d.ecs repo, d.ecs process portal, d.ecs file container, d.ecs pdf, and d.ecs identity tunnel

For adjusting the log level, do the following:

  1. On the d.3one application server, go to the installation directory for the apps you want to adjust. The default name for the installation directory is c:\d3\d3one\<app name>.

  2. Go to the \conf\ folder.

  3. Rename the template file appsettings.config.template as appsettings.config.

  4. Open the appsettings.config configuration file and go to the <appsettings> section.

  5. Go to the <add key="logLevel" value="INFO"/> entry and set the value for the log level for the value property. The possible values are DEBUG, INFO, WARN and ERROR.

  6. Restart the service of the app you adjusted.

<appSettings>
        <!-- Define log level -->
        <add key="logLevel" value="INFO" />
        [...]
</appSettings>