Connect SLD Data Supplier to SLD Forwarder (FRUN)

Contents
Connect SLD Data Supplier to SLD Forwarder (FRUN)................................................................1
1. Identify SAP System/s from it:admin..........................................................................................2
ABAP/JAVA...................................................................................................................................2
HANA Database..............................................................................................................................4
Scenario 1 - HANA without Replication server......................................................................4
Scenario 2 - HANA with Replication server...........................................................................5
2. Take note the customer SLDR FQDN.........................................................................................5
3. Connect Managed ABAP system with HTTP.............................................................................6
3.1 Logon at the Managed ABAP system.......................................................................................6
3.2 Create HTTP Destination with report RSLDHTTPCONF........................................................6
3.3 Test HTTP-RFC "SLD_DS_SLDR".........................................................................................7
3.4 Adding HTTP Destination to SLD-Connection using report RSLDHTTPCONF....................8
3.5 Transmit SLD data and check transmission results.................................................................10
3.6 Prepare SDCCN.......................................................................................................................10
3.6.1 Create new RFC "SDCC_FRP"....................................................................................11
3.6.2. Adapt RFC at SM59 - Change SSL Identity / certificate............................................12
3.6.3 Activate SDCCN with new RFC..................................................................................14
4. Connect JAVA/J2EE stacks......................................................................................................16
5. Connect HANA database...........................................................................................................29
5.1.1 HANA Replication DB................................................................................................29
5.1.2 Main HANA DB: Check if any existing SLD connection...........................................29
5.1.3 SLD Registration..........................................................................................................31
Is your HDB version <= 1.00.122.12 or <= 2.00.012? Then follow the Solution below:.............31
Is your HDB version > 1.00.122.12 or > 2.00.012? Then go on here!..........................................34
5.1.3 Adapt SLD Parameter for HANA DB  Usually this part is done during
installation, please verify and perform when necessary........................................................36
6. Connect SLD for SAP Mobile Platform...................................................................................42
7. Connect SLD Data Supplier - SAP Web Dispatcher.................................................................44
8. Connect Application Kernel......................................................................................................44
Configuration:................................................................................................................................44
UNIX.............................................................................................................................................44
Windows........................................................................................................................................48
Checking Results:..................................................................................................................51
UNIX.....................................................................................................................................51
Windows................................................................................................................................52
9. Have you done Step 6 for ABAP and JAVA / Webdispatcher?................................................53
Error! Hyperlink reference not valid.Error! Hyperlink reference not valid.Error!
Hyperlink reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink
reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink reference not
valid.Error! Hyperlink reference not valid.Error! Hyperlink reference not valid.Error!
Hyperlink reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink
reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink reference not
valid.Error! Hyperlink reference not valid.Error! Hyperlink reference not valid.Error!
Hyperlink reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink
reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink reference not
valid.Error! Hyperlink reference not valid.Error! Hyperlink reference not valid.Error!
Hyperlink reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink
reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink reference not
valid.Error! Hyperlink reference not valid.Error! Hyperlink reference not valid.Error!
Hyperlink reference not valid.Error! Hyperlink reference not valid.Error! Hyperlink
reference not valid.Error! Hyperlink reference not valid.

Description

This article describes how to connect SLD Data Suppliers to SLD Forwarder (SLDR).

1. Identify SAP System/s from it:admin

First step is to verify via it:admin System Overview which component/s (ABAP and/or JAVA) to
connect in the SLDR :

ABAP/JAVA
A system may have ABAP instances and/or Java instances. To identify this, have a look at the
system overview.

You can use the “Global search” field in the it.admin and key-in the hostname and hit enter.
This will open the system details under Inventory tab.

Click on at least Server Name and this will give you the option to scroll on its System Overview.
If you have only an ABAP instance, proceed with Step 1. Connect managed ABAP system with
HTTP.

If you have only JAVA instance, proceed with Step 2. Connect J2EE stacks.

If you have both instances (ABAP and JAVA), you have to connect both systems.

In the screenshot above, you can see Sybase database, there is no additional step to be taken,
however for HANA database, follow steps below.

HANA Database
For HANA Databases we have different situations and there are two possible implementations to
be aware of. For both scenarios go on with 3. Connect HANA DB.

Scenario 1 - HANA without Replication server

This scenario describes a HANA database with only one server (eg. sesvdb11)
Scenario 2 - HANA with Replication server

In this scenario in addition to the first HANA Database server, a replication HANA Database
server is also existing using a virtual server/resource (eg. sessps0d)

2. Take note the customer SLDR FQDN

In the following steps you will need the Host Name of the SLDR (FQDN) several times.
Therefore, once customer’s SLDR is define, write it down as you will reuse it several times.

