Jump to: navigation, search

server Section



Default Value:
Valid Values:
Changes Take Effect: Immediately

Comma-separated list of ORS URLs.


This list will be used for all services sections and can be overridden in each service.


Default Value: circular
Valid Values: circular, linear
Changes Take Effect: Immediately

Strategy for the ORS load balancer in the server section and service sections; this value can be overridden in each service. Supported values are: circular or linear.


Default Value:
Valid Values: Any integer
Changes Take Effect: Immediately

This value is a range of access_code; the value must be unique for each GMS node across the cluster. GMS will randomly choose within this range the access_code_prefix that it will associate as the prefix for access_code. If the option is not present, GMS will use the nodeId value instead. An example range is 455,456-458 where the prefix can be 455, 456, 457, or 458.


Default Value:
Valid Values: Any valid URL
Changes Take Effect: Immediately

Web application "context" path.


Default Value:
Valid Values:
Changes Take Effect: Immediately

The string used to format dates. The string syntax should match the expectations of the java class java.text.SimpleDateFormat. See Simple Date Format for details.


Default Value:
Valid Values: Valid host name.
Changes Take Effect: Immediately

Specifies the external url used by the Storage Service to allow the retrieval of a binary attachment. This is useful in the case of a Load Balancer deployment. The valid value is http://<web_host>:<web_port>/, where web_host is used by the cluster service to identify a node; and where web_port is used by the cluster service to identify a node. The web_port value must be the same as the GMS port described in the jetty configuration file, otherwise an alarm will be displayed in Solution Control Interface (SCI) and GMS will stop.


Default Value: default
Valid Values:
Changes Take Effect: Immediately

Configures the host and port to use in the redirection message that is sent by GSG Admin upon logout process. In a load balancing deployment, you should set up this option to make sure that GMS redirects to the Load Balancer address instead of the local GMS.
The possible values for this option are the following:

  • default—Redirects to the local GMS instance (default behavior).
  • external_url_base—Uses the value of external_url_base for the redirection.
  • <host>:<port>—Specifies another URL to use for the redirection.

Limitation: Internet Explorer may not correctly depict the port redirection set in external_url_base.


Default Value: 5000000
Valid Values: Long (bytes)
Changes Take Effect: Immediately

Allowed maximum size before uploads are refused.

  • -1 indicates no limit


Default Value: 9999
Valid Values: Any integer
Changes Take Effect: Immediately

Maximum number of concurrent sessions for the Service Management UI.


Default Value: 1
Valid Values:
Changes Take Effect:

Specifies a two digit number that should be unique in the GMS deployment. It is used in the generation of DTMF access tokens.


Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

If true, URLs returned in GMS responses are relative; otherwise, these URLs are absolute.


Default Value: Result of InetAddress.getLocalHost()
Valid Values: Valid host name
Changes Take Effect: Immediately

The default InetAddress.getLocalHost() value will be used in the most cases. Change this configuration value if you have issues obtaining the local name when your environment has multiple network interfaces. In this scenario, to ensure GMS internode communication, set this option's value to the IP Address used by the Jetty interface (which is not configurable).

This option is required for internode communication.


Default Value: 80
Valid Values: Valid TCP port; for HTTPS internode communication, 8443 or check either your jetty configuration or restriction port
Changes Take Effect: Immediately

Sets a port different from the port that GMS uses. Note: GMS uses port 8080, which can be changed in the jetty-http.xml file. This option can be used in the case of proxy role of the customer to forward requests.

At startup, GMS checks that a GMS is available on the port specified by web_port. If a GMS is not available, the web_port option alarm (EventId 2002) is thrown.

Required to ensure the GMS internode communication.


Default Value: http
Valid Values:
Changes Take Effect: Immediately

Scheme of the internal URL to https if GMS jetty is configured to support only SSL/TLS for one node or for a cluster of nodes.

Optional, required for GMS internode communication.


Comment on this article:

blog comments powered by Disqus
This page was last modified on 8 March 2017, at 07:48.