SAP NETWEAVER GATEWAY FIORI SYSTEM PERFORMANCE

SAP NetWeaver Gateway and FIORI system performance is critical for delivering a smooth and responsive user experience in your SAP environment. Several factors can influence the performance of such systems, and it's essential to monitor and optimize them to ensure optimal performance. Here are some key considerations:

1. Hardware and Infrastructure:Ensure that your hardware infrastructure (servers, storage, network) is appropriately sized and configured to handle the expected workload. Performance issues can arise if the hardware is inadequate.
2. SAP System Configuration:Properly configure your SAP system, including the SAP NetWeaver Gateway and FIORI components, based on best practices and SAP recommendations. This includes tuning parameters like buffer sizes, thread counts, and memory settings.
3. Database Optimization:The performance of your SAP system is heavily dependent on the underlying database. Regularly optimize your database by running maintenance tasks like indexing, updating statistics, and archiving.
4. Code Optimization:Review and optimize custom code, such as OData services, FIORI apps, and ABAP programs, to minimize resource consumption and execution time. Leverage SAP's code performance analysis tools.
5. Caching:Utilize caching mechanisms to store frequently accessed data and reduce the load on the system. SAP offers various caching options that can be configured to improve performance.
6. Load Balancing:Implement load balancing to distribute incoming requests evenly across multiple application servers. This helps prevent overloading a single server and ensures high availability.
7. Monitoring and Performance Tuning:Continuously monitor the system's performance using SAP Solution Manager or other monitoring tools. Set up alerts to proactively identify and address performance issues.
8. Network Performance:Ensure that your network infrastructure is optimized to reduce latency and improve data transfer rates. Consider using content delivery networks (CDNs) for static resources.
9. FIORI App Design:Design FIORI apps with performance in mind. Minimize the number of round trips to the server, optimize UI rendering, and use asynchronous calls where appropriate.
10. Security:Implement security measures efficiently to avoid unnecessary overhead. Carefully design and configure authentication and authorization mechanisms.
11. System Landscape:Ensure that your system landscape is designed for scalability and flexibility. Consider implementing a distributed architecture if your user base is growing.
12. User Training:Train your end-users to use FIORI apps effectively. Users who understand how to navigate and use the system can help reduce unnecessary system load.
13. Regular Updates:Keep your SAP software up-to-date with the latest patches and updates, as these often include performance enhancements and bug fixes.
14. Performance Testing:Before deploying new applications or making significant changes, perform load testing to assess how the system handles heavy user loads and identify potential bottlenecks.
15. Expert Consultation:If you face persistent performance issues, consider consulting with SAP experts or third-party consultants who specialize in SAP performance tuning.

Optimizing SAP NetWeaver Gateway and FIORI system performance is an ongoing process that requires vigilance and proactive management. Regularly assess your system's performance, identify areas for improvement, and apply appropriate optimizations to ensure a responsive and efficient user experience.

STEPS FOR IMPROVING PERFORMANCE

REGULAR CLEAN-UP JOBS:

Run program /IWFND/R_SM_CLEANUP in batch to clean up the application log. See note 2499354 – Report /IWFND/R_SM_CLEANUP. You can run with clean up scenario * for all, or select a specific scenario:

/IWFND/CLEANUP_APPSLOG will clean up the application log.

/IWFND/SUPPORT_UTILITIES will clean up support utilities.

See more on periodic tasks on help.sap.com.

See also OSS note 2620821 – Periodical jobs and corresponding reports to also run programs /IWBEP/SUTIL_CLEANUP and /IWBEP/R_CLEAN_UP_QRL regularly (daily).

Run report /UI2/PERS_EXPIRED_DELETE weekly to clean up old personalization data (see note 2031444 – Cleanup of expired Fiori personalization data on the frontend server).

METADATA CACHE SETTINGS:

In customizing go to this path:

The setting should look like the following in a productive system:

For the development system, you should deactivate this cache.

LOG LEVEL SETTINGS:

In a productive system, you can reduce data footprint and improve performance by reducing the log level settings. Only in case of issues, you can increase the log levels again.

To avoid excessive SLG1 logging of type “MESSAGE_TEXT”, make sure to apply the solution from OSS note 3247600 – Fiori: /IWFND/MED170 – No service found for namespace ‘/IWBEP/’, name ‘MESSAGE_TEXT’, version ‘0001’.

GATEWAY ERROR LOG:

Go to transaction /n/IWFND/ERROR_LOG. Now select the menu Error Log/Global Configuration. Now the configuration opens:

Set the Error log level in production to Secure. Check the days to realistic dates (the settings above in the screenshot are per SAP advice).

BACKEND ERROR LOG:

Go to transaction /n/IWBEP/ERROR_LOG. Now select the menu Error Log/Global Configuration. Now the configuration opens:

Set the Error log level in production to Secure. Check the days to realistic dates (the settings above in the screenshot are per SAP advice).

METERING:

Make sure you don’t keep all metering data too long. You can aggregate and delete it.

See also note 2871580 – SAP Fiori Launchpad Settings: new Parameters for Enterprise Search for the settings to optimize, and SAP blog on explanation of the settings.

See note 2885249 – How to disable Enterprise Search in Fiori Launchpad to disable the enterprise search part.

See note 2051156 – Deactivation of search in SAP Fiori launchpad for deactivation.

AMOUNT OF TILES ASSIGNED TO THE USER:

The amount of tiles assigned to a user has a big impact on performance. Try to reduce the amount of tiles assigned to the user as minimal as possible.

See OSS notes 2829773 – Fiori Launchpad performance with a large volume of Tiles and 2421371 – Understanding Launchpad Performance Issues.

TABLES THAT ARE GROWING:

Specific notes and solutions for tables that are growing fast in a Netweaver gateway system:

• 2385250 – Rapid growth of Gateway tables /IWFND/L_MET_DAT and /IWFND/SU_STATS
• 2652576 – Table /IWBEP/SU_ERRLOG and/or /IWFND/SU_ERRLOG grow heavily
• 3088332 – Table /IWFND/SU_TPLOAD is continuously growing

Please connect and?follow?me for the next upcoming informative articles.

Cheers :)