Hi @Mani Based on the error message "The operation has timed out," it appears the issue might be related to network connectivity or SSL handshake delays when using the SSL certificate.
Here are a few suggestions to help troubleshoot and resolve the issue:
- Validate SSL Configuration: Ensure the DB2 server is correctly configured to accept SSL connections on the port you're using. You can test this by connecting using a DB2 client tool (e.g., IBM Data Studio) with SSL enabled from the same machine where the Self-hosted Integration Runtime (SHIR) is installed.
- Verify Port Accessibility: SSL connections may use a different port than non-SSL connections. Make sure the correct SSL port is open between the SHIR host and the on-prem DB2 server.
- Update Truststore (if needed): While adding the SSL certificate to the Trusted Root Certification Authorities should be sufficient, consider also importing it into the Java truststore used by the SHIR, especially if you're using a JDBC driver under the hood.
- Check SHIR Logs: Review the SHIR logs (located in
C:\Program Files\Microsoft Integration Runtime\5.0\Shared\Logs
) for any additional error details during the connection attempt. - Driver Version Compatibility: Ensure you are using a version of the DB2 driver that supports SSL and is compatible with both DB2 11.5.9 and ADF.
- Timeout Configuration: If the SSL handshake is taking too long, try increasing the connection timeout value in the linked service configuration (under Advanced settings).
For more details, please refer to the following documentation:
- Copy data from DB2 using Azure Data Factory or Synapse Analytics
- Enable remote access from intranet with TLS/SSL certificate (Advanced)
- Create and configure a self-hosted integration runtime
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.