You may refer to this path of the SLDR host  L:\02 Hosting\Monitoring Documentation\01.
Project\FRUN 2.0\09. MY FRUN - Implementation\I. Preparation\SLDR and Wily Service IP
and FQDN

3. Connect Managed ABAP system with HTTP

ABAP

3.1 Logon at the Managed ABAP system

Open the SAPLogon Pad!

Logon to the system:

Client: 000
User: [e.g. it.sysadm]
Password: [see PassVault]

3.2 Create HTTP Destination with report RSLDHTTPCONF

SE38  Program  RSLDHTTPCONF  Go to tab “Create HTTP Destination” and fill out
the fields with the following information.
 Fields Template Example
HTTP Destination SLD_DS_SLDR SLD_DS_SLDR
SSL Status (HTTPS) <empty> <empty>

Host Name (SLD Host of SLD

= SLD FQDN = <csn>sldr0. mmhsldr0.mydin-sap.local
Forwarder)
[custdomain]
Port (Service No.) 8900 8900

User Name FRN_SLDS_[CSN] FRN_SLDS_MMH

see PassVault see PassVault

Password (Search "FRN_SLDS_[CSN]" as (Search FRN_SLDS_CSN
text) as text)

Confirm with

Expected Result:

3.3 Test HTTP-RFC "SLD_DS_SLDR"

Transaction SM59  Search "*SLD_DS_SLDR*"  Button "Connection Test"
Expected Result: Below result is acceptable.

From SAP note: 2188401 - Enabling HTTP(S) in RZ70

Remark: When you perform a connection test for the created HTTP connection in SM59, the
SLD responds with an error code "400 Bad Request - Error: Bad request. Parse error: Premature
end of file."
This error message can be ignored, as long as the data sent via RZ70 arrives in the SLD.

3.4 Adding HTTP Destination to SLD-Connection using report

RSLDHTTPCONF
SA38  report RSLDHTTPCONF  RZ70 Configuration tab  Option “Add”
Insert the name of HTTP Destination just recently created (SLD_DS_SLDR) and execute
with

Check Result:

Option 1

SA38 report RSLDHTTPCONF  part “RZ70 Configuration”  Option "Show" 

Option 2

Transaction code RZ70  HTTP Destination SLD_DS_SLDR is displayed at RZ70 part

"HTTP(S) Connections to SLD"
Attention:
NW 750, SP0 / NW 740 SP13 and higher already contains the new UI.
For NW ABAP < 740 SP13, Import SAP Note 2188401 with SNOTE and transport according to
transport policy. The SAP note provides function module to create SM59 HTTP destination and
assign it to RZ70. Enabling of HTTP in RZ70 is only supported in SAP_BASIS ≥ 700 SP4.

3.5 Transmit SLD data and check transmission results

Transaction cod RZ70 

If you have configure a RFC and http connection at RZ70 the SLD data will be sent twice.

Do not change any configuration set-up in the RZ70 initial page (leave as is entry of RZ70 in
ABAP

*sample above is customer’s own SLD

3.6 Prepare SDCCN

3.6.1 Create new RFC "SDCC_FRP"

Create new RFC "SDCC_FRP"

Transaction Code  SA38  User Report /BDL/CREATE_HTTP  execute

Use the following information to complete the set-up

General TESTING ACTUAL (LIVE)

HTTP Destination SDCC_FRP SDCC_FRQ SDCC_FRP

Mark the checkbox Mark the checkbox

SSL Status (HTTPS) Mark the checkbox (Active)
(Active) (Active)
my- my-
Host Name frunrp.os.itelligence. frunfp.os.itelligence.com.m my-frunrp.os.itelligence.com.my
com.my y
Port (Service No.) 44300 44302 44300
Path Prefix /sap/bc/sdf/sdcc/ /sap/bc/sdf/sdcc/ /sap/bc/sdf/sdcc/
do NOT mark the
Force Mode do NOT mark the checkbox do NOT mark the checkbox
checkbox

User Name
FRN_EWA_<CSN> FRN_EWA_MMH FRN_EWA_<CSN>
<see Passvault>
Password <see Passvault> <see Passvault>
Filter FRN_EWA_*
Repeat Password <see Passvault> <see Passvault> <see Passvault>
Start creating RFC with the Execute Button

Expected Result:

3.6.2. Adapt RFC at SM59 - Change SSL Identity / certificate

Adapt RFC

The report from SAP Note 2359359 does not setup the correct client certificate.

The correct identity (correct certificate) prepared for FRUN at STRUST has to be selected at the
RFC and save.

Expected Result:
If there is no “FRUN FRUN EWA” SSL such as above, please put a remark "To be prepared"
in migration spreadsheet column “EWA Preparation (SDCCN) (ABAP only)”. TSM needs to
create this entry in the ABAP system. Once TSM created the FRUN EWA SSL entry, upload
the customer PSE file via STRUST. Please refer below document under section [Action =
SolMan team].
L:\02 Hosting\Monitoring Documentation\01. Project\FRUN 2.0\09. MY FRUN -
Implementation\I. Preparation\FRUN EWA Preparation Managed System (ABAP).docx

3.6.3 Activate SDCCN with new RFC

Activate SDCCN

Transaction code SA38 User Report /BDL/CONFIGURE_SDCCN_HTTP  execute

Use the following information to complete the set-up:

 General Example
HTTP Destination SDCC_FRP SDCC_FRP

User with Role Any available user for job like

Job User
SAP_SDCCN_ALL
IT.BATCH or BATCH or IT.CCMS
Enable HTTP active Active
Schedule periodic
deactivate deactivate
EWA

Start configuration with the Execute Button

Result:

Refer to this link if the output is different from above.

Once activated successfully, update the spreadsheet in column “EWA Preparation (SDCCN)
(ABAP only)”
4. Connect JAVA/J2EE stacks
Use Netweaver Admin for Netweaver 71 and higher and use Visual Administrator for Netweaver
7.0.x)

