Define the location of the plugin-cfg.xml configuration
file. The location varies depending on how you have configured
your system. If the Web server and the Application Server are on separate
machines, you have a remote installation.
If the two servers are on
the same machine, you have a local installation.
If
the two servers are on the same machine and the Application Server node or
the custom node is federated, you have a local distributed installation.
In
the following examples, webserver1 is the Web server definition name.
Setting the path to the plug-in
configuration fileSet the WAS_PLUGIN_CONFIG_FILE environment variable
to the location of the plug-in configuration file using one of the following
paths:
If the type of installation is: |
Then use this command to set the environment
variable: |
Remote |
WAS_PLUGIN_CONFIG_FILE=/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml |
Local standalone |
WAS_PLUGIN_CONFIG_FILE=profile_root/config/cells/sa_cell/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml |
Local distributed |
WAS_PLUGIN_CONFIG_FILE=profile_root/config/cells/dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml |
During the installation process, the Plug-ins installation
wizard creates the
setupPluginCfg.sh file in two places:
- The plugins_root/bin directory
- The lotus_root/notesdata directory
You can run the script from either location to set the WAS_PLUGIN_CONFIG_FILE
environment variable. However, if you are reconfiguring the Web server, you
might want to set the path yourself by setting the value of the environment
variable with a path from the preceding table.
The setupPluginCfg.sh script
sets the file path value to the file path that the wizard configured originally.
If you are reconfiguring the Web server to change the original file path,
do not use this script.
Setting the path to the plug-in configuration
fileAdd the appropriate statement to your lotus_domino_root\notes.ini file:
Do not delimit any of the following file
paths with quotation marks unless there is a space in the file path. Otherwise,
the
plugin-cfg.xml file might not load correctly.
If the type of installation is: |
Then use this command to set the WebSpherePluginCfg
variable: |
Remote |
WebSpherePluginCfg=C:\Program Files\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml |
Local standalone |
WebSpherePluginCfg=profile_root\config\cells\sa_cell\nodes\webserver1_node\servers\webserver1\plugin-cfg.xml |
Local distributed |
WebSpherePluginCfg=profile_root\config\cells\dmgrcell\nodes\managednode\servers\webserver1\plugin-cfg.xml |