Regenerate the plugin configuration for a remote HTTP configuration

 

Overview

If you are using remote HTTP, regenerate the plugin-cfg.xml file and copy it to the remote WebSphere instance used by the remote Web server. Also, it is likely you will need to edit the contents of the plugin-cfg.xml file.

1. If the plugin-cfg.xml file is not up to date, regenerate it via the GenPluginCfg script or via the admininstrative console. This will regenerate the file into this location:

   /QIBM/UserData/WebAS5/edition/instance/config/cells

   ...where edition is Base or ND, depending on which product you used to regenerate, and instance is the name of your WebSphere instance.

   Instead of using an existing plugin-cfg.xml file from your WebSphere instance, you may want to consider regenerating this file using the GenPluginCfg script using parameters customized for a specific remote HTTP Web server configuration:

   -destination.root
   -output.file.name

   The -destination.root option customizes the Log directive's file name path and the Transport directive's value attribute. The -output.file.name option specifies an alternate filename so that the script does not overwrite the existing plugin-cfg.xml file that may be in use by the local WebSphere instance. If you do change the name to something other than plugin-cfg.xml, make certain you change the name back to plguin-cfg.xml when it is copied to the remote Web server instance.

   For example, the GenPluginCfg script regenerates the plugin-cfg.xml file (destined for a remote HTTP instance) for the default application server (server1) of the default WebSphere instance.

   GenPluginCfg -instance default -server.name server1 -destination.root /QIBM/UserData/WebAS5/Base/remote -output.file.name plugin-cfg.remote.xml

2. Copy the plugin-cfg.xml file from the WebSphere instance of the previous step to the WebSphere instance used by the remote Web server.

   • if your Web server machine is an iSeries server, save the plugin-cfg.xml file to the directory...

     /QIBM/UserData/WebAS5/Base/remoteinstance/config/cells

     ...where remoteinstance is the name of your remote HTTP server instance. A remote instance named remote is provided for you by default.

   • if your Web server machine is a non-iSeries machine, save the plugin-cfg.xml file to the installroot\config\cells directory, where installroot is the WebSphere Application Server product installation root on the Web server machine.

3. On the Web server machine -- if you did not use the -destination.root property as shown above -- edit the value of the for the Log directive's Name attribute in the plugin-cfg.xml file.

   • if your Web server machine is an iSeries server, change the attribute to match this value:

     Name="/QIBM/UserData/WebAS5/Base/remoteinstance/logs/http_plugin.log"

     where remoteinstance is the name of your remote HTTP server instance.

   • if your Web server machine is a non-iSeries machine, change the attribute to match this value:

     Name="installroot/logs/http_plugin.log"

     where installroot is the WebSphere Application Server product installation root on the Web server machine.

4. If a Transport using Protocol="https" exists in the plugin-cfg.xml file, if necessary, change the "keyring" and "stashfile" property values to these values:

   name="keyring" value="/QIBM/UserData/WebAS5/Base/remoteinstance/etc/plugin-key.kdb"

   name="stashfile" value="/QIBM/UserData/WebAS5/Base/remoteinstance/etc/plugin-key.sth"

   ...where remoteinstance is the name of your remote HTTP server instance.

5. Ensure that the HTTP server job has the necessary authority to read (*R) the plugin-cfg.xml file. The HTTP server job must also have Execute authority (*X) to the subdirectories leading up this file. Use the WRKLNK command to verify the authority that is assigned to the Apache Web server user profile (QTMHHTTP) or the Lotus Domino Web server user profile (QNOTES).