Enabling connector trace on your container, should show you the communications with eConnect but probably not the database. For database connectivity monitoring, you'd need something lower level as that is not an HTTP protocol. Wireshark or SOCKS proxying in Charles would show you the communication ( It will use the IP address currently configured in the connection settings )
We take the connection settings and build out a JDBC string for the JTDS driver in the following format:
And will use the provided domain, username, and password to connect. Putting this information into any SQL browser should allow you to connect to the server and see what's there.
1 person found this helpful