Portal server fails to start with 404 error after being federated and clustered

Technote (troubleshooting)


Problem

Portal server fails to start after being federated and clustered to the DMGR cell.

Exception in systemOut.log shows:

Error 404: javax.servlet.UnavailableException: Initialization of one or

more services failed.
...
Caused by: com.ibm.websphere.wim.exception.EntityNotFoundException:
CWWIM4001E The 'uid=wpadmin,o=defaultWIMFileBasedRealm' entity was not
found.



Cause

This is due to the Portal admin user not being part of the DMGR's user repository

Diagnosing the problem

When you install Portal and set up an ID (wpadmin for example), we set up two properties that say:

- wpadmin (using the example) is the Portal Administrative ID
- wpsadmins (hardcoded by default) is the Portal Administrative Group ID

and create both IDs in the default user repository.

When you federate Portal node to the DMGR cell, it inherits the DMGR's security configuration and Portal starts using the DMGR's user repository.

Portal is still configured to look for 'wpadmin' as the main administrator and 'wpsadmins' as the main administrators group. If it can't find either of these IDs in the DMGR's user repository, we get these errors.

When configuring the DMGR profile for setting up a Portal cluster the Portal Admin Group ID is automatically created (default: wpsadmins), so that ID will be taken care of.

What does not get created is the Portal Admin user ('wpadmin') in the DMGR's user repository, and that's what the problem is.

Resolving the problem

There are two ways to fix this:


1. Add the Portal admin user as a new user in the DMGR admin console (System Administration -> Manager Users).

note: In the above scenario 'wpadmin' would need to be added.

or

2. Run the configEngine task called wp-change-portal-admin-user, to update Portal to start using an existing user in the DMGR's repository who is part of the wpsadmins group.

ie. ConfigEngine.sh|bat wp-change-portal-admin-user -DWasPassword=password -DnewAdminId=<valid admin id> -DnewAdminPw=<admin pw> -DnewAdminGroupId=<valid admin group in DMGR>

note: This user can be the DMGR admin ID or any ID that exists in the DMGR's Portal Admin group.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Portal

Software version:

6.1, 7.0, 8.0

Operating system(s):

AIX, IBM i, Linux, Solaris, Windows, z/OS

Reference #:

1579120

Modified date:

2012-12-24

Translate my page

Machine Translation

Content navigation