Updating Cache through POST or PUT APIs

This section helps you to update cache through POST or PUT APIs.

Generic configuration microservice provides a support to store and update configuration data in the cache service. Whenever configuration data is created or updated in the generic configuration microservice, it is updated in the cache service, if it is configured. If the cache configuration data is not available for an application, the application configuration data is not updated in the cache service.

To enable this feature, perform the following steps.

1. Ensure that the cache service is up and running.
2. Add the configuration (refer the table below) in generic configuration API service environment.
3. Create the cache configuration data for an application using the cache configuration APIs (refer Management APIs section).
4. Create or update the application configuration using POST or PUT APIs.

   The configuration data is stored in the database and the cache service. You can check the data stored in KEY VALUE format (GroupId.ConfigName), in Redis cache service.

The following configuration should be added in the generic configuration API service environment.

Property	Default Value	Description
temn.cache.host	127.0.0.1	Cache service host name
temn.cache.port	6379	Cache service port name
temn.msf.cacheupdation.skip	true	Allowed values are: True – Skips updating the cache. Configuration data is not stored in cache. False – Updates the cache. It connects the cache service and stores the configuration data in cache, if the cache configuration is available.

The following properties should be included for Azure environment.

Property	Default value	Description
temn.cache.password	null	Access key of the cache service.
temn.cache.ssl	true	Allowed values are: True if SSL is enabled. False if SSL is disabled.