Tork Wrench » WebSphere Portal

Uninstall Process Server, keep Portal Server

Graham — Fri, 06 May 2011 04:28:26 +0000

Wow, slow 2011 on the blog so far. Time to get back into it.

I was asked by a customer how to uninstall Process Server, while keeping your Portal Server intact. I couldn’t find any documentation or steps to do this, so I figured it out for them.
“Your mileage may vary” – give this a try on a test box first, before you try on a production box. I didn’t test clusters either, although I don’t see how they would present a problem.

These steps are valid for 6.0 .

Unfortunately, the Process Server uninstaller doesn’t do a great job of cleaning up after itself, so we need to go around after it and clean up the mess.

1. Why not confirm you have Process Server installed first? Try:

AppServer/bin/versionInfo.sh

If you get back something with this in it:

Installed Product
---------------------------------------------------
Name IBM WebSphere Process Server
Version 6.0.2.5
ID BPC
Build Level o0843.03
Build Date 10/31/08

Bingo! You have Process server.

2. Run the config task bpe-unconfig . This config task will uninstall Process Server related components from your Portal Server (like the Task Container Enterprise Apps) .

WPSconfig.sh bpe-unconfig

Stop all AppServer processes and then run the Process server uninstaller, which you will find at :

AppServer/_uninstwbi/uninstall

Take care to make sure this box below is unticked, so your whole AppServer isn’t uninstalled.

4. After the uninstaller is completed, delete the following jars in AppServer/lib . They are Process Server jars, and the Portal Server (or server1) will not start until you do this. As you can see there are tons of them. I got the list from seeing what was on the Process Server install iso. This list worked for me in my testing (which consisted of starting Portal and the Admin Console and making sure the UI still worked), but I can’t vouch for any custom code that you are running. As always, try this out in a test environment first, and take a backup before messing around with AppServer/lib . This seems to be a superset of what was installed on my system too – so don’t be alarmed if some of the jars in this list are not present on your system.

