Install > Installing WebSphere Commerce > Remote Web server tasks


Copy the plugin-cfg.xml file to Web server

If you are not using an IBM HTTP Server as your Web server, complete the steps on this page each time a change is made to the plugin-cfg.xml file to copy the plugin-cfg.xml file to the remote Web server.


Procedure

  1. Stop the Web server

  2. Copy the following file on the Commerce node to the same location on the Web server node...

    • WebSphere Commerce in a clustered environment

      DMGR_PROFILE/config/cells/cellname/nodes/webserver_node/servers/webserver_name/plugin-cfg.xml

    • WebSphere Commerce in a non- clustered environment

      WC_PROFILE/config/cells/cellname/nodes/webserver_node/servers/webserver_name/plugin-cfg.xml

    Overwrite any existing plugin-cfg.xml file on the Web server node.

    If location is unknown, to determine...

    1. Launch the WAS administrative console.

    2. In the Navigation area, expand Servers and click Web servers. The Web servers page displays.

    3. Select the check box next to webserver1 and click Generate Plug-in.

    4. A message box displays with the location of the plug-in configuration file.

    The plugin-cfg.xml file contains directory-specific information. If you do not copy the file to the exact same directory structure on the Web server node, the Web server will not function correctly and WebSphere Commerce will be inaccessible.

  3. Copy the following file on the Commerce node to the same location on the Web Server node:

    WC_PROFILE/config/cells/cellname/nodes/nodename/servers/server_name/plugin-cfg.xml

    Overwrite any existing plugin-cfg.xml file on the Web server node.

    The plugin-cfg.xml file contains directory-specific information. If you do not copy the file to the exact same directory structure on the Web server node, the Web server will not function correctly and WebSphere Commerce will be inaccessible.

  4. For Sun Java System Web Server 7.0 Update 4 users, ensure that the path for the WAS plug-in is shown correctly in the configuration files. The line in a configuration file for the WAS plug-in resembles the following text: 

    Init fn="as_init" 
bootstrap.properties="WAS_HOME/config/cells/plugin-cfg.xml"

Init fn="as_init" 
bootstrap.properties="WAS_HOME\config\cells\plugin-cfg.xml"

    For Microsoft IIS users, the path for the WAS plug-in can be found in the file plugin-cfg.loc.

    If the path in the configuration files does not match the full path to the plugin-cfg.xml file on the Web server node, correct the path.

  5. Start the Web server


+

Search Tips   |   Advanced Search