Installing the Business Process Container using root when the Security Role Mapping does not allow the Container to start
 Technote (troubleshooting)
 
Problem(Abstract)
The installation of the Business Process Container is part of the process to install the component Process Choreographer in IBM® WebSphere® Application Server Enterprise edition.

In the Administrative Console under Servers > Application Server > and Additional Properties > Business Process Container, you must complete several fields to install and configure the container. If you enter the user ID of root for the Security Role Mapping , the configuration process places this value under Mapped Groups instead of Mapped Users.

This can be seen under Applications > Enterprise Applications > Select BusinessContainer_hostname_server1 > Additional Properties > Map security roles to users/groups. This causes the Business Process Container to not start successfully.
 
Cause
This is a problem with the configuration scripts. An underlying JACL script, which by default is BPESystemAdministrator (role), causes the Security Role Mapping to map as a group under MappedGroup.
 
Resolving the problem
The definition of the field states:
Security Role For Process Administrator
The security role that the process container uses to run a process.

Data type String
Default ProcessAdministrator

Use either of these technotes to change the Role of BPESystemAdministrator:
Remove the user ID of root from under Mapped Groups and place it under Mapped Users.

You should now be able to start the Business Process Container.
 
Related information
Installing the business process container
Business Process Container settings
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Enterprise Edition (EE)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1174589
IBM Group: Software Group
Modified date: Apr 7, 2005