Hazelcast is an external in-memory datastore used to help improve memory usage and data consistency on the Gateway. If you have a Hazelcast storage, there are a couple of steps you need to take to set it up as the external in-memory storage for Gateway. 

You can read more about the support CA API Gateway offers if you would like to use Hazelcast as an alternative cache storage here. 
 

CA API Gateway Management 9.4

If Hazelcast is not available in your environment, the default MySQL will be used for in-memory storage and the performance may vary accordingly. In this case, if you do not want any Hazelcast assertions or extensions to be loaded, you can disable it completely with the following steps: 

1. Take a backup of the following assertion files in /opt/SecureSpan/Gateway/runtime/modules/assertions/ : 

a) EmbeddedHazelcastSharedStateProviderAssertion-1.0.00.aar 
b) ExternalHazelcastSharedStateProviderAssertion-1.0.00.aar 

2. Remove or move the assertion files to a location outside of the Gateway directory. 
3. Restart the ssg service. 

Upon restart, you should no longer see any Hazelcast related extensions being loaded in the ssg log. There also shouldnot be any Hazelcast thread observed in the thread dump.

 

Connect to an External Hazelcast Datastore
Hazelcast Storage Best Practice