Update: You may find a more current copy of this article in the PeopleSoft Corner Wiki.
You can purge web server and application server cache even when the system is up and running. These techniques have been around for a while, but they don't seem to be common knowledge so I thought I'd post about them anyway.
Before we begin, let me quote the PeopleTools 8.46 release notes:
And to quote PeopleBooks
OK, the disclaimers are out of the way. Now let's get started.
Starting in PeopleTools 8.46, there's a new option in PSADMIN called Purge Cache under the Administer a Domain submenu. This option will purge application server cache even if the application server domain is up and running.
Select Purge Cache (option 8 in Tools 8.46.05) and if the cache is not empty the following prompt appears:
"Enter log comments about this purge, if any (maximum 256 characters):"
Enter any comments you want recorded and hit Enter. Your comments will be saved in the LOGS directory under PurgeCache_mmddyy_hhmm_ss.log.
Then it will ask if you want to archive the contents of the current cache. I have no idea why anyone would ever want to archive cache, so I select No.
When prompted to continue, enter y to continue the purge operation. If your domain is running, you may see several INFO messages. This is normal, so don't sweat it. It also will take longer than just shutting down the domain and deleting the files so don't worry about the length of time it takes either.
OK, now for the web server.
We'll be using the "Purge" servlet directive to make it happen. Rich Manalang has the best and only post I'm aware of about PeopleSoft Servlet Directives and explains how to do things like purge web server cache, reload your web profile, view your web profile, etc.
To set up your system for servlet directives you need to specify a password in your web profile. So open your web profile (PeopleTools > Web Profile > Web Profile Configuration), navigate to the Custom Properties tab, and look for a property called auditPWD. It should be set to a string, and the property value should be whatever password you want to set. The default is "dayoff". If you make any changes, you'll have to bounce your web server for it to take effect.
Once the auditPWD property is in place, you can simply call the psp servlet with the purge command, and your web server cache will be purged. The syntax of the URL is:
http://[server]/psp/[site]/?cmd=purge&pwd=[password]
For example: http://psoft.erpassociates.com:6500/psp/HDEV/?cmd=purge&pwd=dayoff.
Anyway, update the URL with your specific info, paste it into your browser, and the web server cache will be cleared without a web server bounce.
As always, make sure you test these techniques in a non-production database, and use at your own risk! I hope you find them helpful.
...
written by Brent Martin, April 25, 2006
You can purge web server and application server cache even when the system is up and running. These techniques have been around for a while, but they don't seem to be common knowledge so I thought I'd post about them anyway.
Before we begin, let me quote the PeopleTools 8.46 release notes:
You can purge the cache regardless of whether the application server domain is running; there's no need to shut it down and reboot. However, the procedure is less disruptive and runs more quickly if the domain is shut down or its activity is low.
And to quote PeopleBooks
Important! You should purge the cache only after due consideration, and in conslutation with PeopleSoft.
OK, the disclaimers are out of the way. Now let's get started.
Starting in PeopleTools 8.46, there's a new option in PSADMIN called Purge Cache under the Administer a Domain submenu. This option will purge application server cache even if the application server domain is up and running.
Select Purge Cache (option 8 in Tools 8.46.05) and if the cache is not empty the following prompt appears:
"Enter log comments about this purge, if any (maximum 256 characters):"
Enter any comments you want recorded and hit Enter. Your comments will be saved in the LOGS directory under PurgeCache_mmddyy_hhmm_ss.log.
Then it will ask if you want to archive the contents of the current cache. I have no idea why anyone would ever want to archive cache, so I select No.
When prompted to continue, enter y to continue the purge operation. If your domain is running, you may see several INFO messages. This is normal, so don't sweat it. It also will take longer than just shutting down the domain and deleting the files so don't worry about the length of time it takes either.
OK, now for the web server.
We'll be using the "Purge" servlet directive to make it happen. Rich Manalang has the best and only post I'm aware of about PeopleSoft Servlet Directives and explains how to do things like purge web server cache, reload your web profile, view your web profile, etc.
To set up your system for servlet directives you need to specify a password in your web profile. So open your web profile (PeopleTools > Web Profile > Web Profile Configuration), navigate to the Custom Properties tab, and look for a property called auditPWD. It should be set to a string, and the property value should be whatever password you want to set. The default is "dayoff". If you make any changes, you'll have to bounce your web server for it to take effect.
Once the auditPWD property is in place, you can simply call the psp servlet with the purge command, and your web server cache will be purged. The syntax of the URL is:
http://[server]/psp/[site]/?cmd=purge&pwd=[password]
For example: http://psoft.erpassociates.com:6500/psp/HDEV/?cmd=purge&pwd=dayoff.
Anyway, update the URL with your specific info, paste it into your browser, and the web server cache will be cleared without a web server bounce.
As always, make sure you test these techniques in a non-production database, and use at your own risk! I hope you find them helpful.
Trackback(0)
TrackBack URI for this entry
Comments (4)
Subscribe to this comment's feed
written by Brent Martin, April 25, 2006
Yes, each PSAPPSRV process keeps a certain amount of in-memory cache. A PSAPPSRV process will restart and flush the in-memory cache when the number of transactions processed reaches the Recycle Count specifed in the Application Server configuration file, psappsrv.cfg.
If you find you're having to shut down and clear in memory cache frequently, you might think about reducing the Recycle Count.
Since state is managed on the web server and not the app server, many (if not most) DBA/Admins elect to create two app servers and shut down one at a time when necessary like you described (of course the web server has to be configured to round-robin between both of them). Every once in a while I'll hear about a user getting an unexpected result, but it works well for the most part. All the same, I don't usually stop anything during busy periods unless its an emergency.
If you find you're having to shut down and clear in memory cache frequently, you might think about reducing the Recycle Count.
Since state is managed on the web server and not the app server, many (if not most) DBA/Admins elect to create two app servers and shut down one at a time when necessary like you described (of course the web server has to be configured to round-robin between both of them). Every once in a while I'll hear about a user getting an unexpected result, but it works well for the most part. All the same, I don't usually stop anything during busy periods unless its an emergency.
-
- +0
-
-
Write comment
| < Prev | Next > |
|---|
Last Updated on Wednesday, 10 May 2006 19:37.
We usually clear the memory cache by rebooting the app server; we usually can leave the file cache intact (but not always). In production, we have 2 app servers; the dbas reboot the app servers one at a time to flush the memory of cache (while allowing production to be up and running).