Database Reference
In-Depth Information
At the SAP application level, transaction code SMMS can be used to check the status and
monitor a message server. The message server lists the available application servers, and its
main responsibilities are as follows:
• Load balancing
• Deciding which application server the user will log into
• Providing communication between the application servers
Gateway Process and Gateway Monitor
The gateway process helps in communication with external applications using the CPI-C
protocol. The gateway process starts and runs at the operating system level when the SAP
system is started and can be checked by issuing the following command:
At the SAP application level, transaction code SMGW can be used to check the status
and active gateway connections of the system. A gateway process is installed along with the
standard SAP installation in ABAP systems. In Java-only installations, the gateway is not
installed as a part of a standard installation. If needed, a separate stand-alone gateway in-
stance should be installed.
SAP Operation Modes (SM63, RZ04)
Businesses operating SAP systems need more dialog work processes during work hours and
more background work processes during after hours. When a SAP system is initially con-
figured, the static number of dialog and background work processes is set. This static setup
does not allow us to use the system resources effectively in a 24-hour operation, where more
dialog processes are needed during business hours and more background processes are
needed during the night. SAP has provided us with a concept of operation modes where
work processes are dynamically switched back and forth between dialog and background or
other work process types based on a timetable referred to as the operation modes timetable.
This allows businesses to utilize the system resources to a fuller extent by switching re-
sources based on need. The total number of work processes remains unchanged after the op-
