I already read most of the threads reg. this issue. Please let me know if i miss any point need to be checked. Any help reg. this will be appreciated.
Sorry for lengthy message reg. this.
ECC 6.0 and PI 7.3 systems
we have central SLD for PI DEV and PI QA.
ECC DEV --> PI DEV
ECC QA --> PI QA
in ECC DEV system sproxy is working fine and ECC QA and PIQ systems are newly built.
when I try to check sproxy in ECC QA system, it is not connecting ESR and it does not show PI QA content , it displays only local content
Solution which I attempted so far:
The address of the Integration Builder must be stored in the R/3 System
=>Check/maintain with report SPROX_CHECK_IFR_ADDRESS
The address is taken the from following parameters in the exchange profile (section 'connections'):
The HTTP connection of the R/3 application server must function correctly
=>Check with report SPROX_CHECK_HTTP_COMMUNICATION
The Integration Builder server must be running correctly
=>Check with report SPROX_CHECK_IFR_RESPONSE
Message while running above report:
No connection to exchange profile or address-
logindata are missing
@5C\QError@ No connection to exchange profile or address-logindata are missing
@5C\QError@ Configuration for accessing ESR is incorrect:
Proxy generation must correctly interpret the data of the Integration Builder
- Output when we run the above report in ECC QA system:
Enterprise Services Builder data not understood
5) the address for the ESR is taken from the exchange profile
6) Checked this entry also
SAPAPICUST - Connection to SLD in ECC system
alias name : PID
Host name:PID hostname: xxxpid.xxx.com
and test is working fine
7) checked these RFC connections
SAPSLDAPI - Functionality for SLD in ECC system
Program id: SAPSLDAPI_PIQ
Gateway host: PID host name (Example: xxxpid.xxx.com)
Gateway service: tcsapgwxx
LCRSAPRFC - Get Exchange Profile data -
Program id: LCRSAPRFC_PID
Gateway host: PIQ host name (Example: xxxpiq.xxx.com
Gateway service: tcsapgwxx
8) Checked this one also in ECC system
SXMB_ADM - IE config and IS_URL and HTTP connection to PI also
9) RZ70 - checked this also
10) SLDCHECK tcode is working fine in ECC
I have doubt that I may missed some thing on point 11 or made any mistake on these ones, Plz let me know if i have to check any specific things.
11) PI QA system
- Checked all Destinations in PI NWA ie PI Java side
- Checked exchange profile parameters for in PI QA system for connections to SLD
- checked Jco RFC Provider also
- sproxy is working fine in PI QA system.
12) Compared all SP levels between ECC DEV and ECC QA systems also. - Looks OK
whether SLDAPICUST alias name should be same in PI QA and ECC QA systems?
Thanks in advance.