SLD connection parameters for a central SLD

SLD connection parameters for a central SLD

I know there are arguments for and against one or multiple SLD's but this is not the purpose of this blog... What ever your personal views are I respect that. what I want to show in this blog is what needs to be configured and what needs to be pointing where in the situation where you decide to have only one central SLD. I have seen resume posts on the forums relating to this issue and I hope to be able to help with this blog.

It is often the case that when embarking upon an XI/PI project you start off by installing your development instance and then after some time you install your QA and production instances, once you finally install your production instance you want all of the other instances to use the same SLD so essential you want to configure Dev and QA to point to prod SLD. well the parameters below outline the configuration needed to set up a central SLD in your landscape and what needs to point where.

* ** Please note the part about the central systems exchange profile is only applicable if you are using solman to house your central SLD ***

Process Integration Parameters

Sm59

• Ai_directory_jcoserver-points to the RFC provider in the PI visual Admin
• Ai_runtime_jcoserver-points to the RFC provider in the PI visual Admin
• Lcrsaprfc-points to the RFC provider in the PI visual Admin
• Sapsldapi-points to the RFC provider in the central system visual Admin

Sldapicust

• Contains the parameters for the central system

Exchange Profile

Under the Connections tab the following shocould be true
 

• Cr name and httport-parameters for the central system
• Landscape name and httpport-parameters for the central system

Visual Administrator

Jco RFC provider

• Only the sapsldapi RFC shoshould contain the parameters for the central system including program id

SLD data supplier

• Both HTTP and CIM settings shocould be pointing to the central SLD

 
Central System Parameters

Sm59

• Lcrsaprfc-points to the RFC provider in the central system visual Admin
• Sapsldapi-points to the RFC provider in the central system visual Admin

Sldapicust

• Contains the parameters for the central system

Exchange Profile

The connection shoshould be to the Pi exchange profile and not the central system

Visual Administrator

SLD data supplier

• Both HTTP and CIM settings shocould be pointing to the central SLD
• Assign roles to the user group to allow access to the SLD

Parameters in the SLD

The technical systems for both the pi system and central system shoshould contain their relevant products e.g. Pi shoshould have NetWeaver 2004 S and SAP exchange infrastructure 3.0 products installed.

The Business System for pi shoshould be defined as an Integration Server and contain the following pipleline URL: http: //

A business system for the central system also needs to be defined and have the role of an application system.

Use sxmb_adm à integration engine configuration to ensure that the relevant parameters are imported from the SLD. You can do this by Edit --> global configuration data --> system landscape.

Users and Roles

Ensure that both systems contain all of the PI users along with the SLD users and all of the correct roles are assigned (generally all users from Pi need to be replicated into the central system) and the passwords are exactly the same.

Useful notes

Please also see the below notes for useful insights and more of an overview.

764176
720717
939592