Clear Cache in Secondary Data Center for Omnissa Access

After you finish setting up the primary and secondary data centers, clear the caches in the secondary data center. This is in preparation for a failover. When you fail over to the secondary data center, caches in the secondary data center should be empty.

Use the REST API described here to clear the caches. Another way to clear cache is to reboot the virtual appliances.

Procedure

1. Run the following REST API from a REST client such as Postman.

   PATH: /SAAS/jersey/manager/api/removeAllCaches

   Method: POST

   Add Headers:

   Authorization: HZN <cookie_value>
   Accept: application/json (Access version 24.12.1.0)
           Please contact Support for the correct input for Access version 24.12.0.0.
   Content-type: application/json (Access version 24.12.1.0)
           Please contact Support for the correct input for Access version 24.12.0.0.
   

   Add in Body (raw) section:

   {}
   

   Note:

   • You must run the API as the tenant administrator, that is, the administrator created in the System domain when you install Omnissa Access. Domain accounts synced from your enterprise directory cannot perform this function.
   • You can obtain the HZN cookie by logging into the Omnissa Access service as the tenant administrator, then accessing your browser's cookie cache.
   • Empty cacheNames indicates remove all caches.