8.4.4 Dynamic management of the server settings

You can refer to or change the settings for the server without restarting JP1/DH - Server.

You can change the maximum number of TCP connections in the delivery rule settings (standard delivery policy) and the values for the following server parameters in the JP1/DH - Server configuration file (digikatsuwide.xml).

Network bandwidth limit
Maximum number of client connections (number of concurrent connections)

For details about the standard delivery policy, see the JP1/Data Highway - Server System Administrator Guide.

Organization of this subsection

(1) Format
(2) Arguments
(3) Description
(4) Execution example

(1) Format

DWAdminClient.bat {GETCONFIG|SETCONFIG}
   -property property-file
   -config {server-parameter-file|-result storage-destination-server-parameter-file}

To Page Top

(2) Arguments

Table 8‒14: Arguments of the command for dynamic management of the server settings
No.	Option	Description
1	`-config`	When changing server parameters dynamically (`SETCONFIG`), specifies the server parameter file where the values after change are written. Specify this option when selecting `SETCONFIG`. You cannot specify it when selecting `GETCONFIG`.
2	`-result`	When obtaining the current server parameter file (`GETCONFIG`), specifies the path to the server parameter file at the storage destination. Specify this option when selecting `GETCONFIG`. You cannot specify it when selecting `SETCONFIG`.
3	`-property`	For details, see 8.3.2 Common options.

To Page Top

(3) Description

(a) Format of the server parameter file

The format of the server parameter file is as follows:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<digivery-config>
  <digivery>
    <biz-connect id="bizconnect" >
      <service>
        <throughput-limit>
          <upload>maximum-transmission-bandwidth-for-uploading</upload>
          <download>maximum-transmission-bandwidth-for-downloading</download>
        </throughput-limit>
        <service-task>
          <initial>maximum-number-of-client-connections-(initial-value)</initial>
          <maximum>maximum-number-of-client-connections-(maximum-value)</maximum>
        </service-task>
        <http-connection>
          <maximum>maximum-TCP-connections</maximum>
        </http-connection>
        </service>
    </biz-connect>
  </digivery>
</digivery-config>

The following table describes the elements.

Table 8‒15: Elements in the server parameter file
Element/attribute		Number of elements	Description
`digivery-config` element		1	Fixed.
`digivery` element		1	Fixed.
`biz-connect` element		1	Fixed.
	`id` attribute	1	Fixed. Specifies `bizconnect`.
`service`		1	Fixed.
`throughput-limit`		1	Fixed.
`upload`		1	Specifies the maximum transmission bandwidth for uploading in Mbps. You can specify a value in the range from 0 to 1,000. You cannot omit this value. When you specify `0`, no limit is applied to the bandwidth.
`download`		1	Specifies the maximum transmission bandwidth for downloading in Mbps. You can specify a value in the range from 0 to 1,000. You cannot omit this value. When you specify `0`, no limit is applied to the bandwidth.
`service-task`		1	Fixed.
`initial`		1	Specifies the initial value for the number of concurrent connections between JP1/DH - Server and clients. You can specify a value in the range from 1 to 64. You cannot omit this value.
`maximum`		1	Specifies the maximum value for the number of concurrent connections between JP1/DH - Server and clients. You can specify a value in the range from 1 to 64. You cannot omit this value.
`http-connection`		1	Fixed.
`maximum`		1	Specifies the maximum number of TCP connections during multiplex communication per connection between JP1/DH - Server and a client. You can specify a value in the range from 1 to 64. You cannot omit this value.

(b) Settings

The changes made here are enabled from the first connection to be established after the settings have been changed. The communication at the point of command execution is not affected by these changes.
The changes made by this command are enabled only for the settings of active JP1/DH - Server. When JP1/DH - Server is restarted, the changes made to the settings become disabled.

To Page Top

(4) Execution example

DWAdminClient.bat GETCONFIG
   -result C:\temp\result.xml
   -property "C:\DWCLient\property.xml"

To Page Top