The following screenshots are for NW 7.1 or newer (If screenshots do not fit, you probably have
an older NW version.

1. Call URL: http://<fqdn of managed host>:<5xx00>/nwa where xx = instance # to

logon at the Java Managed System.

In case of unclear port, check it:admin entries. You may find the URL in the description
column of J2EE_ADMIN or Administrator.
>> Login with User J2EE_ADMIN or Administrator

2. Go To: Configuration tab >> Infrastructure >> Destinations >> Tab Destinations >>
SLD_DataSupplier
For SAP Netweaver 7.0 (the path is different) > Configuration>>Destinations

Check the current configuration and the user maintained under logon data
=> If there are NO entries here proceed in Step 3.

If there are any entries, meaning, there is a customer connection already configured. Then we
have to add the connection to the Outbound Connections of the SLD Forwarder (See SLD
Forwarder (SLDR) - add an additional Outbound Connection (9631)) before proceeding here!

Ex:

3. In this view (Configuration or Configuration Management >> Infrastructure >> Destinations

>> Tab Destinations >> SLD_DataSupplier) click the button "Edit" >> Maintain Connection
Data at Tab "Connection and Transport" as follows:

Example
Destination SLD_DataSupplier SLD_DataSupplier
URL (SLD
= http://SLD FQDN:8900 http://nuisldr0.npm-
Host of SLD
=http://[cns]sldr0.[custdomain]:8900 sap.os.itelligence.com.my:8900
Forwarder)
System ID <empty> <empty>
Client <empty> <empty>
Language <empty> <empty>
4. In this view (Configuration Management >> Infrastructure >> Destinations >> Tab
Destinations >> SLD_DataSupplier) in edit mode go to the tab "Logon Data" and Maintain
Connection Data as follows:

Example
Authentication Basic (User ID and Password) Basic (User ID and Password)
FRN_SLDS_KWS
User Name: FRN_SLDS_[CSN]
*change the CSN based on your customer
see PassVault see PassVault
Password:
(Search FRN_SLDS_[CSN]) (search FRN_SLDS*)
5. Save your action with Button "Save"

6. Test your input by clicking the button "Ping Destination"

6. Then send SLD data and check result

Go To: Configuration  Infrastructure  SLD Data Supplier Configuration  Button "Collect

and Send Data"
Click the button “Collect and Send Data” after a short loading time - the row "Target URL" and
"Success" should be updated with the latest SLDR connection.

Beneath the headline the results are displayed as well.

Note: For SAP Netweaver 7.0x, the interface may be different <refer below>
And for to trigger the transfer of SLD data, Start the J2EE Engine Visual Administrator.

1. Choose Cluster ServerServicesSLD Data Supplier.

2. On the Runtime tab in the right frame, select the HTTP Settings tab.

3. Enter the data required for the HTTP connection from the SLD service to the SLD as
follows:

Host: Enter the SLDR fqdn.

Port: SLDR port (8900)
User: FRN_SLDS_<CSN>
Password: Enter the user password.
4. Save your entries.

5. To test your settings by sending test data to the SLD, click the blue arrow with the quick info
text Trigger data transfer to System Landscape Directory.
Verify in FRUN LMDB if Data Supplier Completeness Check has been updated.

In case above doesn’t work, you may also need to perform below, step 6 is not applicable in this
version:

Log in to SLD URL

http://<hostname>:5<system number>00/sld
URL : SLDR ex: http://alpsldr0.allied-sap.local:8900
USER : FRN_SLDS_ALP
PW: refer to itadmin

Then save
Restart SLD to start the send process
It will take sometime to reflect in LMDB of FRUN (wait at least 30 mins)

5. Connect HANA database

5.1.1 HANA Replication DB

ATTENTION: If you have a HANA replication DB you have to do this step on both HANA
systems (see also top of the page description of HANA replication scenario)

5.1.2 Main HANA DB: Check if any existing SLD connection

- As “root” logon to the managed system DB host

Execute the following commands to check, if there is an existing SLD connection
Commands:
export LD_LIBRARY_PATH=/usr/sap/hostctrl/exe/
/usr/sap/hostctrl/exe/sldreg -showconnect /hana/shared/[SID]/global/slddest.cfg

Example:

Check if there is an entry:

If there is an entry (as shown above, where the “host_param” parameter maintained is not the
SLDR fqdn.
In this case,
1. Add an outbound connection to SLDR as described in SLD Forwarder (SLDR) - add an
additional Outbound Connection (9631) using the displayed data as follows:

URL: [http(s)://][host_param]:[port_param]/sld/ds

If https_param = 'n' use "http://" - if https_param = 'y' use "https://"

For the example shown above this would be "http:// my-msolp2.it-sap.os.itelligence.com.my:50200/sld/ds"
User: user_param for the example above this would be SLD_CEN_CBQ
Password: See PassVault or contact the administrator if not available in PassVault.

2. After adding the outbound connection to SLDR, proceed to the next step – SLD
Registration

5.1.3 SLD Registration

Check HANA Version

command
su - [sid]adm -c "HDB version | grep version"

Result:

Is your HDB version <= 1.00.122.12 or <= 2.00.012? Then

follow the Solution below:
Put the HDB version in the migration file.
===============================
HANA Version with SLD bug! Known problem - error was not provoked. If you have the HANA know how - please implement the solution
from the following link HANA - does not send SLD data. Thanks.
===============================

Please don't solve the problem by your own.

Solution - SLD registration with HDBLCM get stuck

SLDREG BUG at HANA 1.0 (SPS12) revision < 122.12 or HANA 2.0 revision < 12

=> Have a look at issue 24 of SAP Note 2082466

 1. Use directly the SLDREG tool instead of HDBLCM. Log on as sidadm and execute:

sldreg -usekeyfile -configure /usr/sap/<SID>/SYS/global/slddest.cfg

2. Enable the SLD registration via Cockpit or studio - set the value of parameter in
nameserver.ini, section [sld] lmStructurePath = <inst_path>/<SID>/lm_structure; set the
value of parameter in nameserver.ini, section [sld] enable = yes

Fields General Template Example for customer MMH

User Name: FRN_SLDS_[CSN] FRN_SLDS_MMH
Password: <see Passvault> <see Passvault>
Server Host = SLD FQDN =[csn]sfor0.[custdomain] mmhsldr0.mydin-sap.local
= SLDR Host
Name
Port 8900 8900
Use HTTPS? n n
*already active*

Checking Results:
Command:
As <sid>adm
cd /usr/sap/MED/SYS/exe/hdb
sldreg -showconnect /usr/sap/MED/SYS/global/slddest.cfg
md-hmesd0:/hana/shared/MED/HDB00/md-hmesd0/trace> more sldreg.log

Note - Does it have HANA replication server? If yes, perform the SLD registration in the
replication server too as <sid>adm (of the Primary HANA DB).

Is your HDB version > 1.00.122.12 or > 2.00.012? Then go on

here!
- Start hdblcm with option configure_sld
Command: Log on as <sid>adm and execute

/hana/shared/[SID]/hdblcm/hdblcm --action=configure_sld

Example
/hana/shared/BIP/hdblcm/hdblcm --action=configure_sld

General: Example:
 = SLD FQDN =[csn]sfor0.
SLD Host Name mmhsldr0.mydin-sap.local
[custdomain]
Port 8900 8900
User Name: FRN_SLDS_[CSN] FRN_SLDS_MMH
Password: <see Passvault> <see Passvault>
Use HTTPS? n n
Note: Cannot connect
to SLD system. Check
the SLD host name
and port. y y

Do you want to
continue? (y/n):

If the command does not receive a result after 3 minutes, please cancel the SLD connection
with the "CTRL" + "c" keys. After this take a Screenshot and update the migration file.
(Link HANA - does not send SLD data)

Restart the service (as <sid>adm)

1. to send the payload /usr/sap/<DBSID>/HDB<inst>/exe> sapcontrol -nr <instance> -
function RestartService

Checking Results

Command:

/usr/sap/H03/HDB00/iblvs03d/trace/sldreg.log

Result:
If the sldreg.log file is not updated or missing, try to send the SLD data again using command
below and check the output (using <sid>adm user):

/usr/sap/H03/HDB00/exe/sldreg -connectfile /usr/sap/H03/SYS/global/slddest.cfg -file

/usr/sap/H03/HDB00/iblvs03d/trace/sldreg.xml

STOP - Does it have HANA replication server? If yes, perform the SLD registration in the
replication server and log in as <sid>adm of the Primary HANA DB.

Note: If hdblcm was executed the first time, the Data transfer is triggered immediately. If an existing
configuration is changed, the data will be send within the next 12 hours.

5.1.3 Adapt SLD Parameter for HANA DB  Usually this part is done during
installation, please verify and perform when necessary.

Pre checks:

1. Hana DB version – run command

2. Verify HANA if it has system replication – verify with TSM or check in HANA studio.

Check HANA Version

-Check HANA Version
Command
su - [sid]adm -c "HDB version | grep version"
Result:
FOLLOW THE PROCEDURE BELOW BASED ON THE PRE CHECKS RESULT:
If your HDB version check result is HANA 1.0 SPS12 Rev16: 1.00.122.16; HANA 2.0 SPS01
Rev04: 2.00.012.04; HANA 2.0 SPS02 Rev23: 2.00.023 and higher

Follow Procedure 1 for HANA without System Replication

HANA (1.0/2.0) without System Replication

Follow Procedure 2 for HANA that has system replication

HANA (1.0/2.0) with System Replication

If your HDB version is <= 1.00.122.12 HANA DB (lower versions)

Follow Procedure 3 for HANA without System Replication

HANA (1.0/2.0) without System Replication

Follow Procedure 4 for HANA that has system replication

HANA (1.0/2.0) with System Replication

Procedure 1 for HANA without System Replication

Example of HANA Database without HANA System Replication (e.g. md-hmeq00)

Please set Parameter for SLD here: /usr/sap/[SID]/SYS/global/hdb/custom/config/global.ini

Section: [system_landscape_hostname_virtualization] via HANA studio or OS level:

The files can be changed during a running HANA - no downtime needed.

SLDSYSTEMHOME needs to be set to the same value as reported by the Application system (e.g. ABAP
or JAVA).
SLDSYSTEMHOME = [service resource name of database / logical name]
= same value of parameter SAPDBHOST in RZ10

RZ10

HANA Studio

HANA Studio
Procedure 2 for HANA that has system replication

To be able to model the relationships above we had to introduce a new parameter for SAP HANA which will be
handled as of revision 110. The parameter is called SLDVIRTDBHOME and contains the logical hostname under
which the SAP HANA DB can always be reached. As the SAP HANA is installed and a SR system there must be one
logical hostname that moves from the primary to the secondary site in case a fail-over to the replicated system
happens. This is the host that has to go into the parameter SLDVIRTDBHOME.

Example of HANA Database with System Replication (e.g. vresphdd)

Please set Parameter for SLD here: /usr/sap/[SID]/SYS/global/hdb/custom/config/global.ini

Section: [system_landscape_hostname_virtualization] via HANA studio or OS level:

The files can be changed during a running HANA - no downtime needed.

vresphdd = service resource name (logical name) of the HANA hosts which is switched to the secondary side in case
of a takeover:
HANA-Hostname: for example vrevphd0 [primary host name]
sldsystemhome = vrevphd0 [primary host name]
sldvirtdbhome = vresphdd
HANA-Hostname Replication: for example vrevphd1 [primary host name]
sldsystemhome = vrevphd1 [primary host name]
sldvirtdbhome = vresphdd

[For SOLMAN TEAM ONLY]

2. Trigger generation of sldreg.xml and transfer of SLD data:

The files can be changed during a running HANA - no downtime needed.

/usr/sap/[SID]/SYS/global/hdb/custom/config/nameserver.ini  via HANA studio
Section: [sld]
enable = yes
enable_virtdbhome = no | yes (if your DB has a virtual name) - see SAP Note 2667806
lmstructurepath = /hana/shared/[SID]/lm_structure
1. Change parameter "enable" to "no" >> save file
2. Change parameter "enable" back to "yes" >> save file
=> SLD data transfer with a new sldreg.xml was triggered without a downtime.
=> For HANA Replication you have to do it at both sides.

Procedure 3 for HANA without System Replication

 HANA DB lower versions
Normally the Parameter have to setup at the HANA DEFAULT.PFL (located under /usr/sap/<SID>/SYS/profile).
Changes at this profile requires a restart of the HANA DB.

Add the parameter SLDSYSTEMHOME=<SAPDBHOST known in RZ10> or <MASTER Hostname> to the

HANA DEFAULT.PFL profile.

Example: HANA DB md-hmesd0 without System Replication

HANA-Hostname: for example md-hmesd0 [primary host name]

Profile: HANA DEFAULT.PFL (located under /usr/sap/<SID>/SYS/profile)
SLDSYSTEMHOME = md-hmesd0
Reminder: To activate the new parameters both HANA Systems and the ABAP / JAVA System have to be
restarted.

Procedure 4 for HANA that has system replication

Example: HANA DB with logical db host and with SR (e.g. spesp70d)

SAP AS ABAP Server: for example spevp010 [primary host name] or spesp01s [service resource name
(logical name) of SAP application server host]
Profile: DEFAULT.PFL (in RZ10)
SLDSYSTEMHOME = spesp70d [service resource name (logical name) of database host]
HANA DB-Server Main: for example spevp700 [primary host name]
Profile: HANA DEFAULT.PFL (located under /usr/sap/<SID>/SYS/profile)
SLDSYSTEMHOME = spevp700 [primary host name]
SLDVIRTDBHOME = spesp70d [service resource name (logical name) of database host]
HANA DB-Server Replication: for example spevp701 [primary host name]
Profile: HANA DEFAULT.PFL (located under /usr/sap/<SID>/SYS/profile)
SLDSYSTEMHOME = spevp701 [primary host name]
SLDVIRTDBHOME = spesp70d [service resource name (logical name) of database host]
Reminder: To activate the new parameters both HANA Systems and the ABAP / JAVA System have to be
restarted.

Reference:

https://itfluence.itelligencegroup.com/display/AppOps/02.04+FRUN+Prerequisites+for+Database+System#expand-
HANAReplication1020
https://wiki.scn.sap.com/wiki/display/TechOps/SLD+Registration+for+SAP+HANA+SR+systems

6. Connect SLD for SAP Mobile

Platform
1. Login to Mobile Platform 3.0
2. In the Management Cockpit  Settings  System Landscape Directory

3. Enter the system landscape directory settings:

 Property Description Default Notes

SLD server host Name or IP address of the system None Example: mmhsldr0.mydin-sap.local
landscape directory server. Data
will be uploaded to this server.
SLD server port None
Port number used for 8900
communication with the system
landscape directory server.
Use HTTPS
Indicates whether to use HTTP or HTTP OFF
HTTPS.
Username for FRN_SLDS_MMH
accessing SLD The username for the account None
server accessing the system landscape
directory.
Password for The password for the account <refer to it.admin>
accessing SLD accessing the system landscape None
server directory.
Enable SLD
upload Indicates whether to automate None
periodically ON
periodic upload of data to the
system landscape directory.
SLD upload
interval Identify the interval for periodic None 1
upload of data.
SLD upload time
unit Identify the interval for periodic None Example: enter “Hours”.
upload of data (select Minutes, For this example, data would be uploaded
Hours, or Days). once per hour.

4. Click Save.
5. In the same page at Management Cockpit, you can see the following options at the bottom of
the screen.

6. (Optional) Click Ping to ensure you can access the SLD server.
 Note – this will give an error but just ignore.

7. Click Upload Payload to perform the initial upload of SAP Mobile Platform system data to the
SLD (Host, Port, and Username of the SLD must be configured prior to this step). The SAP
Mobile Platform Server sends the formatted server information to the SLD server, and shows
the result on Management Cockpit.

8. You can access LMDB in FRUN to verify the settings were uploaded.
9.

7. Connect SLD Data Supplier - SAP Web

Dispatcher
UNIX

Logon at the OS level (until you are root user)

Change user to <sid>adm

su - <sid>adm
Change Folder:
cdglo or cd /usr/sap/<SID>/SYS/global

Start SLD Registration:

./sldreg -configure slddest.cfg -usekeyfile

Fill in the following information:

General template: Example:

User Name: FRN_SLDS_[CSN] FRN_SLDS_MMH
Password: <see Passvault> <see Passvault>
= SLD FQDN =[csn]sldr0. mmhsldr0.mydin-
Server Host:
[custdomain] sap.local
Port 8900 8900
Use HTTPS? n n
Use Proxy? n n
Write this information to secure file
'slddest.cfg' and generate key file yes yes
'slddest.cfg.key'?

Windows

Open Command Prompt (CMD)

=> find out the drive letter for /usr/sap/[SAPSID]

=> Start SLD Reg

command examples:
"[drive letter]:\usr\sap\[SAPSID]\SYS\exe\uc\NTAMD64\sldreg.exe" -configure [drive
letter]:\usr\sap\[SAPSID]\SYS\global\slddest.cfg -usekeyfile

Example with values:

"E:\usr\sap\E01\SYS\exe\uc\NTAMD64\sldreg.exe" -configure E:\usr\sap\E01\SYS\global\
slddest.cfg -usekeyfile
=> Input parameter for SLD Reg:

General: Example:
User Name: FRN_SLDS_[CSN] FRN_SLDS_NUI
Password: <see Passvault> <see Passvault>
= SLD FQDN =[csn]sfor0. nuisldr0.npm-
Server Host:
[custdomain] sap.os.itelligence.com.my
Port 8900 8900
Use HTTPS? n n
Use Proxy? n n
Write this information to
secure file 'slddest.cfg'
yes yes
and generate key file
'slddest.cfg.key'?

For Restart the service of the sapstartsrv instance - How I get a list of sapinstances?

Command examples:
"C:\Program Files\SAP\hostctrl\exe\saphostctrl.exe" -function ListInstances

Results:
C:\Users\dci10413>"C:\Program Files\SAP\hostctrl\exe\saphostctrl.exe" -function ListInstances
Inst Info : D42 - 92 - bitve011 - 720, patch 401, changelist 0
Inst Info : DAP - 95 - bitse01s - 749, patch 301, changelist 1779613
Inst Info : E01 - 00 - bitse01s - 753, patch 324, changelist 1901505
Inst Info : E01 - 01 - bitve011 - 753, patch 324, changelist 1901505
Inst Info : EA1 - 04 - bitse01s - 753, patch 319, changelist 1893869

=> if you have done the SLD registration for system E01 you have to restart instances 00 and 01

For Restart you have two options - SAP MMC or Command Prompt

SAP Management Console

Command Prompt:
Command to restart the Service - (SAP System was not affected by this)
E:\usr\sap\[SID]\SYS\global\sapcontrol -nr [instancenumber] -function
RestartService -user [sidadm] [password from PassVault]
or
E:\usr\sap\[SID]\[Instance_name]\exe\sapcontrol -nr [instancenumber] -function
RestartService -user [sidadm] [password from PassVault]
or
E:\usr\sap\[SID]\[Instance_name]\exe\sapcontrol -nr [instancenumber] -function
RestartService -user [other os-user] [password from PassVault]

8. Connect Application Kernel

We need SLD data of each Application Instance Kernel (ABAP / JAVA).

Configuration:

UNIX

Logon at the OS level (until you are root user)

Change user to <sid>adm

su - <sid>adm -- if a host contains ABAP and JAVA instance, perform on each application as <sid>adm (ABAP) and <sid>adm
(JAVA)

Change Folder:
cdglo or cd /usr/sap/<SID>/SYS/global

Start SLD Registration:

./sldreg -configure slddest.cfg -usekeyfile

Fill in the following information:

General template: Example:

User Name: FRN_SLDS_[CSN] FRN_SLDS_MMH
Password: <see Passvault> <see Passvault>
= SLD FQDN =[csn]sldr0. mmhsldr0.mydin-
Server Host:
[custdomain] sap.local
Port 8900 8900
Use HTTPS? n n
Use Proxy? n n
Write this information to secure file
'slddest.cfg' and generate key file yes yes
'slddest.cfg.key'?

Refer to this path to get the SLDR of the customer  L:\02 Hosting\Monitoring Documentation\
01. Project\FRUN 2.0\09. MY FRUN - Implementation\I. Preparation\SLDR and Wily Service
IP and FQDN

*didn’t ask for Use Proxy unlike DE system sample below*

If you are logged on as <sid>adm:
logout

Restart the service of the sapstartsrv instance –

How do I get the list of sapinstances?

/usr/sap/hostctrl/exe/saphostctrl -function ListInstances

Result:
md-med00:~ # /usr/sap/hostctrl/exe/saphostctrl -function ListInstances
Inst Info : DA1 - 96 - md-med00 - 753, patch 300, changelist 1876288
Inst Info : MED - 00 - md-med00 - 745, patch 400, changelist 1734487
Inst Info : MED - 01 - md-med00 - 745, patch 400, changelist 1734487
Inst Info : DAA - 90 - md-med00 - 753, patch 300, changelist 1876288
md-med00:~ #

=> in this example , system MED you have to restart Instances 00 and 01

Command to Restart the Service - (SAP System was not affected by this restart)
su - [sid]adm -c "sapcontrol -nr [instancenumber] -function RestartService"

Example:
su - medadm -c "sapcontrol -nr 00 -function RestartService"
su - medadm -c "sapcontrol -nr 01 -function RestartService"
Windows

Open Command Prompt (CMD)

=> find out the drive letter for /usr/sap/[SAPSID]

=> Start SLD Reg

command examples:
"[drive letter]:\usr\sap\[SAPSID]\SYS\exe\uc\NTAMD64\sldreg.exe" -configure [drive
letter]:\usr\sap\[SAPSID]\SYS\global\slddest.cfg -usekeyfile

Example with values:

"E:\usr\sap\E01\SYS\exe\uc\NTAMD64\sldreg.exe" -configure E:\usr\sap\E01\SYS\global\
slddest.cfg -usekeyfile
=> Input parameter for SLD Reg:

General: Example:
User Name: FRN_SLDS_[CSN] FRN_SLDS_NUI
Password: <see Passvault> <see Passvault>
= SLD FQDN =[csn]sfor0. nuisldr0.npm-
Server Host:
[custdomain] sap.os.itelligence.com.my
Port 8900 8900
Use HTTPS? n n
Use Proxy? n n
Write this information to
secure file 'slddest.cfg'
yes yes
and generate key file
'slddest.cfg.key'?

For Restart the service of the sapstartsrv instance - How I get a list of sapinstances?

Command examples:
"C:\Program Files\SAP\hostctrl\exe\saphostctrl.exe" -function ListInstances

Results:
C:\Users\dci10413>"C:\Program Files\SAP\hostctrl\exe\saphostctrl.exe" -function ListInstances
Inst Info : D42 - 92 - bitve011 - 720, patch 401, changelist 0
Inst Info : DAP - 95 - bitse01s - 749, patch 301, changelist 1779613
Inst Info : E01 - 00 - bitse01s - 753, patch 324, changelist 1901505
Inst Info : E01 - 01 - bitve011 - 753, patch 324, changelist 1901505
Inst Info : EA1 - 04 - bitse01s - 753, patch 319, changelist 1893869

=> if you have done the SLD registration for system E01 you have to restart instances 00 and 01

For Restart you have two options - SAP MMC or Command Prompt

SAP Management Console

Command Prompt:
Command to restart the Service - (SAP System was not affected by this)
E:\usr\sap\[SID]\SYS\global\sapcontrol -nr [instancenumber] -function
RestartService -user [sidadm] [password from PassVault]
or
E:\usr\sap\[SID]\[Instance_name]\exe\sapcontrol -nr [instancenumber] -function
RestartService -user [sidadm] [password from PassVault]
or
E:\usr\sap\[SID]\[Instance_name]\exe\sapcontrol -nr [instancenumber] -function
RestartService -user [other os-user] [password from PassVault]

Checking Results:
You have to check the following files for each affected instance:

UNIX

verify the logs:

more /usr/sap/[SID]/[Instance_name]/work/dev_sldregs
or
more /usr/sap/[SID]/[Instance_name]/work/dev_sldregk

For JAVA System:

/usr/sap/<SID>/J<Instance Number>/work/dev_sldregk , dev_sldregs

For Web Dispatcher:

Check logs and XML /usr/sap/<SID>/W<Instance Number>/work/ if the dev_sldregk, dev_sldregs
and sapstartsrv_sld.xml are correctly generated

Example:
more /usr/sap/MED/DVEBMGS00/work/dev_sldregs
more /usr/sap/MED/ASCS01/work/dev_sldregs
Check HTTP response: Success. HTTP status code: 200

Windows

Get Instance names:

dir [drive letter]:\usr\sap\[SAPSID]

Example:
C:\Users\Administrator>dir E:\usr\sap\OEP

Volume in drive E is EXE Volume Serial Number is B295-8E12

Directory of E:\usr\sap\OEP
10.12.2015 08:48 <DIR> .
10.12.2015 08:48 <DIR> ..
25.08.2015 14:46 <DIR> ASCS01
25.08.2015 14:46 <DIR> DVEBMGS00
28.08.2015 14:47 <DIR> idocs
25.08.2015 12:35 <DIR> SYS
25.05.2019 13:54 <DIR> tmp 0 File(s) 0 bytes 7 Dir(s)
42.431.586.304 bytes free

Open the logfile

more E:\usr\sap\[SAPSID]\[Instance_name]\work\dev_sldregs
or
more E:\usr\sap\[SAPSID]\[Instance_name]\work\dev_sldregk

Example:

more E:\usr\sap\OEP\ASCS01\work\dev_sldregk

Example content of Logfile

Thu Mar 28 13:56:14 2019 ******************************

Thu Mar 28 13:56:14 2019 HTTP open timeout = 420 sec
Thu Mar 28 13:56:14 2019 HTTP send timeout = 420 sec
Thu Mar 28 13:56:14 2019 HTTP response timeout = 420 sec
Thu Mar 28 13:56:14 2019 Used URL: http://iossfor0.os.itelligence.de:8900/sld/ds
Thu Mar 28 13:56:14 2019 HTTP open status: true - NI RC=0
Thu Mar 28 13:56:14 2019 HTTP send successful.
Thu Mar 28 13:56:15 2019 Return code: 200 --- Return message: (OK)
Thu Mar 28 13:56:15 2019 HTTP response: Success. HTTP status code: 200
Thu Mar 28 13:56:15 2019 ****************************
Thu Mar 28 13:56:15 2019 *** End SLD Registration ***

Both logfiles should be from the current date and have the http status code 200!
9. Have you done Step 6 for ABAP and
JAVA / Webdispatcher?
Yes - Perfect! You are done.

No - You have to do step 5 for ABAP and Java (on in Webdispatcher). This needs to be done in
each instance. Note that the Java part may be based on a different SID than ABAP.