5.3.1 Changing the configuration file

■ Specifying the server IP address

Specify the server IP address.

<end-point>
    <ip>server-IP-address</ip>
</end-point>
<end-point protocol="https">
    <ip>server-IP-address</ip>
</end-point>

Important

To make the server accessible from the Internet, specify a global IP address.

Example:

<end-point>
    <ip>192.168.0.2</ip>
</end-point>
<end-point protocol="https">
    <ip>192.168.0.2</ip>
</end-point>

■ Specifying the mail server

Specify the mail server information. For details about the mail server information, see 3.2.3 Mail server used by the system and 3.2.4 Sender email address.

<mail-notification>
    <mail-server>
        <host>mail-server-host-name</host>
        <port>mail-server-port-number</port>
        <user>SMTP-authentication-user-ID</user>
        <password>SMTP-authentication-password</password>
        <secure-protocol>SMTP-type#</secure-protocol>
    </mail-serer>
    <notification-from>
        <system-address>sender-email-address</system-address>
    </notification-from>
    ...
</mail-notification>

#

For the <secure-protocol> tag, specify the type of protocol used for transmission path encryption. If nothing is specified, encryption is not applied. For encryption, specify either of the following:

SMTPS: Encrypts the transmission path using SSL or TLS.

STARTTLS: Encrypts the transmission path using STARTTLS.

Important

To use SMTP authentication, specify a user ID and password for SMTP authentication for the <user> and <password> tags. If you do not use SMTP authentication, leave the <user> and <password> tags empty. The sender-email-address is used as the email address of the sender of notification emails sent from JP1/DH - Server to the users.

Example:

<mail-notification>
    <mail-server>
        <host>smtp.foo1.foo2.co.jp</host>
        <port>587</port>
        <user>user01</user>
        <password>password01</password>
        <secure-protocol>SMTPS</secure-protocol>
    </mail-serer>
    <notification-from>
        <system-address>jp1dh-system@foo1.foo2.co.jp</system-address>
    </notification-from>
    ...
</mail-notification>

■ Specifying the server FQDN and domain name

Specify the FQDN (Fully Qualified Domain Name) and domain name of the server.

<biz-connect id="bizconnect">
    <service>
        ...
        <bind-hostname>server-FQDN#</bind-hostname>
        <bind-domainname>server-domain-name</bind-domainname>
        <bind-sub-domainname>server-subdomain-name</bind-sub-domainname>
        ...
    </service>
</biz-connect>

#

Do not use an underscore (_) for the host name (computer name). Using an underscore for the host name causes a malfunction.

Examples of the settings are as follows:

• Example 1: When the server FQDN is xxx.yyy.zzz.co.jp

  Server domain name: zzz.co.jp

  Server subdomain name: xxx.yyy

• Example 2: When the server FQDN is xxx.yyy.zzz.com

  Server domain name: zzz.com

  Server subdomain name: xxx.yyy

Example:

<biz-connect id="bizconnect">
    <service>
        ...
        <bind-hostname>jp1dhserver.foo1.foo2.co.jp</bind-hostname>
        <bind-domainname>foo2.co.jp</bind-domainname>
        <bind-sub-domainname>jp1dhserver.foo1</bind-sub-domainname>
        ...
    </service>
</biz-connect>

■ Changing the storage folder for delivery data

Change the storage folder for delivery data^# (absolute path) as needed. For details about the storage folder for delivery data, see 3.2.2 Storage folder for delivery data.

<biz-connect id="bizconnect">
    ...
    <persistence>
        <storage>
            <directory>absolute-path-of-the-storage-folder-for-delivery-data#</directory>
        </storage>
    </persistence>
    ...
</biz-connect>

#: For the storage folder for delivery data, note the following points:

• Specify a folder on the local file system. If you specify a network folder, the file I/O might become a bottleneck, decreasing the transmission speed.

• Specify a path in 4 to 70 characters.

• Before changing the current storage folder for delivery data, create a new storage folder for delivery data in advance.

Example:

<biz-connect id="bizconnect">
    ...
    <persistence>
        <storage>
            <directory>D:\data</directory>
        </storage>
    </persistence>
    ...
