WebSphere Portal Problem after Update

[Cameron Wallace McKenzie]

A bunch of clients are getting strange problems after installing a WebSphere Portal 6.x maintencance pack. After doing the installation of WPS, the admin console seems to crab out, and deploying portlet from IBM's Rational Application Developer (IRAD) is problematic. The stack trace is below.

They call them maintenance packs for a reason - because after you install them, you have to spend your time doing maintenance to get you back to where you were before the darn installation.

-Cameron McKenzie


---------------
Errorcom.ibm.websphere.management.exception.ConnectorException: ADMC0053E:
The system cannot create a SOAP connector to connect to host localhost at
port 10033 with SOAP connector security enabled.

com.ibm.websphere.management.exception.ConnectorException: ADMC0053E: The
system cannot create a SOAP connector to connect to host localhost at port
10033 with SOAP connector security enabled.
at
com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:405)
at
com.ibm.wps.was.helper.WASAdminServiceHelper.getAdminClient(WASAdminServiceHelper.java:135)
at com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.initVars(WAS5Admin.java:331)
at com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.(WAS5Admin.java:205)
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.getInstanceImpl(WAS5Admin.java:259)
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.access$000(WAS5Admin.java:76)
at com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin$1.run(WAS5Admin.java:226)
at
com.ibm.ws.security.auth.distContextManagerImpl.runAs(distContextManagerImpl.java:2784)
at
com.ibm.ws.security.auth.distContextManagerImpl.runAsSystem(distContextManagerImpl.java:2661)
--------------------

[Cameron Wallace McKenzie]

Hmmm....Just got an update as I submitted that.

Apparently, the problem is documented in the readme for IRAD. After doing the update, you have to delete the WAS server that is created with the IRAD server installation, create a new WebSphere Portal Server in the server perspective, and then bounce IRAD, stopping and starting it again.

Then, you need to initialize the server status. Not sure why, but you do. And apparently, you have to do that little initialize server status step in the server perspective every subsequent time you start up IRAD.

Sounds reasonable and straight forward. Surprised I didn't just do that on my own.

-Cameron McKenzie