XI/PI 7.10: Using central SLD instead of local one

[Former Member]

Dear all,

For one of our customers we have installed XI/PI 7.10 using central SLD (on one of their existing systems) rather than a local one. Now, we ran into much trouble trying to configure it. We did change quite a few configuration parameters to redirect it to remote SLD, but it still doesn't work as supposed to.

Just a few examples:

1. Error during communication with SLD: User credentials are invalid or user is denied access (we checked a lot of notes which generally refers to user being locked - which is NOT the case);

2. Under 'Technical Landscape' in the (remote) SLD, in the "Exchange Infrastructure" we find only "Integration Server" logged on correctly. All others (Adapter Engine, Integration Directory, Integration Repository, The Adapter Engine,...) components are missing. We tried registration of the Adapter Engine as described in Note 1031321, with no avail...

We would really like to preserve the central SLD over local ones (we plan to install other ERP/BW systems as well).

Can anyone, please, point us in the right direction to enable our XI/PI system to work with the remote SLD?

Thank you all in advance!

Regards,

Miroslav

[Former Member · Accepted solution]

Hi Miroslav.

Follow this note. Sorry, I don't have the numeber note but the text.

I faced the same problem some time ago and basically you have to duplicate PI service users in the

system where the SLD is allocated.

Other settings are also needed.

Hope this helps you.

Carlos

Symptom 

You want to use an XI 3.0/7.0 or 7.10 system with an SLD that runs on a separate server on which no XI/PI is installed. You must make some additional settings in this case.



Reason and Prerequisites 

Enter the settings for the connection of an SLD using the XI/PI Post Installation Steps. If the SLD runs on a non-XI/PI system, an additional step is required.
Since the XI/PI system components have different users to access the SLD, these XI/PI users with the password that is maintained in the exchange profiles of the XI/PI must also be known in the system on which the SLD runs.

Solution 

The procedure for the creation of the users differs depending on which Release you are using, how the SLD is installed and which user store the SLD uses.


Procedure for XI3.0/XI7.0 

You have installed the SLD on a WEB AS with an ABAP part and are using the ABAP as a user store. 

Log onto the system on which the SLD runs and call transaction SU01.

Create the user, which exists in the XI/PI system with the role SAP_XI_IR_SERV_USER (after a default installation, this is XIREPUSER/PIREPUSER), as service user with the role SAP_XI_IR_SERV_USER and set the password, which is also used in the XI/PI system.

Create the user, which exists in the XI/PI system with the role SAP_XI_ID_SERV_USER (after a default installation, this is XIDIRUSER/PIDIRUSER), as service user with the role SAP_XI_ID_SERV_USER and set the password, which is also used in the XI/PI system.

Create the user, which exists in the XI/PI system with the role SAP_XI_IS_SERV_USER_MAIN (after a default installation, this is XIISUSER/PIISUSER), as service user with the role SAP_XI_IS_SERV_USER_MAIN and set the password, which is also used in the XI/PI system.

Create the user, which exists in the XI/PI system with the role SAP_XI_RWB_SERV_USER_MAIN (after a default installation, this is XIRWBUSER/PIRWBUSER), as service user with the role SAP_XI_RWB_SERV_USER_MAIN and set the password, which is also used in the XI/PI system.

Create the user, which exists in the XI/PI system with the role SAP_XI_AF_SERV_USER_MAIN (after a default installation, this is XIAFUSER/PIAFUSER), as service user with the role SAP_XI_AF_SERV_USER_MAIN and set the password, which is also used in the XI/PI system.

Create the user, which exists in the XI/PI system with the role SAP_BC_AI_LANDSCAPE_DB_RFC (after a default installation, this is XILDUSER/PILDUSER), as service user with the role SAP_BC_AI_LANDSCAPE_DB_RFC and set the password, which is also used in the XI/PI system.

Create the user with which you want to log onto SLD (for example XISUPER/PISUPER), with the role SAP_SLD_ADMINISTRATOR as a dialog user and set the password that you want to use for logging on.

Start the J2EE engine to update the user role assignment in the J2EE.

Log on to Visual Admin of the SLD J2EE and open the 'SLD Data Supplier' service under the 'Server' node. Choose the 'Assign application roles to user groups' button. The correct roles are then assigned.


NOTA 939592

Steps on Integration Server System (IS) (only required if you install SAP NetWeaver 7.00 Service Release 1) 
Start ABAP transaction "Configuration of RFC Connections" (SM59) and maintain in the TCP/IP connections LCRSAPRFC and AI_RUNTIME_JCOSERVER the Integration Server's Gateway Host and Gateway Service. Save and execute the 'connection test'. Note: These connections point to the Integration Server, not to the SLD. You find their counterparts (registered server program IDs) in the Visual Administrator's JCo RFC Provider service.

Note: AI_DIRECTORY_JCOSERVER is not used in NW2004s.
Start the Exchange Profile http://<IS_host>:<port>/exchangeProfile and logon with PISUPER user. The following connections must point to the central SLD system:
com.sap.aii.connect.cr.name,
com.sap.aii.connect.cr.httpport
com.sap.aii.connect.cr.httpsport
com.sap.aii.connect.landscape.name, com.sap.aii.connect.landscape.httpport com.sap.aii.connect.landscape.httpsport
Trigger a full cache refresh. To do this call the URL
http://<IS_host>:<port>/CPACache/refresh?mode=full
with user PIDIRUSER (only this user has the required permission). After that restart the CPA Cache Service. This triggers the self registration of the Adapter Engine in the central SLD. Logon to the central SLD and check this.
Steps on the Central Adapter Engine 
Restart the central J2EE Engine to trigger the Adapter Engine's and Tools self registration again.

Check: Logon to the central SLD and check if the registration was executed successfully.

[Former Member]

Hi Carlos,

Thank you very much for the effort. We found that note (768148 - Using a separate SLD for XI) earlier but that didn't help either...

As it looks now, we'll probably reinstall the PI and go with it's local SLD...