Running Tests in Debug

When the adapter is run in debug, some of the important logs are logged out. These logs help you know exactly what is happening when communicating with the other system. This is true when the adapter is integrated with IAP, and is also true when running standalone testing.

• OPTIONS: Provides all the call options. Authentication information is missing because we intentionally do not want to log any credentials. This is one of the most helpful logs to determine why something is working improperly.
• REQUEST: Provides the payload that will be sent to the other system.
• CALL RETURN: The raw response that is returned.
• RESPONSE: The response being returned (only the first element if an array).

Example: Running in Debug

debug: Test-eai-connectorRest-performRequest: OPTIONS: {"hostname":"replace.hostorip.here","port":80,"path":"/oss-core-ws/rest/oci/site/1/cascadeDelete?fs=dynAttrs%2CderivedAttrs","method":"POST","headers":{"GS-Database-Host-Name":"localhost","GS-Database-Name":"db_0834e8bc13d2b3d7a","interactive":false,"Content-Type":"application/json","Accept":"application/json"}}

debug: Test-eai-connectorRest-performRequest:REQUEST: {"name":"BERKELE1.updated","type":"oci/site"}