What happens when an Identity Manager Environment is stopped or restarted?

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Risk Analytics
• CA Secure Cloud SaaS - Arcot A-OK (WebFort)
• CLOUDMINDER ADVANCED AUTHENTICATION
• CA Secure Cloud SaaS - Advanced Authentication
• CA Secure Cloud SaaS - Identity Management
• CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

A Identity Manager "Environment" is a Management workspace, it is a logical space where you can have all the configuration entities, e.g. users, roles, tasks, etc.
This "Environment" has status, and can be stopped and started.


 

What occurs when a CA Identity Manager "Environment" changes status (i.e. is stopped, started\restarted)? 

Environment

CA Identity Manager\CA Identity Suite 14.x

Resolution

When an environment is stopped, started or restarted a cached hash table identifying the environment is either cleared or created in memory. The Identity Management User Console will serve requests when it sees the environment cache object exists and will not serve requests when the cache is clear.

When an environment stop/start occurs, the serverCommand service publishes a JMS message to each IM cluster node to clear or create the IM cache on each respective node.

There is no file, setting, or configuration that can be seen or modified for stopping/restarting because the stop/start status is managed entirely in memory.

Additional Information

The JBoss\WildFly process is not stopped or started\restarted during.