SAP Portal Installation

SAP NetWeaver 04 Post-Installation Guide

SAP System Landscape Directory on SAP Web AS Java 6.40

Document Version 1.4 November 23, 2004

Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of 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 statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP Library document classification: PUBLIC Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. 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. Documentation on SAP Service Marketplace You can find this documentation at service.sap.com/instguidesNW04

SAP AG Neurottstrae 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Typographic Conventions

Type Style Represents

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of the SAP Library.

Post-Installation Guide: SLD

4 January 2004

Contents

Post-Installation Guide: SLD on SAP Web AS 6.40 ................................... 5

1. Introduction................................................................................................... 5

2. Installation Scenarios of SLD...................................................................... 6 2.1 Single SLD server ...............................................................................................6 2.2 Distributed SLD Servers.....................................................................................6 2.3 Dedicated SLD Server for a System Island.......................................................7 2.4 SLD Server with SAP Exchange Infrastructure ................................................8

3. Post-Installation............................................................................................ 9 3.1 Prerequisites .......................................................................................................9 3.2 Configuration of User Management ................................................................10 3.3 SLD Server and SLD Bridge.............................................................................11

4. Configuration of Data Suppliers ...............................................................14 4.1 ABAP-Based Systems ......................................................................................14 4.2 J2EE-Based Systems .......................................................................................15

5. Configuration for ABAP-Based Clients....................................................16 5.1 Functional Overview.........................................................................................16 5.2 Registering a J2EE Engine as an RFC Server ................................................17 5.3 Defining an RFC Destination in an ABAP Stack.............................................17 5.4 Maintaining SLD Connection Parameters.......................................................18


January 2004 5

Post-Installation Guide: SAP System Landscape Directory on SAP Web AS 6.40 Today, system landscapes consist of multiple distributed software components with different platform dependencies, different interfaces, and different requirements regarding installation and change management. An overall concept is required that facilitates the implementation, upgrade, and maintenance of even the most complex system landscapes. This is where SAP System Landscape Directory (SLD) comes into play. SLD acts as a central information provider where comprehensive information about all the installable and installed elements of your system landscape is stored.

1. Introduction SLD is the central information provider for the whole system landscape. Generally, SLD is deployed after the installation of each SAP Web Application Server Java 6.30 or higher. Nevertheless, to bring the SLD server into operation, it has to be configured and activated.

This documentation includes the following information:

Network topologies for using SLD in different scenarios Post-installation of the SLD server Configuration of data suppliers for SLD Configuration of SLD clients that use the ABAP API for SLD This documentation does not contain information about installing the SAP Web Application Server. For more information, see the Installation Guide SAP Web Application Server Java on : available in SAP Service Marketplace at service.sap.com/instguidesNW04 Installation.


6 January 2004

2. Installation Scenarios of SLD 2.1 Single SLD Server As previously mentioned, the SLD server acts as a central information provider for the enterprise system landscape. Therefore, the most common installation scenario is that all systems inside a system landscape including all sub-networks share a single SLD server.

Figure 1 shows that two sub-networks in an enterprise system landscape that are geographically separated share the same SLD server for landscape information.

Figure 1

The advantages of using a single SLD server for the entire system landscape are:

Consistent data Easier administration and lower operating expense

2.2 Distributed SLD Servers For some large system landscapes that are distributed over different geographic locations, a single SLD server might slow down the performance of involved application systems. In this case, a distributed SLD server installation can be taken into account.

In order to ensure consistent data of the distributed SLD servers, the SLD bridges of each location have to be configured to deliver system data to all distributed SLD servers as depicted in Figure 2 (point C). In addition, if any data has been entered manually, this data has to be entered in the Web-based UI for all SLD servers, too (point B).

Note that the distributed SLD servers can cause higher administration expense with regard to consistent data. Therefore, we recommend that you consider to use a single SLD server first.


January 2004 7

Figure 2

2.3 Dedicated SLD Server for a System Island In certain cases, you need to have a dedicated SLD for a particular group of systems (production landscape, for example) while all systems including the particular group should be kept in another SLD.

