| eG Monitoring |
|---|
Measures reported by TrexRfcTest The RFC server is responsible for the communication between an SAP system and the TREX servers. The SAP system sends requests to an RFC server using an SAP Gateway. The RFC server converts the requests to a TREX-internal format and then forwards them to the corresponding TREX servers. The TREX configuration depends on the structure of the SAP system. The TREX RFC Servers can be configured either in single-thread mode or in multi-thread mode. In the case of TREX RFC servers in single-thread mode, there are at least as many RFC servers (instances/processes) running on each TREX host as there are application servers. In the case of TREX RFC servers in multi-thread mode, exactly one RFC server (instance/process) runs on each TREX host and within this one RFC server, at least as many threads are started as there are applications servers. The TREX configuration depends on the structure of the SAP system. Each TREX host runs at least as many TREX RFC servers as there are application servers. If application servers are added to or removed from the SAP system, the TREX configuration should be changed accordingly. If the TREX configuration is not changed, then the communication between the RFC server and the SAP system may be disconnected. To avoid such disconnects, it is essential to monitor the configuration of the RFC server continuously. The TrexRfcTest test helps administrators in this regard! Using this test administrators can figure out the current configuration status of the RFC server with the target TREX server instance, the status of the RFC server and the number of threads configured on the RFC server. Outputs of the test : One set of results for the target SAP TREX server being monitored. The measures made by this test are as follows:
|