cancel
Showing results for 
Search instead for 
Did you mean: 

consume mdm webservice

Former Member
0 Kudos

HI,

     I deploy mdm webservice on nw7.4 via mdm wsgenerator. now i can find the webservice in ws navigator, but i got error infor after invoking.what's wrong with my operation.

     error message:

     connection_3005-Cannot connect with MDM using destination MDM_BANK_INFO; caused by: Can not connect with UserSessionContext to repository 'TF_BANK_ACCOUNT' on the server 'xx.xx.xx.xx'.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I got another error message if i invoke In test senarios. the error message is :


com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingExceptiononnection IO Exception. Check nested exception for details. (HTTP Client, does not have endpoint url specified.).

Bhargavakrishna
Active Contributor
0 Kudos

Hi dazhong deng,

Please recheck your end point URL, it might be wrong or leading spaces in it.

Refer the below blog

Regards

Bhargava Krishna

Former Member
0 Kudos

HI, Bhargava,

     Error about endpoint has been resolved.

     Now I try to test in soapui,

url = http://IP:50000/CURD_BANK/HTTPNone?wsdl&mode=ws_policy&style=document

I get the same error message with wsnavigator,

connection_3005-Cannot connect with MDM using destination MDM_BANK_INFO; caused by: Can not connect with UserSessionContext to repository 'TF_BANK_ACCOUNT' on the server 'xx.xx.xx.xxx'

how to specify the mdm connection parameter correctly?

former_member186851
Active Contributor
0 Kudos

Dazhong,

Check if the below link helps for configuration part

Bhargavakrishna
Active Contributor
0 Kudos

Hi

Please refer the below note and apply the solutions as suggested.

Note 1691115 - connection_3005-Cannot connect with MDM using destination


Regards

Bhargava Krishna

Former Member
0 Kudos

It seems that there is bug on mdm7.1 SP08 according to note 1691115.but mdm version of mine is 7.1 sp14. I will raise a ticket to sap.

Former Member
0 Kudos

The issue is resolved. Please refer to note 1542631.

Answers (0)