Enabling Web Cache in SAP Web Dispatcher

When an http call is made, it is passed to the application server via the web dispatcher. If the same call is made repeatedly, the WD has to keep sending the same request to the application. There is some level of saving that can be made in the network bandwidth and usage of backend system by saving the fetched pages locally and serving the saved copies from the web dispatcher.

Web caching is inactive by default. To activate the cache on a particular uri, add "icm/HTTP/server_cache_0 = PREFIX=<uri-prefix>, CACHEDIR=<dir>" in the web dispatcher profile.

Comments

Post a Comment

Popular posts from this blog

SAP Memory Parameters Tuning - Part 1

Image
Roll and Extended Memory ztta/roll_first - This is the first area of memory assigned to a work process. This parameter is usually set to 1 as a technically necessity as the modern applications will end up using more memory than the first roll segment. Even if ztta/roll_first is set to 1, the minimum amount required for administrative data is allocated from roll memory. It is best to leave the parameter at 1. ztta/roll_extension - Further memory allocation to the work process is done from Extended Memory, after first roll segment is used up. ztta/roll_extension parameter determines how much memory can be used by a user context in the extended memory. In other words, this is the limit of the SAP Extended Memory for each work process. This is true in most cases, however, ztta/roll_extension is Extended Memory limit for a single "i-mode". Depending on the number of i-modes, normally up to 6, the value of maximum extended memory can raise up to 6*ztta/roll_extension theoret...
Read more

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

com.sap.aii.ib.core.ejbutil.rb_all.SERVER_MS_NOT_AVAILABLE Error on Integration Builder Login

As soon as you enter the credentials on ESR/Integration Repository/Integration Directory/Integration Builder, if you see the  error " com.sap.aii.ib.core.ejbutil.rb_all.SERVER_MS_NOT_AVAILABLE ", it means that the message server could not connect to  the P4 port of the PI system Call the following URL and check if P4 port is listed: http://<msg_server_host>:<msg_server_port>/msgserver/text/logon Try msg_server_port as the port 81NN, when NN is the instance number of ASCS or SCS or Central Instance (where ABAP message server and enqueue servers are running) Depending on which message server lists the P4 port, maintain the message_server_port (81NN) in the following exchange profile parameters com.sap.aii.connect.directory.mshttpport com.sap.aii.connect.repository.mshttpport If the error includes java.net.MalformedURLException, then the above profile parmaters are not maintained at all and must be maintained along with com.sap.aii.connect.rep...
Read more