When compiling the agent within the web server, I would receive the following error, 'java.lang.RuntimeException: Failed to get configuration file:OpenSSOAgentBootstrap.properties'

SOLUTION
When decompiling the jar file, you see that it attempts to locate the System.getProperty value of 'openam.agents.bootstrap.dir

So, within your VM arguments, you need to declare the openam.agent.bootstrap.dir value to point to the OpenSSOAgentBootstrap.properties file. Within eclipse, you can include this within your VM arguments. For your environment, you can include this within your bash_profile file or if there's more than one container, include the value within the container startup script.

For my solution, I included the value -Dopenam.agents.bootstrap.dir="C:\Users\danielredfern\forgerock\j2ee_agents\tomcat_v6_agent\Agent_001\config value within the VM argument and it resolved the issue of failing to locate the forgerock OpenAM configuration
About the author

Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...


Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...

When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
Read More...
