7/31/2019 Activate Local SLD
1/19
SAP System Landscape Directory
Activate Local SLD
7/31/2019 Activate Local SLD
2/19
- 1 -
TABLE OF CONTENTS
1 INTRODUCTION ..................................................................................... 22 INSTALLATION....................................................................................... 32.1 Check the local SLD.................................................................................32.2 Provide SLD permissions..........................................................................3
2.2.1 Creation J2EE SLD Administrator. ................................................................ 32.2.2 Creation J2EE SLD Guest............................................................................4
2.3 Assign default user groups to J2EE security roles ........................................52.3.1 Assign the groups .....................................................................................52.3.2 Check the security roles Double-stack........................................................ 52.3.3 Check the security roles Single-stack J2EE.................................................. 7
3 LOCAL SLD SETUP .................................................................................. 93.1 Launch SLD............................................................................................93.2 Configure SLD ........................................................................................94 CHECK SLD SETUP ................................................................................ 134.1 Introduction. ........................................................................................134.2 Check SLD supplier should have been ok yet: ........................................134.3 Check SLD bridge forwarding..................................................................144.4 Check & Setup SLD Client ......................................................................15
7/31/2019 Activate Local SLD
3/19
- 2 -
1 Introduction
A local SLD can only be activated if a J2EE stack is available because it is part of it.During installation of the J2EE the local SLD can be activated immediately byselecting the flag for it:
In this example the local SLD activation has been skipped:
This document is provided to describe how to activate the local SLD in a later phase.
7/31/2019 Activate Local SLD
4/19
- 3 -
2 Installation.
2.1 Check the local SLD
Following errors will be produced if there is no local SLD:
2.2 Provide SLD permissions
Create at least the SLD Administrator role LcrAdministrator to setup the SLD.
More roles and how to set them up standard are described in the chapterConfiguring SLD Security Roles of the SLD Post-Installation Guide.
It is our intention to provide standard Roles & Groups for the portal for these
functions (separate project).
2.2.1 Creation J2EE SLD Administrator.
General information:
Single J2EE-stack: assign it to group administrators (standard LDAP groups haveto be created for this purpose) & user administrator:
7/31/2019 Activate Local SLD
5/19
- 4 -
Double stack assign it to group SAP_SLD_ADMINISTRATOR (R3 role)
Assign the correct action:
2.2.2 Creation J2EE SLD Guest.
Cuurently only created in double stack (to be finalized for J2EE-only when LDAPgroups have been defined):
General information:
Double stack
assign it to group SAP_SLD_GUEST (R3 role):
Assign the correct action:
7/31/2019 Activate Local SLD
6/19
- 5 -
2.3 Assign default user groups to J2EE security roles
2.3.1 Assign the groups
This is only required to assign the R3 ABAP roles (UME Groups) to the J2EE security
roles. The J2EE assignments are already done and therefore this action should not beexecuted on a single J2EE-stack.
Launch Visual Administrator and select service SLD Data Supplier. Execute Assign
application roles to user groups:
2.3.2 Check the security roles Double-stack
DataSupplierLD, LcrAdministrator, LcrClassWriter, LcrSupport:
7/31/2019 Activate Local SLD
7/19
- 6 -
Other security roles:
7/31/2019 Activate Local SLD
8/19
- 7 -
2.3.3 Check the security roles Single-stack J2EE
All roles except LcrUser:
7/31/2019 Activate Local SLD
9/19
- 8 -
LcrUser:
7/31/2019 Activate Local SLD
10/19
- 9 -
3 Local SLD Setup
3.1 Launch SLD
Use http://:/sld/ and login with SLD Administrator rights. Permissionerrors now have disappeared:
3.2 Configure SLD
Launch Initial Setup:
- Object server name: unique name
- Gateway Hostname/Port: only for ABAP where we use the gateway of the J2EEcentral instance
- Deselect Import Software Catalog will be done later
7/31/2019 Activate Local SLD
11/19
- 10 -
Start Initial Setup:
Check Log:
7/31/2019 Activate Local SLD
12/19
- 11 -
Check Details:
Import CR & CIM until last version. First Import initial CR content (can also be doneduring initial setup, but this takes time!!):
Na imports:
7/31/2019 Activate Local SLD
13/19
- 12 -
7/31/2019 Activate Local SLD
14/19
- 13 -
4 Check SLD Setup
4.1 Introduction.
Finally check and change the SLD setup so that it meets the Standard requirements(separate document). By default every SLD client (J2EE & ABAP) points to its own
local SLD.
Actually there are 2 exceptions:
1) If the J2EE server is not used, the local SLD should not be setup neither and aJava SLD client is not required. The ABAP SLD client should point to the
central SLD.
2) If the ABAP system is used as PI Proxy (Integration server) the ABAP SLDclient should point to the central SLD.
Example of setup check/set for J2EE-only system:
4.2 Check SLD supplier should have been ok yet:
Trigger SLD DS:
7/31/2019 Activate Local SLD
15/19
- 14 -
4.3 Check SLD bridge forwarding
Setup the central SLD so that is returns the SLD data back to the local SLD:
7/31/2019 Activate Local SLD
16/19
- 15 -
Check if the data is returned to the local SLD (first trigger a data push)
On XD6:
On ED2 can take some time (more then a day ):
4.4 Check & Setup SLD Client
Take care!
Export the JCO destination data from the actual configured SLD client to the newly
created SLD by exporting and importing.
7/31/2019 Activate Local SLD
17/19
- 16 -
In central SLD:
Export from central and import in local SLD:
After import in local SLD:
7/31/2019 Activate Local SLD
18/19
- 17 -
Switch SLD Client:
7/31/2019 Activate Local SLD
19/19
- 18 -