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

  • Project
  • Task
  • Web service action
  • Message
  • File
  • Data synchronization log
  • Outbound queue
To monitor an outbound web service integration, use the Connectivity studio Integration operations workspace.


Application Consultant Application Consultant Start Start Monitor project history Monitor project history The project history shows, the project runs of the selected project. And for each project run, for example, its status is shown and if the project tasks have run with errors. Procedure 1. Click Connectivity studio Integration operations. 2. Click Projects. 3. In the list, find and select the desired project. 4. On the Action Pane, click Operation. 5. Click Project history. 6. In the list, find and select the desired project history record. 7. Sub-task: View project-related history. 8. Click Task history. 9. Close the page. 10. Click Batch history list. 11. Close the page. 12. Click Subprojects. 13. Close the page. 14. Close the page. 15. Close the page. Monitor task history Monitor task history Usually, you run a task by running the related project. However, you can also run a single task, for example, for testing purposes.When a task is run, you can view the task history. The task history shows, for example, the status of the task run and if the related messages have run with errors. Procedure 1. Click Connectivity studio Integration Design. 2. In the Related links section, click Tasks. 3. In the list, find and select the desired task. 4. Click Task history. 5. In the list, find and select the desired task run. 6. Sub-task: View task-related history. 7. Click History. 8. Close the page. 9. Click Batch history list. 10. Close the page. 11. Close the page. 12. Close the page. Monitor web service action history Monitor web service action history 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. Procedure 1. Click Connectivity studio Integration operations. 2. Review the web service action runs for which errors occurred. Click the Webservice errors tab. Note: You can also click the Web service tab, which shows all web service action runs. 3. In the list, find and select the desired web service action run. 4. Click Web service history. 5. You can view history that is related to the web service action run history. The Web requests tab shows all web requests that are sent during the web service action run. Expand the Details section. Note: You can view detailed information about a web request: - If a web request has an error, select it, and, on the Error tab review the details of the reported error. - For outbound web service actions, you can view the web request header in JSON format. Authorization information is excluded from the header. - For inbound and outbound web service actions, you can view the transferred data in the format as defined by the applicable message. 6. The Message history tab shows all messages that are run for the web service action run. Click the Message history tab. Note: If a message has an error, review the details of the message run. To do so, on the Action pane, on the History tab, click Message history. 7. Close the page. Monitor message history

Monitor message history

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.

 

@videoref:CS7

End End On which level do  you want to monitor  the history? On which level do  you want to monitor  the history? Monitor file history

Monitor file history

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 outbound queue

Monitor outbound queue

For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the data synchronization log. On processing the data synchronization log, based on the logged events, records are added to the outbound queue. On processing the outbound queue, for each record, the related message or web service action is run to export the applicable data.

When the outbound queue is processed, errors can occur. You can reset the outbound queue record status to New. For example, when running a web service action, the external web service can be down. As a consequence, running the related outbound queue records fails and these get the status Error. When the issue is solved, you can reset the status to New, And the next time the outbound queue is processed, these records are processed again.
This flow explains how to:
  • View the outbound queue.
  • Reset the outbound queue to rerun outbound queue records. Usually, you do so in case of any issue.
To monitor the outbound queue, use the Connectivity studio Integration operations workspace.
If the outbound queue does not run at all, the batch server can be down.

Monitor data synchronization log

Monitor data synchronization log

For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.
This topic explains how to monitor the data synchronization log.

If table events are not logged in the Data synchronization log as expected, you can check the data synchronization setup for your message or outbound web service action.

If logged events in the data synchronization log are not processed to the outbound queue, you can:

  • Check if processing the data synchronization log is set up correctly.
  • Test the data synchronization log processing.

If processing the data synchronization log does not run at all, the batch server can be down.

Project Task Web service  action Message File Outbound queue Data synchronization log

Activities

Name Responsible Description

Monitor project history

Application Consultant

The project history shows, the project runs of the selected project. And for each project run, for example, its status is shown and if the project tasks have run with errors.

Monitor task history

Application Consultant

Usually, you run a task by running the related project. However, you can also run a single task, for example, for testing purposes.
When a task is run, you can view the task history. The task history shows, for example, the status of the task run and if the related messages have run with errors.

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 outbound queue

Application Consultant

For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the data synchronization log. On processing the data synchronization log, based on the logged events, records are added to the outbound queue. On processing the outbound queue, for each record, the related message or web service action is run to export the applicable data.

When the outbound queue is processed, errors can occur. You can reset the outbound queue record status to New. For example, when running a web service action, the external web service can be down. As a consequence, running the related outbound queue records fails and these get the status Error. When the issue is solved, you can reset the status to New, And the next time the outbound queue is processed, these records are processed again.
This flow explains how to:
  • View the outbound queue.
  • Reset the outbound queue to rerun outbound queue records. Usually, you do so in case of any issue.
To monitor the outbound queue, use the Connectivity studio Integration operations workspace.
If the outbound queue does not run at all, the batch server can be down.

Monitor data synchronization log

Application Consultant

For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.
This topic explains how to monitor the data synchronization log.

If table events are not logged in the Data synchronization log as expected, you can check the data synchronization setup for your message or outbound web service action.

If logged events in the data synchronization log are not processed to the outbound queue, you can:

  • Check if processing the data synchronization log is set up correctly.
  • Test the data synchronization log processing.

If processing the data synchronization log does not run at all, the batch server can be down.

Monitor message history

Monitor file history

Monitor data synchronization log

Monitor outbound queue

Provide feedback