Versions Compared

Old Version 4

changes.mady.by.user Mihai Bob

Saved on

compared with

New Version 5

changes.mady.by.user Mihai Bob

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

The session manager(IAquimaSessionsMap) is responsible for storing IAquimaSession instances. Blueriq uses a specific session manager depending on the properties that are set. By default there are two types of session managers, named "memory" and "external".

Info

In order to run Blueriq in a clustered environment, the "external" session manager must be used.

Table of Contents

Configure Session Manager

The Session Manager can be configured by placing the below a property in application.properties file. The following values may be used for this property:

Memory

The default implementation, which stores IAquimaSessions on the HTTP session.

Code Block
blueriq.session.session-manager=externalmemory

This property selects which IAquimaSessionsMap If the property is missing, this implementation is used for session management. The following values may be used for this property:

Property ValueDescription

by default.

External

Code Block
blueriq.session.session-manager=external

An implementation which stores IAquimaSessions in a key-value store using the available IKeyValueStore implementation.

Note

 An IKeyValueStore implementation must be made available in the Spring application context

, either by enabling the keyvalue-redis-store profile or by providing another IKeyValueStore implementation

.

Note Before an external session manager is activated, a Key-Value store component must be enabled in Blueriq.

Documentation how this can be done can be found here.

memoryThe default implementation, which stores IAquimaSessions on the HTTP session. If the property is missing, this implementation is used by default.

Activate/pasivate pattern

...

Best practicies

 

 

 

External Session Store

The External Session Store

Custom code

Putting things on the scope / what customers should not do anymore now that we use redis

Activate / passivate pattern

Custom Session Manager