You are on page 1of 12

Registration setup of ABAP based system in the SAP

System Landscape Directory (Note 584654)


You want to register an SAP system in the SAP System Landscape Directory (SLD).
With the SLD, you can maintain your system infrastructure centrally using CIM data.
CIM means "Common Information Model" of the "Distributed Management Task Force"
organization (www.dmtf.org).
Reason and Prerequisites
Initially, the SAP System Landscape Directory was delivered with the SAP Exchange
Infrastructure (XI). In the SAP_BASIS releases after Release 620, SLD forms part of the
system. However, the SLD server can only accept the data of SLD agents automatically
as of Release 6.30.
Older systems can still log on to a central Landscape Directory as this functionality is
delivered with Support Packages. In contrast to the higher releases, the registration is
configured manually in Releases 40B to 470 (SAP_BASIS 620).
The ability to register with the SLD is not restricted to R/3 systems. In addition, BW,
APO or CRM systems can also automatically register with the SLD.
Solution
The manual entry of data in the System Landscape Directory is replaced by an
"instrumentation" of the SAP system. The instrumentation for the automatic information
transfer is carried out by the configuration of "SLD agents". The relevant software is
imported with the latest SAP Support Package.
The following description assumes that the "SLD Bridge" is already set up on the SLD.
This bridge is only available on the SLD server as of Release 6.30.
For more information, refer to the documentation for the installation and configuration of
the SAP System Landscape Directory.
To set up your system for the automatic transfer of data to the SLD, proceed as follows:
1. Use transaction RZ70 to start the local administration of the SLD agents.

2. The "Data Transport" and "Other Settings" sections already contain some default
settings. For the first configuration, remove the "Schedule background job" checkmark.
This indicator is only set in the last configuration step to initiate the automatic update of
the system data (periodically and with every system restart).
3. In the "Transport Information" section, add information about the SAP Gateway used
by the SLD Bridge. Enter the host name of the gateway computer and the service name
(sapgwNN with NN being 00, 01... 97). The recommended configuration uses the
gateway on the SLD server. If necessary for load distribution reasons, or because the
gateway cannot be reached because a firewall system is being used with RFC traffic
disabled, you can also place the gateway and SLD Bridge on a different host. This also
includes (in particular) the local host. (Make sure that the entries for the gateway host
and service is exactly the same as for the "JCO RFC Provider" on the productive SLD,
named SAPSLDAPI_<SolMan_SID> and maintained in Visual Administrator (on the
productive SLD). Indeed, the Productive SLD and the Solution Manager ABAP Data
Supplier must use the same Gateway (the one which is "local" to the Productive SLD).

4. Initially, populate the table of the data collection programs with the "Default Value"
pushbutton
(the last button in the "Data Collection Programs" section). This provides
you with an initial default SLD agent configuration. The "_SLD_RFC" program is not
active. It collects all RFC destinations and is usually not required.

5. Test the active programs in two steps.


a) Start a local test where the reported data is output in a list. For this purpose, select
the active programs in the "Data Collection Programs" section with "Select All" and
exclude the "_SLD_RFC" line. Then select "Test" . This test may take a while
depending on how much data is collected. However, usually it only takes a few seconds.
The collected information is output in a list.

b) Start the data transfer once with "Start Data Collection"


