The task of the message server is to inform all the servers (instances) belonging to an SAP System of the existence of the other servers. It can also be contacted by other clients (for example, SAPlogon, RFC clients with load balancing) to get information about load balancing.
The SAP Message Server runs as a separate process mostly on the same host as the central instance.
Only one message server can run on each SAP System.
If the messages server stops working, it must be restarted as quickly as possible, to ensure system continues to operate trouble-free.
Monitoring the Message Server in the SAP System
To monitor the message server, you can use the Message Server Monitor (transaction SMMS) in the SAP System. You can check and change all the important settings, create and view traces, read statistics, and so on.
Monitoring the Message Server from the Browser
You can display details of the servers and logon groups from the Web browser too. To do this, in the URL use the host of the message server and the HTTP port of the message server (profile parameterms/server_port_<xx>).
Monitoring and Testing the Message Server at Operating System Level
To monitor the message server at operating system level you need access to the host on which the message server is running. You can log on here with user <sid>adm.
At operating system level there are various programs available, which are delivered with the standard system.
You will usually find the test programs in the executable directory /usr/sap/<SID>/SYS/exe/run.
The SAP Web dispatcher lies between the Internet and your SAP System. It is the entry point for HTTP(s) requests into your system, which consists of one or more Web application servers. As a "software web switch", the SAP Web dispatcher can reject or accept connections. When it accepts a connection, it balances the load to ensure an even distribution across the servers.
You can use the SAP Web dispatcher in ABAP/Java systems and in pure Java systems, as well as in pure ABAP systems.
It is also beneficial to use the SAP Web dispatcher, if you do not need security functions (entry point in the DMZ, SSL, URL filtering), but you simply want to balance the load between several SAP Web AS instances.
The SAP Web dispatcher is recommended when you use an SAP system with several SAP Web Application Servers for Web applications.
The SAP Web dispatcher is a program that you can run on the machine that is connected directly to the Internet. It requires minimal configuration - you just have to enter the following data in the profile file:
· Port, on which the HTTP(s) requests are to be received (parameter icm/server_port_<xx>)
· Host and HTTP port of the SAP message server (parameter rdisp/mshost and parameter ms/http_port)
If you want to be able to call the Web application externally, for example using the URL www.shop.acme.com, this host name must be mapped internally to the SAP Web dispatcher. This then forwards the HTTP(S) request to a suitable SAP Web AS.
The SAP Web dispatcher performs the following tasks:
· Selects an appropriate application server (persistence with stateful applications, load balancing, ABAP or Java server), see Server Selection and Load Balancing Using the SAP Web Dispatcher.
· Filters URLs – you can define URLs that are to be rejected, see SAP Web Dispatcher as a URL Filter
· Depending on the SSL configuration, forwards, terminates, and (re)encrypts requests. See SAP Web Dispatcher and SSL
The SAP Web dispatcher is only useful in the Web environment. In the classic SAP system, load is balanced by the message server.
The SAP Web dispatcher forwards only incoming HTTP(S) requests to the Web application server and the response is then returned to the client.
Outgoing requests (such as requests to a different SAP Web Application Server) are not sent via the SAP Web dispatcher. They are sent via the proxy server for the appropriate intranet.
Fragmented index results in increased usage of database space and more blocks being read into the buffer. This can be avoided by rebuilding the index.
One can measure index fragmentation using the report RSORATAD or using DB02 --> Detailed Analysis --> Enter Index --> Detailed Analysis --> Analyze Index --> Storage Quality. If storage quality is less than 50% you may need to reorg the index.
If you wish to run an analysis on all the indexes, run the report RSORAISQN. Check SAP note 970538 for more details for more information on the restriction with using this report. Do not run the report without reading the note. You can also get an idea on the amount of fragmentation by comaring the size of the table and the index. If the size of the index is larger than that of the table, the index is fragmented.
Recently I got an issue that one of our XI production system’s Business Process is not working correctly.
So to check the Business Process status we can use the TCode : SWF_XI_ADM_BPE_DISP or SWF_XI_ADM_BPE
Below is the screenshot of tcode SWF_XI_ADM_BPE_DISP
Here in the below screen, we can see that all the BPE components are running (green status) along with the BPE status.
The status display shows the status of the BPE and its components.
- Green: Component running
- Red: Component stopped
- Amber: Component currently being stopped or started
- Error icon: Error when starting or stopping the component.
We need to have below 2 roles for accessing these tcodes:
http://<host name> <j2ee port>/rwb
Go to Component Monitor in Runtime Workbench. Now select Integration Server > Business Process Engine