KB Article #178394

Copilot task starts, even if wrongly configure messing-up the CG registration

Problem

Copilot task starts, even if wrongly configure or if jar or other files are not installed


It mess-up the registration to CG


How to troubleshot


Resolution

If a logon to Copilot is not working, check the Copilot configuration

If the CG registration is not working, start to get more details from the requests between CG and CFT during the registration or during heartbeats:


Se the environment variable $_JAVA_OPTIONS as below ( *UNIX example )


Request from CG to CFT ( call to webservices )
export _JAVA_OPTIONS=$_JAVA_OPTIONS" -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog"
export _JAVA_OPTIONS=$_JAVA_OPTIONS" -Dorg.apache.commons.logging.simplelog.defaultlog=debug"
export _JAVA_OPTIONS=$_JAVA_OPTIONS" -Dorg.apache.commons.logging.simplelog.showdatetime=true"
export _JAVA_OPTIONS=$_JAVA_OPTIONS" -Dorg.apache.commons.logging.simplelog.log.org.apache.http=debug"

Requests from CFT to CG ( registration / heartbeat )
export _JAVA_OPTIONS=$_JAVA_OPTIONS" -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog"
export _JAVA_OPTIONS=$_JAVA_OPTIONS" -Dorg.eclipse.jetty.LEVEL=DEBUG"

Restart Central Governance, to get the changes activated.

-Ensure the "Transfer CFT Connector" service in CG is in debug mode
cli > serviceLog -l DEBUG -name "Transfer CFT Connector"



-Then to return to info mode:
cli > serviceLog -l INFO -name "Transfer CFT Connector"


-Logs will be located in:

$CG_HOME/runtime/com.axway.nodes.cftconnector_{un_UUID}/uma/logs/provider.log.*