external_url_base
Section: server
Default Value:
Valid Values: http://<hostname>:<port>/ or https://<hostname>:<port>/
Changes Take Effect: Immediately
Specifies the external URL used by the Storage Service to allow the retrieval of a binary attachment. Configure this option in the case of a Load Balancer deployment.
- The valid value is http://<hostname>:<port>/, where:
- <hostname> is used by the cluster service to identify a node
- <port> is used by the cluster service to identify a node.
The <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.
_services_credentials
Section: callback
Default Value: ""
Valid Values:
Changes Take Effect: Immediately
The credentials to be used for the Callback strategy.
_fetch_retry_delay
Section: callback
Default Value: 10
Valid Values: Any positive integer
Changes Take Effect: Immediately
The retry interval before a retry is made for the Session/Fetch.
_fetch_retry_attempt
Section: callback
Default Value: 3
Valid Values: Any positive integer
Changes Take Effect: Immediately
Defines the retry attempts for a Session/Fetch action.
_fetch_timeout
Section: callback
Default Value: 15
Valid Values: Any positive integer
Changes Take Effect: Immediately
Timeout interval (in seconds) at which GMS should verify if the fetch operation is timed out.
_enable_gms_dfm
Section: callback
Default Value: true
Valid Values: true, false
Changes Take Effect:
Enables using DFM. Set to false to enable Fetch/Session.
Using Callbacks without DFM
To use the Callback strategy without using DFM, the GMS API can be used with the Session/Fetch requests (HTTP requests) using the URL configured in the external_url_base configuration option in the server section.
The GMS API will be called from the Callback strategy using the Session/Fetch requests (HTTP request), the URL used for these HTTP operations is the GMS application option external_url_base in server section. The following options are available to configure this feature.
[service.<callback service name>]
...
_enable_gms_dfm=false
...You can also create a GMS Services Credentials Transaction List when accessing the GMS API with credentials:
When GMS API are using credentials, create GMS Services Credentials Transaction List (called for example GMS_Credentials) with the following annex:
[server]
username=username
password<password>The server username is the same username as the username option in GMS Application options in server section and the server password is the same password as the password option in GMS Application options in server section.
Add an _services_credentials option in Callback service section:
[service.<callback service name>]
...
_enable_gms_dfm=false
...
_services_credentials=GMS_Credentials
...Limitations
When using the Callback strategy without using DFM, the following limitations apply:
- The Session/Fetch HTTP request uses the URL from GMS: external_url_base option value.
- There are no round-robin hosts as in the DFM definition.
- Credentials on GMS API are activated on server section only (not per service) via a Transaction List.