|
| Problem | There are some good reasons to not regenerate plugin files, except when changes occur, such as when many application servers are defined and the generation of the plugin files takes more than a minute. WebSphere now provides options to disable automatic generation of these files. | | | | Solution | Every time when we bring up the admin server, the plugin files in the WebSphere temp directory get regenerated (e.g. /usr/WebSphere/AppServer/temp). The files that are generated are vhosts.properties, queues.properties and rules.properties. These files are then read by the WebSphere plugin.1. Create a new file: "global.properties" in properties directory (e.g. <was_root>/properties/global.properties)2. In global.properties file, insert the following line:com.ibm.servlet.engine.disableAutoPluginCfg=true( Make sure global.properties has a newline at the end of the file)3. Stop and restart WebSphere (application servers and admin server)4. Check the time stamp in the plugin properties file to verify that they are NOT being updatedIn order to prevent the WebSphere plugin from reading the properties files after it has started, update the bootstrap.properties file in the properties directory (e.g. <was_root>/properties/bootstrap.properties):ose.refresh.interval=-1
(You may want to note that setting the refresh interval to -1 does NOT prevent the plugin from checking the timestamp of the properties files. It actually causes the plugin to check the timestamp on every request.)Warning, this change suppresses updating the properties files when:- admin server starts
- application server is started or restarted
- when configuration changes are made using the admin console, XMLConfig or wscp
It is necessary to press the "Regen Plugin Configuration" button to update files.Notes: - If properties files are not updated, check to see if each application server has authority to update the properties files (application servers can run under different user ID and group IDs).
- For OSE Remote installations, bootstrap.properties is updated on the web server system.
- For tracing the "PluginRegen" failure we can enable following traces in admin.config
#In one continuous line...!!#First Line...(There is a "." between components and ":" between trace string...!!)
com.ibm.ejs.sm.adminServer.traceString=com.ibm.servlet.engine.oselistener.
systemsmgmt.PluginCfgGenerator=all=enabled:com.ibm.servlet.engine.
PluginRegenScheduler=all=enabled:com.ibm.servlet.engine.plugincfg.*=all=enabled #Second Line...one continuous line..!!
com.ibm.ejs.sm.adminServer.traceOutput=<was_root>/logs/<nameoftrace> | | | | | Historical Number | PMR08453
344
000 | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Administrative Console (all non-scripting) Operating system(s): Multi-Platform Software version: 3.5 Software edition: Advanced Reference #: 1009175 IBM Group: Software Group Modified date: 2002-11-21
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|