What's LCRSAPRFC/INTEGRATION_DIRECTORY_HMI's functionality?

[Former Member]

Hi!

Please help. Thanks! Points guaranteed.

[Former Member]

HI,

<b>AI_DIRECTORY_JCOSERVER</b> from the Integration Server to the Integration Builder. The program ID corresponds to the entry under JCo RFC provider for the SAP J2EE Engine (used for refreshing the runtime cache).

<b> AI_RUNTIME_JCOSERVER</b> from the Integration Server to the mapping runtime. The program ID corresponds to the entry under JCo RFC provider for the SAP J2EE Engine (used for the mapping runtime, value mapping, and the exchange profile).

<b>INTEGRATION_DIRECTORY_HMI</b> of type HTTP, used for the cache update.

&#56256;&#56443; Path prefix /dir/CacheRefresh

&#56256;&#56443; HTTP 1.0

&#56256;&#56443; Accept Cookies: Yes (All)

Always use user XIISUSER.

The RFC destinations <b>LCRSAPRFC</b> and <b>SAPSLDAPI</b> 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 XI 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 SAP J2EE Engine on the Integration Server host. This means that all business systems can use the same server program ID (SAPSLDAPI _UNICODE or SAPSLDAPI _NONUNICODE) for their RFC destinations LCRSAPRFC and SAPSLDAPI.

In the case of Unicode business systems (program ID SAPSLDAPI UNICODE), the Unicode flag is set in the RFC engine settings. In the case of non-Unicode business systems (program ID SAPSLDAPINONUNICODE), the Unicode flag is deactivated.

Thanks,

Tanuj