Maximo Open Forum

 View Only

 VMMSYNC caching?

  • Administration
  • Integrations
Erwin Hebing's profile image
Erwin Hebing posted 10-17-2024 07:36

We have configured maximo to synchronize users from active directory using the VMMSYNC cron task

Users can either be added in Active Directory or added to the Virtual Member Manager on the Deployment Manager itself

What we noticed is that users added in the Virtual Member manager itself are not picked up by the VMMSYNC cron task

This only happens after we stop and start the application server on which the VMMSYNC cron task is executed

So it seems that there is somewhere a kind of 'caching'

Does anybody know if this 'caching' is the case?

And if so does anybody know if we can configure anywhere what the cache time is so that this cache is refreshed for example every hour?

Or if we can force this cache to be refreshed (without restarting the application servers); we tried a full resync of the nodes where the (cron task) application servers are running but this had no impact...

Thanks in advance,

Erwin

Hariprasad R's profile image
Hariprasad R posted 10-18-2024 08:12


Hi,

Hope this helps,

WebSphere typically caches records retrieved from AD for a period of time. As a result, VMMSYNC should be triggered after this cache period to synchronize any changes made in WebSphere with the Maximo system.

WebSphere provides configuration to adjust the cache expiration time or disable caching to allow real-time updates. However, disabling caching may affect performance.

To configure the cache settings, follow these steps:

  1. Log in to WebSphere, expand Security, and click on Global Security.
  2. Click Configure next to your current realm definition (Federated Repositories).
  3. Select Manage Repositories, then choose the repository you want to manage.
  4. Under Additional Properties, select Performance.

In Cache the search results, the Cache Timeout determines how long it takes for changes made to users on the directory server to reflect in WebSphere. You can increase or decrease this timeout based on your requirements (default is 600 seconds).

Verify the timeout setting in your environment, as it may help resolve your issue.

Unchecking the Cache the search results option will display changes in real time, but this may impact performance.

Related Content