Wednesday, April 27, 2011

Propagating WAS 7.0 Plugin to Remote IHS Server

Sometimes it looks like everything is right in the httpd.conf and admin.conf files, but stuff still just doesn't want to work.  Very frustrating and time consuming until you realize that you missed one little step.

If propagating a plugin from WAS 7.0 admin console to an IHS 7.0 server results in the following errors, then you may be simply missing an admin.passwd file. 

These two messages appear in the WAS console and the dmgr SystemOut.log:

PLGC0063E: The propagation of the plug-in configuration file ... on the Web server computer failed.
PLGC0049E: The propagation of the plug-in configuration file failed for the Web server.
... and this one appears in the admin_error.log of your IHS server's logs directory: 

[Wed Apr 27 14:57:15 2011] [error] [client 127.0.0.1] user MyAdmin not found: /wasadmin
Even though all of the user and account names are set correctly in the WAS console and on the target IHS server's various config files, the admin.passwd file is probably missing.  Try setting the admin.passwd file by using the following command (of course, substituting "MyAdmin" for your local account name):

./htpasswd -c /opt/IBM/HTTPServer/conf/admin.passwd MyAdmin
Then restart your admin server using the /HTTPServer/bin/adminctrl stop | start commands, and try to propagate the plugin again.  With any luck, you're in business.

This will create the admin.passwd account in the HTTP Server's conf directory.  Restart the admin server and try the propagation again.... worked for me!

1 comment: