cancel
Showing results for 
Search instead for 
Did you mean: 

Web Service Monitoring in ECC - SRT_MONI

former_member500122
Discoverer

We are trying to use point-to-point Web Services (No PI or other middleware) for inbound and outbound SOAP messages between SAP and 3rd party application and intend to use WS-RM functionality with SRT_MONI for message monitoring and error handling of asynchronous messages.

The outbound messages are asynchronous while inbound messages could be either asynchronous or more likely synchronous.

Here are the steps we took:

1. Created a consumer service in ECC with no return parameter and Asynchronous Reliable (see image below).

2. Completed the configuration using SRT_TOOLS and ran program SRT_ADMIN_CHECK, all steps were successfully checked. Followed this doc:

https://archive.sap.com/discussions/thread/3510591

3. Executed my Z program which consumes the service above...did not build any sequencing logic just yet to keep it simple for the first step in our PoC.

4. Ran SRT_MONI but were unable to see any messages (success or failure) for our web services but when running SRT_TEST we are able to see messages.

This is exactly the behaviour we like to see:

https://wiki.scn.sap.com/wiki/display/ABAPConn/ABAP+Web+Service+Monitors

Your help would be greatly appreciated.

daveplayfair
Discoverer
0 Kudos

Hey Saeed, I know you got this working, but what was the solution in the end?

Accepted Solutions (0)

Answers (1)

Answers (1)

Saeed_Mousavi
Newcomer
0 Kudos

Hi Dave,

The issue was related to a missing 'commit work' statement...see below:

create object lcl_my_service

exporting
logical_port_name = 'Z_EXT_SYSTEM'.

lcl_my_service->create_saleorder( input = input ).
cl_soap_tx_factory=>commit_work( ).
* Get Message ID from SRT
l_message_id_protocol ?= lcl_my_service->get_protocol( protocol_name = if_wsprotocol=>message_id ).
m_msgid = l_message_id_protocol->get_message_id( ).

The commit should be avoided if you are calling the service within an SAP BADI i.e. 'before update' or 'at save' event as it may interfere with an SAP commit in the subsequent chain of calls.

Hope this helps!

Regards,

Saeed