Regenerate the plug-in configuration for a remote HTTP configuration

If you are using remote HTTP, you must regenerate the plugin-cfg.xml file and copy it to the WebSphere Application Server - Express instance that uses the remote Web server. You might also need to edit the contents of the plugin-cfg.xml file.

If the plugin-cfg.xml file is not current, regenerate it with the GenPluginCfg script or the administrative console. The updated file is saved in the /QIBM/UserData/WebASE51/ASE/instance/config/cells directory, where instance is the name of your instance. For more information about the script, see Regenerate the Web server plug-in configuration.

Note: Instead of using an existing plugin-cfg.xml file from your instance, you can regenerate this file with the GenPluginCfg script and specify the -destination.root and -output.file.name parameters. 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. If you change the name of the plug-in configuration file, you must change the name back to plugin-cfg.xml when you copy the file to the remote Web server instance.

In this example, GenPluginCfg script regenerates the plugin-cfg.xml file for the default application server (server1) of the default instance. The new file, plugin-cfg.remote.xml, is copied to the remote HTTP instance.
```
GenPluginCfg -instance default -server.name server1
  -destination.root /QIBM/UserData/WebASE51/ASE/remote
  -output.file.name plugin-cfg.remote.xml
```
Copy the plugin-cfg.xml file from the application server instance to the remote HTTP instance. If you specify the -output.file.name parameter when you run the GenPluginCfg script, you must change the name the file to plugin-cfg.xml after you copy it to the remote HTTP instance.
- If your Web server machine is an iSeries server, save the plugin-cfg.xml file to the /QIBM/UserData/WebASE51/ASE/remoteinstance/config/cells directory, 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 - Express product installation root on the Web server machine.
(Optional) If you do not specify the -destination.root parameter for the GenPluginCfg script, edit the value of the for the Log directive's Name attribute in the remote HTTP server's plugin-cfg.xml file.
- If your Web server machine is an iSeries server, change the attribute to match this value:
```
Name="/QIBM/UserData/WebASE51/ASE/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 - Express product installation root on the Web server machine.
If a Transport that uses Protocol="https" exists in the plugin-cfg.xml file, change the "keyring" and "stashfile" property values to these values:
```
name="keyring" value="/QIBM/UserData/WebASE51/ASE/remoteinstance/etc/plugin-key.kdb"
```
```
name="stashfile" value="/QIBM/UserData/WebASE51/ASE/remoteinstance/etc/plugin-key.sth"
```
where remoteinstance is the name of your remote HTTP server instance.
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 directories and subdirectories that contain the file. You can use the Work with Object Links (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).