ABAP client Proxy authentication required

[gianluca_tacchella2]

Hallo, my problem is about ABAP client Proxy authentication.

Scenario:

Our Dev. BW MWDCLNT600 queries “forward” a (RetailPro) database (JDBC Receiver C.Channel), by Dev. XI , in order to "drive" data extraction (realized, backward, from RetailPro to BW).

Forward communication from BW uses a call on ABAP Client Proxy technology (I mean, a BW class implements an XI outbound Message Interface).

Problem:

Something changed, we don't know what or where, and since last week everytime you execute the report (F8) you are prompted for an authentication popup.

Official manual guide is: (ABAP Proxy Generation)

http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm

in which you have to manage the 2 properties for credential supplying:

com.sap.aii.applicationsystem.serviceuser.name

com.sap.aii.applicationsystem.serviceuser.pwd

in order to "drive" authentication to Integration Engine.

In our scenario, ABAP report ZRTP_FLOW_CONTROL drives data extraction query, by a call to execute method

of class: ZCO_MI_FLOW_CONTROL_OB

which implements Outbound MI: MI_Flow_Control_OB (...all in SPROXY).

In SXMB_ADM, XI IEngine URL is correct...

In Exchange Profile, the 2 properties (see above) are correctly maintained (user: XIAPPLUSER, and password is OK)

Any suggestion?

Thanks all in advance!

Gianluca

[gianluca_tacchella2]

Hi all,

the problem is solved, as specified in Blog:

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

Error was putting in SXMB_ADM directly the URL of Integration server, instead of reference to RFC Destination. (dest://XI_INTEGRATIONSERVER).

Thanks all!

Gianluca

[VijayKonam]

Check the HTTP RFC destinations and the authentication details used there.. use test connection to see if the password is correct.

VJ

[Former Member]

Hi

I would like to suggest you to change the password in http destination (sm59) configured to comunicate with XI and put another one using UPPER case only. Another thing to check is tx SLDAPICUST. There is a problem in this transaction (I think it is a problem, maybe it's a feature , you need to use password with UPPER there to, and you need to double save the data there (change something, click save, change another thing, click save, and will work, otherwise not). Check tx SLDCHECK to see if connection with SLD and Integration Directory are ok.

Regards.

Roberti

[Former Member]

Hi,

have it worked?

regards.

roberti