Assign users to administrator roles



Search Tips   |   Advanced Search



Administrator roles are used to control access to WAS administrative functions. There are four roles: administrator, configurator, operator and monitor.

Administrator role

Users and groups assigned to the administrator role can perform all administrative operations and can set up both J2EE role-based and Java 2 security policy.

Configurator role

Users assigned to the configurator role can perform all of the day-to-day configuration tasks including installing and uninstalling applications, assigning users and groups to role mapping for applications, setting run-as configurations, setting up Java 2 security permissions for applications, and customizing CSIv2, SAS, and SSL configurations.

Operator role

Users assigned to the operator role can view the WAS configuration and its current state, but also can change the run-time state such as stopping and starting services.

Monitor role

Users assigned the monitor state can view the WAS configuration and its current state only.

Before you assign users to administrative roles (administrator, configurator, operator, and monitor), set up your user registry, which can be LDAP, local OS, or a custom registry. You can set up your user registries without enabling security.

After you assign users to administrative roles, restart the Deployment Manager for the new roles to take effect. However, the administrative resources are not protected until you enable security.



  1. In the administrative console, click...

    System Administration | Console settings | Console Users or Console Groups

  2. To add a user or a group, click Add on the Console users or Console groups panel.

  3. To add a new administrator user, enter a user identity in the User field, highlight Administrator, and click OK. If there is no validation error, the specified user is displayed with the assigned security role.

  4. To add a new administrative group, either enter a group name in the Specify group field or select EVERYONE or ALL AUTHENTICATED from the Select from special subject menu, and click OK. If no validation error exists, the specified group or special subject displays with the assigned security role.

  5. To remove a user or group assignment, click Remove on the Console Users or the Console Groups panel. On the Console Users or the Console Groups panel, select the check box of the user or group to remove and click OK.

  6. To manage the set of users or groups to display, expand the filter folder on the right panel and modify the filter. For example, setting the filter to user* only displays users with the user prefix.

  7. After the modifications are complete, click Save to save the mappings.

  8. Stop and start the dmgr server.

  9. Restart all application servers.

  10. Shut down the nodes, node agents, and the deployment manager.

  11. Verify that Java processes are not running. If they are running, discontinue these processes.

  12. Restart the deployment manager.

  13. Resynchronize the nodes using install_root/bin/syncNode

  14. Restart the nodes using install_root/bin/startNode

  15. Start any clusters, if applicable.


See also

Console groups and CORBA naming service groups


See Also

Role-based authorization
Access control exception
Administrative console and naming service authorization


Related Tasks

Assigning users and groups to roles
Assigning users to RunAs roles


See Also

syncNode command
startNode command