Figure 3 illustrates a production landscape as a system island that obtains a dedicated SLD server for its own use. The main SLD server, in contrast, stores information about all systems in the landscape including the production landscape.

In this case, the SLD bridge, which is connected with the production systems, has to be configured to deliver data to both the dedicated and the main SLD server (point C). If systems have been entered manually in the production system landscape, they have to be entered manually in the Web-based UI for both SLD servers (point B).

Figure 3


8 January 2004

2.4 SLD Server with SAP Exchange Infrastructure SAP Exchange Infrastructure (SAP XI) uses SLD for common landscape information. SAP XI 2.0 contains a previous version of SLD (6.20). For SAP XI 2.0 users, there are three alternatives:

As long as you are using SLD only for SAP XI, there is no need to upgrade. You can use two independent SLD servers in parallel, one SLD 6.20 for SAP XI 2.0 and one SLD 6.40

for all other purposes. The drawback is that you have to administrate two SLD servers to keep their data consistent.

You can use SLD 6.40 for SAP XI 2.0. The prerequisite is that all involved ABAP-based systems (Integration Server, clients, and business systems) must have patch level 24 (or higher) for SAP_BASIS 6.20.


January 2004 9

3. Post-Installation Both the SLD server and the SLD bridge are deployed after each SAP Web AS Java 6.40 has been installed. Only post-installation steps are necessary to activate SLD in an SAP Web AS Java 6.40. These steps are listed in this section.

3.1 Prerequisites You have imported the relevant Support Packages and binary patches for SAP Web AS 6.40.

We recommend that you regularly check the SAP Service Marketplace for up-to-date support information at service.sap.com/sp-stacks SAP NetWeaver 04 Java Server.

You have set the heap size of the Java VM for your J2EE Engine to the following minimum values by using the J2EE Engine Config tool:

JDK / JRE vendor Heap size

SUN 512 M

IBM / Compaq 1024 M

Figure 4

For more information about using the J2EE Engine Config Tool, see the Administration Manual of SAP Web AS available in the SAP Library.

The values in the table above only relate 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, you should increase the heap size according to the particular applications.

You must be a J2EE administrator for user management configuration (section 3.2). You must be a J2EE administrator or be assigned to the J2EE group SAP_SLD_ADMINISTRATOR for

all other SLD-specific configuration steps.


10 January 2004

3.2 Configuration of User Management The SLD functions are protected from unauthorized access. There are seven security roles assigned to different SLD functions:

User Role Permission

LcrUser Read access to SLD data

LcrClassWriter Create, modify and delete CIM classes (includes LcrUser)

LcrInstanceWriterLD Create, modify and delete CIM instances of the subset Landscape Description (includes LcrUser)

LcrInstanceWriterCR Create, modify and delete CIM instances of the subset Component Information (includes LcrUser)

LcrInstanceWriterNR Create, modify and delete CIM instances of the subset Name Reservation (includes LcrUser)

LcrInstanceWriterAll Create, modify and delete all types of CIM instances (includes LcrUser, LcrInstanceWriterCR, LcrInstanceWriterLD, LcrInstanceWriterNR)

LcrAdministrator Administrative tasks for both system and application (includes all other roles)

Figure 5

Before you can use SLD, you have to map these security roles to the individual users or user groups to grant them different authorizations. It is advisable to create user groups and map them to the appropriate security roles. Users belonging to a particular group will receive all permissions granted to the group. We recommend that you create the following user groups:

Group Permission

SAP_SLD_GUEST Read permission for the whole content

SAP_SLD_DEVELOPER Plus write permission on development object names (name reservation)

SAP_SLD_CONFIGURATOR Plus write permission for system landscape elements (systems, etc.)

SAP_SLD_ORGANIZER Plus write permission for component information (software components)

SAP_SLD_ADMINISTRATOR Plus administration permission

Figure 6

If the User Management Engine (UME) is used with an ABAP-based system as the back-end user storage, ABAP user roles appear as user groups on the J2EE side. Use transaction PFCG for creating user roles and assign the roles to the appropriate users. The ABAP Engine of SAP Web AS 6.40 contains these default user roles.

