When executoing a flow in debug via Central, the CENTRAL_URL variable in the global context is http://localhost:8080/oo.
Is there any way through a scriptlet to access the Central URL that the debugger is connected to?
Try to check the value of the management url in the central wrapper file.
if that is set to localhost:8080 it would be great to change it to the FQDN of the central machine and the right port.
After restarting central and remote debugging again - I wonder what's the CENTRAL_URL that you'll get.
I have checked the central-wrapper.conf file and can see the following entry:
I can look to get this changed within our environment, however, are you able to elaborate on any potential consequences of changing this entry or is it solely used for remote debugging?
I made the change to the central-wrapper.conf file but the URL provided was still localhost.
I then made the same change to the ras-wrapper.conf file (in this environment, central and the ras are co-hosted) which solved the problem and the correct URL is now returned when debugging.
Thanks for your help.
Actually making this change didn't work entirely.
It did resolve the issue of the CENTRAL_URL variable being populated correctly, however, it made the RAS unavailable and the RAS logs showed there was an SSL error...
org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [https://<HOSTNAME_REMOVED>/oo/central-remoting/workerNodeService]; nested exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
I have rolled back the config changes made to investigate how to resolve.
That is because the RAS should point to the proper URL.
This is not just for the remote debugger. The best practice is to thave that URL to the FQDN of the machine.