Adding Instances

You use this procedure to add instances to the landscape and make them available for performing operations in SAP Landscape Management.

Prerequisites

You have configured the following:
- Pools
- Networks
If you are using different SAP passwords for hosts of the same system, including replication, you have added and configured the hosts.
- Adding Hosts
- Configuring Hosts
To discover, manage, and monitor SAP HANA as a database, make sure that:
- You have installed the hdbclient on each SAP HANA host.
- You have specified a database user either on the detection screen, in the instance configuration, or in the <HANA-SID> SAPDBCTRL hdbuserstore key for the <hana-sid>adm user.
- You have installed SAP Adaptive Extensions.
  For more information, see SAP Adaptive Extensions.
To discover, manage, and monitor SAP HANA tenant databases, make sure that you comply with all prerequisites described in the Operations Guide for SAP HANA tenant databases.
- If ABAP systems are running on the SAP HANA tenant database:
  
  Discover the systems in your landscape managed by SAP Landscape Management by detecting based on the ABAP hosts. All ABAP instances and assigned tenant databases will be detected properly. This includes SAP HANA tenants with and without ABAP instances.
- If no ABAP systems are running on the SAP HANA tenant database:
  
  Discover the systems in your landscape managed by SAP Landscape Management by detecting based on the SAP HANA tenant hosts.
For more information, see SAP HANA Tenant Databases Operations Guide.
The instances you want to detect are prepared. The virtual hostname is bound and services such as the instance agent are up and running.

The SAP Landscape Management host can connect to the following ports on the managed host:

SAP Host Agent

HTTP	1128
HTTPS	1129

Instance Agent

HTTP	5`<SAPSYSTEM>`13
HTTPS	5`<SAPSYSTEM>`14

Optional: You have configured custom instances.

For more information, see Configuring Custom Instances.

Context

The instances are the individual instances such as the central instance, database instance, dialog instance, TREX instance, liveCache, and so on, that run on one or more hosts.

Ensure that you always detect and configure all individual instances that belong to one system.

Start the detection of SAP NetWeaver systems always on the SAP NetWeaver instance and not on the database instance. Database instances are automatically detected along with the SAP NetWeaver instances.

You can add these instances in the following ways:

Scenario	Source	Description
Find application instances available in the landscape and add them to SAP Landscape Management.	Detect using host and instance agents	SAP Landscape Management directly communicates with the instance agent to retrieve the instance information from the landscape. The instances found are directly configured in SAP Landscape Management.
	Detect on managed hosts	SAP Landscape Management searches for the new instances available on hosts already configured.
	SAP Landscape Management Landscape scanner	You can set the automatic landscape scanning attribute when configuring SAP Landscape Management using the configuration wizard or when configuring the engine settings. The landscape is automatically scanned for newly added host and instances based on the attribute set. The number of instances detected is shown in SAP Landscape Management under Overview.
	Virtualization Manager	SAP Landscape Management searches for new hosts available in the virtualization manager.
	Local System Landscape Directory	SAP Landscape Management retrieves instance details from the local System Landscape Directory using a pre-configured System Landscape Directory destination.
	Remote System Landscape Directory	SAP Landscape Management retrieves instance details from the remote System Landscape Directory by accessing it through the System Landscape Directory URL.
	Detect appliances	SAP Landscape Management detects solution instances in SAP Cloud Appliance Library. Prerequisites for using this source: In SAP Landscape Management you have configured the Amazon virtualization manager. For more information, see Obtaining Virtual Host Details from Virtual Host Provider and SAP Note 1861561 . In SAP Cloud Appliance Library you have created one or more solution instances. For more information, see Creating a Solution Instance in the application help.
Import the instance configuration data	XML file	You reuse the instance configuration data by importing the configuration data to SAP Landscape Management.

Procedure

Choose Configuration Systems.
Choose Discover.
From the Source dropdown box, choose the desired source.

Recommendation Choose Detect Using Host and Instance Agent.

Note If you choose Detect Using Host and Instance Agent as the source and X.509 Client Certificate as the authentication type, all public and private keys must be stored in the key storage. To configure the keys, choose Goto Certificates and Keys: Key Storage.
In the Find dropdown box, specify whether you want to find instances or hosts, or both.

Depending on the source chosen, enter any other information as required:

Checkbox	Description
Include Instances/Hosts Managed Already	To discover instances and hosts already managed, select this checkbox. SAP Landscape Management also discovers the DB2 DPF and Oracle RAC instances as well as MSSQL mirrored databases. SAP Landscape Management cannot manage but monitor these databases.
Include Diagnostics Agents for Instances	To discover and configure the Diagnostics Agent for the corresponding instances based on the SAPLOCALHOST/DBHOST, select this checkbox.
Detect Standalone Databases	To detect databases not related to any SAP system, select this checkbox. Note Standalone databases can only be stopped with the forced shutdown option.
Detect Shadow Databases	To detect inactive databases which are updated by the active system databases select this checkbox. Note You cannot start or stop these shadow databases using SAP Landscape Management. To manage shadow databases, you have to configure custom operations and custom hooks (if included in the system provisioning processes). You have to assign shadow databases manually to the corresponding SAP system.
Ignore Custom Instances	If you do not want to detect custom instances, for example, for performance reasons, select this checkbox.
Detect Single Tenant DB as HANA MDC	To detect a system which can be classified as system with a single tenant database as MDC system, select the checkbox. SAP Landscape Management detects two systems and creates the tenant. Example FRH: SAP HANA multi-tenant database FRH Primary (SiteA) Databases: SAP HANA SAP HANA MDC Instance: Primary(SiteA) MASTER SAP HANA MDC Instance: Primary(SiteA) WORKER SAP HANA MDC Instance: Secondary(SiteB) MASTER SAP HANA MDC Instance: Secondary(SiteB) WORKER FRS: NetWeaver ABAP 7.45 Tenant database Central services AS instance To detect the system which can be classified as system with a single tenant database as single instance together with the application server, keep the checkbox deselected. SAP Landscape Management detects one system without the tenant. Example FRS: NetWeaver ABAP 7.45 FRS Primary(Site A) Databases: SAP HANA System database: Primary(SiteA) MASTER System database: Primary(SiteA) WORKER System database: Secondary(SiteB) MASTER System database: Secondary(SiteB) WORKER Central services AS instance

Depending on the source chosen, choose Detect or Retrieve.
Note
- It is not always possible to find all instances that belong to a system in one step. For example, it is not possible to find a TREX instance that belongs to a given system by running the detection process for a single SAP Host Agent. Therefore, if you want to detect a complete system set, you may need to execute the detection process for multiple SAP Host Agents.
- If problems occur during detection, choose View Detection Issues.
To configure the instances detected using the auto-assign facility, choose Next.
Save your entries.

Results

The instances detected are added to an existing pool and are available to perform operations without any further configuration.