Installation and Monitoring SAP Frontend Server including NW Gateway

18
SAP Front-End Server including NW Gateway Installation, Configuration and Monitoring Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 1 Front-End Server SID=FES SAP NW 751 SAP GW_FND 751 SAP UI 7.51 SYBASE 16.0.02.06 S4HANA SID=S4H SAP NW 7.51 HANA DB SID=H4S Trusted RFC

Transcript of Installation and Monitoring SAP Frontend Server including NW Gateway

SAP Front-End Server including NW GatewayInstallation, Configuration and Monitoring

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 1

Front-End Server SID=FES

SAP NW 751

SAP GW_FND 751

SAP UI 7.51

SYBASE 16.0.02.06

S4HANA SID=S4H

SAP NW 7.51

HANA DB SID=H4S

Trusted RFC

This is a compilation of notes taken during installation of IDES Front-end Server.

It contains configuration steps, which include ‘linking’ the frontend server to the backend S/4HANA system.

Also include monitoring of both systems, using the IT-Conductor – with additional emphasis on the RFC connections between the two systems.

The installation, configuration and monitoring of the backend S/4HANA system was covered in previous presentation ‘S/4HANA Installation Quickstart Guide and Monitoring S/4HANA’

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 2

Introduction/References

IDES based on S4HANA was available as per OSS note 2445594

Main References:

2445594 - IDES S/HANA 1610

2355644 - SAP Fiori front-end server 3.0 - General Information

Additional References:

•SAP NW Installation Guide

•Published blogs and documents

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 3

Installation – NW Front End Server (1)

As root, from the SWPM extract folder, run sapinst1. Preparation – Prerequisite check

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 4

Installation – NW Front End Server (2)

2. Install Standard system, using IDES Export

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 5

IDES export

SID=FES

Installation – end product

The IDES FrontEnd Server was installed with the following

• AS ABAP 7.51

• SAP_GWFND 751 S00 - upgraded to SP03

• SAP_UI 751 S00 - upgraded to SP03

• DBMS SYBASE 16.0.02.06

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 6

Post-Tasks - Configuration using Task Lists (1)

Configuration of the front-end server and link to the backend server.

From SAP help – Configuration using Tasks Lists, using transaction STC01.

The help page indicates which systems the task should be performed.

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 7

Post-Tasks - Configuration using Task Lists (2)

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 8

TIP: When working on two SAP systems concurrently, it’s a good idea to change the color to easily distinguish which one is frontend and backend, using profile parameter sapgui/signature_color.

Post-Tasks - Configuration using Task Lists (3)

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 9

Installed/Configured Systems

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 10

Front-End Server SID=FES

SAP NW 751

SAP GW_FND 751

SAP UI 7.51

SYBASE 16.0.02.06

S4HANA SID=S4H

SAP NW 7.51

HANA DB SID=H4S

Trusted RFC – S4HCLNT001Trusted RFC – FESCLNT001

The newly installed Frontend Server FES is ’configured’ to relate it to the backend system S4H

The backend system S4H was presented in previous blog ‘S44HANA installation Quick Guide’

ITC Monitoring of FrontEnd Server and S/4HANA

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 11

• New system FES registered in ITC, and all related objects are ‘automatically discovered.

• Monitoring available in few minutes

Both FrontEnd Server and backend S/4HANA can be viewed in a single page

FES - FrontEnd ServerS4H – Backend S/4HANA

ITC Monitoring – RFC (1)

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 12

The RFCs between the FrontEnd Server and the backend S4HANA are critical to the transaction processing. ITC provides a feature called ‘RFC Destinations’ which provides visibility on the availability and latency of each RFC.

RFC to backend

RFC to Frontend

ITC Monitoring – RFC (2)

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 13

Threshold values can be defined for availability and latency

ITC Monitoring – RFC (3)

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 14

When the threshold is reached, an alert raised and email is sent to specified recipients. The detail of the alert is displayed when the link is selected

Miscellaneous notes (1)

• Table /IWFND/C_MGDEAM contains the ODA and related system aliases

• View /IWFND/V_DFSYAL shows the relationship between the system alias and RFC definition.

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 15

Miscellaneous notes (2)

Troubleshooting

• Transaction /UI2/FSAC to display consistency issues for a selected system alias or RFC destination

• Transaction /iwfnd/error_log to display error log. Note that sometimes it does not work – go through the transaction /iwfnd/maint_service and select the error_log button

• The error_log is in table /IWFND/SU_ERRORLOG

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 16

Summary – Frontend Server Installation

Author: Terry KempisEditor: Linh Nguyen

ITConductor.com 17

• The installation process is not much different than other SAP NW installation

• SAP ‘task lists’ are available to ‘semi-automate’ the configuration of the system, including ‘relating’ it to the backend system

• Similar to other SAP products, the Frontend server can be registered into IT-Conductor easily, and monitoring is available after few minutes.

• IT-Conductor has an additional feature of monitoring the availability and latency of the RFC definitions between the frontend and backend systems – with configurable threshold values/conditions – alert and email notification provided when the values are not met.

• Any Questions?

• Contact Info:

Linh Nguyen [email protected]

Terry Kempis [email protected]

Let

itconductor.com

@itconductor