Plug-in propagation fails with PLGC0063E and PLGC0049E when copying to remote Web server

Resolving The Problem

Verify you have taken the following steps to allow propagation to be successful.

Note: As a work around you can manually copy, from the Application Server side, the plugin-cfg.xml file to the remote Web server. This will allow you to verify that your remote Web server is working properly with your Application Server, until you get your propagation working.

1. Set the username and password on the IBM HTTP Server side. Run per the instructions provided in the link below, under Related information, for the htpasswd command.
   install_root/bin/htpasswd -m <install_dir>/conf/admin.passwd [login name]
   
   The user ID and password should now be set.
   
   
2. Restart the IBM HTTP Server admin process by first using the following command:
   install_root/bin/adminctl stop
   
   
   Then use the following command to start the admin process.
   install_root/bin/adminctl start
   
   
3. In the WebSphere administrative console under the webserver > Remote Web server management page set the same username and password that was used in the setup in step 1. It is very important that the user ID and password of both match. The port used is 8008.
   
   
4. In the administrative console, stop and start the Web server, under Web servers.
   
   
5. Set permissions. For example, if the remote Web server path to the plug-in is the following:
   /usr/IHSPlugin/Plugins/config/webserver1/plugin-cfg.xml
   
   
   Change the permissions on “OTHER” to have executable permission up the complete path:
   rwx --- --x
   
   
   So /usr would have "OTHER" set to execute:
   rwx --- --x
   
   
   Then /usr/IHSPlugin would have the following, and so on:
   rwx --- ---x
   
   Match your original permissions, just add execute to "OTHER".
   
   
6. If you have manually copied the plugin-cfg.xml file to the remote Web server as a workaround, remove the copied plug-in, then propagate the new plug-in. Otherwise, it will try to open the old plugin-cfg.xml file rather than creating a new one.
   
   
7. If your plugin-cfg.xml file still does not propagate, see Troubleshooting: Plug-in Generation and Propagation for V6.1, V7, V8 and V8.5
   
   To debug, perform the following:
1. In the admin.conf change the loglevel to debug.
   
   
2. Restart the IBM HTTP Server admin process by first using the following command:
   install_root/bin/adminctl stop
   
   Then use the following command to start the admin process.
   install_root/bin/adminctl start
   
   
3. Propagate the plug-in from the administrative console.
   
   
4. Send in the admin.conf, admin.error_log, admin.access_log and save the exception from the administrative console.
   
   
5. From the remote Web server, run the following command and send in the output:
   ps -ef | grep http
   
   
6. On UNIX®, run the following command for each level of the directory path leading up to where the plugin-cfg.xml is actually stored and send in this output:
   ls -la
   
   

• Web Server Configuration
• Enabling access to the administration server using the htpasswd utility