Situations requiring manual editing of the plug-in configuration

 

The following situations require manual editing of the plugin-cfg.xml file:

  1. If the Web server and plugin-cfg.xml file are installed on a separate remote system, change the paths in plugin-cfg.xml file if:

    • The plug-in was generated on a Win32 system and needs to be copied to a remote UNIX system with an HTTP Server and a WAS V5 plug-in.

    • The plug-in was generated on a UNIX system and needs to be copied to a remote Win32 system with an HTTP Server and a WAS V5 plug-in.

    • The plug-in was generated on one UNIX distribution and needs to be copied to a remote UNIX system that is a different distribution.

      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 distribution with the plug-in installed in the default location.

  2. In a Network Deployment environment, if the single-server (base) product, Network Deployment product, plug-in, and HTTP Server are all on the same machine, change the paths in plugin-cfg.xml if:

    • The plugin-cfg.xml file is located in...

      /opt/WebSphere/DeploymentManager/config/

      ...and not...

      /opt/WebSphere/AppServer/config/...

      During installation of the base product, copy the plugin-cfg.xml file to...

      /opt/WebSphere/AppServer/config/

      ...because the plug-in and modifications to the HTTP Server configuration files are looking for plugin-cfg.xml in...

      /opt/WebSphere/AppServer/config

    • The paths in the plugin-cfg.xml file specify

      /opt/WebSphere/DeploymentManager/...

      These paths exist because the deployment manager runs the plugin-update procedure. You must change the paths to

      /opt/WebSphere/AppServer/config

      /opt/WebSphere/AppServer is the default path for the base product, if the base product is installed in a different location, change the paths to that location.

  3. If the single-server (base) or Network Deployment product, or the plug-in, are installed in a non-default location, change the paths in plugin-cfg.xml. The plug-in generator assumes that the plug-in path is the same as the base product's path structure. For example, if you install the base product in...

    /export/home/WebSphere/AppServer50
    ...and install the plug-in on a remote system in...

    /opt/WebSphere/AppServer

    ... generate the plug-in using the administrative console on the base product and then edit the plug-in at

    /export/home/WebSphere/AppServer/config

    You must change all of the...

    /export/home/WebSphere/AppServer/...
    ...path structures to...

    /opt/WebSphere/AppServer

  4. When the deployment manager is installed on a machine that is remote from the base WAS installation, plugin-cfg.xml must bed edited /opt/WebSphere/AppServer directory structures, and not assume those of the /opt/WebSphere/Deployment Manager directory structure after a regeneration of the plug-in and full synchronization.

    • To change from the command line:

      At a command prompt, change to the Deployment Manager/bin directory and type GenPluginCfg -destination.root/opt/WebSphere on the machine where Deployment Manager is installed. This creates or updates the plugin-cfg.xml file. This will change all of the directories in the plugin-cfg.xml file to the...

      /opt/WebSphere/AppServer
      ...directories. For example, run

      GenPluginCfg -destination.root "/opt/WebSphere/AppServer"

    • Edit plugin-cfg.xml file directly:

      Edit the deployment manager/config/cells plugin-cfg.xml file to point to the correct directory structure for the log file, keyring, and stashfile. Perform a full sync so the plugin-cfg.xml file is replicated in all the WAS nodes. The Deployment Manager plugin-cfg.xml file can point to the appserver directories without any conflict.

Manually editing the plug-in configuration
plugin-cfg.xml file

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.

 

AIX is a trademark of the IBM Corporation in the United States, other countries, or both.