How To Check HTTP Responses Log File in PI/PRO

Introduction

We always need to troubleshoot incoming requests into PI, some times before coming to application the call failed and these requests we unable to see in our message monitoring or default trace logs.

For example if you you have a scenario SOAP sender if you test the message from SOAP UI or any other client you will get the error response in SOAP UI, some type of errors you cannot see in PI message monitoring or NWA Log Viewer then we dont know what is exactly reason for this error.

For every HTTP request coming into PI system the responses are logged in responses_xx.x.trc file in file system. I want to show you where to access these files in PI.

Access HTTP Responses File

You can access this file in the below path in PI server. By default there will be 5 files and each one the maximum size is 10MB.

The example file look like below, so every HTTP request response code will be available in this file.

From above file you can see below:

• Date and Time of the request
• Source IP Address
• HTTP Method
• Path of the HTTP URL
• Response Code

Example#1

When you send the request from SOAP UI where sender is SOAP adapter, if you dont give any query parameters for sender business system, sender interface and sender namespace then you will get below response in SOAP UI.

You dont see this error in PI message monitoring or default traces. You can find these entries in HTTP responses file.

We can see the URL path from this log and by seeing this we can easily identify the error that sender did not send any query parameters in endpoint URL

Example #2

This time i want to give wrong user name and password when i send the request from SOAP UI.

You can see we get 401 unauthorized error in SOAP UI.

We can see 401 response code in the responses log file.

Conclusion

By using HTTP responses log file we can troubleshoot incoming calls which we cannot monitor in PI, this is very useful especially in case of SOAP sender or HTTP sender or REST sender. I hope using this blog we can easily find the root cause of the problem.