ABAP Client proxy authentification

[Former Member]

Hi,

I created a client proxy via SPROXY that executes a webservice on SAP XI. I also created a logical port via LPCONFIG for the generated proxy class.

In my report i execute the generated method but when execute the report i always get a popup to enter user and password to make the connection to XI.

Is it possible to make a connection without having the popup to enter user and password? Is it possible to use a default user and password?

Thanks a lot,

Vincent.

[Former Member]

Vincent,

Please check your RFC destination (SM59) from the application system that points to your XI system. Make sure you have given proper user id there.

If that is fixed, then it should not ask for the User id again.

Regards,

Ravi

Note : Please mark the helpful answers.

[Former Member]

Ravi,

I checked SM59 and the correct user and password is entered but we still get the popup at runtime.

It's something like

Resource XISOAPApps

User name

Password

Is there a method to give the user and password at runtime?

Regards,

Vincent.

[Former Member]

Vincent,

Ideally it should not ask for any user credentials.

Can you check the XI adapter settings once?

Regards,

Ravi

[Former Member]

Ravi,

I created a RFC of type G with following data:

• Technical settings tab:

Target host: my_server

service no : my_serverno

path prefif : /rep

• Logon & security tab:

basic authentication

ssl inactive

user username

password userpassword

*Special options tab

icm default timeout

http 1.0

compression inactive

compressed response yes

accept cookies no

Is this correct or do i have to make additional settings?

What is strange is that in SPROXY i can navigate thru the services on XI without any popup for userdata, but when i'm testing the generated client proxy in SPROXY i also get the popop for userdata.

Is it possible to give additional user data in the definition of the logical port?

Regards,

Vincent.

[Former Member]

Vincent,

I don't think there is any other setting.

In SM59, when you do a REMOTE LOGON, is it directly opening the XI system, or is it asking for logon password?

In port you only specify the RFC destination, there will NOT be any place to logon details.

Regards,

Ravi

Note : Please mark the helpful answers

[Former Member]

Hi Vincent,

when I look into my RFC setting I am using connection type H (for HTTP connection to R/3 system) to connect to the integration server.

As a path prefix I am using '/sap/xi/engine/?type=entry'.

The proxy communication works fine.

Maybe this helps.

Regards,

Andreas

[Former Member]

I was able to fix the problem.

In the logical port definition I must use HTTP destination in stead off URL in the call parameters tab.

Regards,

Vincent.

[jacob_ellsworth]

We have been having the same problem it sounds like you had.

When we do a function module test, it works fine set to use Exchange Infrastructure in LPCONFIG, but we always get prompted for an ID and password.

When we change LPCONFIG to use Web Service Infrastructure and our Call Parameters to use the HTTP Destination with path suffix /sap/xi/engine?type=entry we now get an error 'Soapfaultcode:4 Error during conversion of XI message'.

Our RFC has the HTTP proxy piece empty, as all pieces of this are on the internal network.

Is this something you ran into or know something about for fixing this issue? Any ideas of where to start looking at this?

any ideas would be really appreciated.

Thanks,

Jake

[Former Member]

Hi,

I created client proxy to consume external web service and also created logical port for this proxy class in LPCONFIG.

Now in my program when I'm trying to invoke this service i'm getting pop-up to enter user and password. Could you please let me know how I can avoid this.

in my logical port in call parameter tab i'm using URL destination.

Do I need to create RFC(HTTP) destination for this in SM59.

Could you guys please let me know how this can be done.

Regards

Vikram

[Former Member]

Hi,

The error "Error during conversion of XI message" was due to the fact that you set Path Prefix to "/sap/xi/engine?type=entry," in the HTTP desitnation. This error will go if you set Path Prefix to BLANK.

Tim