on 07-16-2007 1:32 PM
Hi
Can anybody list down the steps that need to be configured (in XI and R/3) system for executing ABAP <b>server proxies</b>?????
specifically, i am looking for steps that would connect XI with R/3 . There are a few issues we are facing during runtime in sxmb_moni.
it would also be helpful if someone can give a technical description of the ABAP server proxy runtime.
Note:I have seen the blogs that describe how to create ABAP server proxies
Thanks and regardsk
krishna
Hi,
>>>specifically, i am looking for steps that would connect XI with R/3
noting more than here needs to be done:
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
>>>>it would also be helpful if someone can give a technical description of the ABAP server proxy runtime.
what exactly would you like to know ?
Regards,
michal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
michal
But that blog is about activating ABAP proxies but my problem is i can in fact create and activate abap server proxy but having problems during runtime, due to the config in the XI adapter.
In sxmb_moni, we get a runtime error as
"System not configured as XI Integration Engine"
What would you think will be the cause of this problem?
regards
krishna
hi Jai
In XI , under sxmb_adm , the value for
Role of business System is : <b>Integration server </b>
and the value for Corresponding Integration Server is the value that is defined in SLD for the XI business system.
In R/3, under sxmb_adm , the value for
Role of business System is : A<b>pplication System</b>
Here , we are not able to pull the value for Integration Server due to the following error
No access to system landscape present.
In R/3, the sldcheck fails with the error
<b>"No business system maintained in SLD</b>" but if i check in SLD, there exists a Business system.
Regards
krishna
Hi,
>>>In R/3, the sldcheck fails with the error
"No business system maintained in SLD" but if i check in SLD, there exists a Business system.
so you didn't do the weblog for proxy activation...
SLDcheck has to work
at first make sure SLD check works on R3 and then try the proxy
Regards,
michal
Hi michal
>>>you jut have to fill SXMB_ADM - integration engine
In R/3 isnt it going to be "Application System" for the Role of Business System??
also, the faQ that you have mentioned is about
""Connecting Business Systems with an Integration Engine to the Central Integration Server" "
But in the abap server proxy it is the reverse case. i.e XI (the central IS) is trying to establish connection with IE on the Business system of R/3 right??
Can you please clarify?
regards
krishna
Hi
I have created the http destination of Type H in r/3 system, but it is giving reponse as "Empty Http Request Received" when i test the connection
Regards
krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi henrique
thanks 4 ur response
Did you create RFC Destinations for SLD JCo Providers in R/3?
Yes
Are you maintaining SLD connection data in SLDAPICUST?
Yes
Did you execute RZ70 in R/3?
Is it required? this is not mentioned in the blog to activate abap proxies. Also how would i execute RZ70 and what needs to be executed?
thanks
krishna
Hi
I just checked that SLDCHECK invokes the URL of SLD with the host name of the ERP ssystem like
http:erp:50000/sld
instead of
why is this so?
i have checked sapsldapi rfc destination in R/3 and also the http connection of type H.
regards
krishana
HI
I have fixed the issue. It was config on sldapicust, which was pointing to r/3 system
now. i get an error for sldcheck as follows
"Connection to SLD does not work"
whereas the LOGIN screen for sld comed up in the browser.
Do you think sldcheck would automatically login to sld?
is is the reason for the error?
regards
krishna
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.