Situations requiring manual editing of the plug-in configuration
Some situations require you to edit the plug-in-cfg.xml file.
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, 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 WAS 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...
- During installation of the base product, copy the plugin-cfg.xml file to the $WAS_HOME/AppServer/config/cells directory because that is where the plug-in and the HTTP Server will look for it. (The plugin-cfg.xml file is initially located in the $WAS_HOME/DeploymentManager/config/cells directory.)
- In the plugin-cfg.xml file, change references to the $WAS_HOME/DeploymentManager/config/cells path to $WAS_HOME/AppServer/config/cells. The references to the $WAS_HOME/DeploymentManager/config/cells path exist because the deployment manager runs the plugin-update procedure.
The $WAS_HOME/AppServer path is the default for the base product. If the base product is installed in a different location, change the paths to refer to the actual location.
- 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 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, 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 WAS installation, implement one of the following solutions to allow the plugin-cfg.xml file to retain the $WAS_HOME/AppServer directory structures, and to not assume those of the $WAS_HOME/DeploymentManager, after a regeneration of the plug-in and full synchronization. The plugin-cfg.xml file is located in the $WAS_HOME/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$WAS_HOME 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 $WAS_HOME\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 WAS nodes. The deployment manager plugin-cfg.xml file can point to Application Server directories without any conflict.
- When you intend to allow Web servers to access the administrative console.
See AlsoManually editing the plug-in configuration
Allowing Web servers to access the administrative console