cancel
Showing results for 
Search instead for 
Did you mean: 

Connection to SLD does not work

Former Member
0 Kudos

Hi All

In transaction SLDCHECK we are getting the following message so can somebody help us in figurin out what the problem is.

-


Exchange Infrastructure: Test LCR Connection

Properties of RFC destination SAPSLDAPI

RFC host: %%RFCSERVER%%

program id: SAPSLDAPI_XX3

gateway host: sxxxxx.aaa.bbb.ccc

gateway service: sapgw03

Testing the RFC connection to the SLD java client...

RFC ping returned exception with message:

Error opening an RFC connection.

Summary: Connection to SLD does not work

=> Check SLD function and configurations

Now checking access to the XI Profile

Properties of RFC destination LCRSAPRFC

RFC host: %%RFCSERVER%%

program id: LCRSAPRFC_XX3

gateway host: sxxxxx.aaa.bbb.ccc

gateway service: sapgw03

Testing the RFC connection to the SLD java client...

RFC ping returned exception with message:

Error opening an RFC connection.

-


Suresh

Accepted Solutions (0)

Answers (7)

Answers (7)

0 Kudos

I had the same issue.

It resolved when I used the role SAP_SLD_CONFIGURATOR while configuring SLDAPICUST.

Maintained HTTP parameters as below:

Alias - SAP_CONFIG

Host Name - PI Host(Depends on how you configure your central SLD ours was PI)

Port -PI port

User - SLD_CL_SID(With above mentioned role.)

As said in above threads below RFC destinations of type T needs to be maintained.

SAPSLDAPI with registred program SAPSLDAPI_SID

LCRSAPRFC with registered program LCRSAPRFC_SID

sunilchandra007
Active Contributor
0 Kudos

Hi,

Go thru this blog . It might help you.

SLD Connection Parameters for a Central SLD

Access To SLD From ABAP Fails

http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm

Regards,

Chandra

former_member238007
Contributor
0 Kudos

HI..

Previously SAP prefers to have the common SLD for all landscapes, but as per today's business requirments there is need to go for seperate SLD for development, Quality & Prod.

It completely depends if the Integration of the various applications or Business are based on various landscapes.

For .eg If in case the Sender and recevier applications are same for dev, Quality, Prod. XI servers then its better to have common SLD, but the sender and receivers systems are seperate for dev, pord etc. then it becomes very vauge to maintain all landscape in common SLD. rather maintaining seperate SLDs could help to channelaize it in well organized way.

You go through this Disscussion

Configuration of CMS in Central NWDI & SLD to transport XI objects:

Refer the configuring group and transport group for Business systems.

http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/frameset.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b01876ac-abbb-2a10-788e-95a7c5a5...

regards,

kishore

Former Member
0 Kudos

check the RFC destination is working properly or not

SAPSLDAPI

LCRSAPRFC

Former Member
0 Kudos
Former Member
0 Kudos

hi

check whether the program ids which are specified in the RFC destinations lcrsaprfc , sapsldapi corresponds to the program ids which are maintained in the RFC engine settings in the visual administrator

regards

kummari

Former Member
0 Kudos

Hi, Suresh.

It seems that your RFC settings have some problems. Especially, SAPSLDAPI and LCRSAPRFC in transaction SM59.

Please check with "Test Connection" button for the above connection settings in SM59 whether your settings are correct.

And in the special options tab, don't forget to check Unicode option.

Hope this helps.

Former Member
0 Kudos

Hi Sejoon,

I am also facin the same problem and I have checked the test connection but it is not working. please guide me on the problem.

Regards,

Nitin Patil