Modifying Instance Configuration Parameters
Overview
This section describes how to configure common parameters of components in an instance. By modifying configuration parameters, you can adjust related function configurations of components.
Modifying Configuration Parameters
On the Instance Information page of the ROMA Connect console, click the Configuration Parameters tab and view the configuration parameters of the instance. You can also change the values of Current Value.
|
Parameter |
Description |
|---|---|
|
Parameter Name |
Name of a parameter. You can move the cursor to |
|
Default Value |
Default value of a parameter. |
|
Value Range |
Value range of a parameter. |
|
Current Value |
Current value of a parameter. |
|
Updated |
Time when a parameter was last updated. If the parameter has never been modified, this parameter is left blank. |
|
Operation |
Click Edit to change the value of Current Value. |
Parameter Description
The following table lists the instance configuration parameters of ROMA Connect.
|
Parameter |
Description |
|---|---|
|
ratelimit_api_limits |
Default request throttling value applied to all APIs. If no request throttling policy is bound to an API, the total number of times the API can be called is determined by this parameter value. If a request throttling policy has been bound to an API, the total number of times the API can be called is determined by the bound policy. |
|
request_body_size |
Maximum size of the body allowed in an API request. |
|
backend_timeout |
Maximum timeout duration for ROMA Connect to send a request to a backend service. |
|
app_token |
Whether to enable app_token authentication. After this function is enabled, the obtained access token can be used in API requests for authentication during API calling.
|
|
app_basic |
Whether to enable app_basic authentication. After this function is enabled, you can add the Authorization parameter to an API request to carry the key and secret of an integration application (or the AppKey and AppSecret of a client) for authentication during API calling. |
|
app_secret |
Whether to enable app_secret authentication. After this function is enabled, you can add the X-HW-ID and X-HW-AppKey parameters to an API request to carry the key and secret of an integration application (or the AppKey and AppSecret of a client) for authentication during API calling. |
|
app_route |
Whether to support IP address access. After this function is enabled, APIs in non-DEFAULT groups can be called by using IP addresses. |
|
cascade |
Whether to enable the API cascading function. After this function is enabled, APIs can be called across instances.
|
|
default_group_hide |
Whether to hide the DEFAULT group. After this function is enabled, the DEFAULT group is hidden. |
|
livedata_config |
Custom backend configuration.
|
|
backend_client_certificate |
Whether to enable two-way authentication for a backend. After this function is enabled, you can configure the two-way authentication for a backend when configuring the backend information during API creation. |
|
ssl_ciphers |
HTTPS cipher suite that can be configured. You can select the cipher suites as required. |
|
apiclient_first_use_x_hw_id |
Whether to preferentially use the X-HW-ID field to verify the ApiClient class of the custom backend. |
|
real_ip_from_xff |
Whether to use the IP addresses in the X-Forwarded-For header as the criterion for access control and request throttling. xff_index: Sequence number of an IP address in the X-Forwarded-For header. The value can be positive, negative, or 0.
For example, assume that the X-Forwarded-For header of a request received by API Gateway contains three IP addresses: IP1, IP2, and IP3. If the value of xff_index is 0, IP1 is obtained. If the value of xff_index is 1, IP2 is obtained. If the value of xff_index is –1, IP3 is obtained. If the value of xff_index is –2, IP2 is obtained. |
|
opentracing_options |
Whether to enable the opentracing function. After the opentracing function is enabled, you can use the tracing tool of a specified type to view the entire link of an API request and the time consumed at each phase, and then optimize the link based on data analysis.
NOTE:
If Tracer is set to jaeger, you need to deploy the jaeger-collector service and set Tracer Endpoint to the IP address of the jaeger-collector service. The default port number is 14250. |
|
custom_log |
Indicates whether to enable the custom log function. After the custom log function is enabled, the specified location (header, query, and cookie) and parameter values are printed in the calling logs of all APIs in the ROMA Connect instance. After this function is enabled, click Add to add the parameters to be printed in the calling logs. |
|
real_ip_header_getter |
Whether to obtain the source IP address from the user-defined header. |
Last Article: Viewing Details of an Instance
Next Article: Creating a Data Dictionary

Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.