How To:Capture Trace Events related to SSL when using Windows Keystore under .NET Managed client
ANILKSAHU 270007BXD4 Visits (2681)
MQ v8 onwards managed .Net clients can establish a secure SSL connection to the Queue Manager. IBM MQ ships a number of samples Here that demonstrate creating SSL connections to a queue manager in .Net Managed mode. One of challenges that comes across while debugging SSL issues with a managed .Net client using windows keystore is that standard strmqtrc does not capture all SSL tracing artifacts when the scenario involves usage of Windows keystore in the client application side.
The blog aims are articulating the steps to be followed to capture a detailed managed .Net client SSL flow when configured when using windows keystore to aid in debugging and problem determination.
Steps To capture Managed .Net SSL client Trace:
2. Add the following system diagnostics configuration section.
3. Add the App.Config to your project
i.e Add->Existing Item..
4. Once Build/Compile is successful start the trace using the following command
strmqtrc -p Application.exe -t all -t detail
5. Run the application
6.The required trace will be captured in the following path
To confirm whether the Trace is captured or not please check the call i.e. MQEx
Note:No additional/new log file or .TRC file will be created to capture the SSL flow by application. The application trace itself will contain the captured
SSL flow e.g AMQ<pid>.trc