Monitor inbound web service history

Depending on how you run an inbound web service integration, you can monitor the integration on these levels:

Web service action
Message
File
Inbound web service staging table (only applicable if the asynchronous mode of the web service action is 'Batch')

To monitor an inbound web service integration, use the Connectivity studio Integration operations workspace.

Activities

Name	Responsible	Description
Monitor web service action history	Application Consultant	When a web service action is run, you can view the web service history. The web service history shows, for example, the: Status of the web service action run. Related web service requests. Related message runs. Possible issues can occur, for example, in the: Message run. Connection with the web service.
Monitor message history	Application Consultant	You can review and analyze the history of message runs that have run with errors. You can investigate these errors and take the appropriate actions to solve the errors. If the errors are solved, you can re-run the message run. To monitor the message history, use the Connectivity studio integration operations workspace.
Monitor file history	Application Consultant	You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history. Registered file actions are the: Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered. Additional file actions as set up for the Azure file storage connector. You can monitor the file history from the Connectivity studio Integration operations workspace.
Monitor inbound web service staging table	Application Consultant	Depending on the asynchronous execution mode of the inbound web service action, the inbound web service process runs directly or asynchronously. If the asynchronous execution mode is 'Batch' and the web service action is triggered, the data, as received by the web service request, is stored in the Inbound web service staging table. You can monitor the inbound web service staging table.

Activities

Name	Responsible	Description
Monitor web service action history	Application Consultant	When a web service action is run, you can view the web service history. The web service history shows, for example, the: Status of the web service action run. Related web service requests. Related message runs. Possible issues can occur, for example, in the: Message run. Connection with the web service.
Monitor message history	Application Consultant	You can review and analyze the history of message runs that have run with errors. You can investigate these errors and take the appropriate actions to solve the errors. If the errors are solved, you can re-run the message run. To monitor the message history, use the Connectivity studio integration operations workspace.
Monitor file history	Application Consultant	You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history. Registered file actions are the: Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered. Additional file actions as set up for the Azure file storage connector. You can monitor the file history from the Connectivity studio Integration operations workspace.
Monitor inbound web service staging table	Application Consultant	Depending on the asynchronous execution mode of the inbound web service action, the inbound web service process runs directly or asynchronously. If the asynchronous execution mode is 'Batch' and the web service action is triggered, the data, as received by the web service request, is stored in the Inbound web service staging table. You can monitor the inbound web service staging table.

Related to	Notes
Run inbound web service staging records
Set up default response text

Provide feedback