Performance tuning for Integrator for SAP

See the following hints and tips that might help improve performance of the Integrator for SAP.

General considerations

• Cache sizes have a direct impact on the memory requirements of WebSphere Portal, specifically the demands on the Java heap. To determine if the portal has enough memory resources available to handle an additional increase, monitor the usage of caches and the portal memory usage under a heavy workload, before you increase the cache sizes.

• If you do not use the portlet menu for IBM API portlets, disable it:

  1. Access the WAS admin console.

  2. Navigate to Resources > Resource Environment > Resource Environment Providers.

  3. Select WP ConfigService.

  4. Add the following custom property:

     • Property name: navigation.portletmenu.mode

     • Value: 0

Limiting availability of the SAP navigation page for users

Each time a user accesses the SAP navigation page for the first time during a WebSphere Portal session, WebSphere Portal sends a request to the SAP NetWeaver Portal. Therefore limit the access to the SAP navigation page to the correct audience, for example, to all or selected SAP users. To perform this task, use the WebSphere Portal Access Control. This measure limits request volume to the appropriate requests only. For more information about Portal Access Control refer to the topic Controlling access.

Caches for performance and memory consumption

For tuning purposes, Integrator for SAP provides two portal caches with entries for each integrated SAP portal page and for each logged in user. Set their size and lifetime according to the environment.

com.ibm.wps.integration.sap.NodeCache

Content: This cache holds one entry for each integrated page per locale, independent of the user.

For example, if the SAP NetWeaver Portal contains a maximum of 500 pages and all the users use one and the same locale, this cache can never exceed 500 entries.

com.ibm.wps.integration.sap.NodeCache.size = (1000)

Default size: 1000 entries

com.ibm.wps.integration.sap.NodeCache.lifetime = (-1)

Default lifetime: This cache never expires.

com.ibm.wps.integration.sap.ModelCache

Content: This cache holds one entry for each logged in user who has access to the SAP navigation. This cache entry is removed on logout by the user.

If you have only limited memory available, we can use this cache to limit the memory consumption of the SAP navigation integration. However, limiting memory consumption this way might in turn affect performance. Note that if we add pages to SAP NetWeaver Portal, the memory consumption grows accordingly, even if you do not increase this cache size. If you set this cache size too small, performance might decrease.

com.ibm.wps.integration.sap.ModelCache.size = (1000)

Default size: 1000 entries

com.ibm.wps.integration.sap.ModelCache.lifetime = (-1)

Default lifetime: This cache never expires.

For more information about how to configure WebSphere Portal caches, see the section about the Cache Manager Service in the topic about Portal configuration services.

Ajax Proxy configuration

Set appropriate values in proxy-config.xml according to the environment for the maximum number of connections and the number of connections per host. Otherwise, a limitation of available connections can occur.

Set appropriate values for the parameters socket-timeout and retries . If SAP NetWeaver Portal is not available for some reason, these two parameters limit the length of time that the task spends on the inaccessible connection. For details about the two parameters see Prepare the system environment and the prerequisites. For each user who logs in to WebSphere Portal and who has access rights to the SAP NetWeaver Portal navigation page, WebSphere Portal tries a connection at least once, depending on the cache settings described in the previous section. If these attempts fail for many users, it can affect the performance of WebSphere Portal.

For more information about configuring the Ajax Proxy, see the topic about Ajax Proxy configuration.

Parent: Integrate with SAP NetWeaver Portal
Related:
Prepare the system environment and the prerequisites
Related reference:
Tips for Integrator for SAP
Portal configuration services