$WAS_HOME/lib/ArtifactLoaderImpl.jar
$WAS_HOME/lib/ArtifactLoader.jar
$WAS_HOME/lib/ArtifactResolver.jar
$WAS_HOME/lib/ast-ejbrdbmapping.jar
$WAS_HOME/lib/ast-ejbwsext.jar
$WAS_HOME/lib/ast-j2eewsext.jar
$WAS_HOME/lib/ast-sqlmodel.jar
$WAS_HOME/lib/ast-wrdj2ee.jar
$WAS_HOME/lib/bpcdma.jar
$WAS_HOME/lib/bpcinterop.jar
$WAS_HOME/lib/bpcupgrade.jar
$WAS_HOME/lib/bpc-validation.jar
$WAS_HOME/lib/bpeappinstall.jar
$WAS_HOME/lib/bpecommon.jar
$WAS_HOME/lib/bpecore.jar
$WAS_HOME/lib/bpedeployment.jar
$WAS_HOME/lib/bpegenerator.jar
$WAS_HOME/lib/bpeheaders.jar
$WAS_HOME/lib/bpe.jar
$WAS_HOME/lib/bpel.jar
$WAS_HOME/lib/bpelpp.jar
$WAS_HOME/lib/bpelservices.jar
$WAS_HOME/lib/bpelterms.jar
$WAS_HOME/lib/bpertfw.jar
$WAS_HOME/lib/bpevalidation.jar
$WAS_HOME/lib/brbClient.jar
$WAS_HOME/lib/brbRuleMgmtApp.jar
$WAS_HOME/lib/brbServer.jar
$WAS_HOME/lib/brcore.jar
$WAS_HOME/lib/brulescore.jar
$WAS_HOME/lib/brulescore_nl1.jar
$WAS_HOME/lib/brulescore_nl2.jar
$WAS_HOME/lib/brules.jar
$WAS_HOME/lib/brules-model.jar
$WAS_HOME/lib/brules-scdl.jar
$WAS_HOME/lib/brules-scdl-validation.jar
$WAS_HOME/lib/brules-scdl-validation_nl1.jar
$WAS_HOME/lib/brules-scdl-validation_nl2.jar
$WAS_HOME/lib/brules-validation.jar
$WAS_HOME/lib/brules-validation_nl1.jar
$WAS_HOME/lib/brules-validation_nl2.jar
$WAS_HOME/lib/bsm-runtime.jar
$WAS_HOME/lib/cbcore.jar
$WAS_HOME/lib/cem.jar
$WAS_HOME/lib/cemsop.jar
$WAS_HOME/lib/cmmImpl.jar
$WAS_HOME/lib/cmm.jar
$WAS_HOME/lib/commondbinstall.jar
$WAS_HOME/lib/commonj.connector.jar
$WAS_HOME/lib/commons-jxpath.jar
$WAS_HOME/lib/compensate_blob4k_ejb.jar
$WAS_HOME/lib/compensate_ejb.jar
$WAS_HOME/lib/compensate.jar
$WAS_HOME/lib/compensate_oracle9i_oci_ejb.jar
$WAS_HOME/lib/compensation.jar
$WAS_HOME/lib/core-validation.jar
$WAS_HOME/lib/corona-ejbplugin.jar
$WAS_HOME/lib/corona-emfworkbenchedit.jar
$WAS_HOME/lib/corona-emfworkbench.jar
$WAS_HOME/lib/corona-j2eeplugin.jar
$WAS_HOME/lib/corona-wsdl.jar
$WAS_HOME/lib/correlationsphere.jar
$WAS_HOME/lib/ctcbpeluiex.jar
$WAS_HOME/lib/ctcformatmodel.jar
$WAS_HOME/lib/ctcj2ee.jar
$WAS_HOME/lib/ctc-wsdl.jar
$WAS_HOME/lib/ctcwsdl.jar
$WAS_HOME/lib/customization.jar
$WAS_HOME/lib/customization-model.jar
$WAS_HOME/lib/dmaemf.jar
$WAS_HOME/lib/eclipse-ecore.resources.jar
$WAS_HOME/lib/eclipse-jdtcore.jar
$WAS_HOME/lib/eclipse-mapping.jar
$WAS_HOME/lib/eclipse-osgi.jar
$WAS_HOME/lib/eclipse-resources.jar
$WAS_HOME/lib/eclipse-runtime.jar
$WAS_HOME/lib/eflow2.jar
$WAS_HOME/lib/extensionmodel.jar
$WAS_HOME/lib/fdl2bpelcore.jar
$WAS_HOME/lib/htmlshellwbi.jar
$WAS_HOME/lib/idgenerator.jar
$WAS_HOME/lib/ilm_impl.jar
$WAS_HOME/lib/ilm.jar
$WAS_HOME/lib/installbrmgr.jar
$WAS_HOME/lib/mediation_model.jar
$WAS_HOME/lib/mfc_model.jar
$WAS_HOME/lib/migration-wbi-CommonMigrationInterface.jar
$WAS_HOME/lib/migration-wbi-ics-heritageapi.jar
$WAS_HOME/lib/migration-wbi-ics.jar
$WAS_HOME/lib/mockobjects-alt-jdk1.3-0.09.jar
$WAS_HOME/lib/mockobjects-alt-jdk1.3-j2ee1.2-0.09.jar
$WAS_HOME/lib/mockobjects-core-0.09.jar
$WAS_HOME/lib/mockobjects-jdk1.3-0.09.jar
$WAS_HOME/lib/mockobjects-jdk1.3-j2ee1.2-0.09.jar
$WAS_HOME/lib/modelutils.jar
$WAS_HOME/lib/processbinding.jar
$WAS_HOME/lib/recoveryAdmin.jar
$WAS_HOME/lib/recoveryMBean.jar
$WAS_HOME/lib/relcodegen.jar
$WAS_HOME/lib/resolverutils.jar
$WAS_HOME/lib/rsadaptercci-wbi.jar
$WAS_HOME/lib/rsaexternal-wbi.jar
$WAS_HOME/lib/sca-async.jar
$WAS_HOME/lib/sca-common.jar
$WAS_HOME/lib/sca-container.jar
$WAS_HOME/lib/sca-deploy.jar
$WAS_HOME/lib/sca-ejb.jar
$WAS_HOME/lib/sca-j2c.jar
$WAS_HOME/lib/sca.jar
$WAS_HOME/lib/sca-java.jar
$WAS_HOME/lib/sca-jms.jar
$WAS_HOME/lib/sca-managed.jar
$WAS_HOME/lib/sca-style.jar
$WAS_HOME/lib/sca-webservice.jar
$WAS_HOME/lib/scdl-ae.jar
$WAS_HOME/lib/scdl-eis.jar
$WAS_HOME/lib/scdl-ejb.jar
$WAS_HOME/lib/scdl-infoserver.jar
$WAS_HOME/lib/scdl.jar
$WAS_HOME/lib/scdl-java.jar
$WAS_HOME/lib/scdl-mediation.jar
$WAS_HOME/lib/scdl-mfc.jar
$WAS_HOME/lib/scdl-moduletype.jar
$WAS_HOME/lib/scdl-process.jar
$WAS_HOME/lib/scdl-task.jar
$WAS_HOME/lib/scdl-webservice.jar
$WAS_HOME/lib/scdl-wsdl.jar
$WAS_HOME/lib/selector.jar
$WAS_HOME/lib/selector-model.jar
$WAS_HOME/lib/selector-scdl.jar
$WAS_HOME/lib/selector-scdl-validation.jar
$WAS_HOME/lib/selector-scdl-validation_nl1.jar
$WAS_HOME/lib/selector-scdl-validation_nl2.jar
$WAS_HOME/lib/selector-validation.jar
$WAS_HOME/lib/selector-validation_nl1.jar
$WAS_HOME/lib/selector-validation_nl2.jar
$WAS_HOME/lib/sibx.admin.commands.jar
$WAS_HOME/lib/sibx.aspects.jar
$WAS_HOME/lib/sibx.common.jar
$WAS_HOME/lib/sibx.context.jar
$WAS_HOME/lib/sibx.eets.debug.jar
$WAS_HOME/lib/sibx.mediation.eets.jar
$WAS_HOME/lib/sibx.mediation.engine.jar
$WAS_HOME/lib/sibx.mediation.flowaction.impl.jar
$WAS_HOME/lib/sibx.mediation.flowaction.jar
$WAS_HOME/lib/sibx.mediation.model.jar
$WAS_HOME/lib/sibx.mediation.primitives.jar
$WAS_HOME/lib/sibx-metadata.jar
$WAS_HOME/lib/sibx-profiles.jar
$WAS_HOME/lib/sibx.scax.runtime.jar
$WAS_HOME/lib/sibx-extensionchecker.jar
$WAS_HOME/lib/sibx.admin.commands.wsrr.jar
$WAS_HOME/lib/sibx.admin.runtime.impl.jar
$WAS_HOME/lib/sibx.wccm.config.wsrrresources.jar
$WAS_HOME/lib/sibx.wsrr.proxy.jar
$WAS_HOME/lib/sibx.admin.runtime.jar
$WAS_HOME/lib/sibx.admin.runtime.wsrr.jar
$WAS_HOME/lib/sibx.wccm.config.sibxscaresources.jar
$WAS_HOME/lib/smaputils.jar
$WAS_HOME/lib/smobo.jar
$WAS_HOME/lib/srm_impl.jar
$WAS_HOME/lib/srm.jar
$WAS_HOME/lib/staffsupport.jar
$WAS_HOME/lib/taskapi.jar
$WAS_HOME/lib/taskappinstall.jar
$WAS_HOME/lib/taskcemsop.jar
$WAS_HOME/lib/taskdeployer.jar
$WAS_HOME/lib/taskgenerator.jar
$WAS_HOME/lib/task.jar
$WAS_HOME/lib/taskldap.jar
$WAS_HOME/lib/taskmbean.jar
$WAS_HOME/lib/taskscdlvalidation.jar
$WAS_HOME/lib/tasksystem.jar
$WAS_HOME/lib/taskuserregistry.jar
$WAS_HOME/lib/taskvalidation.jar
$WAS_HOME/lib/tel.jar
$WAS_HOME/lib/vfdcore.jar
$WAS_HOME/lib/WBIAdapterBGRuntime.jar
$WAS_HOME/lib/WBIAdapterRuntime.jar
$WAS_HOME/lib/wbia.jar
$WAS_HOME/lib/wbiBOmigration.jar
$WAS_HOME/lib/wbiBOS.jar
$WAS_HOME/lib/wbiBOValidator.jar
$WAS_HOME/lib/wbiCore.jar
$WAS_HOME/lib/wbicoreupgrade.jar
$WAS_HOME/lib/wbiinstall.jar
$WAS_HOME/lib/wbiMapService.jar
$WAS_HOME/lib/WBIMCBEBuilder.jar
$WAS_HOME/lib/wbi-mediation-core.jar
$WAS_HOME/lib/wbiMonitorCore.jar
$WAS_HOME/lib/wbiMonitorPolicy.jar
$WAS_HOME/lib/wbiPS.jar
$WAS_HOME/lib/wbiRelMgr.jar
$WAS_HOME/lib/wbiRS.jar
$WAS_HOME/lib/wbischedulercommon.jar
$WAS_HOME/lib/wbisession.jar
$WAS_HOME/lib/wbisessionPolicy.jar
$WAS_HOME/lib/wbiupgrade.jar
$WAS_HOME/lib/wbiutil.jar
$WAS_HOME/lib/wbi-validation.jar
$WAS_HOME/lib/wccm_services_bpc.jar
$WAS_HOME/lib/wccm_services_core.jar
$WAS_HOME/lib/wccm_services_wbi.jar
$WAS_HOME/lib/wcdl.jar
$WAS_HOME/lib/wcdl-process.jar
$WAS_HOME/lib/wcdl-service.jar
$WAS_HOME/lib/wcdl-wsif.jar
$WAS_HOME/lib/wpcr.jar
$WAS_HOME/lib/wpsanttasks.jar
$WAS_HOME/lib/WPS_IVTClient.jar
$WAS_HOME/lib/ws-bpc-config-appdeploy.jar
$WAS_HOME/lib/ws-bpc-config-resources.jar
$WAS_HOME/lib/ws-bpc-config-server.jar
$WAS_HOME/lib/ws-config-admin.jar
$WAS_HOME/lib/ws-core-config-server.jar
$WAS_HOME/lib/ws-core-j2eex.jar
$WAS_HOME/lib/ws-wbi-config-cell.jar
$WAS_HOME/lib/ws-wbi-config-resources.jar
$WAS_HOME/lib/ws-wbi-config-server.jar
$WAS_HOME/lib/ws-wbi-j2eex.jar
$WAS_HOME/lib/wtembean.jar