</biz-connect>

■ Changing the network bandwidth limit

Change the network bandwidth limit as needed. For details about the network bandwidth limit, see 3.3.2 Network bandwidth limit.

<biz-connect id="bizconnect">
    <service>
        ...
        <throughput-limit>
            <upload>maximum-transmission-bandwidth-for-uploading#</upload>
            <download>maximum-transmission-bandwidth-for-downloading#</download>
        </throughput-limit>
        ...
    </service>
</biz-connect>

#: For values you can specify, note the following points:

• A specified value is recognized as a value in Mbps.

• Specify a value in the range from 0 to 1,000. You cannot omit the value.

• means no bandwidth limit.

Example: When you specify 80 Mbps for the bandwidth limit for uploading and 100 Mbps for the bandwidth limit for downloading:

<biz-connect id="bizconnect">
    <service>
        ...
        <throughput-limit>
            <upload>80</upload>
            <download>100</download>
        </throughput-limit>
        ...
    </service>
</biz-connect>

■ Changing the keep-alive timeout period

Change the keep-alive timeout period as needed. For details about the keep-alive timeout period, see 3.3.3 Keep-alive timeout period.

<biz-connect id="bizconnect">
    <service>
        ...
        <keep-alive>
            <client>client-keep-alive-timeout-period#</client>
            <server>server-keep-alive-timeout-period#</server>
        </keep-alive>
        ...
    </service>
</biz-connect>

#: For values you can specify, note the following points:

• A specified value is recognized as a value in seconds.

• Specify a value as 0 or in the range from 30 to 7,200. You cannot omit the value.

• 0 means disabled timeout (no timeout).

Example: When you specify 180 seconds for the client keep-alive timeout period and 180 seconds for the server keep-alive timeout period:

<biz-connect id="bizconnect">
    <service>
        ...
        <keep-alive>
            <client>180</client>
            <server>180</server>
        </keep-alive>
        ...
    </service>
</biz-connect>

■ Changing the number of concurrent connections

Change the number of concurrent client-server connections as needed. For details about the number of concurrent connections, see 3.3.4 Concurrent connections.

<biz-connect id="bizconnect">
    <service>
        ...
        <service-task>
            <initial>number-of-initial-connections#</client>
            <maximum>maximum-number-of-connections#</server>
        </service-task>
        ...
    </service>
</biz-connect>

#: For values you can specify, note the following points:

• Specify a value in the range from 1 to 64. You cannot omit the value.

• Specify values so that the initial value is equal to or less than the maximum value.

Example: When you specify 4 for the number of initial connections and 64 for the maximum number of connections:

<biz-connect id="bizconnect">
    <service>
        ...
        <service-task>
            <initial>4</initial>
            <maximum>64</maximum>
        </service-task>
        ...
    </service>
</biz-connect>

■ Changing the connection queue size

Change the connection queue size as needed. For details about the connection queue, see 3.3.5 Connection queue size.

<biz-connect id="bizconnect">
    <service>
        <backlog>connection-queue-size#</backlog>
        ...
    </service>
    ...
</biz-connect>

#: Specify a value in the range from 2 to 64. You cannot omit the value.

Example: When you specify 16 for the connection queue size:

<biz-connect id="bizconnect">
    <service>
        <backlog>16</backlog>
        ...
    </service>
    ...
</biz-connect>

■ Specifying the block size during transfer and reception

Specify the block size for sending a file from a client to JP1/DH - Server, or for downloading a file from JP1/DH - Server as needed. For details about the block sizes during transfer and reception by default, see 3.3.7 Block size during transfer and reception.

<biz-connect id="bizconnect">
    <service>
      ...
      <communication-engine>
        <block-size>
          <send>block-size-for-transfer#</send>
          <receive>block-size-for-downloading#</receive>
        </block-size>
      </communication-engine>
      ...
    </service>
    ...
</biz-connect>

#: For the block size, specify a value as 0 or in the range from 32 to 512. A value is set in KB. If you omit the value or specify 0, the system automatically determines the size depending on the network condition when starting to send or receive a file. If you specify a value in the range from 32 to 512, regardless of the network condition, communication is performed based on the specified block size.

