How to Add New Servers to SQLRepositoryEventServer For Distributed Cache Invalidations Without a Server Restart
(Doc ID 2115287.1)
Last updated on JUNE 03, 2018
Applies to:Oracle Commerce Platform - Version 10.0 and later
Information in this document applies to any platform.
When new servers are added to the production cluster, it is sometimes necessary to restart so that the new servers become part of the cluster. For example, customers may follow a procedure similar to the following to allow the new servers to receive cache invalidation messages (when repositories are configured with distributed cache mode):
1. add/remove servers
2. reconfigure the DAS_GSA_SUBSCRIBER table
3. restart the required servers for the new/old connections to be picked up/dropped by the SQLRepositoryEventServer
Are there any REST or other web calls that can be sent to the Oracle Commerce application that will add/remove a server from the SQLRepositoryEventServer in-flight without requiring a server restart?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document