Scribd
Upload
5 views

Installation_scenarios_for_a_standalone_ASCS_instance_1739783232

The document outlines the installation scenarios for a standalone ABAP central services instance (ASCS) on a separate host, emphasizing the importance of high availability (HA) configurations. It details the use of SAPinst for installation and the necessity of third-party vendor solutions for ensuring HA in standalone setups. Additionally, it provides guidance on RFC connections and the importance of logon groups for maintaining connectivity and load balancing in the SAP landscape.

Uploaded by

8pgckvkccc
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

Installation_scenarios_for_a_standalone_ASCS_instance_1739783232

The document outlines the installation scenarios for a standalone ABAP central services instance (ASCS) on a separate host, emphasizing the importance of high availability (HA) configurations. It details the use of SAPinst for installation and the necessity of third-party vendor solutions for ensuring HA in standalone setups. Additionally, it provides guidance on RFC connections and the importance of logon groups for maintaining connectivity and load balancing in the SAP landscape.

Uploaded by

8pgckvkccc
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

SAP Knowledge Base Article

1678705 - Installation scenarios for a standalone ASCS instance


Component: BC-OP-NT (Basis Components > Operating System Platforms > Windows), Version: 5, Released On:
30.07.2020

Symptom
You want to install a central services instance for ABAP (ASCS instance) on a separate host.
The names in these following examples are fake names. Any resemblance to real data is purely coincidental.

Resolution
As of SAP NetWeaver 7.0 you can use SAPinst to install a central services instance for ABAP (ASCS instance) in a non-HA
system (distributed system). Use the latest SAPinst from SAP Service Marketplace.
SAP designed the installation of the ASCS instance to work together with local ERS instances in a Microsoft Failover Cluster
to ensure high availability without having to restart the SAP system if a failure occurs.

Installation of SAP components in a Microsoft Failover Cluster


The following example shows a Microsoft Failover Cluster with 2 cluster nodes "donald" and "daisy", which run the single-
point-of-failure components database instance and ASCS instance as clustered resources. The primary application server
instance (PAS) and the additional application server instance (AAS) are installed locally together with the enqueue replication
server instances (ERS).
Note: For SAP NetWeaver 7.1 and higher, the technical terms used for the central and dialog instances have changed. The
"central instance" (CI) is called "primary application server instance" (PAS) and the "dialog instance" (DI) is called
"additional application server instance".

Such a HA configuration has the following benefits:


It is a fully supported installation with the SAPinst installation and SAP upgrade tools
Local ERS instances ensure continuous availability of the SAP lock table in case of a failure
SAP recommends local PAS and AAS to ensure that the ASCS runs together with an application server anytime
Windows Failover Cluster guarantees continuous operation in case of hardware failures
Windows Failover Cluster guarantees continuous operation in case of software failures (e.g. msg_server.exe crashes)
without having to restart the SAP system
Windows Failover Cluster guarantees continuous operation in case of OS failures or OS resource bottlenecks on one
cluster node
This configuration allows mistakes in the configuration of the RFC communication from and to this SAP system
because the application server can be reached anytime via all host names – local host names or virtual host names
The following scenario shows an alternative of installing local application server instances on cluster nodes:
If you use this scenario, for example, in a multi-SID cluster running several SAP instances in a Microsoft failover cluster, you
have to carefully maintain the inbound and outbound RFC connections to and from external RFC clients/server applications
to ensure the high-availability of all parts of an application landscape. See also below in section: What you need to know to
choose the right HA solution => 5. RFC connections to the SAP system.

Installation of a standalone ASCS instance


The following graphic shows an ASCS instance that is installed on an separate host (standalone ASCS instance):

To guarantee high availability, the operation of the standalone ASCS instance as well as the database instance require third-
party-vendor solutions.

What you need to know to choose the right HA solution:


1. What are the features of the third-party-vendor HA solution?
Depending on the third-party-vendor HA solution, only limited HA functionality is guaranteed. For example, most
solutions cover hardware, network, or storage failure, but not software failure. In a Microsoft failover cluster scenario,
the cluster does active health checking of the clustered components (SAP message server and SAP enqueue server). In
standalone ASCS scenarios this must be covered by other monitoring and alerting solutions.
2. Non-cluster HA solutions from third-party vendors are not certified by SAP and will only be supported by the vendor
itself. You have to consider this when choosing maintenance support with guaranteed SLAs for these third-party vendor
solutions.
3. Sizing
The installation of one or more standalone ASCS instances with optional standalone gateways for external RFC
servers require special sizing of the Windows host running these applications. You also have to consider
additional software in the sizing, for example, backup or monitoring agents, the SAP Solution Manager
diagnostics agent. For third-party vendor solutions where Windows only runs with one (virtual) CPU, there is a limit of
application scalability and stability.
The sizing must be done by the vendor of the HA solution.
4. Standalone ASCS installations with SAPinst. SAP releases that are based on SAP NetWeaver 7.0, 7.1, 7.3 and higher do
not have automatically installed an Solution Manager diagnostics agent (SMD) together with the standalone ASCS
instance. The SMD must be installed afterwards with the SAPinst option "Standalone Engines / Diagnostic Agent. If
required, you can install an optional standalone gateway to start external programs via RFC on the standalone
ASCS host.
5. RFC connections to the SAP system
External RFC clients require a logon group based connect to any available SAP application server. An external RFC
application must not use the host name of a PAS or an AAS instance. Instead, you must use the SAP message server
running on the standalone ASCS host to get the logon group and load information and then connect to the application
server that is returned by the message server. Another issue is the registration of external RFC servers to a SAP gateway.
The external RFC server needs a high-available SAP gateway for the connection. Therefore it might be necessary to
install an additional standalone gateway on the standalone ASCS host.
Refer to the installation guides for your SAP system, and the documentation of third-party-vendor RFC clients and RFC
servers, to make the whole landscape high-available.
The following example is not recommended, because the loss of an application server instance results in the loss of the RFC
communication:

Use logon groups to ensure high availability and load balancing:


This example shows the need for a high available standalone gateway if external RFC server applications need to register
themselves:

See Also
SAP Note 1010990 configuring a standalone gateway in an HA ASCS instance

Keywords
standalone ASCS, ABAP central services instance, high availablity, standalone gateway

Products
Products

SAP NetWeaver Application Server for ABAP all versions


This document is referenced by
SAP Note/KBA Component Title

1409608 Virtualization on Windows

You might also like