cancel
Showing results for 
Search instead for 
Did you mean: 

PI 7.11 - Import from SLD

michael_buchli
Participant
0 Kudos

Hi experts,

We installed our new PI 7.11 with a local SLD. Afterwards, we decided to use the "old" central one. So our basis guys changed the settings. On the tool page in the browser (sxmb_ifr) the right SLD starts and I can log on.

If I try to import SC in the ESB i get following error:

Could not read list of software component versions from SLD

Details (STOP): Could not read list of software component versions

from SLD (COULD_NOT_READ_SWCV)

Details (!): User credentials are invalid or user is denied access

Because i can log on to the SLD, I don't think that the problem is on the SLD itself.

Now, we don't know:

a) Is the are setting/configuration we missed during reconfiguration of the "old" SLD?

b) Do I need a special user role to do this?

Thanks in advance

Michael

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi again,

In regard of the "Could not read list of software component versions from SLD", follow:

Firstly, add additional security roles to the following users

PIRWBUSER, PISUPER, PIISUSER and PIAFUSER in the central SLD. Also

assign applications roles to user groups in the Central SLD.

Check the note: #999962 - PI 7.10: Change passwords of PI service users

Please ensure the following AII properties in the PI Exchange Profile

are pointing at the correct SLD host:

com.sap.aii.connect.cr.httpport xxxxxx

com.sap.aii.connect.cr.name xxxx

com.sap.aii.connect.landscape.httpport xxxxxx

com.sap.aii.connect.landscape.name xxxx

Please make sure the following parameter are configured

correctly in exchange profile:

com.sap.aii.repository.serviceuser.name

com.sap.aii.repository.serviceuser.pwd

Please make ensure PIREPUSER is defined as a service user in SU01

and has the following roles assigned for SLD communication:

SAP_SLD_CONFIGURATOR

SAP_SLD_DEVELOPER

SAP_SLD_ORGANIZER

Please also take a look at the attached notes:

#939592 - PI Usage Configuration versus Central SLD

#720717 - Reduce the number of System Landscape Directories (SLD)

#764176 - Error in XI due to inconsistent SLD contents

I think all of that will solve your issue

Regards,

Caio Cagnani

Answers (3)

Answers (3)

michael_buchli
Participant
0 Kudos

The cause of the problem was our "old" central SLD.

0 Kudos

Hello Michael,

Check note: #1152640 - SAP NetWeaver 7.1 including EHP 1: Importing ESR content

Also, if you face problems in importing from an old system, check:

#1141862 - Message Mapping loses imports after upgrade to PI 7.10

With regards,

Caio Cagnani

stuart_campbell
Active Contributor
0 Kudos

Hi Michael

All J2EE installations may automatically come with an installed or installable SLD service

That is all J2EEs could potentially be an SLD

Technically you can call any SLD a central SLD - however technically the central SLD concept is an SLD that contains ALL systems (not just PI systems) for Solution Manager useage and we do not recommend having a dual purpose SLD

- that is a central SLD used by PI AND Solution Manager - PI should always have a dedicated SLD for runtime purposes

which certainly can be synchronized or integrated with othe SLDs in the landscape

As I see to set up any SLD following the guidelines at

- for PI there may be specific considerations like ensuring all PI and PI interfaces point to the required SLD and

all relevant data supplier connections point to and are visible in the required SLD and all business systems are maintained correctly for use in the required SLD

Hope this helps

Stuart