Runtime Configuration

The Runtime Configuration tab on the Settings screen of App Services enables you to view and edit the runtime configuration settings of the Fabric Server. The configuration details comprise of the following sections:

• General Configuration
• Log Configuration
• CORS Configuration
• SSL Configuration
• Storage Database Configuration
• GDPR Policy
• File Storage Configuration
• Web Apps Configuration
• Cache Configuration
• Global Throttling Configuration

General Configuration

The General Configuration section displays the general settings of the Fabric server. You can modify any setting and click Save to update the change.

The following table describes the settings in the General Configuration section:

Log Configuration

The Log Configuration section displays the configuration settings related to the server logs. You can modify any setting and click Save to update the changes.

The following table describes the settings in the Log Configuration section:

CORS Configuration

The CORS Configuration section displays the configuration settings related to Cross Origin Resource Sharing (CORS) access. You can modify any setting and click Save to update the changes.

The following table describes the settings in the CORS Configuration section:

SSL Configuration

The SSL Configuration section is used to connect the Fabric Server to the customer enterprise server using appropriate SSL certificates and settings. This type of configuration is required only when you want to connect the Fabric Server by using the HTTPS protocol. You can modify any setting and click Save to update the changes.

The following table describes the settings in the SSL Configuration section:

Storage Database Configuration

The Storage Database Configuration section displays the database properties of storage services of Fabric server. This is used only for on-premise installs. You can modify any setting and click Save to update the changes.

The following table describes the settings in the Storage Database Configuration section:

GDPR Policy

The GDPR Policy section provides settings that enable the protection of the Personally Identifiable Information (PII) of a user. When the settings are enabled, data such as the User ID and the IP Address is not stored in the integration server logs. Additionally, a flag variable is sent to the metrics pipeline along with the PII to protect the data.

The GDPR Policy section contains the following settings:

Encoding of PII in metrics

The metrics pipeline encodes the PII (UserID and IP Address) in the reports and metrics if the request originates from any of the following countries.

Austria Belgium Bulgaria Germany Denmark Estonia Spain Finland France

Greece Croatia Hungary Ireland Iceland Italy Liechtenstein Luxembourg Latvia

Malta Netherlands Norway Poland Portugal Romania Sweden Slovenia Slovakia

If the Protect PII property is enabled, the metrics pipeline encodes the PII (userID and IP Address) for all requests (irrespective of the country of origin).

File Storage Configuration

The File Storage Configuration section displays the configuration properties related to File Storage adapter. It is applicable only for on-premise install.

The following table describes the settings in the File Storage Configuration section:

Web Apps Configuration

The Web Apps configuration section displays the configuring properties of the new optimized web apps package format that improves the app performance and minimize the downtime during deployments. The section displays the properties such as Response Content Type Mappings, Cache Control age, HTTP session caching, and Custom Response Headers. You can modify any setting and click Save to update the changes.

The following table describes the settings in the Web Apps Configuration section:

[
  {'name': 'X-Content-Type-Options', 'value': 'nosniff'}
] 

Cache Configuration

Quantum Fabric supports EHCache, Memcached, and Redis cache vendors. An On-premise setup of Quantum Fabric uses EHCache as the default cache mechanism. A cloud environment uses Memcached as the default cache mechanism. The Cache Configuration section displays the configuration properties of the new cache mechanism. The section displays the properties such as Cache Type, Expiry time, Cache Server URLs, Advanced Cache properties, and Enable Session Distribution. You can modify any setting and click Save to update the change.

IMPORTANT: If Ehcache is chosen, the middleware automatically configures the cache to hold a maximum of 4000 entries. After reaching this limit, eviction will occur to make room for new entries.

To adjust this setting, you can specify a new value for "cacheSize" in the environment_properties section of the Advanced Properties.
For example: {"environment_properties": {“cacheSize" : “6000”},"jcache_configuration_properties":{},"additional_properties":{}}

The following table describes the settings in the Cache Configuration section:

NOTE: It is advised to avoid directly inserting Custom Objects into Session or ResultCache within Preprocessors, Postprocessors, and Java Services.

Instead, Custom Objects should be converted to a byte Array before insertion into Session or ResultCache. The Serialization and Deserialization of Custom Objects should be managed by implementation classes to guarantee proper data handling.

Global Throttling Configuration

Apart from configuring the service level throttling from the Quantum Fabric console, you can also configure the operation level throttling from the Global Throttling Configuration field. The throttling limit set for a service is applicable to all the operations within the service, whereas, the throttling information given here will be implied to the respective operation of the service that you mention here.

NOTE: If you have set the throttling limit at both service and operation level, then the service will not respond when either of the limit is met first.

The following table describes the settings in the Global Throttling Configuration section:

Following are the parameters required to define the throttling limit for the respective service type:

Integration and Orchestration Service:

[ 
   { 
      "resourcePath":"NameService/getFirstName",
      "httpMethod":"POST",
      "totalRateLimitPerMinute":100,
      "ipRateLimitPerMinute":10
   },
   { 
      "resourcePath":"NameService/getLastName",
      "httpMethod":"POST",
      "totalRateLimitPerMinute":110,
      "ipRateLimitPerMinute":11
   }
]

Object Service:

[ 
   { 
      "resourcePath":"ObjectServiceName/Object",
      "httpMethod":"GET",
      "totalRateLimitPerMinute":100,
      "ipRateLimitPerMinute":10
   },
   { 
      "resourcePath":"ObjectServiceName/Object",
      "httpMethod":"GET",
      "totalRateLimitPerMinute":100,
      "ipRateLimitPerMinute":10
   }
]

IMPORTANT: You can only configure the POST httpMethod for Integration service and Orchestration service types. For Object service, you can configure GET and DELETE httpMethod as is, whereas, the POST and PUT httpMethod should be configured as CREATE and UPDATE respectively.

NOTE: If you want to apply throttling on some custom verb, then you can configure the custom verb as the httpMethod.

NOTE: ** displayed beside the property implies the changes to the property groups required restart of the server to reflect modified values.