How to Fix Uneven HTTP Load Balancing in SAP PI


Starting from SAP NetWeaver 7.1, the Java stack does not have a dispatcher node as it was the case with earlier release. The job of the dispatcher--load balancing the incoming HTTP requests to J2EE server nodes--is now taken over by ICM. The ICM is designed to load balance http sessions (stateful http calls), which is not optimal for applications like PI which primarily uses stateless calls. The result is decreased message throughput.

In order to optimize load balancing on SAP PI (7.1 to 7.3) add the parameters below in the SAP instance profile:

j2ee/HTTP/request_strategy = STATELESS
j2ee/HTTP/request_STATELESS_0=0,7,2,0,1,0
j2ee/HTTP/request_STATELESS_1=0,3,3,0.9,0.01,1
j2ee/HTTP/request_STATELESS_2=0,2,6,1,1,0.01
j2ee/HTTP/request_STATELESS_3=0,5,2,0,0.01,1
j2ee/HTTP/request_STATELESS_4=1,1,0,0,2,0.5
j2ee/HTTP/request_STATELESS_5=1,3,1,0,1,0.01
j2ee/HTTP/request_STATELESS_6=1,6,1,0,20,0.5
j2ee/HTTP/request_STATELESS_7=1,4,3,0,0.0001,0.0001

Restart ABAP+Java instances to activate these changes.

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 creat...
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