Activate Local SLD
Activate Local SLD
Activate Local SLD
TABLE OF CONTENTS
INTRODUCTION ..................................................................................... 2
2 2.1 2.2
2.2.1 2.2.2
2.3
3 3.1 3.2
LOCAL SLD SETUP .................................................................................. 9 Launch SLD ............................................................................................9 Configure SLD ........................................................................................9
CHECK SLD SETUP ................................................................................ 13 Introduction. ........................................................................................ 13 Check SLD supplier should have been ok yet: ........................................ 13 Check SLD bridge forwarding.................................................................. 14 Check & Setup SLD Client ...................................................................... 15
-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 by selecting 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.
-2-
Installation.
2.1
2.2
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 chapter Configuring 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
General information:
Single J2EE-stack: assign it to group administrators (standard LDAP groups have to be created for this purpose) & user administrator:
-3-
Double stack
2.2.2
Cuurently only created in double stack (to be finalized for J2EE-only when LDAP groups have been defined): General information:
Double stack
-4-
2.3
2.3.1
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 be executed on a single J2EE-stack. Launch Visual Administrator and select service SLD Data Supplier. Execute Assign application roles to user groups:
2.3.2
-5-
-6-
2.3.3
-7-
LcrUser:
-8-
3.1
Launch SLD
Use http://<host>:<port>/sld/ and login with SLD Administrator rights. Permission errors 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 J2EE central instance - Deselect Import Software Catalog will be done later
-9-
Check Log:
- 10 -
Check Details:
Import CR & CIM until last version. First Import initial CR content (can also be done during initial setup, but this takes time!!):
Na imports:
- 11 -
- 12 -
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 a Java 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 SLD client should point to the central SLD. Example of setup check/set for J2EE-only system:
4.2
- 13 -
4.3
Setup the central SLD so that is returns the SLD data back to the local SLD:
- 14 -
Check if the data is returned to the local SLD (first trigger a data push) On XD6:
4.4
Take care! Export the JCO destination data from the actual configured SLD client to the newly created SLD by exporting and importing.
- 15 -
In central SLD:
- 16 -
- 17 -
- 18 -