Skip to main content

SAP System Logs : Part 4 GWRD and ICM Logs

In the world of SAP, a complex system landscape demands comprehensive monitoring and troubleshooting capabilities. To ensure smooth system operations and seamless communication with external systems, understanding the significance of different logs becomes crucial. In this blog, we will dive deep into the Gateway (gwrd) and ICM (Internet Communication Manager) logs in SAP and explore their role in monitoring and optimizing system performance. Let's demystify these logs and empower SAP professionals to navigate the intricacies of system operations. 🚀💻

Gateway (gwrd) Logs:

The Gateway logs (gwrd) are indispensable for monitoring the SAP Gateway processes responsible for facilitating communication between external systems and the SAP system. These logs are stored in the work directory with the following file names:

  1. gwrd_<host>_<instance>.log: This log captures general information about the SAP Gateway processes, including incoming and outgoing requests, service registrations, and communication errors.

Example Scenario: When troubleshooting communication issues between the SAP system and external systems, analyzing the gwrd logs can help identify network-related errors, failed connections, or misconfigured settings affecting communication. It can also provide insights into service registration failures, helping diagnose and resolve registration issues.

Example of SAP Gateway Process:

Let's consider a scenario where an external system needs to communicate with the SAP system to retrieve customer data. The SAP Gateway process acts as the intermediary, facilitating this communication. Here's an example of how the SAP Gateway process works:

  1. External System Sends Request: The external system sends an HTTP request to the SAP Gateway, specifying the service and the data it requires, such as customer information.

  2. SAP Gateway Receives the Request: The SAP Gateway process receives the incoming request and validates it. It checks if the requested service is registered and if the necessary authorizations are in place.

  3. SAP Gateway Processes the Request: The SAP Gateway process initiates the relevant SAP backend processes to fetch the requested data. It communicates with the appropriate backend systems, such as SAP ERP or SAP S/4HANA, to retrieve the customer information.

  4. Data is Transmitted to the External System: Once the SAP Gateway receives the requested data from the backend systems, it formats the data according to the requested protocol (e.g., JSON or XML) and sends it back to the external system as an HTTP response.

  5. External System Receives the Response: The external system receives the HTTP response from the SAP Gateway, containing the requested customer information. It can then process the data as needed within its own environment.

Throughout this process, the SAP Gateway logs (gwrd logs) capture valuable information about the incoming and outgoing requests, service registrations, and any communication errors encountered. Analyzing these logs can help diagnose and troubleshoot issues related to communication, performance, or service registrations, ensuring smooth and seamless integration between the SAP system and external systems.

ICM (Internet Communication Manager) Logs:

The ICM logs are instrumental in managing HTTP(S) communication between SAP applications and external clients. These logs are stored in the work directory with the following file names:

  1. icm_<host>_<instance>.log: This log captures detailed information about incoming HTTP(S) requests, response times, HTTP errors, and performance-related data.

Example Scenario: When optimizing web services or diagnosing performance issues, analyzing the ICM logs can provide valuable insights. It helps identify bottlenecks, analyze response times, detect HTTP errors, and fine-tune system configurations for optimal performance. It also plays a crucial role in identifying potential security vulnerabilities by detecting unusual patterns or suspicious activities in HTTP communication.

Example of Internet Communication Manager (ICM):

Let's imagine a scenario where an organization runs a web application hosted on an SAP system, and multiple users access the application simultaneously. The Internet Communication Manager (ICM) plays a crucial role in handling the incoming requests and managing the communication between the users and the SAP system. Here's an example of how the ICM works:

  1. User Requests Access: A user opens their web browser and enters the URL of the SAP web application they want to access.

  2. Request Reaches the ICM: The request sent by the user reaches the ICM, which acts as the entry point for incoming HTTP requests.

  3. Load Balancing (if configured): If load balancing is configured, the ICM determines the appropriate SAP application server based on factors like server availability, performance, and workload distribution. It forwards the request to the selected application server.

  4. Request Processing: The application server processes the request and retrieves the necessary data from the SAP backend systems.

  5. Response Generation: The application server generates a response based on the user's request and the data retrieved from the backend systems.

  6. Response Sent to the ICM: The application server sends the response back to the ICM.

  7. Response Delivered to the User: The ICM receives the response from the application server and delivers it to the user's web browser, which displays the web application's content.

Throughout this process, the ICM logs (icman logs) capture important information about the incoming requests, load balancing decisions, communication between the ICM and application servers, and any errors or performance issues encountered. Analyzing these logs can provide insights into the system's responsiveness, identify potential bottlenecks, and help diagnose and troubleshoot any communication or performance-related issues.

Monitoring and analyzing the Gateway (gwrd) and ICM (Internet Communication Manager) logs in SAP are crucial steps towards ensuring smooth system operations, seamless communication, and optimal performance. By understanding the significance of these logs and their specific file names, SAP professionals can effectively diagnose and resolve issues, optimize system configurations, and enhance system security. Embracing the power of these logs empowers SAP administrators and basis consultants to navigate the complexities of system operations with confidence and precision.

Remember, the Gateway (gwrd) and ICM (Internet Communication Manager) logs are your trusted allies in maintaining a robust and reliable SAP system infrastructure.  

Labels:

Comments

  1. KrishnaPhilips19 September 2023 at 06:27

    It shows the effort you put in this article This is a very nice blog that I will definitively come back to more times this year! custom erp company in chennai

    ReplyDelete

Post a Comment

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with
23 comments
Read more

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need
Post a Comment
Read more

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe
3 comments
Read more

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D
4 comments
Read more

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note
3 comments
Read more

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set
7 comments
Read more

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info
Post a Comment
Read more

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.
1 comment
Read more

SUM Tool : An Introduction

Let’s Discuss about the famous tool, that is asked in almost all the Basis and HANA interview and it is very easy to understand but a bit tricky. Tighten your seatbelts and Let’s understand in one go. SAP Technical Upgrade is a periodic project that is implemented across companies to upgrade their SAP system to the latest released version. Most of the upgrade activities are done by the technical team and the role of functional consultants is limited and mostly confined to regression testing What are the maintenance that are performed by help of SUM ? Release upgrade (major release change) System update (EHP installation) applying Support Packages (SPs) / Support Package Stacks applying Java patches correction of installed software information combine update and migration to SAP HANA (DMO: Database Migration Option) System Conversion from SAP ERP to SAP S/4HANA   First thing first , never confuse in these two things : Upgrade and Update. Updating SAP products is for applying support pac
2 comments
Read more

SAP application log tables: BALHDR (Application Log: Header Data) and BALDAT (Application Log: Detail Data)

  BALHDR (Application Log: Header Data): Usage : The BALHDR table stores the header information for application logs. It serves as a central repository for managing and organizing log entries. Example Data Stored: The table may contain entries for various system activities, such as error messages, warnings, or information logs generated during SAP transactions or custom programs. Columns Involved: LOGNUMBER: Unique log number assigned to each log entry. OBJECT: Identifies the object associated with the log entry (e.g., a program, transaction, or process). SUBOBJECT: Further categorizes the object. USERNAME: User ID of the person who created the log entry. TIME: Date and time when the log entry was created. ADD_OBJECT: Additional information or details related to the log entry. BALDAT (Application Log: Detail Data): Usage : The BALDAT table contains the detailed data for each log entry, linked to the corresponding entry in the BALHDR table. It stores the specific log details and me
Post a Comment
Read more