The AFX Server is in a Running state but the RSA Identity Governance & Lifecycle AFX Connectors are stuck in a Deployed state and do not progress to a Running state. For example,
The $AFX_HOME/esb/logs/esb.AFX_INIT.log has the following error:
2019-04-24 00:00:03.882 [ERROR] com.aveksa.afx.server.manager.MMCRequestManagerImpl:118 - Unable to get status for all Connectors from MMC com.aveksa.afx.server.manager.MMCException: Failed to get flows for server. No associated server Id. Check Request Manager Initialization
This error indicates a problem with mmc-console. We have seen this error when there is a problem with the version of Java installed on the AFX server or there is a problem with the AFX environment setup.
The mmc-console collects connector information in order for the connectors to run. If mmc-console fails to start, then the connector information is never collected and the connectors cannot move from Deployed to Running.
Check that Java is installed on your AFX server and that it is the same version of Java that is required by your version of RSA Identity Governance & Lifecycle. If Java is not installed, or the incorrect version of Java is installed, then install the appropriate Java version on your AFX server. For example, RSA Identity Governance & Lifecycle 7.1.1 requires Java 1.8.