WebSphere Portal Server - Solution - "Document Manager cannot communicate with content repository"

Author

Solution - "Document Manager cannot communicate with content repository"

2005-11-18, 7:51 am

Hi

Just saw this problem today. After a clean installation of WP 5.1.0.1 on Red Hat Linux (using Cloudscape with no LDAP), the Document Manager portlet fails to render with: -

"Document Manager cannot communicate with content repository"

The Configure and Edit modes also fail to render.

The SystemErr.log shows: -

badEnv.jsp pe = null

repeatedly ( for every attempt to hit the portlet, I assume ).

We saw no other relevant errors in the Portal or WAS logs - we could see badEnv.jsp being init'd within the SystemOut.log and, on further examination, the JSP in question seems to be trying, and failing, to retrieve the user's session, hence the null retu
rn.

This appears to be caused by a failure, during the installation, to properly initialise the content repository.

The solution is to run the following command: -

WPSConfig cfg-jcr-resources

to re-initialise the repository.

The script will start the Portal server, make the required changes, and then stop/start the server again. At that point, you should be able to log in and all should be fine.

PS In our case, we had to add the PortalAdminPwd property to wpconfig.properties as the script needs to authenticate with the Portal server.

Hope this helps.

Dave Hay
david_hay@uk.ibm.com

2006-01-23, 7:53 am

Hi Dave,

I also experienced this problem with a WebSphere Portal v5.1 installation on XP. I ran the configuration task but it failed with the following error:

Invalid directory C:/Portal51/WebSphere/PortalServer/Content

I looked on another successful installation where the document manager was working and I discovered that this directory was present and contained a jar file; contentdefinition.jar. I copied this file to my installation and re ran the configuration task a
nd everything was fine.

Thanks
Joanne Butler