If you don’t delete these jars, you will get the following error message after issuing startServer.sh :

ADMU0116I: Tool information is being logged in file
/opt/WebSphere/AppServer/profiles/wp_profile/logs/server1/startServer.log
ADMU0128I: Starting tool with the wp_profile profile
ADMU3100I: Reading configuration for server: server1
com.ibm.ws.exception.WsException: Error processing plugin for
jar:file:/opt/WebSphere/AppServer/lib/scdl-infoserver.jar!/META-INF/ws-server-model.init
class: com.ibm.wsspi.sca.scdl.infoserver.impl.InfoserverPackageImpl
at com.ibm.ws.config.ModelMgr.initializeModels(ModelMgr.java:110)
at com.ibm.ws.config.ModelMgr.initialize(ModelMgr.java:49)
at com.ibm.ws.runtime.service.RepositoryImpl.(RepositoryImpl.java:48)
at com.ibm.ws.runtime.service.RepositoryImpl.(RepositoryImpl.java:39)
at com.ibm.ws.runtime.service.RepositoryFactoryImpl.createRepository(RepositoryFactoryImpl.java:32)
at com.ibm.ws.runtime.service.RepositoryFactory.createRepository(RepositoryFactory.java:55)
at com.ibm.ws.management.tools.WsServerLauncher.initializeRepositoryAndLauncher(WsServerLauncher.java:393)
at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:265)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:230)
at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:108)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:571)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.config.ModelMgr.initializeModels(ModelMgr.java:106)
... 16 more

