sxmb_ifr on PI leads to http://<host>:<port>/sap/public/myssocntl?sap-client=001

[monika_eggers]

When I call transaction sxmb_ifr on my PI system I expect http://<host>:<port>/dir to open, but instead http://<host>:<port>/sap/public/myssocntl?sap-client=001 opens and says "Internet Explorer cannot display the webpage".

Opening http://<host>:<port>/dir manually works fine.

The Exchange Profile (http://<host>:<port>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp) seems to be okay, the fully qualified domain name is maintained for all relevant parameters:

com.sap.aii.ib.server.connect.webas.r3.ashost

com.sap.aii.rwb.server.centralmonitoring.name

com.sap.aii.rwb.server.centralmonitoring.r3.ashost

com.sap.aii.rwb.server.centralmonitoring.r3.mshost

com.sap.aii.connect.repository.name

com.sap.aii.connect.directory.name

com.sap.aii.connect.landscape.name

com.sap.aii.connect.rwb.name

com.sap.aii.connect.cr.name

com.sap.aii.connect.rwb.r3.mshost

com.sap.aii.connect.integrationserver.name

com.sap.aii.connect.repository.mshost

com.sap.aii.connect.integrationserver.sld.name

com.sap.aii.connect.integrationserver.r3.mshost

com.sap.aii.connect.directory.mshost

The SAP instances have been restarted from the SAP console after updating the Exchange Profile. (Is there an easier way to make the system re-read the Exchange Profile?)

Transaction sicf shows that /sap/public/myssocntl is active.

SLDCHECK runs fine.

Another suggestion I found was creating destination SAP_PROXY_ESR, however it appears this should only be done in the connected business systems, but not in the PI system. In sproxy on the PI system the ESR contents are loaded fine (no error message that only offline data is available), so this seems to confirm this information.

What else could be causing this? I found a lot of threads on the topic, but in the end they all seemed to amount to one of the above problems, mostly the exchange profile (and in business systems destination SAP_PROXY_ESR missing).

[Harish · Accepted solution]

Hi Monika,

Please check Michal's reply in below discussion

'com.sap.aii.connect.integrationbuilder.startpage.url' has the value 'dir/start/index.jsp'

regards,

Harish

[monika_eggers · Accepted solution]

That parameter is also okay.

[Harish · Accepted solution]

Hi Monika,

The Similar problem is discussed in the below thread

Please also check the RFC destination LCRSAPRFC and SAPSLDAPI.

regards,

Harish

[monika_eggers · Accepted solution]

Those destination are used for the SLD connection. As I mentioned SLDCHECK works fine. I have also tested the destinations, they don't give an error message.

[Harish · Accepted solution]

Hi Monika,

Can you please check the discussion which has the similar issue

Opening diff URL when i enter Tcode SXMB_IFR

• Start the SAP NetWeaver Administrator.
• Choose Operation Management -> Systems -> Start & Stop Java EE Applications .
• To trigger the SLD self-registration of the Integration Directory, stop and restart the application com.sap.xi.directory
• After you have restarted the application, call the URL http://<host>:<port>/dir/start/index.jsp with PI-User.
• Wait for 10 seconds to allow the SLD to do the work.
• To trigger the SLD self-registration of the Enterprise Services Repository, stop and restart the application com.sap.xi.repository
• After you have restarted the application, call the URL http://<host>:<port>/rep/start/index.jsp with PI-User.
• Wait for 10 seconds to allow the SLD to do the work.
• To trigger the SLD self-registration of the Runtime Workbench, stop and restart the application com.sap.xi.rwb
• To trigger the SLD self-registration of the Advanced Adapter Engine, stop and restart the application com.sap.aai.af.app
• Apply note 1117249 if relevant
• Restart com.sap.xi.directory again.

[monika_eggers · Accepted solution]

It was a problem with the destination SAPSLDAPI after all! It didn't give an error during test and the SLDCHECK ran fine, but this destination was still not okay - the gateway host that was entered was wrong!

Thank you!