Situations requiring manual editing of the plug-in configuration
Some situations require you to edit the plug-in-cfg.xml file.
IBM WebSphere Application Server for z/OS integrates
the WebSphere Application Server product and the Network Deployment product
into a single package. When you see WebSphere Application Server product or
Network Deployment product in reference to WebSphere Application Server for
z/OS, the term product equates to function.
The following situations require manual editing of the plugin-cfg.xml file:
- If the Web server and plugin-cfg.xml file are installed on a
separate remote system, you must change the paths in plugin-cfg.xml file
if:
- The plug-in was generated on a Windows 32 system platform. Copy it to
a remote Linux or UNIX system with an HTTP Server and a WebSphere Application
Server Version 5 plug-in.
- The plug-in was generated on a Linux or UNIX system. Copy it to a remote
Windows platform with an HTTP Server and a WebSphere Application Server Version
5 plug-in.
- The plug-in was generated on a Linux or UNIX system and needs to be copied
to another, remote Linux or UNIX system that has a different configuration.
For example, the plug-in was generated on a system having a single-server
(Base) or Network Deployment installation on AIX in the default path, and
the remote HTTP Server and plug-in are installed on a Solaris or Linux system
with the plug-in installed in the default location.
- In a Network Deployment environment, if the single-server
(base) product, Network Deployment product, plug-in, and HTTP Server are all
installed on the same node, change entries in the plugin-cfg.xml file
that refer to the /config/cells directory in the installation root
of the deployment manager to instead, refer to the /config/cells directory
in the installation root of the base Application Server. References exist
to the /config/cells directory of the installation root of the deployment
manager because the deployment manager runs the plugin-update procedure.
The
installation root of the Application Server is the default path for the base
product. If the base product is installed in a different location, change
the specified paths to refer to that location.
- If the single-server (base) or Network Deployment product, or the plug-in,
are installed in a non-default location, you must change the paths in plugin-cfg.xml.
The plug-in generator assumes that the plug-in path is the same as the base
product path structure. For example, if you install the base product in c:\myApps\WebSphere\AppServer50
and install the plug-in on a remote Windows system in c:\WebSphere\AppServer50,
you must generate the plug-in using the administrative console on the base
product and then edit the plug-in at c:\myApps\WebSphere\AppServer50\config.
You must change all of the c:\myApps\WebSphere\AppServer50\... path structures
to c:\WebSphere\AppServer50\...
- When the deployment manager is installed on a machine that is remote from
the base WebSphere Application Server installation, implement one of the following
solutions to allow the plugin-cfg.xml file to retain the install_root/AppServer directory
structures, and to not assume those of the install_root/DeploymentManager,
after a regeneration of the plug-in and full synchronization. The plugin-cfg.xml file
is located in the install_root/AppServer/config directory.
- Command line:
At a command prompt, change to the /bin directory
of the installation root of the deployment manager machine. Type GenPluginCfg
-destination.root<install_root> on the machine where the Network
Deployment product is installed. This creates or updates the plugin-cfg.xml file.
This changes all directory specifications in the plugin-cfg.xml file
to the install_root\AppServer directories. For example, run
the GenPluginCfg -destination.root "E:\WebSphere\AppServer" command
from the \bin directory of the installation root of the Network Deployment
node.
- plugin-cfg.xml file:
Edit the plugin-cfg.xml file in
the /config/cells directory of the deployment manager, to point to
the correct directory structure for the log file, keyring, and stashfile.
Perform a full synchronization so the plugin-cfg.xml file is replicated
in all the WebSphere Application Server nodes. The deployment manager plugin-cfg.xml file
can point to Application Server directories without any conflict.
Note: To get the current usage information for the
plugin_cfg.xml file,run the GenPluginCfg -help script. You will receive the
following information in response to this query:
Usage: GenPluginCfg [[-option.name optionValue] ...]
Valid Options:
==============
-config.root configroot_dir
(defaults to environment variable CONFIG_ROOT)
-cell.name cell
(defaults to environment variable WAS_CELL)
-node.name node
(defaults to environment variable WAS_NODE)
-server.name server
(required for single server plugin generation)
-output.file.name file_name
(defaults to configroot_dir/plugin-cfg.xml)
-destination.root root
(install root of machine configuration will be used on)
-destination.operating.system windows/unix
(operating system of machine configuration will be used on)
-debug yes/no
(defaults to no)
==============
Examples:
To generate a plugin config for all of the clusters in a cell:
GenPluginCfg -cell.name NetworkDeploymentCell
To generate a plugin config for a single server:
GenPluginCfg -cell.name BaseApplicationServerCell -node.name serverNode
-server.name serverName

Manually editing the plug-in configuration

plugin-cfg.xml file
Searchable topic ID:
crun_editplugin
Last updated: Jun 21, 2007 9:56:50 PM CDT
WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/cwsv_editplugin.html