If these default J2EE user groups already exist at the time of the SLD deployment, the deployment will perform the mapping as listed in Figure 7. If the J2EE user groups are created after the SLD server has been deployed, you can perform the mappings by using the SLD configuration service in the J2EE Visual Administrator. Proceed as follows:

1. Log on to the J2EE Visual Administrator as an administrator.

2. Choose Services SLD Data Supplier. 3. Click with the quick info text Assign User Groups to Roles.

The SLD configuration service performs the default mappings.


January 2004 11

Security Role Mapped to Group(s)

LcrUser SAP_SLD_GUEST

LcrInstanceWriterNR SAP_SLD_DEVELOPER and SAP_SLD_CONFIGURATOR

LcrInstanceWriterLD SAP_SLD_CONFIGURATOR

LcrInstanceWriterAll SAP_SLD_ORGANIZER

LcrAdministrator SAP_SLD_ADMINISTRATOR

Figure 7

The roles LcrClassWriter and LcrInstanceWriterCR are not mapped to any user groups. Creating, modifying and removing CIM classes and instances of component information are highly sensitive functions. The role LcrAdministrator includes these two roles by default.

3.3 SLD Server and SLD Bridge As mentioned above, the SLD server is deployed at the installation time of SAP Web AS Java 6.40. The URL for accessing SLD is http://:/sld, where stands for the host name or the IP address of the host, respectively, and represents the service port. The default setting of the port number is 500, where is the instance number of the SAP Web Application Server. This page is referenced as the main page of SLD in this document.

If your SAP Web AS Java is running on host sldhost and has the instance number is 36, the URL for accessing the SLD is http://sldhost:53600/sld.

During installation, a directory gets created in the file system for SLD. It is located under \SYS\global\sld.

3.3.1. Server and Persistence Settings After you have entered the URL for SLD, the system prompts you to enter logon data for authentication. Any user from the group SAP_SLD_ADMINISTRATOR or the J2EE user group administrators is authorized for administrative tasks on the SLD server.

For server and persistence settings, choose Administration Server Settings on the main page. Enter an ABAP namespace without enclosing slashes for Object Server and the path of the working directory for Working Directory. You can reserve an ABAP namespace in SAP Service Marketplace at service.sap.com/namespaces. If you are not able to reserve a prefix at SAP, use a host name as Object Server. In this case, you are not able to use this SLD server for name reservation in the SAP NetWeaver Java Development Infrastructure. Additionally, the SLD server requires a directory on the file system for automatic upload purposes. Use the directory \SYS\global\sld as working directory.

Ensure that the persistence mode is Database. Database is the default persistence mode. File System is only needed for test purposes.

You can make server settings only if the SLD server has been stopped.


12 January 2004

After you finished these necessary settings, you can start the SLD server. Afterwards, the SLD server will be started during the startup process of SAP Web AS.

You can fine tune the SLD server by using server parameter settings. Administration Profile leads you to the page of server parameter settings. You can adjust the parameters on the Web UI. Also you can download the profile and modify it locally. After you have finished the modifications, you can upload the profile onto the SLD server.

If you run the SLD server in a cluster, 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.

3.3.2. SLD Bridge In order to receive automatically reported data that is sent by data suppliers that run in individual systems, you have to configure and start the SLD bridge. The SLD bridge transforms the system data sent by data suppliers to the SLD server into CIM-compliant format.

The data exchange between the data suppliers of ABAP-based systems and the SLD bridge takes place by means of RFC. Therefore, an SAP Gateway service has to be configured. On the main page of SLD, choose Administration Data Supplier Bridge, and specify the SAP Gateway server and the service number.

After you have set up the gateway service, the SLD bridge has to be restarted so that the settings can take effect.

A gateway service must not be shared by multiple SLD servers. If you implement scenarios as described in sections 2.2 and 2.3, you have to assign a dedicated gateway service to each SLD server.

If you want the SLD bridge to send data to multiple SLD servers, choose Administration Data Supplier Bridge SLD Clients New SLD ... on the main page of SLD. Specify the server and logon data for the additional SLD servers.

Make sure that you have correctly set up the data suppliers in the systems that have to report system data automatically. See section 4 for detailed information.


