on 10-20-2008 3:09 AM
Hi Friends,
I was woking on the Abap Proxy scenerio ( Server Type). I was going through the link
I hav still not started, but I hav a question.
I cannnot see the Software components and name spaces of the Integration Repository in the SPROXY transaction in my R/3 system. As per the URL
, Design Time - point No 2 , can any 1 tell me which/ which all specific settings enable the availability of the software components and name spaces to be availabe in the SPROXY transaction of the R/3 server!
Regards,
Arnab
Will come back with more relevant queries!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sarvesh,
i hav folwed the URL
at the very begining. All the 3 RFC connections are working fine, I donno why is it still not working .
SXMb_ADM settings done .... !
Gaurav Bhargava ,
I am using PISUPER id and its has super access, i hope this wont be a problem, as it is far more
authoriesd trhan XIAPPLUSER.
REGARDS,
Arnab
Hi,
see i cannot change the SCV now, as implementation is already done, is it mandatory...are you sure, because, in a different project, the vendor name as well as SCV is SAP.COm, but still is working,.....and see, my scenerio is ABAP Clent proxy, and in the R/3 system, SPROXY transaction -->GO TO --> Connection test , I get the following :
Check List for Setting Up a Connection to the Integr
1. The address of the Integration Builder must be stored in teh
system
=>Check/maintain with report SPROX_CHECK_IFR -- Tested positiev except for that fact taht SPROXSET table is empty?? but is it mandatory??
The address is taken from the following para
profile ('Connections' section):
com.sap.aii.connect.repository.name: Server
com.sap.aii.connect.repository.httpport: Por
com.sap.aii.connect.repository.contextroot:
The logon data is also read from the exchang
('ApplicationSystem' section):
com.sap.aii.applicationsystem.serviceuser.na
com.sap.aii.applicationsystem.serviceuser.pw
If no address is found, then an HTTP destina
table SPROXSET, which already contains these
information:
Column NAME: "IFR_HTTP_DEST"
Column VALUE: for example, "MY_DESTINATION"
The destination must have been created using transaction SM59.
For the repository URL "http://myserver:4711/rep", for example, the
following values must be maintained:
Connection type: "G" Target host:"myserver" Service No:"4711" Path
prefix: "/rep"
User and password accordingly.
If maintained, the settings from the exchange profile are always
used. If you want to deviate from this and only take the address
from the table SPROXSET, you must enter ADDRESS_ONLY_FROM_SPROXSET =
"X".
2. The HTTP connection of the ERP application server must
correctly
=>Check with report SPROX_CHECK_HTTP_COMMUNICATION
If necessary, contact your system administrator. The H
the ERP application server may be configured incorrect
Alternatively, you can log on to another application s
system where the HTTP port is functioning correctly. I hav made this -- tested OKK
3. The Integration Builder server must be running c
=>Check with report SPROX_CHECK_IFR_RESPONSE
(This link should display a valid XML document,
with 'Page Not Found', 'Internal Server Error 50
If necessary, contact your system administrator,
Integration Repository server, or import the cor
release. ok.. showing all the IR software component version names in XML Pls note this is important, indicating, some kind of coonetivity HAS occured !!
4. Proxy generation must interpret the data of the
correctly
==>Check with report SPROX_CHECK_IFR_CONNECTION -- OKK
Pls suggest something!
Regards,
Arnab !
Hi Arnab,
U need to connection between the XI & R/3 systems. Once its HTTP & RFC connections is their its showing the SPROXY.
Regards,
Sateesh N.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
1. Plz check SAPSLDAPI and LCRSAPRFC RFC destination on R3.
2. Check data transaction SLDAPICUST is maintain correctly for sld.
3. Also check whether attached integration server is maintain in transaction SXMB_ADM. If not then maintain it. If not then maintain is under category Runtime, Parameter IS_URL and then the put URL for integration server in default value.
If those things are fine then run SLDCHECK transaction in R3 it should logon to the sld of XI.
Regards,
Sami.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Arnab,
Check this
https://websmp202.sap-ag.de/~sapidb/012006153200000920262007E/Readiness_Check_Version4.pdf
Market place ID required to access.
Regards,
Sachin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
first establish the RFC connections http/tcpip, from XI to R/3 and R/3 to XI
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
On running the transaction SLDCHECK, in my R/3 system, I am hetting this error.
Summary: Connection to SLD does not work
=> Check SLD function and configurations.
When testing the connection for SAPISU_XID, I am getting the error as
ICM_HTTP_Connection_Failed .
When, in my r/ I go to the SXMB_ADM - Integration Engine Configuration data and try for System Landscape - Load Configuration -- I get the messege "
No Access To system landscape at present!"
Any feeds!
Regards,
Arnab !
Edited by: Arnab Mondal on Oct 20, 2008 7:19 AM
HI
Check with the PIAPPLUSER and PIISUSER authentication. These need to have basic SLD access authorization
Follow this thread you can get more steps
Old troubleshooting guide which always helps
Thanks
Gaurav
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.