Vmware Adapter for sap landscape Management Administration Guide for LaMa Administrators OpenTopic

n

A minimalist set of OS utiltiies and VLA-specific programs and configuration files required to

provide the functionality described here. These include:

n

The 

vla-service

 — A web service running in 

tomcat

 that receives and processes commands

from the VLA Adapter. It also serves out the VLA dashboard web UI. By default, this server

listens on port 8443.

n

Tomcat user database — Database with usernames / passwords used to authenticate access to

that instance’s services. VI Administrators create an entry in the database for the VLA instance

during deployment of the VLA environment using the 

vla_user

 command as detailed later in

this document.

n

A 

credentials store

 (separate from the username / password database for tomcat access) that

contains information needed for the various components of the VLA environment to

communicate with one another. Each entry in the credentials store includes a component type

(vRealize Orchestrator, LaMa, vCenter Server etc), the hostname and port (if configurable) for

the component’s API, and a username / password used to authenticate to the component’s API.

You create entries in this database using the 

vla_credentials

 command as detailed later in this

document.

VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators

10 

 VMware, Inc.

---

Environment Setup

3

This chapter includes the following topics:

n

“Configure SAP Landscape Management (LaMa),”

 on page 11

n

“Configure DNS,”

 on page 11

n

“VLA Server Side Configuration,”

 on page 13

n

“SAP Landscape Management (LaMa) Side Configuration,”

 on page 13

n

“Configure LaMa to use the VMware Adapter for SAP Landscape Management,”

 on page 15

Configure SAP Landscape Management (LaMa)

In this chapter you discuss various environment setup that you should have in place in order for you to be

able to perform various operations in your existing SAP system infrastructure. The operations themselves

are discussed in chapter 

Chapter 4, “Operations Overview,”

 on page 19. You begin this chapter with a

discussion of the DNS configuration for your SAP Landscape Management (LaMa). Then you learn, how to

configure the VMware adapter for SAP Landscape Management to be able to connect to the VLA server. You

know that the SAP LaMa manages the hosts and instances on the SDDC. The VMware Adapter for SAP

Landscape Management receives LaMa commands and forwards them to the VLA for execution.

Configure DNS

The VLA package includes the 

dnsmasq

 package, which includes a command by the same name. The

following Debian Wiki page, 

https://wiki.debian.org/HowTo/dnsmasq

 describes the 

dnsmasq

 package as

follows: 

dnsmasq

 is a lightweight, easy to configure, DNS forwarder and DHCP server. It is designed to

provide DNS and optionally, DHCP, to a small network. It can serve the names of local machines which are

not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP

allocated addresses to appear in the DNS with names configured either in each host or in a central

configuration file. 

dnsmasq

 supports static and dynamic DHCP leases and BOOTP/TFTP for network booting

of diskless machines.

The 

dnsmasq

 subsystem works as follows:

1

The 

dnsmasq

 package accepts DNS queries.

2

The 

dnsmasq

 package then either answers the DNS queries from its small, local cache or forwards them

to a real, recursive, DNS server.

VMware, Inc. 

 11

---

3

The 

dnsmasq

 package also loads the contents of 

/etc/hosts

 so that local hostnames which do not appear

in the global DNS can be resolved and also answers DNS queries for DHCP configured hosts. The

dnsmasq

 package can thus act as the authoritative DNS server for one or more domains, allowing local

names to appear in the global DNS.

You must configure the VLA server to set up a firewall on 

dnsmasq

 such that only the SAP Landscape

Management (LaMa) VM can use it. You must do this by adding the LVM credentials to the VLA via the

vla_credentials

 command. You must then configure the network settings for all the network interfaces on

the SAP Landscape Management (LaMa) VM to use the 

dnsmasq

 service on the VLA server for domain name

resolution, instead of the regular DNS server. This diagram depicts the DNS configuration setup in your

SAP Landscape before and after you do the following configuration:

Figure 3

‑1.  DNS Configuration - Before

VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators

12 

 VMware, Inc.

---

Figure 3

‑2.  DNS Configuration - After

VLA Server Side Configuration

The 

dnsmasq

 package is installed as part of VLA deployment.

Procedure

u

Enter the following command to setup a firewall on the 

dnsmasq

 such that only the SAP Landscape

Management (LaMa) VM can use it.

vla_credentials -a -n -u -s -P http:50000

where 

-a — Add server credential to VLA

-n — Specify server hostname,the FQDN of your LaMa VM

-u — Speficy username 

-s — Specify ServerType

-P — Schema and port, http:50000 is the protocol and port number here

SAP Landscape Management (LaMa) Side Configuration

Execute the following steps to complete the configuration on the SAP Landscape Management (LaMa) side.

Procedure

1

Open the vCenter client to your SAP Landscape Management (LaMa) VM using root credentials.

2

Change the network settings for all the network interfaces on your SAP Landscape Management (LaMa)

VM in order to use the 

dnsmasq

 service on VLA for domain name resolution.

This is depicted in the following figure:

Chapter 3 Environment Setup

VMware, Inc. 

 13

---