Need help connecting new portal system to existing SLD

[Former Member]

My hardware outsourcer has just built my first portal system and I now need to connect it to my existing SLD so I can configure the JCo RFC destinations for my new BI environment.

I have configured the SLD and I have managed to get the portal to register itself in the SLD but when I go to the WebDynpro->Content Administrator iView I get an error message saying "Connection to System Landscape Directory (SLD) could not be opened successfully.".

The "Check SLD" button pops up a dialogue box which shows the portal's own host name, the real SLD's port number, the portal's Java admin userid and the portal's internal SLD's URL so something is a bit confused.

Where/how do I configure this system to know where the SLD really lives?

The outsourcer did not import any SLD roles into the portal system when built (we don't want to run the SLD here) but this means that I cannot start the SLD locally to test anything.

[Former Member]

Regards.

[Former Member]

Thank you for this link. I'll need to do more research into the content there but at a first glance I seem to have done what's necessary. From my portal system I can send configuration updates to the SLD so the portal can describe itself to the SLD and the portal is now a registered system in the SLD.

The problem I have is that the WebDynpro iView has the wrong information about the location of the SLD. This iView thinks that the portal host is the SLD host which is not true. Even more confusing is the fact that this iView knows the CORRECT port for the SLD and, since the SLD and the portal have different instance numbers, this configuration is technically inconsistent.

Let's call my portal "PRT", instance 10, and my SLD "SLD", instance 20.

The iView in PRT should try to reach SLDhost on port 52000 via url http://SLDhost:52000/sld if my configuration was correct. It actually tries to reach PRThost on port 52000 (not 51000!) via url http://PRThost:52000/sld. So, somewhere, I've managed to store the SLD's port correctly but I've got the hostname and instance wrong.

[Former Member]

Try to check in VA --> SLD DATA SUPPLIER. Regards.

[Former Member]

Thanks again for the pointers. I had been to SLD data supplier and there the upload of data to the SLD was successfully completed. This is how I knew I had no firewall or other "technological" issue.

I managed to track down a contact at SAP and he suggested that I should be looking at the CIM content part of the SLD data supplier - here I found the wrong host name and userid but the correct SLD port specified (my fault). Correcting that information made all the difference.