(the "Schedule
background job" checkmark is not set). The data currently entered on the screen is
activated automatically. If the list reports problems with the RFC connection, test the
connection separately with transaction SM59. Unicode systems, by default, use the
TCP/IP connection SLD_UC, non-Unicode systems the TCP/IP connection SLD_NUC.
The relevant RFC destination is selected automatically as long as the default selection
Automatic RFC Destination is used in the "Transport Information" section, as we
recommend.
6. To schedule regular updates, set the "Schedule background job" option after you
have tested the data transfer successfully and then use the "Start Data Collection"
button to start the automatic collection process. The default setting for the period is 12
hours (720 minutes). Check that the subsequent output contains messages indicating
that an RFC call was executed successfully and that a background job was scheduled.
7. Use transaction SM37 to check that the "SAP_SLD_DATA_COLLECT" and
"SAP_SLD_DATA_COLLECT_STARTUP" SLD background jobs were scheduled
correctly. Both background jobs should have the status "Released". The first job is
executed periodically and the second job is executed with every system restart. This
automatically updates the system information in the SLD.

You can reschedule the batch jobs or change the configuration at any time using
transaction RZ70. You can also use the transaction to reset the regular update
operation by selecting the "Delete" button.

Registration setup of JAVA based system in the SAP


System Landscape Directory (Note 673144)

The SAP System Landscape Directory was initially delivered with the SAP Exchange
Infrastructure (XI). The SLD is a permanent component in releases with a SAP_BASIS
greater than 620. However, the SLD server can only automatically accept the data of
SLD Data Suppliers as of Release 6.30.
As of Release 6.40, a J2EE Engine is automatically able to deliver information about
itself to the SLD. This happens via a special service that is installed with the J2EE
Engine and is automatically started for each J2EE Engine. Furthermore, this service
keeps the data transferred to the SLD up to date by performing regular data transfers.
This SLD service is managed by the Visual Administrator for the J2EE Engine.
Solution
Instead of manually entering the data into the System Landscape Directory, the SAP
J2EE Engine is equipped with an SLD-specific service that automatically returns data
via the engine to the SLD. You can use the J2EE server tool, Visual Administrator (VA),
to access the J2EE Engine. In the following, the prerequisite here is that the SLD Bridge
was already set up on the SLD. This bridge will only be available on the SLD server as
of Release 6.30. The required information is contained in the documentation for
installing and configuring the SAP System Landscape Directories.
Configuring the SLD Service
To configure the automatic transfer of data from your J2EE Engine to the SLD, proceed
as follows.
1.
Start
the
VA
for
the
J2EE
Engine
by
executing
the
<drive>:\usr\sap\<SID>\JC<no.>\j2ee\admin\go.bat
(Windows)
or
/usr/sap/<SID>/JC<no.>/j2ee/admin/go (Unix) description any of the nodes on the J2EE
Engine.
In this case, <SID> means the system ID that you used to install the J2EE Engine
("C11", for example) and <no.> is the instance number (<no.>=00,01...,99) for the J2EE
instance.
2. After you start the VA, the first thing you will be requested to do is to connect to a
J2EE Engine. Select an already existing connection to your Engine or select "New" to
create a new connection. The VA tool will connect to the Engine after you select the
"Connect" button (you can select this button in the overview).
3. In the subsequent "Login" window, you are requested to enter the password of the
user created in the connection information. This user must be a valid user on the J2EE
Engine and he/she must have administrator rights. Here, for example, you can use the

"Administrator" user who was automatically created during the installation of the J2EE
Engine.
4. After a successful logon, you will find a tree comprising all of the nodes that are
currently active for the J2EE Engine under the "Cluster" tab in the left window of the VA.
Expand any server node under the "Server" entry. Then expand the "Service" entry.
Here, you will find, among other things, the SLD Service, which is indicated by the SLD
Data Supplier. Select this service. You are then in the "Runtime" area of the SLD
service.

5. At the lower part of the display screen, select the HTTP settings tab and then specify
the connection data for the automatic transfer of J2EE Engine data to the SLD.
In this case, you must specify the following information.
a) Host: Here, enter the TCP name of the host on which the SLD bridge is started.
b) Port: Here, specify the TCCP port used by the J2EE Engine as a HTTP port. The
exact value was determined during the installation of the J2EE Engine. The usual value
is 5<no.>00 (<no.>=00, 01...,99) where <no.> denotes the instance number for the
J2EE node.
c) User: Enter a valid J2EE user name here (default user SLDDSUSER, having the
UME group: SAP_SLD_DATA_SUPPLIER on the productive SLD.
d) Password: Here, specify the password for the J2EE user.

