Agent not seen in the Orchestrator

Products

• CA Process Automation Base

Issue/Introduction

Installed an agent, but it is not showing up when viewing the configuration screen in CA Process Automation

Environment

Process Automation versions 4.2 through 4.3.1Windows or Linux SSL enabled

Java 1.7 on the Process Automation orchestrator

Java 1.8 on the Agent server

Cause

Java versions between the server and the agent are different. You "could" pass

-Dcom.sun.net.ssl.enableECC=false 

from the orchestrator in the Java arguments to tell it to not use the ecliptic curve ciphers, but the better answer is to make the Java versions the same. Here we have a Java 8 release on the agent and a Java 7 release on the server. Java 8 restricts ECC ciphers, but Java 7 still uses them.

The error messages in the c2o.log file on the agent show

ERROR [com.optinuity.c2o.c2oagent.AgentManager] [A Agent Startup] Exception occurred while booting up the Agent 
com.optinuity.c2o.util.C2OException: Error retrieving a signed certificate from Domain and importing it to local store - Unsupported curve: [example curve number] 

The unsupported curve is the key message.

Resolution

Downgrade the JRE on the agent server to the same release as is installed on the orchestrator.

For instance, if you have JDK 1.7 update 80 on the orchestrator server, install this same release JRE 1.7 update 80 on the agent server.

You must uninstall the 1.8 JRE first.

Once you install the 1.7 JRE, open the file c2oagtsvcw.conf located under C:\Program Files\CA\PAM Agent\PAMAgent and modify line number 5. For example from this:

wrapper.java.command=c:/program files/java/jre1.8.0_77/bin/java

change it to this:

wrapper.java.command=c:/program files/java/jre1.8=7.0_80/bin/java

Verify the path before making the update. Save the changes, close the file and restart the agent.

When you log into Process Automation, from the configuration screen you should now see the agent. If it is not immediately shown, select Agents, right click and refresh.