Hi,
I have done using the following procedure. Have a try.
Installation of the SAP gateway service in MSCS
The node where the DB group resides before you install the gateway service is referred to as node A. Any additional node is referred to as node B. Perform all steps as <sid>adm user.
1. Choose the <SID> and <system number> for the gateway (*). Make sure that they are different from those used by the SAP system. For the system number you can assign a value from 0 to 97, but not the numbers 2, 25, 43, 72, 89 or 99.
2. Create a folder named "sapgw" in the %windir%\sapcluster directory of all cluster nodes.
3. Create the subfolders "work" and "log" in the folder "sapgw".
4. Copy gwrd.exe and sapxpg.exe to the "sapgw" folder.
5. Create the default, start and instance profiles in the folder "sapgw".
Make sure that you enter the parameters definitions in a single line.
Also make sure that in both profiles there is at least one empty line after the last line with parameter definitions.
Note that parameters are case-sensitive.
Here you find examples for the profiles:
o default.pfl
SAPDBHOST = <virtual DB hostname>
o startgw.pfl
SAPSYSTEMNAME = <SID>
INSTANCE_NAME = GW<system number>
SAPSYSTEM = <system number>
DIR_EXECUTABLE = <%windir%>\sapcluster\sapgw
DIR_PROFILE = <%windir%>\sapcluster\sapgw
DIR_INSTANCE = <%windir%>\sapcluster\sapgw
_GW=gwrd.exe
#Caution! Enter the following profile entry in a single line
Start_Program_00 = local $(DIR_EXECUTABLE)\$(_GW) pf=$(DIR_PROFILE)\gw<system number>.pfl
o gw<system number>.pfl
SAPSYSTEMNAME = <SID>
INSTANCE_NAME = GW<system number>
SAPSYSTEM = <system number>
DIR_PROFILE=< %windir%> \sapcluster\sapgw
DIR_EXECUTABLE=< %windir%>\sapcluster\sapgw
DIR_INSTANCE=<%windir%>\sapcluster\sapgw
SAPLOCALHOST = <virtual database hostname>
SAPLOCALHOSTFULL = <virtual database hostname>
6. Add the following entries to "%windir%\system32\drivers\etc\services" on all application servers in your landscape:
sapgw<system number> 33<system number>/tcp
sapgw<system number>s 48<system number>/tcp
7. Set the environment variables for user <SID>adm on the control panel of node A:
SAPMNT=
<virtual R3 hostname>\sapmnt
SAPEXE=<%windir%>\SapCluster
8. Create the service SAP<SID>_<system number> on node A.
To do this, run the command %windir%\sapcluster\sapstartsrv.exe and choose: "Install Service + Register COM Interface + Start Service".
Enter <SID>, <system number> and path to the start profile (startgw.pfl), the DOMAIN\SAPService<SID> user and the password (in this case use the same user accounts as for your clustered SAP system).
Check (X) "User Environment of user" and enter the DOMAIN\<SID>adm account.
Set the startup type to "Manual" and choose "OK".
Make sure that you start sapstartsrv.exe from the %windir%\sapcluster and not from another directory.
9. Move the DB group to node B and perform steps 2 to 8 on node B.
10. On node B, add a gateway resource to the DB group, as follows:
a) Right-click the DB group in the Cluster Administrator.
b) Select "New -> Resource", enter the resource name SAPGW<SID>, select "SAP Resource" as resource type and choose "Next"
c) Select both nodes A and B as possible owners and choose "Next".
d) Add "Disk Resource", "IP Address" and "Network Name" as resource dependencies and choose "Next".
e) Enter the gateway <SID> and gateway <system number> as SAP resource parameters and choose "Finish".
f) Bring the gateway resource SAPGW<SID> online.
11. Create the event ID to describe the event in the application event log. Perform this step on node A and node B. Run the Registry Editor "regedit.exe" and create the new key "SAP<SID>_<system number>" in "HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application" and create the following values for key "SAP<SID>_<system number>":
o STRING value:
EventMessageFile = <%windir%>\sapcluster\sapevents.dll
o DWORD value:
TypesSupported = 7
!!! CAUTION !!! If you use the Registry Editor incorrectly, your system may be damaged. Perform a registry backup before you apply any changes.
Configuring the RFC destinations in the SAP system
In an MSCS configuration, maintain the following RFC destinations:
- SAPOSCOL_<virtual_DB_hostname>
- SAPOSCOL_<virtual_R3_hostname>
- SAPXPG_DBDEST_<virtual_DB_hostname>
You maintain the two SAPOSCol destinations as follows:
1. Enter the following parameter in the instance profile of your
SAP system:
gw/netstat_once = 0
2. Call Transaction SM59. Select TCP/IP connections and double-click the available SAPOSCOL destination.
3. Select "Destination -> Copy", to copy the destination to SAPOSCOL_<virtual_DB_hostname> and to SAPOSCOL_<virtual_R3_hostname>. If no SAPOSCOL RFC connection exists, you have to create it. Adjust the name of the target host to be set to the virtual name of the SAP and DB instances respectively.
4. Adjust the gateway settings for SAPOSCOL_<virtual_DB_hostname> and SAPXPG_DBDEST_<virtual_DB_hostname>. Choose the destination in SM59 and edit it. Choose "Change", select "Deastination -> Gateway option", and enter the following:
Gateway host = <virtual_DB_hostname>
Gateway service = sapgw<system number>
"Start on Explicit Host" (X - checked if available)
Make sure that for SAPXPG_DBDEST_<virtual_DB_hostname> you enter "sapxpg" in the "Program" field, adjust "Communication type with target system" to "Non-Unicode" on "MDMP_Unicode" tab. For SAPOSCOL_<virtual_DB_hostname> and SAPOSCOL_<virtual_R3_hostname> destinations "Program" field should be set to value "c:\windows\sapcluster\rfcoscol.exe". Test the RFC connection.
5. Implement the BR* tools for transaction DB13 (see SAP Notes 403704 and 378648).
6. Make sure that the latest version of librfc32.dll is located in %windir%\system32. librfc32.dll is downwards-compatible with the older version. We recommend that you use the newest version for the 6.x kernel, as well as the latest version of sapxpg.exe. You can download them from SAP Service Marketplace.
7. Make sure that you have completely uninstalled all rsh-daemons (Microsoft, Ataman).
8. If you are using Unicode executables for sapstartsrv.exe and gwrd.exe make sure that all Unicode dlls (librfcu32.dll, icu*.dll, libsapu16.dll etc.) are visible in PATH.
(*) List of Known Problems
1. If you use the same <SID> and system number as for your productive system, the definition of SAP Service will be overwritten and you cannot start your clustered SAP system.
To solve the problem, run sapstartsrv.exe from the shared disk of your SAP system and remove the wrong service entry on both nodes. Register SAP service for your clustered system with the correct parameters on both nodes by running the sapstartsrv.exe.
2. An offline backup does not work after you have replaced Ataman with standalone gateway.
Check the table contents of SDBAC with table maintenance transaction SE16 (SM31 up to release 4.5B). Search for the entries with backup types (SHORTCUT) PRTOF, ALGOF and ALLOF and change the command entry (CNAME) from ZBRBACKUP to BRBACKUP if necessary.
3. Oracle: Offline backup with BRBACKUP.
During the offline backup, BRBACKUP must stop and start the Oracle database by using the OFS interface. Configure it according the SAP note 378648.
Troubleshouting
1. The gateway resource does not come online.
u2022 Put the gateway resource offline. During this operation the DB group and its resources remain fully operational if no dependencies on gateway resource are defined.
u2022 Check if SAP gateway service runs. Start SAP MMC on the node where DB is running and check if the symbol for SAP system with gateway SID is grey (no crossed symbol) or check MMC snap-in "services" if the SAP<SID>_<NR> is running. If the gateway service cannot be started check the system event log for error entries. Check also path to executables and path to profiles for service registration.
u2022 Check if the gateway can be started via SAP MMC. If the gateway service runs, try to start the gateway in SAP MMC. If it does not start, check the sapstart.log, sapstart.trc and dev_rd in gateway "work" folder. Usually the problem could be wrong SID or system number or missing end of line at the end of each profile file.
2. RFC connection in SM59 cannot be established.
u2022 Check if the correct gateway host (virtual DB name) and gateway port (service) are specified.
3. RESET N1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.