Professional Documents
Culture Documents
System Landscape
Directory of SAP
NetWeaver 2004s
Document Version - October, 2005
SAP AG
Neurottstrae 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com
form or for any purpose without the express permission of SAP AG.
notice.
in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their
any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP
Group products and services are those that are set forth in the express
warranty.
Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
Disclaimer
Any Java Source Code delivered with this product is only to be used
by SAPs Support Services and may not be modified or altered in any
way.
Typographic Conventions
Icons
Type Style
Represents
Icon
Example Text
Example text
EXAMPLE TEXT
Example text
Example text
<Example text>
EXAMPLE TEXT
Meaning
Caution
Example
Note
Recommendation
Syntax
Contents
October 2005
Bear in mind that the abbreviation SLD is not intended to define a product, since the System
Landscape Directory is part of SAP NetWeaver. This abbreviation is only intended to improve
readability.
SLD contains a description of your system landscape (that is, actually installed software components) and a
repository of software components that can theoretically be installed in your landscape (such as the software
components available from SAP). As this data gets updated automatically, SLD provides reliable and up-todate system landscape information with as little effort for you as possible. This way, SLD is a central
information provider for SAP and third-party tools that use this data to deliver the services you need to keep
your landscape up and running.
1 Introduction
SLD is already contained in the installation of every SAP NetWeaver 2004s system with usage type AS Java.
Therefore, no further installation is required to activate SLD. Furthermore, the initial configuration is also
performed during installation. The configuration of the data suppliers in the systems of your landscape is also
very easy; you only have to specify the SLD address there. This Post-Installation Guide describes the
configuration of the SLD server side, For configuration of the data suppliers and the ABAP API please see
respective Chapters in SLD User Guide.
Therefore, this Post-Installation Guide is mainly intented to describe how to control or eventually change the
configuration after the installation and to describe the configuration of the SLD security.
For newer SAP products, the configuration of the data suppliers is already included in the
standard installation and configuration procedure.
For more information, see service.sap.com/sld Media Library Planning Guide - System Landscape
Directory.
This paper does not contain information about installing SAP NetWeaver 2004s systems. For more
information, see the Installation Guide SAP NetWeaver available in SAP Service Marketplace at
service.sap.com/instguidesnw2004s Installation.
October 2005
Action
Prerequisites Adjusting JVM heap size for the server nodes:
The SLD server requires a minimum heap size of 512MB. The value is set using the
J2EE Engine Config Tool.
For more information, see 3 Prerequisites [page 8].
Configuration of SLD security Assigning SLD security roles and actions to
users/user groups:
1. Configure the SLD UME Roles and Groups in a Web browser
2. Start the J2EE Engine Visual Administrator.
3. Navigate to Administration Server Services SLD Data Supplier to apply
the standard SLD role mapping.
For more information, see 4 Configuring [page 9].
Setting of Server Parameters Activating the SLD Server:
1. Open the SLD home page http://<host>:<port>/sld in a Web browser.
2. Choose Administration Profile Server Settings.
3. Enter a name for the Object Server. Preferably, use a prefix reserved on the SAP
Service Marketplace as an Object Server name.
4. If you have multiple server nodes, the profile parameter ObjectManager
BufferInstances must be set to false (default true).
5. Start the SLD Server.
For more information, see 5.1 Setting Server and Persistence Parameters [page 11].
Performing Initial Data Import:
1. On the SLD home page, choose Administration Import.
2. Press Import CR Content.
For more information, see 5.3 Performing Initial Data Import [page 13].
Configuring the SLD Bridge
1. On the SLD home page, choose Administration Profile datasupplier.
2. Maintain the gateway host and the name of the gateway service. If you are using
the SAP NetWeaver AS Java standalone configuration, a standalone SAP Gateway
October 2005
October 2005
3 Prerequisites
You have:
Set the heap size of the Java VM for your J2EE Engine to the minimum value of 512 MB by using
the J2EE Engine Config tool. Restart the J2EE Engine after setting the heap size.
For more information about using the J2EE Engine Config Tool, see the following in the SAP
Library: SAP NetWeaver Library SAP Net Weaver Key Capabilities Application Plattform
by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine
Administration.)
The value of 512 MB only relates to the scenario that the SLD server runs as the single
application in the relevant J2EE Engine. If you run multiple applications in the same J2EE
Engine, extend the value appropriately.
You must:
Be a J2EE administrator for user management configuration (section 4 Configuring [page 9]).
October 2005
UME Action
Permissions
LcrUser
com.sap.lcr.LcrUser
LcrSupport
com.sap.lcr.LcrSupport
LcrClassWriter
com.sap.lcr.LcrClassWriter
LcrInstanceWriterLD
com.sap.lcr.LcrInstanceWriterLD
DataSupplierLD
LcrInstanceWriterCR
com.sap.lcr.LcrInstanceWriterCR
LcrInstanceWriterNR
com.sap.lcr.LcrInstanceWriterNR
LcrInstanceWriterAll
com.sap.lcr.LcrInstanceWriterAll
LcrAdministrator
com.sap.lcr.LcrAdministrator
Figure 1
Before you can use the SLD, you have to map these security roles and actions to individual users or user
groups.
October 2005
To simplify configuration efforts it is advisable to create user groups and map them to the
appropriate security roles and actions instead of assigning them to individual users.
Users belonging to a particular group will receive all permissions granted to the group. We recommend that
you use the following user groups with the specified role assignment:
User Group
SAP_SLD_GUEST
LcrUser
SAP_SLD_DEVELOPER
LcrInstanceWriterNR
SAP_SLD_CONFIGURATOR
SAP_SLD_ORGANIZER
LcrInstanceWriterAll
SAP_SLD_ADMINISTRATOR
LcrAdministrator
SAP_SLD_DATA_SUPPLIER
DataSupplierLD
SAP_SLD_SUPPORT
LcrSupport
Figure 2
You need to create these groups with the appropriate tool for your user store (for example, J2EE, ABAP or
LDAP). If the User Management Engine (UME) is used with an ABAP-based system as the back-end user
storage, these groups will already exist except for SAP_SLD_DATA_SUPPLIER and SAP_SLD_SUPPORT.
(ABAP user roles appear as user groups on the J2EE side. The ABAP Engine of the SAP Web AS 6.40 or
above contains these default user roles.)
Once these groups exist, you can perform the required mappings as defined in the table above.
Procedure
1. Log on to the UME User Management with your Web browser (/useradmin).
2. Choose Roles to create UME roles for each UME action related to the SLD. We recommend that you
define these roles with the same name as the corresponding J2EE role. Associate each role with the
corresponding UME action, e.g.
LcrUser -> com.sap.lcr.LcrUser
3. Assign each new UME role to the appropriate user group as defined in the table above. For example,
assign group SAP_SLD_GUEST to UME role LcrUser.
4. Log on to the J2EE Engine Visual Administrator as an administrator.
5. Choose Services SLD Data Supplier.
6. Click
The SLD configuration service performs the default mappings of user groups to J2EE security roles.
A sandbox SLD security set-up for test purposes requires only the role LcrAdministrator to be mapped to
SAP_SLD_ADMINISTRATOR and an administrator user to be assigned to this group.
10
October 2005
Prerequisites
To access the administration area, you require a user ID with the security role LcrAdministrator. The
standard role mapping provides this security role for the J2EE administrator. If you do not have a user ID
with this authorization, contact your system administrator.
Procedure
1. Enter the URL of the application using the following pattern: http://<host>:<port>/sld.
<host> stands for the host name or the IP address of the host
The default setting of the port number is 5xx00, where xx is the instance number of the SAP Web
Application Server. This page is referenced as the main page of SLD in this document.
When you call a server function for the first time, the system prompts you to log on so that it can
check your authorizations. If you do not have the necessary authorizations for the function that
you want to call, the system prompts you to log on again.
2. Enter your User ID and Password and select Log on.
Result
The system checks your user ID and password. If both are valid, the Web browser displays the SLD main
page.
You can make server settings only if the SLD server is stopped.
The SLD service supports two ways of saving data:
Database persistence
We recommend that you use database persistence. File system persistence is useful for (local)
test purposes only.
Prerequisites
You have navigated to the Administration screen.You have stopped the SLD
October 2005
11
Procedure
Server Parameters
1. On the main page choose Administration Profile Server Settings.
2. Enter the name of the object server.
Make sure that the object server name is unique at least within your system landscape, if not
globally. Use an ABAP prefix that has been reserved at SAP, without the slashes. If you cannot
reserve an ABAP prefix, use the name of the host where your SLD is running. The working
directory is /usr/sap/<SAPSID>/SYS/global/sld (UNIX) or
\\<server>\usr\sap\<SAPSID>\SYS\global\sld (Microsoft Windows). You have to set
the server parameters for each type of persistence.
If SLD acts as:
Landscape directory in the system landscape, the host name of the system is sufficient, for example
mysldhost.
Name server for SAP NetWeaver Development Infrastructure, the name must be reserved on the
SAP Service Marketplace at http://service.sap.com/namespaces (for more information, see SAP
Notes 105132 and 710315).
Database Persistence
Under persistence, choose Database Set.
Result
The SLD server sets the relevant persistence method.
After you have finished the modifications, you can upload the profile onto the SLD server.
If you run the SLD server in a cluster (more than one J2EE engine instance or node), the profile parameter
BufferInstances in the section ObjectManager must have the value false.
If you change this parameter, the change will only take effect after the SLD server has been
restarted.
Prerequisites
To modify configuration data, you require the user role LcrAdministrator.
12
October 2005
Setting Parameters
To modify a system profile online, proceed as follows:
1. On the main screen, choose Administration Server Profile. The browser displays the Profile screen.
2. Make the modifications and then choose Save. The modifications are saved.
If you want to discard modifications that you made, choose Reset to Defaults. All parameter values
recommended by SAP take effect again.
Uploading a Profile
When you start the SLD server for the first time, the system profile is automatically uploaded. This profile
contains default settings.
We recommend that you use the default settings when you use the SLD server for the first time
with one exception: On an SAP J2EE Engine cluster with more than one node, you must set the
parameter BufferInstances to "false".
To modify a system profile offline, you have to download and upload it to a file. Proceed as follows:
1. On the Administration screen, choose Server Profile.
2. On the Profile screen, choose Download.
3. Choose Save This File to Disk, and then enter the file name and the directory where you want to save
the file.
The configuration file is now available for processing in the specified directory. After you have processed
the configuration file as described in the previous section, you have to transfer this file back to the
server. You must also do this after the SLD server has been installed.
4. On the Profile screen, choose Upload. The browser displays the Profile Upload screen.
5. Enter the file name (or choose Browse to navigate to the file), and then choose Upload. The browser
transfers the file to the server.
The default profile is located in the file sldprofile.xml in the following directory (on Microsoft
Windows): \\<server>\usr\sap\<SAPSID>\SYS\global\sld. You can transfer the
configuration file to the server directly as an XML or ZIP file.
The changes to the configuration take effect only when you restart the SLD service.
October 2005
13
The model file and CR content file are located in the file system in the directory <system-installdir>\SYS\global\sld\model.
Since CR_Content.zip contains all available SAP components, the content of this file grows
with time. The extensions contain information about new components (new releases and
Support Packages, for example). This content in the SLD has to be updated from time to time.
You can download the most up-to-date files from the SAP Service Marketplace. See SAP Note
669669 for details.
Prerequisites
The instance descriptions must be either XML files or compressed XML files in ZIP format.
You have set the heap size for all nodes to 512 MB in the J2EE Engine Config Tool.
Procedure
1. Choose Content Import. The browser displays the Import Selection screen.
2. Next to the Import File field, choose Browse.
3. To import the component information data, navigate to the following file:
\\<server>\usr\sap\<SAPSID>\SYS\global\sld\model\cr_content.zip (Microsoft
Windows) and then choose Open.
If the import process has been interrupted due to memory lack (for instance, the Java VM runs
out of memory), you must increase the heap size of the Java VM and restart the J2EE Engine.
After that you must re-import the CR_Content.zip file in order to have the complete data. In
case you re-import after a failed import, you can exceptionally ignore a warning about a non
fitting content update.
Result
After you have triggered the import, the browser returns to the Administration screen. The status bar on this
screen indicates the status of the import procedure.
October 2005
Procedure
1. Choose Administration Data Suppliers on the main page of SLD.
2. Set the parameter Update local namespaces for sld/active to true, so that the SLD data supplier bridge
forwards system data received from data suppliers to the default namespace sld/active of this SLD
server.
3. Specify the SAP Gateway server and the service number at Administration Profile datasupplier.
You can find this information on the main page of SLD under Administration Profile at Data Supplier.
After you have set up the gateway service, the SLD bridge has to be restarted so that the
settings can take effect.
One SAP Gateway server must only be linked to one SLD server as data receiver. Sharing an
SAP Gateway server for multiple SLD servers leads to errors.
Make sure that you have correctly set up the data suppliers in the systems that have to report
system data automatically. See section for detailed information.
4. If you want the SLD bridge to send data to multiple SLD servers, choose Administration Data Supplier
Bridge Add SLD.... on the main page of SLD. Specify the server and logon data for the additional SLD
servers.
October 2005
15
Description
Internet Address
Title
SAP Notes
http://service.sap.com/notes
105132,
710315,
669669,
712594
service.sap.com/sld Media
Library
service.sap.com/sld Media
Library
service.sap.com/instguidesNW04
Installation
Standalone Gateway
Installation Guide
Security
service.sap.com/security
16
October 2005