cancel
Showing results for 
Search instead for 
Did you mean: 

Access to SLD from ABAP fails

Former Member
0 Kudos

Hello,

we have moved our Solution Manager SMP to another Hardware therefore

the hostname has changed to dszsmp. But internally the hostname is the

same as before, the SAP system runs with the hostname sm1 but the

system can be reached from outside with the hostname dszsmp.

This is the entry of /etc/host in the system:

10.100.137.138 sm1 sm1.hydac.com dszsmp dszsmp.hydac.int

I maintained the new hostname in the JAVA Engine in the JCO RFC

Destination of the Visual Administrator correctly to dszsmp according

to the document Access to SLD from ABAP fails - Transaction SLDCHECK

reports error. The JAVA Engine of the system SMP is running correctly.

After Executing the transacting SLDCHECK the following Error occurs:

Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server...

Function call terminated sucessfully

No business systems maintained in the SLD

=> Check data integrity within the SLD!

Summary: Connection to SLD works technically, but the SLD content may

need maintenance

=> Check and maintain the SLD data content

This is the complete Output of the transaction SLDCHECK:

Exchange Infrastructure: Test der LCR-Anbindung

Properties of RFC destination SAPSLDAPI

RFC host:

%%RFCSERVER%%

program id: SAPSLDAPI_UNICODE

gateway host:

dszsmp

gateway service: sapgw00

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

RFC ping was successful

SLD server access settings:

host name: dszsmp

port number: 50000

user : SLDDS_SM

Use transaction SLDAPICUST if you wish to maintain the SLD server

access data

Launching the SLD GUI in a separate browser window...

=> Verify in the browser GUI that the SLD is in a healthy running state!

Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server...

Function call terminated sucessfully

No business systems maintained in the SLD

=> Check data integrity within the SLD!

Summary: Connection to SLD works technically, but the SLD content may

need maintenance

=> Check and maintain the SLD data content

At the moment it is not possible to Create New Maintenance Transaction.

What can be done to make SLDCHECK work correctly.

Kind Regards

Hartwig Latz

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Hartwig,

A couple of things:

1. the SAPSID or SID remains the same (SM1)

2. the hostname has changed

3. Try transaction SLDAPICUST to set the new hostname for the SLD connection.

4. in visual admin, there are 4 JCo connections you need to change and restart

5. set RZ70 for the new hostname

All systems which send data to the SolMan will now need to have RZ70 changed to point to the new hostname .

See if that helps.

regards,

Graham

Former Member
0 Kudos

Hello Graham,

1.) Yes the system ID is the same as before

2.) the hostname has changed from sm1 to dszsmp

3.) I set in SLDAPICUST already the new hostname

4.) I set in Visual Admin 2 JCO:

     LCRSAPRFC_UNICODE and SAPSLDAPI_UNICODE

  which are the two other Destinations ?

I set in RZ70 the new hostname in all Destinations

At the moment the error still occurs.

Kind Regards

Hartwig

Answers (0)