Example: When you specify the fixed block size during transfer and reception (512 KB):

<biz-connect id="bizconnect">
    <service>
      ...
      <communication-engine>
        <block-size>
          <send>512</send>
          <receive>512</receive>
        </block-size>
      </communication-engine>
      ...
    </service>
    ...
</biz-connect>

■ Specifying the buffer size during transfer and reception

Specify the buffer size used for sending a file from JP1/DH - Server to a client and receiving a file from a client. For details about the buffer size during transfer and reception by default, see 3.3.8 Buffer size during transfer and reception.

<biz-connect id="bizconnect">
    <service>
      ...
      <communication-engine>
        <server-buffer-size>
          <send>transfer-buffer-size#</send>
          <receive>reception-buffer-size#</receive>
        </server-buffer-size>
      </communication-engine>
      ...
    </service>
    ...
</biz-connect>

#: For the buffer size during transfer and reception for JP1/DH - Server, you can specify a value in the range below. A value is set in KB. If you omit the value, operation is performed in the default value, 8,192 KB (8MB).

• Minimum value: 64

• Maximum value: 65,536

Example: When you specify 65,536 (64 MB) for the buffer size during transfer and reception:

<biz-connect id="bizconnect">
    <service>
      ...
      <communication-engine>
        <server-buffer-size>
          <send>65536</send>
          <receive>65536</receive>
        </server-buffer-size>
      </communication-engine>
      ...
    </service>
    ...
</biz-connect>

■ Specifying the packet queue size of clients

Specify the packet queue size of clients as needed. For details about the packet queue size of clients by default, see 3.3.9 Packet queue size of clients.

<biz-connect id="bizconnect">
    <service>
      <communication-engine>
        <packet-queue-capacity>packet-queue-size-of-clients#</packet-queue-capacity>
      </communication-engine>
      ...
    </service>
    ...
</biz-connect>

#: For the packet queue size of clients, you can specify a value in the range below. A value is set in KB. If you omit the value or specify a value outside the range, the system assumes that the default value is specified.

• Minimum value: 16,384

• Maximum value: 131,072

Example: When you specify 131,072 (128 MB) for the packet queue size of clients:

<biz-connect id="bizconnect">
    <service>
      ...
      <communication-engine>
        <packet-queue-capacity>131072</packet-queue-capacity>
      </communication-engine>
      ...
    </service>
    ...
</biz-connect>

■ Specifying the maximum size of files available for transfer

Specify the maximum size of a single delivery attempt and the maximum file size per file as needed. For details about the maximum size of files available for transfer by default, see 3.3.10 Maximum size of files available for transfer.

The specified values are displayed in the delivery policy window. When the administrator creates or edits a delivery policy, the values specified here are applied. For this reason, even if you change the maximum size of files available for transfer, the maximum values before the change are effective for a file transfer that uses the delivery policy created by using the maximum values before the change.

<biz-connect id="bizconnect">
    <service>
      ...
      <data-capacity>
        <per-file>maximum-size-per-delivery#</per-file>
        <per-delivery>maximum-size-per-file#</per-delivery>
      </data-capacity>
      ...
    </service>
    ...
</biz-connect>

#: For the maximum size per delivery and the maximum size per file, you can specify a value in the range below. A value is set in GB. Note that if you omit the values, the JP1/DH Web application server fails to start. If you specify a value less than 1, the system assumes that 1 is specified. If you specify a value more than 1,024, the system assumes that 1,024 is specified.

• Minimum value: 1

• Maximum value: 1,024

Example: When you specify 1,024 GB for the maximum size of files available for transfer:

<biz-connect id="bizconnect">
    <service>
      ...
      <data-capacity>
        <per-file>1024</per-file>
        <per-delivery>1024</per-delivery>
      </data-capacity>
      ...
    </service>
    ...
</biz-connect>

■ Specifying the SALT string for password obfuscation

