cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE_GUEST SOAP: Call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized

Former Member
0 Kudos

Dear Experts

Using PI 7.4 (Dual stack) I have configured the ICO for JDBC to Proxy scenario with SOAP receiver adapter and getting the error message at Adapter engine level,

SOAP: Request message entering the adapter processing with user J2EE_GUEST

Failed to call the endpoint: Error in call over HTTP: HTTP 401 Unauthorized

SOAP: Call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized.

We configured the ABAP proxy setups by referring Michal blog and SAP Guide.

How to Set Up the Communication between ABAP Backend and SOAP Adapter using XI Protocol

Please kindly provide your support.

Regards

RK Neelagiri.

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member607993
Contributor
0 Kudos

Hi Neelagiri,

In the Netweaver administrator, Goto to SOA > Technical Configuration > Destinations.

Please check whether respective HTTP destination ping test is working fine or not.

URL should look like below and this URL go to transaction SICF (SAP back-end) and choose ‘Execute’. Service tree will be displayed in the result.

http://ipaddress:port/sap/xi/engine?type=entry

and assign the additional settings for SAP systems correctly and under Basic Authentication 'User id' should hold the below role.

SAP_XI_APPL_SERV_USER

For additional debugging you can use XPI Inspector which gives a clear picture.

Thanks and Regards - Rajesh PS

former_member184720
Active Contributor
0 Kudos

Hi Neelagiri - The blog you followed gives information about setup in ECC for sending proxy messages through PI.

In your case as proxy is your receiver system, you can configure the channel directly.

URL : http://<<host>>:<<port>>/sap/xi/engine?type=entry

Use Logon Data for SAP System

You have to provide the ECC system details here and the user should exists in ECC(in that specific client) with the role "SAP_XI_APPL_SERV_USER"

Former Member
0 Kudos

Dear All,

Thank you for your inputs.

We have resolved the Issue.

Regards

RK Neelagiri

Former Member
0 Kudos

It would be great if u let us know how did u solved this?

Former Member
0 Kudos

Hi,

could you please tell us how you solved this issue.

We are facing excactly the error.

Regards

Former Member
0 Kudos

Hello Cyrson,

Sorry for delay in response.

Please confirm the Target URL you are maintain in Proxy SOAP adapter connection parameters.

Regards

RK N

Former Member
0 Kudos

Hi,

HTTP: HTTP 401 Unauthorized comes when either user got locked or credentials are wrong.


Check in your respective rfc destination by clicking on connection test and authorization test.



Regards

Venkat

iaki_vila
Active Contributor
0 Kudos

Hi Neelagiri,

Are you sure that you have set the j2ee_guest password correctly in the sm59?, have you tried to enter into the system with that user?, have you checked the user is not blocked?

Regards.

Former Member
0 Kudos

Hello,

Make sure the user which u are using is having SAP_XI_APPLY_SERV user access??

Thanks

Amit Srivastava

Former Member
0 Kudos

Hi Amit,

Role is already assigned. Still no luck..

Regards

RK Neelagiri

Former Member
0 Kudos

Hello,

I hope u have assigned "SAP_XI_APPL_SERV_USER" role to the user which is created in ECC and the same u are using in SOAP receiver channel?

http://host:port/sap/xi/engine?type=entry 

From SAP HELP

Messaging Components and Required Roles

Messaging Component

Role

ABAP proxy sender

No special authorization required

Java proxy sender

SAP_XI_APPL_SERV_USER

Advanced Adapter Engine

SAP_XI_APPL_SERV_USER

Integration Server

SAP_XI_APPL_SERV_USER

ABAP proxy receiver

SAP_XI_APPL_SERV_USER (additional application-specific authorizations required)

Java proxy receiver

SAP_XI_APPL_SERV_USER (additional application-specific authorizations required)

Thanks

Amit Srivastava