5. It’s also a good idea to clean out wp_profile/logs/* as there is a cache of jar file paths and their associated classes (the preload cache) that will need to be regenerated after deleting those jars.

6. The only thing the bpe-unconfig task doesn’t seem to do is delete the BPE shared library. To do this, start server1, and log in to the admin console. Navigate to Environment -> Shared Libraries and highlight the BPE library and click delete.

7. You’re done, start Portal and test everything works!

I also wrote a little script that does some checks and then does all this for you (except for step 6 which I couldn’t be inspired enough to write a jacl script for). It’s fairly quick and dirty, but if nothing else it will give you an idea of what has to happen to remove Process Server. You can get it here. Just rename the suffix after you download it. Understandably, WordPress would not yet me save a shell script up to my server.

How to get rid of SECJ0055E error message in WebSphere Portal

Graham — Mon, 11 Oct 2010 23:44:34 +0000

On a Portal 6.0 server I’m working on, I kept seeing the following error message in my SystemOut.log . It came up every half hour.

[10/11/10 12:17:41:439 EST] 0000005b MethodDelegat A SECJ0055E: Authentication failed for wasadmin. The user id or password may have been entered incorrectly or misspelled. The user id may not exist, the account could have expired or disabled. The password may have expired.

But my Was Password was correct. I had set it myself and just used it to log into the admin console.

The key is the “MethodDelegat” part of the log message. This column is the source of the log message. “Delegate method” made me think of bundled applications that use the RunAsRole . The pznscheduler application runs on a schedule, and sure enough also has a RunAsRole associated with it.

So what has happened, is that the WAS password has changed but the password is also saved with the pznscheduler application, and that saved password hasn’t been changed. Quite simply, there is a mismatch. This can happen on 6.1 and 7.0, and may also be related to the Portal Admin Password – it just depends which user is mapped as the RunAsRole . There are more applications that use the RunAsRole for Portal 6.0 .

For 6.0 here are the default out of the box applications you need to worry about when changing the password. LWP_TAI, pznscheduler, LWP_CAI, LWP_Security_Ext.

Of course, you may have other custom applications you need to worry about. The LWP apps use the Portal Admin user by default, so that’s why I didn’t have to change them.

For 6.1 you should check pznscheduler and CatalogHandler and for 7.0 the pznscheduler application is the only one you need to worry about.

So to fix it up, if you log into the WAS Admin Console and look for the pznscheduler app in the list of Enterprise Applications, you will see the “Map RunAs roles to users” link like in the picture below.

Then in the next dialog, reenter the new password.

This dialog can be a bit funny so you may have to play around with it a bit. Restart Portal and the error should be gone!

CNTR0019E: Initialization failed due to invalid property “supportedMemberTypes”.

Graham — Mon, 14 Dec 2009 06:47:44 +0000

Any problem where WMM (WebSphere Member Manager) doesn’t start properly is a deal breaker for Portal. Once WMM fails, every other component will fail, and you’ll be faced with a nasty 404 message.

After installing 6.0.1.4-WP-IFPK83731.zip and 6.0.1.4-WP-IFPK70263.zip on a machine here I got this error message, and a 404 when I tried to hit portal. These fixes update the version of WMM to the (current) latest version. Here’s what was in my SystemOut.log

[12/14/09 17:31:09:618 EST] 0000002a SystemOut O WMM Implementation Version: WMM5.6_PK83731 (April 1 2009)
[12/14/09 17:31:09:618 EST] 0000002a WSMM Message E com.ibm.ws.wmm.MemberRepositoryManager init() Initialization failed due to invalid property “supportedMemberTypes”.
[12/14/09 17:31:09:653 EST] 0000002a WSMM Message E com.ibm.ws.wmm.objectimpl.MemberServiceBeanBase ejbCreate() com.ibm.websphere.wmm.exception.InitializationException: Initialization failed due to invalid property “supportedMemberTypes”.
[12/14/09 17:31:09:655 EST] 0000002a ExceptionUtil E CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method “getConfigurationData”. Exception data: com.ibm.ejs.container.CreateFailureException: ; nested exception is:
java.lang.reflect.InvocationTargetException
at com.ibm.ejs.container.StatelessBeanO.(StatelessBeanO.java:172)
at com.ibm.ejs.container.CMStatelessBeanO.(CMStatelessBeanO.java:58)
at com.ibm.ejs.container.CMStatelessBeanOFactory.create(CMStatelessBeanOFactory.java:40)
at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:913)
at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:1016)
at com.ibm.ejs.container.activator.UncachedActivationStrategy.atActivate(UncachedActivationStrategy.java:83)
at com.ibm.ejs.container.activator.Activator.activateBean(Activator.java:595)
at com.ibm.ejs.container.EJSContainer.preInvokeActivate(EJSContainer.java:3439)
at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2836)
at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2745)
at com.ibm.websphere.wmm.objects.EJSRemoteStatelessMemberService_14d751a3.getConfigurationData(Unknown Source)
at com.ibm.websphere.wmm.objects._MemberService_Stub.getConfigurationData(_MemberService_Stub.java:2292)
at com.ibm.wps.services.puma.SystemWMMAccessBean$39.run(SystemWMMAccessBean.java:906)
at com.ibm.ws.security.auth.distContextManagerImpl.runAs(distContextManagerImpl.java:2771)
at com.ibm.ws.security.auth.distContextManagerImpl.runAsSystem(distContextManagerImpl.java:2651)
at com.ibm.wps.services.puma.SystemWMMAccessBean.getConfigurationData(SystemWMMAccessBean.java:912)
at com.ibm.wps.services.puma.RealmAwareURManager.initRealms(RealmAwareURManager.java:117)
at com.ibm.wps.services.puma.RealmAwareURManager.(RealmAwareURManager.java:103)
at com.ibm.wps.services.puma.PumaServiceImpl.init(PumaServiceImpl.java:215)
at com.ibm.wps.services.Service.init(Service.java:107)
at com.ibm.wps.services.Service.init(Service.java:83)
at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:400)
at com.ibm.wps.services.ServiceManager.getService(ServiceManager.java:527)
at com.ibm.wps.services.ServiceManager.getService(ServiceManager.java:553)
at com.ibm.wps.services.puma.Puma.(Puma.java:52)
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl.initializeDomainConfig(AccessControlDataManagementServiceImpl.java:885)
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl.reinit(AccessControlDataManagementServiceImpl.java:792)
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl.init(AccessControlDataManagementServiceImpl.java:439)
at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:400)
at com.ibm.wps.services.ServiceManager.getService(ServiceManager.java:527)
at com.ibm.wps.ac.impl.AccessControlDataManagement.(AccessControlDataManagement.java:41)
at com.ibm.wps.ac.impl.AccessControlServiceImpl.initializeServices(AccessControlServiceImpl.java:138)
at com.ibm.wps.ac.impl.AccessControlServiceImpl.init(AccessControlServiceImpl.java:114)
at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:400)
at com.ibm.wps.services.ServiceManager.getService(ServiceManager.java:527)
at com.ibm.wps.ac.internal.AccessControlLookupManager.getAccessControlLookup(AccessControlLookupManager.java:37)
at com.ibm.wps.ac.ACManager.getAccessControl(ACManager.java:132)
at com.ibm.hrl.siapi.search.admin.utils.PortletUtils.getPortalAdminUserID(PortletUtils.java:321)
at com.ibm.hrl.siapi.search.admin.portlets.manage.SearchAdminPortletManager.(SearchAdminPortletManager.java:64)
at com.ibm.hrl.siapi.search.admin.portlets.SiapiSearchAdminPortlet.init(SiapiSearchAdminPortlet.java:532)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:320)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1821)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:141)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:885)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:612)
at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:479)
at com.ibm.ws.webcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:123)
at com.ibm.ws.webcontainer.VirtualHost.addWebApplication(VirtualHost.java:146)
at com.ibm.ws.webcontainer.WebContainer.addWebApp(WebContainer.java:940)
at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:893)

I’m not sure what was updated in WMM for this one, but the solution is simple: install WAS 6.0.2.37 to fix it.

5 Steps to installing Portal 6.1.5 on Ubuntu 9.10

Graham — Mon, 07 Dec 2009 04:06:20 +0000

Another new version of Portal, another new version of Ubuntu . Here’s how to get them to play nicely together. Most of these steps are needed for any recent version of Ubuntu. Obligatory disclaimer, Ubuntu is a non supported platform, so don’t run anything important on this it. IBM support won’t help you!

1. Install libstdc++5 from here. Apparently this has been dropped from karmic (9.10) but you can use 9.04 packages instead and it will work.

2. Make sure you can ping yourself on the fully qualified hostname that you will be using in the install. This is a good general tip for installing Portal. If the machine doesn’t respond, add an alias in your /etc/hosts file, like this:

127.0.0.1 localhost yourhostname yourhostname.fullyqualified.com

Also think about disabling any firewalls . The install process needs to be able to connect to certain ports running on your machine.
If you let the install run all the way through, and then re enable your firewall after, debugging and adding new firewall exceptions should be way easier.

3. Drop this file in /etc . It will make AppServer think that you are running RHEL
5, which is a supported OS.

4. Unlink /bin/sh and link it to /bin/bash, like this:

cd /bin
unlink sh
ln -s /bin/bash sh

Here’s a more detailed post about why you need to do this, if you are interested.

5. Don’t use sudo ./install.sh, but rather execute sudo su and then run ./install.sh . The installer executes a ConfigEngine.sh task late in the install, and if you use sudo to execute install.sh, the installer will attempt to run the ConfigEngine task as your logged in user, not as root, and the task will fail.

I think you should also be able to run the install as a non root user, I just haven’t tried it yet, I will post back when I have.

These steps also work with 6101.

Oracle runstats oneliner (ok, two liner)

Graham — Thu, 03 Sep 2009 08:24:30 +0000

Use this to generate a runstats script for your Oracle system. Only works for 6.1 . Also very ugly

#!/bin/bash
export PROFILE_PATH=/opt/WebSphere/wp_profile
cat ${PROFILE_PATH}/ConfigEngine/properties/wkplc_comp.properties | grep DbUser | grep -v source | grep -v '#' | grep -v DBA | awk -F = '{print "execute dbms_stats.gather_schema_stats(ownname=>'"'"'" $2 "'\'', cascade=> TRUE);"}' > reorg.sql

Now copy this file to your oracle system and run this:

sqlplus / as sysdba @reorg.sql

Pow! All done.

Tips for changing your Portal datasources

Graham — Tue, 04 Aug 2009 05:33:09 +0000

For some reason, we’ve got a test system that is hooked up to a db2 database that is using DHCP. This would be ok if Portal was configured to talk to the hostname of the database server, but it’s using the IP. So the inevitable happened and the IP of the database changed and the Portal server went down.

So the obvious fix is to change the datasource so it’s using the hostname of the database server, rather than the ip (or set a static IP for the database server, but that wouldn’t really require a whole blog post now would it!).

To do this, fire up the WAS admin console and navigate to datasources.

Your list of datasources might be different to mine, depending on your database, but the principles are the same.

Go into each datasource and at the bottom you will see a properties dialog. Change the old IP to a hostname.

change the IP

All of them need to be changed, so go back into each one and change it. Now run the test, by selecting each one and clicking the test connection button.

You should get a message like this:

successful test connection message

Now start Portal. Hmm, I get this when I try to go to the site….

” Error 404: Initialization of one or more services failed. ”

Check the SystemOut.log :

Caused by: com.ibm.websphere.ce.cm.StaleConnectionException: [ibm][db2][jcc][t4][2043][11550] Exception java.net.SocketException: Error opening socket to server /9.185.226.121 on port 50,000 with message: Operation timed out: connect:could be due to invalid address.DSRA0010E: SQL State = null, Error Code = -4,499

at sun.reflect.GeneratedConstructorAccessor64.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:522)

at com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHelper(GenericDataStoreHelper.java:523)

at com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(GenericDataStoreHelper.java:578)

at com.ibm.ws.rsadapter.AdapterUtil.mapException(AdapterUtil.java:2159)

... 11 more

Hang on, the datasource test worked? Why won’t the server start? It looks like it’s using the old database server IP still!

The answer lies in the transaction logs that WAS uses. These binary log files contain XA transactions that might not have been executed yet. You should take care when messing about with these files – they are there for a reason. But on the other hand, the server won’t start now, so we can hardly make things worse, can we ) . Stop the server1 and WebSphere_Portal application servers and go to your wp_profile directory. Delete the contents of the tranlog and recoverylogs directories and try to start the server again.

This message should appear in SystemOut :

[4/08/09 15:23:16:825 EST] 00000012 LogHandle I CWRLS0007I: No existing recovery log files found in C:/WebSphere/wp_profile\tranlog\win61\win61\WebSphere_Portal\transaction\tranlog. Cold starting the recovery log.

[4/08/09 15:23:16:825 EST] 00000012 LogFileHandle I CWRLS0006I: Creating new recovery log file C:/WebSphere/wp_profile\tranlog\win61\win61\WebSphere_Portal\transaction\tranlog\log1.

[4/08/09 15:23:16:841 EST] 00000012 LogFileHandle I CWRLS0006I: Creating new recovery log file C:/WebSphere/wp_profile\tranlog\win61\win61\WebSphere_Portal\transaction\tranlog\log2.

[4/08/09 15:23:16:856 EST] 00000012 LogHandle I CWRLS0007I: No existing recovery log files found in C:/WebSphere/wp_profile\tranlog\win61\win61\WebSphere_Portal\transaction\partnerlog. Cold starting the recovery log.

[4/08/09 15:23:16:856 EST] 00000012 LogFileHandle I CWRLS0006I: Creating new recovery log file C:/WebSphere/wp_profile\tranlog\win61\win61\WebSphere_Portal\transaction\partnerlog\log1.

[4/08/09 15:23:16:856 EST] 00000012 LogFileHandle I CWRLS0006I: Creating new recovery log file C:/WebSphere/wp_profile\tranlog\win61\win61\WebSphere_Portal\transaction\partnerlog\log2.

[4/08/09 15:23:16:903 EST] 00000012 RecoveryManag A WTRN0028I: Transaction service recovering 0 transactions.

Success, now the server will start up!

How to get your own local copy of the Infocenter

Graham — Wed, 01 Jul 2009 02:42:33 +0000

If I’m going out to meet a customer, I’ll always make sure to have a local copy of the infocenter on hand in case I have to look something up.

Luckily enough, there’s an easy way to do this. The infocenters for WebSphere Application Server and WebSphere Portal are available in Eclipse Help System form, which is pretty much the same way they are presented over the web.

You can download the infocenter in Eclipse Help System format from this page for WAS and this page for Portal.

If you don’t have Eclipse already, download it from here. Any one of the versions should do. Unzip Eclipse and then copy the infocenter zips into the eclipse/plugins directory. Then unzip the infocenter zips in the plugins directory.

Now start Eclipse, and pick any old workspace. Click Help -> Help Contents, and the Infocenter zips that you copied in should be along side any other help files that come with Eclipse originally.

Now you have a local copy, make sure to update it since the infocenter is updated monthly.

Getting WebSphere Portal to install on Ubuntu

Graham — Mon, 04 May 2009 04:32:20 +0000

Ok, ok, I know Ubuntu isn’t supported by IBM, but if you’re a developer, and you run Ubuntu on your laptop and would like to run Portal on there too, here’s how you do it. This should work for Debian too . I guess this isn’t really a Portal only problem, rather it’s a general Application Server + Ubuntu issue. I’ve only tried this with 6.1, but it is probably an issue with 6.0 as well, since it uses similar profile creation code.

For some reason Ubuntu, ships a shell called ‘dash’ as their default, rather than good old bash. (Well, they have their reasons.) This presents a problem for App Server, as all the scripts in AppServer/bin use #!/bin/sh (the Bourne shell) as their command interpreter, which on a Redhat machine is symlinked to /bin/bash . The reason why AppServer uses the Bourne shell is that it needs to work on AIX and Solaris too, and you can’t be sure that you have bash on one of those machines.

If you try to call wsadmin.sh on an Ubuntu system you get this error :

/opt/WebSphere/AppServer/bin/wsadmin.sh: 116: Bad substitution

Now, when you’re installing Portal, it installs AppServer, and then calls the manageprofile.sh script to create the default profile for Portal “wp_profile” . Manageprofile.sh calls a bunch of ant scripts that needs to use wsadmin.sh (you can see where I’m going here….) . You might notice in AppServer/log/wp_profile_create.log messages like this :

Checking for wsadmin listener initialization
Is wsadmin listener available? ? false
Returning with returnCode=-1
Failure detected in fatal config action.
wsadmin failed with exception = wsadmin task failed with return code :-1

It actually hangs for 20 minutes waiting for wsadmin to start!

So how do you fix it? Simply, before you install it, unlink /bin/sh -> /bin/dash , and relink so it reads /bin/sh -> /bin/bash

Carefully:

cd /bin
unlink sh
ln -s /bin/bash sh

Now the install should run properly.