cancel
Showing results for 
Search instead for 
Did you mean: 

outbound proxy acknowledgment user

michel_dekimpe
Participant
0 Kudos

hello,

we have the following scenario

async. outbound proxy -> file adapter

this works correctly but the acknowledgment that we would like to receive uses an unexisting user

and returns following error "HTTP 401 - Unauthorized"

anybody knows were to adjust this user ?

we could create the user but we would like to know where to find it

thanks

regards,

michel

Accepted Solutions (1)

Accepted Solutions (1)

stefan_grube
Active Contributor
0 Kudos

You have to define a receiver channel type XI and a generic receiver agreement for the ack message.

You put the user here.

Answers (1)

Answers (1)

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi,

check you have authorization to place files in file directory,may this could be the reason,

The user using communication chnale doesnot have proper rights.

Regards,

Raj

michel_dekimpe
Participant
0 Kudos

hello,

thanks for your reply but the file is put on the server correctly

that's not the problem, the problem is when the xi system tries to return the acknowledgment

then he uses a user which doesn't exist

like I said, we could create it but we would like to know where to change it

regards

Former Member
0 Kudos

Hi,

Is this 401 error raised by XI/PI ? If so, why not activating the HTTP logs so you can see which user and ICF service are being used when it occurs ?

Rgds

Chris

michel_dekimpe
Participant
0 Kudos

hello,

thanks for your reply Chris

where / how should we activate those logs ?

regards,

michel

Former Member
0 Kudos

HTTP logs have to be activated at instance profile level, ie :

icm/HTTP/logging_0 PREFIX=/,LOGFILE=devs_http.trc,MAXSIZEKB=50000, SWITCHTF=day,FILEWRAP=on

icm/HTTP/logging_client_0 PREFIX=/,LOGFILE=devc_http.trc,MAXSIZEKB=50000, SWITCHTF=day,FILEWRAP=on

and then restart the ICM (tcode SMICM and soft restart) ... Then, in SMICM, there is a HTTP logs menu that will display contents of these traces, you can often find user/url/rcode in it

But maybe Stefan's solution could solve your issue (I'm not familiar with ACKs )

Rgds

Chris