Specify as needed the SALT string for obfuscating a user password (a user password used for connecting to JP1/DH - Server). For details about how to specify the SALT string, see 3.3.11 Password obfuscation (SALT string).

<biz-connect id="bizconnect">
  ...
  <security>
    <password-salt>SALT-string#</password-salt>
  </security>
  ...
</biz-connect>

#: Specify the SALT string to be added to a JP1/DH - Server user password. If you specify an empty character or omit a value, a SALT is not added. The characters that you can use for a SALT string are the same as those used for a password. You can use no more than 20 characters for a SALT string.

Example: When you specify HITACHI1234 for the SALT string:

<biz-connect id="bizconnect">
  ...
  <security>
    <password-salt>HITACHI1234</password-salt>
  </security>
  ...
</biz-connect>

Important

• Do not change the SALT string immediately after starting operation. If you change the SALT string after starting operation, you must register the registered user passwords again. Before starting operation, sufficiently consider the SALT string and then specify it.

• When you specify the SALT string, you must reset the password for the system administrator. See 5.5.2 Changing the password for the system administrator, and then reset the password for the system administrator.

■ Specifying the maximum storage period of files

Specify the maximum file storage period as needed. For details about the maximum storage period of files, see 3.3.12 Maximum storage period of files.

<biz-connect id="bizconnect">
  ...
  <persistence>
    <storage>
      <max-storage-period>number-of-days-for-the-maximum-file-storage-period</max-storage-period>
    </storage>
  </persistence>
  ...
</biz-connect>

#: For the number of days for the maximum file storage period, specify a value in the range from 1 to 3,650 (10 years).

Important

• In JP1/DH - Server 11-00 or earlier, the system treats the value specified here as the maximum value allowed for Storage period in the New Delivery Policy window and the Edit Delivery Policy window.

• In JP1/DH - Server 11-10 or later, the system treats the value specified here as the maximum value allowed for Maximum storage period of files in the New Group window and the Edit Group window.

Example: When you specify 100 days for the maximum file storage period:

<biz-connect id="bizconnect">
  ...
  <persistence>
    <storage>
      <max-storage-period>100</max-storage-period>
    </storage>
  </persistence>
  ...
</biz-connect>

■ Specifying the maximum number of destinations

In the web window, specify the maximum number of destinations that can be specified by the user for sending as needed. For details about the maximum number of destinations for sending, see 3.3.13 Maximum number of destinations.

<digivery id="dh">
    ...
    <mail-notification>
        ...
<send-screen-maximum-destinations>maximum-number-of-destinations-for-sending#</send-screen-maximum-destinations>
        ...
    </mail-notification>
    ...
</digivery>

#: For the maximum number of destinations for sending, specify a value in the range from 1 to 500.

Example: When you specify 500 for the maximum number of destinations that can be specified for sending:

<digivery id="dh">
    ...
    <mail-notification>
        ...
<send-screen-maximum-destinations>500</send-screen-maximum-destinations>
        ...
    </mail-notification>
    ...
</digivery>

■ Specifying whether to enable the initial environment setup function

If necessary, specify whether to automatically create a default address book, a default delivery policy, and default delivery rules when creating a domain. For details about the default setting of the initial environment setup function, see 3.3.14 Enabling or disabling the initial environment setup function.

<digivery id="dh">
    ...
    <biz-connect id="bizconnect">
      ...
      <use-domain-initialization>whether-to-enable-the-initial-environment-setup-function</use-domain-initialization>
    </biz-connect>
    ...
</digivery>

Example: When you use the initial environment setup function:

<digivery id="dh">
    ...
    <biz-connect id="bizconnect">
      ...
      <use-domain-initialization>TRUE</use-domain-initialization>
    </biz-connect>
    ...
</digivery>

■ Specifying the default delivery status type for the in-box

Specify the default delivery status type for the display of the user's in-box as needed. For details about the default delivery status type for the in-box, see 3.3.15 Default setting for the processing status type of deliveries to be displayed in the in-box.

<digivery id="dh">
    ...
    <user-interface>
        ...
        <mail-box>
          <receiving-box-default-status>default-display-type-for-the-in-box#</receiving-box-default-status>
        </mail-box>
        ...
    </user-interface>
    ...
