Redis for On-Premises
Redis Session Manager for Tomcat is an off-the-shelf product that allows you to store sessions of Apache Tomcat in Redis. This On-Premises feature enables you to use cache in multiple Tomcats, i.e, to share the cache between multiple sessions.
Caching accelerates application response times and helps applications scale by placing data that needed frequently close to the application. Redis, which an open source, in-memory, data structure server, allows application processes to have full statelessness, and at the same time, reduces duplication of data or requests to external data sources.
Customers who use this solution will need to verify that Redis is already installed and running on their end and then to connect to it.
There are no additional requirements for connecting to the Redis product.
Deployment Best Practice
We recommend running the Redis On-Premises solution in a separate machine - not the Backend - to provide maximum efficiency.
Configuring Redis for On-Premises
To configure Redis for the OverOps On-Premises solution, run the server (using
./takipi-server.sh...) with the following parameters:
These are the Redis nodes.
Multiple nodes can be configured with the redis-nodes parameter.
Redis nodes must be appear between quote marks.
When specifying multiple nodes, they can be separated by a semicolon (;) or by a space.
Remember that you must provide a port for each node (e.g., 6379).
Redis cluster type: these can be SINGLE, ELASTICACHE or MASTER_SLAVE.
The Redis for On-Premises feature supports three Redis types. The default type is SINGLE.
When specifying the --redis-nodes:
|--no-redis||Cancels/removes the Redis configurations||After configuring Redis, the configuration is retained for future sessions.To cancel or remove these configurations, use this parameter.|
All parameters are persisted under
/opt/takipi-server/bin/server-envs.shincluding the Redis endpoints.
Updated 3 months ago