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
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 wanted
insertion line, then press .
- Press F3 to save and exit.
Table 1. 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 |
The
setupPluginCfg.sh file is
created 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 re-configuring
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.