</digivery>

#: You can specify one of the types below for the default display type. The default display type is not case-sensitive.

• NOTOPENED

• OPENED

• ALL

Example: When you specify OPENED for the default display type for the in-box:

<digivery id="dh">
    ...
    <user-interface>
        ...
        <mail-box>
          <receiving-box-default-status>OPENED</receiving-box-default-status>
        </mail-box>
        ...
    </user-interface>
    ...
</digivery>

■ Specifying whether to display the Compress Method options

If necessary, specify whether to display the Compress Method options in the window for creating or editing delivery policy. For details about whether to display the Compress Method options by default, see 3.3.16 Displaying the Compress Method options.

Standard and Extended are displayed as options. By using a delivery policy based on the Extended compression method, you can compress and send a file or folder exceeding 4 GB. Note that even if the system parameter settings are changed during operation, the already-set delivery policy data is not changed. The system parameter values are applied when the representative user edits the above delivery policy.

<digivery id="dh">
  ...
  <user-interface>
    <delivery-policy>
      <display-compression-method>Compress-Method-options-display</display-compression-method>
    </delivery-policy>
    ...
  </user-interface>
  ...
</digivery>

Example: When you display the Compress Method options:

<digivery id="dh">
  ...
  <user-interface>
    <delivery-policy>
      <display-compression-method>TRUE</display-compression-method>
    </delivery-policy>
    ...
  </user-interface>
  ...
</digivery>

■ Specifying the method for storage on the server for the Extended compression method

If necessary, specify whether to store the sending target data in an external folder on the server when sending a folder by using a delivery policy based on the Extended compression method or when sending a file or folder by selecting STRONG, MIDDLE, or WEAK for Compress Level. For details about the default method for storage on the server for the Extended compression method, see 3.3.17 External storage options for the data sent by using the extended compression method.

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
    ...
    <persistence>
      ...
      <gcp-external-file-saving-condition>
        <count-threshold>maximum-number-of-files-to-be-externally-stored-from-among-files-or-files-in-a-folder-in-a-single-delivery#1
        </count-threshold>
        <size-threshold>maximum-total-file-size-of-files-to-be-externally-stored-from-among-files-or-files-in-a-folder-in-a-single-delivery#2
        </size-threshold><!--KB-->
      </gcp-external-file-saving-condition>
    </persistence>
    ...
  </biz-connect>
  ...
</digivery>

#1: For the maximum number of files to be externally stored from among files or files in a folder in a single delivery, you can specify one of the following values:

• -1: All files are externally stored without limit.

• 0: No files are externally stored.

• 1 to 262144: As many files as specified are externally stored.

#2: For the maximum total file size of files to be externally stored from among files or files in a folder in a single delivery, you can specify one of the values below. A value is set in KB.

• -1: All files are externally stored without limit.

• 0: No files are externally stored.

• 1 to 1048576: Files that are smaller than the specified file size are to be externally stored.

Example: When you store files in an external folder:

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
    ...
    <persistence>
      ...
      <gcp-external-file-saving-condition>
        <count-threshold>262144</count-threshold>
        <size-threshold>1048576</size-threshold><!--KB-->
      </gcp-external-file-saving-condition>
    </persistence>
    ...
  </biz-connect>
  ...
</digivery>

■ Specifying whether to display the number of TCP connections

If necessary, specify whether to display the following items in a delivery policy other than the standard delivery policy: Max. TCP sessions per Connection and Always connect with Max. TCP sessions. For details about the default display of the number of TCP connections, see 3.3.18 Displaying the options related to number of TCP connections.

If you specify to display the items, you can specify the number of TCP connections for each policy.

<digivery id="dh">
  ...
  <user-interface>
    <delivery-policy>
      ...
      <display-max-tcp-connections>displaying-Max.-TCP-sessions-per-Connection</display-max-tcp-connections>
      <display-always-connect-max-tcp-connections> Always-connect-with-Max.-TCP-sessions</display-always-connect-max-tcp-connections>
    </delivery-policy>
    ...
  </user-interface>
  ...
