cancel
Showing results for 
Search instead for 
Did you mean: 

SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided.

former_member203117
Active Participant

Dear Team,

When I call a standard webservice I'm getting the below error in T-code SRT_UTIL "SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided."

Can anyone please help me out, If I had missed any setting.

Regards,

Tushar.

Accepted Solutions (0)

Answers (2)

Answers (2)

mageshwaran_subramanian
Active Contributor
0 Kudos

Hi Tushar, Did you get this issue resolved?. I tried what Goverdhan has mentioned (adding MessageID to the endpoint) but it did not work on SoapUI.

jitendra_it
Active Contributor
0 Kudos

Hello ,

Check this thread http://scn.sap.com/thread/3278733

Former Member
0 Kudos

Hi,

Unfortunately the option is disabled.

Regards,

Tushar.

former_member182290
Participant

Hi Tushar,

Please check that you are passing message ID in the URL.

How are you consuming the webservice (Async) from soapUI or SAP or Third Party.

The endpoint should be in below format

http://host:port/sap/bc/srt/xip/sap/xyz_in/705/xyz_in/binding1_xyz_in?MessageId=999C6E5C-5672-2CC1-1...

If SAP is the consumer of the service you can should need configure the "Logical Port" with below settings

Messaing Tab.

RM Protocol: SAP RM

Message ID Protocol : WS-A Message ID

MessageId is used to detected duplicate messages, if you trigger the service with same MessageId the response from previous sucessful execution will be sent back to the consumer.

Another parameter that can passed in URI is QueueId, two or more messages with same Queue ID are processed in same queue on the provider side.

Thank You

Regards

Goverdhan Totawar

Former Member
0 Kudos

Hi Goverdhan,

In SOAMANAGER, I selected 'service defination' and I searched for "BusinessPartnerSUITEBulkReplicateRequest_In" then I created a service and then generated the WSDL. When I'm trying to use the WSDL in SOAPUI for testing I'm getting the error as described initially. I would want to call this WSDL from SAP as well as from NON-SAP.

Are you suggesting that I create a consumer proxy and then use the WSDL in SOAPUI or other programs..

Regards,

Tushar.

former_member182290
Participant

Hi

For testing from soap UI your endpoint should look in below format .

http://host:port/sap/bc/srt/xip/sap/xyz_in/705/xyz_in/binding1_xyz_in?MessageId=${=java.util.UUID.ra...()}

So once WSDL is imported edit the endpoint to add Message Id part.

or

http://host:port/sap/bc/srt/xip/sap/xyz_in/705/xyz_in/binding1_xyz_in?MessageID=${=java.util.UUID.ra...()}

this piece of code will generate random UUID in soap UI ${=java.util.UUID.randomUUID()}.

For testing from SAP you need to follow the steps put in my previous response.

former_member141
Discoverer
0 Kudos

This worked for us thanks. We are using SOAP UI to test the service and first URL mentioned by Totawar worked with a UUID created by us.