[AIX Solaris HP-UX Linux Windows][z/OS]

Propagating the plugin-cfg.xml file to web servers

For web servers that are defined in the WebSphere Application Server Network Deployment (ND) configuration, you can automatically propagate the generated plugin-cfg.xml file to web servers using the autoPropagate keyword option, or by using the propagatePluginCfg.py script.

About this task

To propagate the generated plugin-cfg.xml file using the autoPropagate keyword option, or the propagatePluginCfg.py script, follow this procedure:

Procedure

  1. In the administrative console, go to the On demand router settings page:
    • For stand-alone on demand router (ODR) processes, click Servers > Server types > On demand routers > ODR_name > On demand router properties > On demand router settings.
    • For a static cluster of ODR processes, click Servers > Clusters > On demand router clusters > ODR_static_cluster_name > On demand router properties > On demand router settings.
    • For a dynamic cluster of ODR processes, go to Servers > Clusters > Dynamic clusters > ODR_dynamic_cluster_name > Server template > On demand router properties > On demand router settings.
  2. In the Proxy plugin configuration policy section, select the scope from the Generate plugin configuration drop-down list.
  3. In the Proxy plugin configuration policy section, define an absolute path to the script that you enter in the Plugin config change script text box. The defined script is invoked every time the plugin-cfg.xml is dynamically updated.
    • Enter the autoPropagate keyword in the Plugin config change script text box to automatically propagate the generated plugin-cfg.xml file.
      Example:
      • autoPropagate,*:*:*
      • /tmp/executeFirst.sh;/bin/executeSecond.sh;autoPropagate,*:*:*
    • Enter the propagatePluginCfg.py script in the Plugin config change script text box to automatically propagate the generated plugin-cfg.xml file.
      Example:
      • /opt/WAS/bin/wsadmin.sh -f /opt/WAS/bin/propagatePluginCfg.py -lang jython https://myIHSHost:8192 
        ihsusr ihsusrPassword /tmp/plugin-cfg.xml /opt/HTTPServer/plugins/config/webserver1/plugin-cfg.xml
      • /tmp/executeFirst.sh;/bin/executeSecond.sh;/opt/WAS/bin/wsadmin.sh -f /opt/WAS/bin/propagatePluginCfg.py 
        -lang jython https://myIHSHost:8192 ihsusr ihsusrPassword /tmp/plugin-cfg.xml 
        /opt/HTTPServer/plugins/config/webserver1/plugin-cfg.xml
  4. Click Apply, and save and synchronize the changes.
  5. Restart the ODR for the changes to take effect. plugin-cfg.xml is generated every time the ODR starts, when there are administrative actions performed that impact what URIs the ODR handles, and when changes in the environment affect the content of the plugin-cfg.xml file.
Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 08:46 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twve_propplugcfgweb
File name: twve_propplugcfgweb.html