SAP从业者联盟

 找回密码
 立即注册

QQ登录

只需一步,快速开始

搜索
SAP从业者联盟 信息 SAP notes 查看内容

Note 1010990 - Configuring a Standalone Gateway in an HA ASCS instance

2012-9-3 23:09| 发布者: isap| 查看: 8809| 评论: 0|来自: SAP

摘要: Summary Symptom You run a SAP NetWeaver '04 (6.40), SAP NetWeaver 7.0, or SAP NetWeaver 7.1 or higher system in a failover cluster with only the (A)SCS instance(s) running inside the cluster environme ...

Summary

Symptom

You run a SAP NetWeaver '04 (6.40), SAP NetWeaver 7.0, or SAP NetWeaver 7.1 or higher system in a failover cluster with only the (A)SCS instance(s) running inside the cluster environment. You want to configure an RFC-server program in such a failover cluster solution.

Other terms

Microsoft Cluster Service (MSCS), gateway, gwrd, RFC-Server, high availability, HA, ASCS, SCS

Reason and Prerequisites

In SAP releases up to SAP ABAP kernel 6.40, the ABAP central instance was configured to run in a seperate cluster resource group or package. The ABAP central instance always had a gateway that could be configured to start external RFC-servers. In this context, an RFC-server is a non-ABAP, native Windows or UNIX executable, which is typically configured with transaction SM59 / TCP/IP-connections using the activation type Starting on Explicit Host or Registered Server Program.
With the introduction  of the (ABAP) central services instance ((A)SCS) in the cluster concept, there is no longer a failover-protected SAP gateway in the cluster resource group or package available to be configured for HA RFC-servers.

The following minimum patchsets are required for Enqueue Server, Enqueue Replication Server and Gateway (enserver.exe, enrepserver.exe, gwrd.exe):
SAP Kernel release 640: Patch Level 189
SAP Kernel release 700: Patch Level 116
SAP Kernel release 710 or higher: initial delivery is sufficient

RFC-Client programs (external programs and SM59 ABAP connections) connecting to a high-availability ABAP system need to use load balancing in order to connect to one of the non-clustered ABAP servers of an SAP system.

Solution

Add a standalone gateway to the ABAP central services instance (ASCS).
In the following example procedure, the gateway is configured to use the ASCS instance profile. Additional gateway-specific parameters such as gw/startup have to be entered in this profile to become effective for the gateway.

Procedure:

    1. On Windows edit: \\\sapmnt\\SYS\exe\\scs.lst
    Add the following lines at the end of the file:
         gwrd.exe
         gwrd.pdb
    2. On UNIX edit: /sapmnt//exe/scs.lst
    Add the following lines at the end of the file:
         gwrd
    3. Edit the instance profile of the ASCS instance:
    (Windows: \\\sapmnt\\SYS\profile\_ASCS_;
    UNIX: /sapmnt//profile/_ASCS_)
    Add the following line:
         gw/netstat_once = 0
    4. SAP versions based on Netweaver earlier 7.20:
    Edit the start profile of the ASCS instance:
    (Windows: \\\sapmnt\\SYS\profile\START_ASCS_;
    UNIX: /sapmnt//profile/START_ASCS_)

    SAP versions based on Netweaver 7.20 or later:
    Edit the instance profile of the ASCS instance:
    (Windows: \\\sapmnt\\SYS\profile\_ASCS_;
    UNIX: /sapmnt//profile/_ASCS_)

    Add the following line:
      a) Identify the Start_Program_ entry with the highest number in the profile.
      b) On both platforms, add the following line:
      _GW=gwrd$(FT_EXE)
      c) On Windows, add the following line:
      Start_Program_ = local $(DIR_EXECUTABLE)\$(_GW) pf=$(DIR_PROFILE)\_ASCS_ -no_abap
      d) On UNIX, add the following line:
      Start_Program_ = local $(DIR_EXECUTABLE)/$(_GW) pf=$(DIR_PROFILE)/_ASCS_ -no_abap
    5. Check that the gateway port definitions, sapgw and sapgws, are maintained in all files:
    (Windows: %windir%\system32\drivers\etc\services;
    UNIX: /etc/services)
    Note: is the value of the ASCS profile parameter SAPSYSTEM
    6. Since you updated the clustered ASCS startup profile, on Windows you have to take the SAP Service Resource offline to activate the changes. For other failover solutions, perform the appropriate activity to restart the ASCS instance.
    7. Restart both replication servers to activate the instance profile changes.


Header Data

Release Status: Released for Customer
Released on: 04/02/2012  15:25:31
Master Language: 英语
Priority: Recommendations/additional info
Category: Installation information
Primary Component: BC-OP-NT Windows NT
Secondary Components: BC-CST Client/Server Technology

Affected Releases

Software
Component
Release
From
Release
To
Release
And
subsequent
KRNL32NUC
6.40
6.40
6.40EX2
 
KRNL32NUC
7.00
7.00
7.01
 
KRNL32NUC
7.10
7.10
7.20
 
KRNL32NUC
7.20EXT
7.20EXT
7.20EXT
 
KRNL32NUC
7.21
7.21
7.21
 
KRNL32NUC
7.21EXT
7.21EXT
7.21EXT
 
KRNL32UC
6.40
6.40
6.40
 
KRNL32UC
7.00
7.00
7.00
 
KRNL64NUC
6.40
6.40
6.40
 
KRNL64NUC
7.00
7.00
7.00
 
KRNL64UC
6.40
6.40
6.40
 
KRNL64UC
7.00
7.00
7.00
 

鲜花

握手

雷人

路过

鸡蛋

Archiver|SAP从业者联盟 ( 京ICP备09055458号-2 

GMT+8, 2022-5-21 08:22 , Processed in 0.189890 second(s), 14 queries .

Powered by i-sap.org X2

© 2001-2011 Comsenz Inc.

回顶部