To aid in debugging of jobs, you can enable the logging of the request and response message that Connect sends to SOAP or OData end points. These additional log messages appears in the job execution history.
There are two ways to apply these settings.
Through the Connect UI
Follow these steps to enable debugging via the UI.
-
Click on the System Utilities
-
Click on the SETTINGS tab.
-
Click the Add button to add a new setting.
-
Enter the Property Name, Property Value, and select the Component Agent as the component the value will apply to. The valid values are:
Purpose
Property Name
Property Value
SOAP Incoming
connect.debug.soap.logIncomingMessages.enabled
true/false
SOAP Outgoing
connect.debug.soap.logOutgoingMessages.enabled
true/false
OData
connect.debug.odata.logMessages.enabled
true/false
-
Click Apply. No restart of the Agent is required.
Through the property files (Requires access to the k8s cluster)
Follow these steps to enable debugging:
-
Modify the connectAgent.properties file located in your GIT repository.
-
For SOAP, set the following settings to true:
-
connect.debug.soap.logIncomingMessages.enabled
-
connect.debug.soap.logOutgoingMessages.enabled
-
-
For OData, set the following setting to true:
-
connect.debug.odata.logMessages.enabled
-
-
-
Restart the Agent by running the command.
-
For Azure AKS – ‘kubectl -n connect-agent rollout restart deployment agent’
-
For Microk8s – ‘microk8s kubectl -n connect-agent rollout restart deployment agent’
-