cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP:Server Server Error XIAdapter ADAPTER.JAVA_EXCEPTION 500Internal Server Error

Former Member
0 Kudos

Hi,

I have been testing an API (WSDL file) through SOAPUI from which I am getting successful response however when I am posting it from POSTMAN for chrome I am getting Server Error XIAdapter ADAPTER.JAVA_EXCEPTION 500 Internal Server Error . Is that I have to check from the Adapter configuration side ? 

Below I have pasted the URL and the the xml for the reference used to test the API.

http://piqas.xxxxx.com:50000/XISOAPAdapter/MessageServlet?channel=:BS_MOBILE_PORTAL:senderParty=&sen...

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

  <SOAP-ENV:Header/>

  <SOAP-ENV:Body>

  <ns3:MT_Cash_IN_Deposit_SavingAccount_Request xmlns:ns3="http://adarsh_mob_ecc.com" xmlns:ns4="http://adarsh_crm.com">

  <Transaction_Request_Number>1454582123082</Transaction_Request_Number>

  <BranchCode>1057</BranchCode>

  <AccountType>SS</AccountType>

  <AccountNumber>003</AccountNumber>

  <Amount>1000</Amount>

  <AdvisorCode>852</AdvisorCode>

  <NetworkID>+3584433445566</NetworkID>

  <MAC>F</MAC>

  </ns3:MT_Cash_IN_Deposit_SavingAccount_Request>

  </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

A prompt response will be appreciated.

Thanks

Sumanta

Accepted Solutions (0)

Answers (2)

Answers (2)

markangelo_dihiansan
Active Contributor
0 Kudos

Hi Sumanta,

First check if your PI system is allowed to connect to the target URL. This can be done by a simple ping command via OS (SM69), SM59 (type G) or in NWA (HTTP Destination). If it is working, analyse the http headers in SOAP UI and see if you missed a configuration in your SOAP receiver adapter.

Regards,

Mark

Former Member
0 Kudos

Thanks Mark will check n revert

Regards,

Sumanta

Former Member
0 Kudos

Hi Mark, The test results are fine. Any thing else if you can suggest. Regards, Sumanta

former_member186851
Active Contributor
0 Kudos

Hello Sumantha,

Make sure your adapter is configured with HTTP protocol.

markangelo_dihiansan
Active Contributor
0 Kudos

Hi Sumanta,

In that case it has something to do with the request. You can use this to trace the request coming from PI and compare it with SOAP UI

Regards,

Mark

engswee
Active Contributor
0 Kudos

Hi Sumanta

Any reasons why you need to test with both SOAPUI and POSTman since both are test tools and using one would be sufficient? What is the actual end-to-end scenario? What application would be sending the SOAP message to the PI system?

Rgds

Eng Swee

Former Member
0 Kudos

Hi Eng,

Actually our PI is integrated to a third party Mobile application and they are performing the test of APIs' in POSTMAN for chrome and they are encountering the said error. However, we are testing the same in SOAPUI we are getting successful response.

The flow is the input will be accepted through an mobile app (3rd party) and send to PI (SAP) and later on request processed at ECC side.

Regards,

Sumanta

engswee
Active Contributor
0 Kudos

Hi Sumanta

If you are able to test with SOAPUI and it is successful, I don't think there is anything wrong with your PI configuration.

My guess would be that when using POSTman, they are not constructing either the URL endpoint or the SOAP envelope correctly.

Rgds

Eng Swee