Making the Connection With Purview
Go Up to Understanding Purview Integration
You first must set up the connection for your Purview Integration. Once a user clicks the Test button on the Purview Integration Connection page, Team Server performs several tests to ensure connectivity with Purview. During this process, ERTS displays a progress pop-up window that shows which tests pass or fail. Detailed errors and responses received from Purview for these tests are stored in the purview.log file.
These tests include:
- HTTP GET test. This test performs an HTTP GET request to a known working endpoint (https://www.idera.com) and checks whether you are connected to the internet.
- Proxy Server test. ERTS uses the input for host and port from the UI post, checks for the existence of a Proxy Server, and then verifies whether authentication is required.
- Team Server Keystore test. Team Server checks whether the protocol is HTTPS. If so, then an SSL certificate or keystore is necessary to support HTTPS. The system then tests for the existence of a Team Server keystore file.
- Purview Server Ping test. This test verifies the reachability of the Purview server from Team Server. Depending on the selected Purview address (HTTP or HTTPS) it makes an HTTP GET request to Purview and logs the response.
- Username and Password Test. This test makes sure that the entered usernames and passwords are correct, valid, and properly supported.
- HTTPS Certificate test. The system checks for the existence of the Purview server keystore file to verify the HTTPS certificate.
- API test. This test checks the connection to the available Purview API.
All of the above tests are essential to confirm proper connectivity with Purview. In case of any failures, detailed errors and responses received from Purview for each test is recorded in the 'purview.log' file.