By default, the globally configured Redis (session store) instance of the Gateway is used, but this can be changed as follows:

0. Define the new Redis instance in the global Expert Settings.
1.  

   Example

   Redis.Service.0.Name                                 "Local" 
   Redis.Service.Local.Mode                             "SOCKET" 
   Redis.Service.Local.SocketFile                       "/var/run/redis-ml/redis-ml.sock" 
     
   Redis.Service.1.Name                                 "RedisWithSsl" 
   Redis.Service.RedisWithSsl.Mode                      "SERVER" 
   Redis.Service.RedisWithSsl.Server.0.Host             "80.264.93.142" 
   Redis.Service.RedisWithSsl.Server.0.Port             "6379" 
   Redis.Service.RedisWithSsl.Server.0.SSLEnable        "TRUE" 
   Redis.Service.RedisWithSsl.Server.0.SSLServerCA      "/opt/airlock/custom-settings/gatekeeper/redis_server_ca.pem" 
   Redis.Service.RedisWithSsl.Server.0.SSLClientCert    "/opt/airlock/custom-settings/gatekeeper/redis_client_cert.pem" 
   Redis.Service.RedisWithSsl.Server.0.SSLClientCertKey "/opt/airlock/custom-settings/gatekeeper/redis_client_cert_key.pem" 
   
2. Reference which Redis service is used as HotDB for the Anomaly Shield AnomalyShield.Redis.Service.
3.  

   Example

   AnomalyShield.Redis.Service          "RedisWithSsl"
4. Add the Redis server address and port information to the configuration file of the ML-Service.
5.  

   Example

   Path: /opt/airlock/ml-service/conf/ml.ini

   hot_db = server:80.264.93.142:6379