6. Select the "Save" button to save your entry. This saves the entered data in encoded
form in the database in the "Secure Storage" of the J2EE Engine.
To check whether data is transferred correctly to the SLD, you can trigger an immediate
data transfer. For this, select the button with the blue arrow on the header page in the
VA. You are asked whether you want to transfer the J2EE data ("Trigger SLD Data
Transfer?"). If you answer "Yes" to the question, the system automatically collects data
using the J2EE Engine and then immediately tries to transfer this data to the SLD. An
additional message informs you that the transfer was successful.

Automatic data transfer to the SLD

The automatic transfer of J2EE data to the SLD occurs in a chronological cycle that can
be configured. This information is on the Properties page of the SLD Service in the VA.
To configure the cycle, select the Properties tab on the header page of the VA. You will
then see the SLD Service parameters. With the Repeat Time Minutes parameter, set the
time in minutes between two data transfers to the SLD.
Note that if you specify a value lower than five minutes, this value is automatically set to
the value five. On the other hand, higher minute specifications remain unchanged.
However, you should not change the default value of 720 minutes (12 hours) unless you
have a good reason to do so.
If you changed the minute value and want the chronological cycle to start immediately
with the new value, restart the SLD Service by opening the context menu of the SLD
Service in the Service overview on the left and select "Stop" and then "Start". Note that
a service restart also triggers a simultaneous retransfer of the J2EE data to the SLD.
However, this initial data retransfer is only performed after a wait time of two minutes.
If you do not restart the service after a change to the time interval, the previous setting
will remain active until you start the SLD Service or J2EE Engine.

Registration setup of NON ABAP/JAVA system in the


SAP System Landscape Directory (Note 1018839)
The sldreg executable is used to transfer data to the SLD for a system that is neither
ABAP nor J2EE-based. When triggered by other SAP systems, the sldreg sends data in
an XML format using a predefined document type definition (DTD). It uses an HTTP
connection, as shown in the figure below:

For example, Search and Classification (TREX), SAPOSCOL, MDM, IGS and so on,
generate such an XML and trigger the transfer of data to SLD via sldreg. The sldreg
executable and the required libraries, which are linked dynamically, are installed with
your ABAP or J2EE-based system.
Availability of "sldreg"
The program sldreg[. exe] is delivered with the SAP kernel as of Release 7.0. The
patches for the two binaries, "sldreg[.exe]" and "sldreglib.{dll|sl|so|o}", are available on
Service Marketplace under SAP NetWeaver as of Release 2004S (under the
component SAP KERNEL). After you select the operating system and choose the link
"#Database independent", SAR archives that begin with "SAPEXE" are displayed in the
list provided. These archives contain both of the aforementioned binaries.
As of Release 7.10, there will a separate archive SAPSLDREG_...SAR on SAP Service
Marketplace under the component SAP KERNEL. This archive contains all binaries
required for the call, including the shared libraries used.
Configuring sldreg
1.

From /usr/sap/<SAPSID>/SYS/global enter sldreg.

The sldreg command line parameters are printed.


2.

Enter sldreg -configure slddest.cfg usekeyfile.

3.
information.

You will be prompted to enter HTTP user, password, host, and port

You are prompted to enter the following HTTP connection information:

User
Name

any
valid
user
having
the
UME
SAP_SLD_DATA_SUPPLIER
Password
Server Host the host on which the SLD server is running
Port the HTTP/HTTPS port on which the SLD server is running
Use HTTPS

group:

The program creates the slddest.cfg and slddest.cfg.key files.


The latter file contains the key for encrypting the contents of "slddest.cfg". Protect the
key file as much as possible from unauthorized access( Make sure that users other than
<sapsid>adm do not have read and write permissions for the slddest.cfg.key file)
Using this global directory, all generic data suppliers of the current SAP NetWeaver
system can send data to the same SLD with one central configuration.
Transferring Data to SLD (Registering a host)
Test your configuration by sending detailed data about your computer to SLD:
1.

Enter saposcol b.

A short XML document is printed.


2.

Enter saposcol b | sldreg -connectfile slddest.cfg -stdin -oldtransferdtd.

The oldtransferdtd option is required for compatibility reasons and is specific for
SAPOSCOL only.
The program output is as follows:
HTTP response: Success. HTTP status code: 200
End SLD Registration
Data send status: true
You can see your computer as an SAP_ComputerSystem instance in SLD. In addition,
details such as the sizes of the physical and virtual memory are reported.
Automatic data transfer to the SLD
You can also schedule this command using a "cron job" (UNIX) or a Windows task
(when you start the computer) and/or you can schedule this command periodically. 12
or 24 hours is the standard period for registering information in the SLD.

You might also like