SAP Gateway 2.0 Parameter Tuning

Here are some important SAP profile parameters that can help the gateway performance:

The number of dialog work processes should be sufficient to handle the requests: rdisp/wp_no_dia is recommended to be set at Number of Cores x 4. You can always increase this number as long as the average CPU usage is below 80%. Check ST03 %Wait Time for DIALOG type tasks. If this values is more than 50 ms or 10% of average response time, then the number of WPs are not sufficient.

The keep-alive timeout should be set at 60 sec. The timeout is controlled by icm/keep_alive_timeout and overridden by the timeout set in the parameter icm/server_port_<xx>

The maximum number of simultaneous open connections in ICM is determnined by icm/max_conn. Set this parameter to Number of Active Users x 1.2. Check SMICM and ensure that Peak value is less than the Maximum value against "Connections Used". When you change icm/max_conn, change the maximum number of sockets (icm/max_sockets)  to icm/max_conn x 2.

The data between ICM thread and ABAP work processes is transferred through memory pipes (MPI). The total size of shared memory used by MPIs is limited by the parameter mpi/total_size_MB. The recommendation is to set this values to Number of Active Users / 10. Check SMICM > Goto > Memory Pipes > Display and ensure that Peal buffer usage is below Total #Mpi Buffer.

The maximum number of users per instance (rdisp/tm_max_no), the maximum number of RFC/CPIC connections on an application server (rdisp/max_comm_entries) and the maximum number of active gateway connections (gw/max_conn) should set at a value more than Number of Active Users.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more