Skip to main content
Skip table of contents

SMGW

Data Description

The SMGW event is used in SAP to manage and view the RFC gateways of the SAP system.

Potential Use Cases

This event could be used in the following scenarios:

  • Provide a snapshot of gateway connections at a particular time.

  • Trend utilization of logged on clients, remote gateways, and connections over time.

  • Alert on high memory utilization for the gateway.

Splunk Event

SMGW with EVENT_SUBTYPE=””

This event shows the list of RFC connections in SMGW. The data provided is a snapshot. The event will look like this in Splunk:

SMGW with EVENT_SUBTYPE=”LOG_CLNT”

This event shows the list of logged on systems in SMGW. The data provided is a snapshot. The event will look like this in Splunk:

SMGW with EVENT_SUBTYPE=”REM_GW”

This event shows the list of currently logged on SAP Gateways. The data provided is a snapshot. The event will look like this in Splunk:

SMGW with EVENT_SUBTYPE=”GWADM”

This event shows the Gateway summary information and current status from the SMGW transaction. The data provided is a snapshot. The event will look like this in Splunk:

SAP Navigation

SMGW with EVENT_SUBTYPE=””

Execute the SMGW transaction in the SAP system. The information displayed at the bottom of the screen will match the data that is extracted and sent to Splunk.

SMGW with EVENT_SUBTYPE=”LOG_CLNT”

Execute the SMGW transaction in the SAP system. Click on Goto → Logged on Clients

The information displayed on the screen will match the data that is extracted and sent to Splunk.

SMGW with EVENT_SUBTYPE=”REM_GW”

Execute the SMGW transaction in the SAP system. Click on Goto → RFC Connections

The information displayed on the screen will match the data that is extracted and sent to Splunk.

SMGW with EVENT_SUBTYPE=”GWADM”

Execute the SMGW transaction in the SAP system. The information displayed at the top of the screen will match the data that is extracted and sent to Splunk.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.