</digivery>

Example: When you display the items for the number of the TCP connections:

<digivery id="dh">
  ...
  <user-interface>
    <delivery-policy>
      ...
      <display-max-tcp-connections>TRUE</display-max-tcp-connections>
      <display-always-connect-max-tcp-connections>TRUE</display-always-connect-max-tcp-connections>
    </delivery-policy>
    ...
  </user-interface>
  ...
</digivery>

■ Specifying the timeout period when using a directory server

If the directory server is used for user authentication for login to JP1/DH - Server, specify the LDAP connection timeout period and the timeout period for user searches by the directory server in milliseconds. For details about the default timeout period, see 3.3.19 Timeout period when using a directory server.

If you specify a value equal to or less than 0, the timeout period specified in the network protocol such as TCP is used.

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
    ...
    <authentication-system>
      <ldap-connection-timeout>timeout-period-for-connecting-to-the-directory-server#</ldap-connection-timeout>
      <ldap-search-timeout>timeout-period-for-searching-a-user#</ldap-search-timeout>
      </authentication-system>
      ...
  </biz-connect>
  ...
</digivery>

#: For values you can specify, note the following points:

• A specified value is recognized as a value in milliseconds.

• Specify a value in the range from 0 to 30,000.

Example:

When you specify 10 seconds for the timeout period:

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
    ...
    <authentication-system>
      <ldap-connection-timeout>10000</ldap-connection-timeout>
      <ldap-search-timeout>10000</ldap-search-timeout>
      </authentication-system>
      ...
  </biz-connect>
  ...
</digivery>

■ Specifying whether to enable the approval exclusion function

When you use JP1/Data Highway - AJE or the data transfer command, specify whether to exclude the approval processing in the specified approval route at the time of sending.

For details about the default setting of the approval processing when using JP1/Data Highway - AJE or tthe data transfer command, see 3.3.20 Approval exclusion function. If you enable the approval exclusion function, approval request emails are not sent to the approver. This makes the approval processing (accept or reject) unnecessary. In addition, a recipient can receive a file or folder without waiting for the approval processing by the approver.

<digivery id="dh">

  ...
  <biz-connect id="bizconnect">
      ...
      <use-command-approval-exclusion>approval-exclusion-function</use-command-approval-exclusion>
      ...
  </biz-connect>
  ...
</digivery>

Example:

When you exclude the approval processing:

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
      ...
      <use-command-approval-exclusion>TRUE</use-command-approval-exclusion>
      ...
  </biz-connect>
  ...
</digivery>

■ Specifying whether to enable the file validation disabling function

When you use JP1/Data Highway - AJE or the data transfer command, specify whether to disable file validation at the time of sending and receiving. For details about the default setting of the file validation disabling function when using JP1/Data Highway - AJE or the data transfer command, see 3.3.21 Using the file validation disabling function.

If you enable this function, file validation is not carried out when a file sent from JP1/Data Highway - AJE or the data transfer command is received in the web window. In addition, even if the specified value is changed while a file is being sent or received, the value specified at the time of sending or receiving is effective. However, if sending or receiving is suspended by the suspend command in 8.4.1 Suspension and cancellation of the active file transfer, the specified value after the change is applied when the suspended sending or receiving is resumed because the specified values are checked again when resuming the transfer.

Important

This function is enabled only when JP1/Data Highway - AJE 10-10 or later is used.

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
      ...
      <use-command-digest-validation-exclusion>file-validation-disabling-function</use-command-digest-validation-exclusion>
      ...
  </biz-connect>
  ...
</digivery>

Example:

When you enable the file validation disabling function:

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
      ...
      <use-command-digest-validation-exclusion>TRUE</use-command-digest-validation-exclusion>
      ...
  </biz-connect>
  ...
</digivery>

■ Specifying the maximum number of destinations

Specify the maximum number of destinations that can be specified when a file or folder is sent by using JP1/Data Highway - AJE or the data transfer command. For details about the maximum number of destinations by default when a file or folder is sent by using JP1/Data Highway - AJE or the data transfer command, see 3.3.22 Maximum number of destinations.