January 2004 13

3.3.3. Initial Data Import The SLD server implements the DMTF Common Information Model (CIM) (www.dmtf.org). Before you start to use the SLD server, you have to import the information about available SAP components (CR_Content.zip). The file is located in the directory \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 (for example, new releases and Support Packages). This content in SLD has to be updated from time to time. You can download the most up-to-date files from SAP Service Marketplace. For more information, see SAP Note 669669.

To import the file:

1. On the main page of SLD, choose Administration Import. 2. Specify the file name.

3. Choose Import Data.

The files are transferred to the SLD server. The typical load time for this import step is 20 minutes.

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.


14 January 2004

4. Configuration of Data Suppliers 4.1 ABAP-Based Systems As mentioned earlier, you can set up data suppliers in ABAP-based systems (SAP R/3 Release 4.0B and higher) so that these systems can report system data automatically to the SLD.

The ABAP-based data supplier delivers system data to the SLD server in two ways:

Directly by means of an RFC connection to the SLD bridge By writing the data to the central shared memory server. An SLD plug-in for the CCMS agent exports the

data from the shared memory by means of RFC to the SLD bridge.

The first method is set as the default. In both cases, the SLD bridge transfers the received raw data by means of HTTP to the SLD server as defined by the WBEM specification (http://www.dmtf.org/standards/standard_wbem.php).

Figure 8

The data supplier modules for ABAP-based systems are delivered with Support Packages for all SAP R/3 releases higher than 4.0B. Make sure that you have already imported the relevant Support Packages. For more information, see SAP Note 584654.

After importing the appropriate Support Packages, you can use transaction RZ70 to configure the data supplier. In this transaction, you can specify the data transport method, the time interval of scheduled batch jobs, the gateway host and service, as well as the data collection programs.


January 2004 15

4.2 J2EE-Based Systems Figure 9 illustrates how a data supplier for J2EE-based systems reports system information to the SLD server. The data supplier can use either an HTTP or an RFC connection for this purpose. We recommend that you use the HTTP connection.

Use the J2EE Visual Administrator to set up the data supplier for the J2EE Engine. Before you start the setup, check the property SynchPermissionsWithDatabase under Cluster Server Service Security Provider Properties. It must be set to true. In the J2EE Visual Administrator choose Cluster Server Services SLD Data Supplier for performing the configuration. You can specify the server and logon data, as well as the time interval of scheduled batch jobs.

Figure 9


16 January 2004

5. Configuration for ABAP-Based Clients There are APIs for both Java and ABAP clients that enable clients to access the SLD server. Whereas the Java API is easy-to-use, some configuration steps have to be performed for the ABAP API.

This section is only relevant if you use the ABAP API for accessing the SLD from an ABAP-based system.

5.1 Functional Overview The ABAP API accesses the remote SLD server by using the RFC concept. The ABAP API sends the requests to the Java layer by means of RFC. The Java layer acts as an RFC server and forwards the calls to the SLD server by using the Java API.

Figure 10

As depicted in Figure 10, the J2EE Engine that receives the RFC calls from the ABAP Engine has to be registered on the SAP Gateway server with a unique program ID. The ABAP Engine defines an RFC destination that contains the reference to the registered J2EE Engine as the RFC server. In addition, the J2EE Engine gets information about the calling ABAP function modules from a defined repository server.

To enable an ABAP-based system to call SLD functions by means of the ABAP API, proceed as follows:

1. Register a J2EE Engine as an RFC server (see section 5.2).

2. Define an RFC destination in the ABAP Engine (see section 5.3).

3. Maintain the SLD connection parameters (see section 5.4).


January 2004 17

5.2 Registering a J2EE Engine as an RFC Server In the J2EE Engine, the RFC function is implemented by the JCo RFC Provider service. Follow the steps below to register a J2EE Engine as an RFC server:

1. Start the J2EE Visual Administrator.

2. Choose Cluster Server Services JCo RFC Provider. a. In the section RFC Destination enter a unique Program ID, the gateway host, and the gateway

service. The unique program ID could be SAPSLDAPI_, for example. Additionally, set the number of processes to 3.

b. In the section Repository specify the data for the application server that acts as the repository server. The user must be of the type Communications in the appropriate ABAP system (SAPJSF, for example).

c. Select the flag Unicode, if the gateway service is installed with a Unicode system.

3. Choose Set.

5.3 Defining an RFC Destination in an ABAP Stack To define an RFC destination in an ABAP-based system for the registered J2EE RFC server, proceed as follows:

1. Call transaction SM59.

2. Choose Create.

3. Enter the following:

- RFC destination: SAPSLDAPI

- Connection type: T (Start an external program via TCP/IP).

4. Choose Enter.

5. Choose Technical settings and specify the following data:

a. Select Registered Server Program as the activation type.

b. Enter the program ID of the J2EE Engine that acts as the RFC server. The program ID must be exactly the same as the one registered on the SAP Gateway server (see section 5.2) (for example, SAPSLDAPI_).

c. Enter the gateway host and the gateway service.

To find out the parameters for the gateway server that is installed with an ABAP-based system, choose Goto Parameters Display in the transaction SMGW. The parameters Gateway Host and Gateway Service are listed as attributes.

d. If the ABAP-based system is a Unicode system, navigate to Special Options and select the option Non-Unicode or Unicode in the section Character Width in Target System according to the gateway server.

6. Save your entries.


18 January 2004

5.4 Maintaining SLD Connection Parameters As shown in Figure 10, the SLD server does not need to be on the same J2EE Engine that serves as an RFC server. The J2EE Engine that acts as the RFC server simply forwards the requests from the ABAP side as defined by WBEM. Therefore, connection data to the remote SLD server has to be set in the ABAP-based system.

1. Call transaction SLDAPICUST.

2. Switch to editing mode and choose Insert Row. Specify the connection parameters (host name, port, user, and password) and set this SLD server as Primary.

Only the entry marked as Primary is active.

3. Save your entries.

TitleCopyrightTypographic Conventions / SLDContents

Post-Installation Guide: SAP System Landscape Directory on S1. Introduction2. Installation Scenarios of SLD2.1 Single SLD Server2.2 Distributed SLD Servers2.3 Dedicated SLD Server for a System Island2.4 SLD Server with SAP Exchange Infrastructure

3. Post-Installation3.1 Prerequisites3.2 Configuration of User Management3.3 SLD Server and SLD Bridge

4. Configuration of Data Suppliers4.1 ABAP-Based Systems4.2 J2EE-Based Systems

5. Configuration for ABAP-Based Clients5.1 Functional Overview5.2 Registering a J2EE Engine as an RFC Server5.3 Defining an RFC Destination in an ABAP Stack5.4 Maintaining SLD Connection Parameters

/ColorImageDict > /JPEG2000ColorACSImageDict > /JPEG2000ColorImageDict > /AntiAliasGrayImages false /DownsampleGrayImages true /GrayImageDownsampleType /Bicubic /GrayImageResolution 300 /GrayImageDepth -1 /GrayImageDownsampleThreshold 1.50000 /EncodeGrayImages true /GrayImageFilter /DCTEncode /AutoFilterGrayImages true /GrayImageAutoFilterStrategy /JPEG /GrayACSImageDict > /GrayImageDict > /JPEG2000GrayACSImageDict > /JPEG2000GrayImageDict > /AntiAliasMonoImages false /DownsampleMonoImages true /MonoImageDownsampleType /Bicubic /MonoImageResolution 300 /MonoImageDepth -1 /MonoImageDownsampleThreshold 1.50000 /EncodeMonoImages true /MonoImageFilter /CCITTFaxEncode /MonoImageDict > /AllowPSXObjects false /PDFX1aCheck false /PDFX3Check false /PDFXCompliantPDFOnly false /PDFXNoTrimBoxError true /PDFXTrimBoxToMediaBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXSetBleedBoxToMediaBox true /PDFXBleedBoxToTrimBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXOutputIntentProfile () /PDFXOutputCondition () /PDFXRegistryName (http://www.color.org) /PDFXTrapped /False

/Description >>> setdistillerparams> setpagedevice

Documents

SAP Portal Installation