FreeKB - IBM WebSphere Resolve "PLGC0063E and PLGC0049E"
IBM WebSphere - Resolve "PLGC0063E and PLGC0049E"

PLGC0063E and PLGC0049E appears when attempting to propagate the web server plugin in WebSphere.


IHS Admin Server

On the IHS web server, ensure the admin server is running. If the admin server is not running, start the admin server.

~]# ps -ef | grep admin
nobody  12345     1  0  07:04  ?  00:00:00 -f /path/to/admin.conf -k start
nobody  12345  1234  0  07:04  ?  00:00:00 -f /path/to/admin.conf -k start
nobody  12345  1234  0  07:04  ?  00:00:00 -f /path/to/admin.conf -k start
nobody  12345  1234  0  07:04  ?  00:00:00 -f /path/to/admin.conf -k start


Ensure you can access the admin server over HTTP, and that the admin server URL produces a page prompting you for your username and password. 


Then, check the admin_error.log file. To resolve the following issue, I had to update the admin.password file to be owned by the user that started the admin server.

AH01620: Could not open password file: /opt/IBM/WebSphere/IHS/conf/admin.password


If the wasadmin page produces something like "page cannot be displayed", SSL may be enabled in admin.conf. You'll want to comment out the SSL directives in admin.conf and then restart the admin server so that you can access the admin server over HTTP.

#SSLServerCert default
#Keyfile "/path/to/keyfile.kdb"


If the wasadmin page produces 403 Forbidden, you probably have a syntax error in your URL, such as "wsadmin" instead of "wasadmin". Or, refer to this article.

Once you can get to the admin page URL over HTTP, when you provide your username and password, the following page should be displayed. This is normal, and not suggestive of a problem. This confirms you are using the appropriate username and password.


In the dmgr, at Servers > Server types > Web servers > your web server > Remote web server management, ensure the port and username match the port and username in the admin.conf file on the admin server.

On the server running the admin server, use the htpasswd command line tool to verify the password is valid.

${ihs_install_root}/bin/htpasswd -v ${ihs_install_root}/conf/admin.passwd john.doe



Directory Permissions

When you attempt to propagate the plugin, the directory where the plugin is being propagated to will be displayed. In this example, the directory is /opt/IBM/WebSphere/Plugins/config/ Ensure the user (john.doe in this example) has write permission to the directory. Setting the user as the owner of the directory with rwx (read write execute) permissions will ensure the user has permission to write to the directory.

chown john.doe /opt/IBM/WebSphere/Plugins/config/
chmod u+rwx /opt/IBM/WebSphere/Plugins/config/


If the plugin-cfg.xml file already exists in the target directory, remove the plugin-cfg.xml file.

rm /opt/IBM/WebSphere/Plugins/config/


You should now be able to propagate the plugin.

Add a Comment

We will never share your name or email with anyone. Enter your email if you would like to be notified when we respond to your comment.

Please enter c19f2 in the box below so that we can be sure you are a human.


Web design by yours truely - me, myself, and I   |   |