If you enable this function, for the maximum number of destinations when a file is sent by using JP1/Data Highway - AJE or the data transfer command, the value specified here is given priority over the value defined in the delivery policy. However, if you omit the value or specify a value equal to or less than 0, the maximum number of destinations defined in the delivery policy is applied.

<digivery id="dh">
  ...
  <user-interface>
    <delivery-policy>
      <force-command-maximum-destinations>maximum-number-of-destinations#</force-command-maximum-destinations>
    ...
    </delivery-policy>
  </user-interface>
  ...
</digivery>

#: For values you can specify, note the following points:

• 0: Follows the definition of a delivery policy.

• 1 to 500: Allows a user to specify as many destinations as specified.

Example:

When you specify 500 for the maximum number of destinations:

<digivery id="dh">
  ...
  <user-interface>
    <delivery-policy>
      <force-command-maximum-destinations>500</force-command-maximum-destinations>
      ...
    </delivery-policy>
  </user-interface>
  ...
</digivery>

■ Specifying whether to enable the file validation disabling function when using the web user-interface

When you use the web user-interface, specify whether to disable file validation at the time of sending and receiving. For details about the default setting of the file validation disabling function when using the web user-interface, see 3.3.23 Using the file validation disabling function when using the web user-interface.

Even if you enable this function, when you receive files sent from JP1/Data Highway - AJE or the data transfer command, the setting for the file validation disabling function when using JP1/Data Highway - AJE or the data transfer command is applied. If the setting value is changed while a file is being sent or received, the value specified when sending or receiving the file becomes effective.

Important

This function is enabled only when JP1/Data Highway - Server 11-00 or later is used.

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
      ...
      <use-web-digest-validation-exclusion>file-validation-disabling-function-when-using-the-web-user-interface</use-web-digest-validation-exclusion>
      ...
  </biz-connect>
  ...
</digivery>

Example:

When you enable the file validation disabling function in the web user-interface:

<digivery id="dh">
  ...
  <biz-connect id="bizconnect">
      ...
      <use-web-digest-validation-exclusion>TRUE</use-web-digest-validation-exclusion>
      ...
  </biz-connect>
  ...
</digivery>

■ Specifying the initial state of selection for choosing an approver

Specify an initial state of selection when senders choose their approver on the web window. You can specify TRUE (in which the check box is selected) or FALSE (in which the check box is not selected). When you specify a value, it is applied to the following:

• Whether The sender must select the approver (except for the commands) check box in the New Delivery Rule window is selected by default

• What is selected by default in the Select Approver window that is displayed when a sender chooses the approver in the New Delivery window

For details about how to specify the default settings for the initial state of selection when an approver is chosen, see 3.3.24 Initial state of selection for choosing an approver.

<digivery id="dh">
  :
  <biz-connect id="bizconnect">
      :
    <persistence>
        :
      <select-approvers-state-default-on>initial-state-of-selection-for-choosing-an-approver
      </select-approvers-state-default-on>
        :
    </persistence>
      :
  </biz-connect>
  :
</digivery>

Example:

When you specify that the check box is selected by default:

<digivery id="dh">
  :
  <biz-connect id="bizconnect">
      :
    <persistence>
        :
      <select-approvers-state-default-on>TRUE</select-approvers-state-default-on>
        :
    </persistence>
      :
  </biz-connect>
  :
</digivery>

■ Specifying the function to automatically delete files before the storage expiration date based on the evaluation of download completion by all recipients

This function automatically deletes files before the storage expiration date is reached if all the users specified as the recipients download all the files. With the function, the system finds out that all the users specified as the recipients already downloaded all the files and then deletes the files automatically before the storage expiration date is reached. This function can be enabled for each of the address types (TO, CC, and BCC).

The value you can specify is either TRUE (in which the system evaluates if downloads are completed) or FALSE (in which the system does not evaluate if downloads are completed).

For details about how to specify the default settings for the function to automatically delete files before the storage expiration date based on the evaluation of download completion by all recipients, see 3.3.25 Function to automatically delete files before the storage expiration date based on the evaluation of download completion by all recipients.

<digivery id="dh">
  :
  <biz-connect id="bizconnect">
    <persistence>
       <downloaded-data-auto-delete>
         <target-recipient-type>
          <to>evaluation-of-download-by-users-in-the-to-field</to>
          <cc>evaluation-of-download-by-users-in-the-cc-field</cc>
          <bcc>evaluation-of-download-by-users-in-the-bcc-field</bcc>
         </target-recipient-type>
       </downloaded-data-auto-delete>
    </persistence>
      :
  </biz-connect>
  :
</digivery>

Important

• If you specify FALSE (in which the system does not evaluate if downloads are completed) for all of the to, cc, and bcc tags, this function is not available.

• If all the three tags above are omitted, the system evaluates the completion of download by users specified only in the TO field to automatically delete files before the storage expiration date is reached.

Example:

When the system evaluates the completion of downloads by users specified in the TO field to automatically delete files before the storage expiration date is reached:

<digivery id="dh">
  :
  <biz-connect id="bizconnect">
    <persistence>
       <downloaded-data-auto-delete>
         <target-recipient-type>
          <to>TRUE</to>
          <cc>FALSE</cc>
          <bcc>FALSE</bcc>
         </target-recipient-type>
       </downloaded-data-auto-delete>
    </persistence>
      :
  </biz-connect>
  :
</digivery>

■ Specifying the window interface for the New Delivery window

Specify the window interface for the New Delivery window that is used for file transfer on the web window. The following interfaces can be used:

• Java applet interface

• JWS interface

• Application interface

For details about how to specify the default window interface for the New Delivery window, see 3.3.26 Window interface for the New Delivery window.

<digivery id="dh">
        :
  <user-interface>
        :
    <transfer-interface>
      <transfer-application-mode-applet>whether-to-use-the-java applet -interface
      </transfer-application-mode-applet>
      <transfer-application-mode-jws>whether-to-use-the-JWS-interface
      </transfer-application-mode-jws>
      <transfer-application-mode-client-app>whether-to-use-the-Application-interface
      <transfer-application-mode-client-app>
    </transfer-interface>
        :
  </user-interface>
        :
</digivery>

The window interface to be used for the New Delivery window is determined by the settings where you specify whether you will use each interface.

The following table shows the relation between the settings and the New Delivery window:

Important

• If a value other than TRUE or FALSE is set, it is deemed that FALSE is specified.

• If tags are omitted, it is deemed that TRUE is specified.

Tip

The initial values for new installations and overwrite installations are TRUE for each setting.

Example:

When you enable the Java applet interface only:

<digivery id="dh">
        :
  <user-interface>
        :
    <transfer-interface>
        <transfer-application-mode-applet>TRUE</transfer-application-mode-applet>
        <transfer-application-mode-jws>FALSE</transfer-application-mode-jws>
    </transfer-interface>
        <transfer-application-mode-client-app>FALSE</transfer-application-mode-client-app>
        :
  </user-interface>
        :
</digivery>

■ Setting up SAML SSO authentication

With this feature, SSO authentication can be performed per domain using JP1/DH - Server as the service provider. You set up SAML Single Sign-On (SSO) authentication.

For details about the default setting of SAML SSO authentication, see 3.3.27 SAML SSO authentication.

<digivery id="dh">
  ：
  <biz-connect id="bizconnect">
     ：
     <authentication-system>
          ：
     </authentication-system>
     <use-saml-domain>SAML-SSO-authentication</use-saml-domain>
     ：
  </biz-connect>
  ：
</digivery>

If you specify TRUE, the settings for SSO authentication are displayed in the windows for creating or editing users. If you change TRUE to FALSE, SSO authentication specified for the domain is disabled and access through SSO is no longer available. Also, the NameID(SAML) item you specified when creating the user is disabled.

Example:

When you use SAML SSO authentication:

<digivery id="dh">
  ：
  <biz-connect id="bizconnect">
     ：
     <authentication-system>
          ：
     </authentication-system>
     <use-saml-domain>TRUE</use-saml-domain>
     ：
  </biz-connect>
  ：
</digivery>