XI unable to access SLD

[hasanajsh]

Hi experts,

In the managed system (ABAP), the Solman User (SM_<solman_sid>) is getting the following log message:

XI unable to access SLD: "Unable_to_determine_SLD_access_data"

SL XI5

____________________________________________________

XI unable to access SLD: "&A"

In the function module LCR_GET_OWN_BUSINESS_SYSTEM, the attempt to read XI data from the System Landscape Directory has failed. If the data is still in the local cache, XI can continue to use it.

Check whether the System Landscape Directory is operational and whether the communication connection is configured correctly. For more information, see the SAP Exchange Infrastructure installation and configuration guide.

I found this note, but it is not released.

1655229

XI runtime: LCR_GET_OWN_BUSINESS_SYSTEM w/o SLD access

Kindly asking your suggestions on this.

Thanks and regards...

[former_member45419 · Accepted solution]

HI Shk,

pls refer below links,

Regards

Nayeem

[hasanajsh · Accepted solution]

Hi khaja,

Thanks for the links.

SLDCHECK shows that RFC destinations SAPSLDAPI and LCRSAPRFC do not exist.

My question now is: what is the use of those and at what point of Configuration were those RFC destinations supposed to be created.

Regards

[Former Member · Accepted solution]

Hi

RFC are used to communicate to IB (Integration Builder) related to Proxy Genrations, following information is available at exchange profile.

SAPSLDAPI and LCRSAPRFC are created in the BS(Business System).

Below is for further quick readings & learning.

Connecting to the System Landscape Directory

You only require a connection to the System Landscape Directory (SLD) when you use the ABAP proxy generation or runtime.

Business systems with an Integration Engine require a connection to the SLD server to obtain their name from the SLD. The business system name is used in the header of the message sent to the Integration Server. The connection to the SLD is established by creating an RFC destination (as described below) and calling a registered server program (which is defined on the J2EE RFC engine of the Integration Server). The server program is called with the HTTP address as a parameter that is maintained with transaction SLDAPICUST.

For security reasons, you can also secure your SLD connection with HTTPS. For more information, see SAP Note 766215.

You have to use transaction SLDAPICUST in the business system to define the SLD access data. This data consists of the host and port of the SLD as well as a user and password (PIAPPLUSER, for example). You can use the entries that you maintained on your Integration Server.

The RFC destinations LCRSAPRFC and SAPSLDAPI are used for the SLD connection. They use the SLD access data maintained with transaction SLDAPICUST. The RFC destination LCRSAPRFC is used to read the exchange profile; SAPSLDAPI is used by the ABAP API.

The RFC destinations are also used to retrieve the information about where to find the Integration Builder required for the proxy generation. This information is located in the exchange profile.

You have to create both RFC destinations in your business system. They use the same registered server program, which is defined as part of the RFC engine settings of the J2EE Engine on the Integration Server host. This means that all business systems can use the same server program for their RFC destinations LCRSAPRFC and SAPSLDAPI. This program ID is:

●      SAPSLDAPI_UNICODE for Unicode business systems

●      SAPSLDAPI_NONUNICODE for non-Unicode business systems

[Former Member]

Has your problem been resolved yet?