![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[z/OS]](../images/ngzos.gif)
Configuring an ODR to dynamically update the web server plug-in configuration
In a topology with a web server which forwards requests to an on demand router (ODR), the ODR can be set to dynamically generate and update the web server plug-in configuration file plugin-cfg.xml. By configuring an ODR to dynamically update plugin-cfg.xml, you avoid manually updating the file during administrative actions, which can affect the content.
Before you begin
- All: Includes all ODRs in the environment.
- Cell: Includes all ODRs within the same cell as the ODR that generates plugin-cfg.xml.
- Node: Includes all ODRs on the same node as the ODR that generates plugin-cfg.xml.
- Server: Includes only the ODR that generates plugin-cfg.xml.
About this task
An ODR configured to generate plugin-cfg.xml must be running in order for dynamic updates to occur. If a single ODR is configured to generate the plugin-cfg.xml file, and that ODR is stopped, plugin-cfg.xml is not regenerated until the ODR is restarted. Therefore, run the plugin-cfg.xml file generator as a highly available service. For more information, read about generating the plug-in configuration in a high availability environment.
The plugin-cfg.xml file is generated by an ODR process. Therefore the file is generated on the file system that hosts the generating ODR. For all, cell, and node, WAS_HOME/profiles/profile_name/etc/ is the default directory where the ODR generates the plugin-cfg.xml file. The default directory for server is WAS_HOME/profiles/profile_name/etc/odr_name/. The default generation directory can be overridden by setting a Java™ virtual machine (JVM) system property on the generating ODR. To set the JVM system property, go to . Name the JVM system property ODCPluginXmlDir and enter a value that contains the absolute path to the generation directory.