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.
Table 1. Setting the path to the plug-in configuration file. Set
the WAS_PLUGIN_CONFIG_FILE environment variable to the location of
the plug-in configuration file using one of the paths in this table.
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.
Table 2. Setting the path to the plug-in configuration file. Add
the appropriate statement to your lotus_domino_root\notes.ini file.
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 |
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.
Setting the path to the plug-in configuration
fileEdit your notes.ini file.
- From a CL command prompt, enter the Work with Domino Servers
(WRKDOMSVR) command.
- Type 13 next to the applicable Domino server,
then press .
- Add or edit the WebSphereInit property. (See the following table.)
To
add a new line, type "i" next to the desired
insertion line, then press .
- Press F3 to save and exit.
Table 3. Editing the notes.ini file . Use this table when
editing you notes.ini file.
If the type of installation is: |
Then use this command to set
the environment variable: |
Remote |
WebSpherePluginConfig profile_root/config/webserver1/plugin-cfg.xml |
Local standalone |
WebSpherePluginConfig profile_root/config/cells/my_cell/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml |
Local distributed |
WebSpherePluginConfig profile_root/config/cells/my_cell/nodes/my_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.