Home
Designating an administrative user for a pilot deployment
The installation wizard creates a default administrative user for each feature called connectionsAdmin and assigns the search-admin role to that user. If necessary, grant administrative access to more users for a Lotus Connections feature.
If you do not need more administrative users for any of the features, then you do not need to perform this task.
You can grant administrative access to users who are allowed to configure designated features. Without administrative access to the Home page, for example, you cannot add, enable, or disable widgets. Similarly, without administrative access to Blogs, you cannot configure a home page for the Blogs feature.To grant administrative access to a user for a feature...
- From the WAS admin console, select Applications > Enterprise Applications.
- Click the link to the feature for which you want to provide administrative access.
- In the Detail Properties area, click Security role to user/group mapping.
- To map a user to the administrative role, select the check box beside the admin role, and then click Look up users or Look up groups.
- In the Search String field, type the name of the user that you would like to designate as an administrator, and then click Search.
- Select the user's ID from the Available field, and then move it to the Selected column by clicking the right-arrow button.
- Repeat steps 5 and 6 to add more users to the administrative role.
- Click OK.
- From the Enterprise Applications > feature > Security role to user/group mapping page, click OK, and then click Save to save the changes.
- Restart WebSphere Application Server.
Repeat this procedure to add an administrative user for another feature.
Previous topic:
Change the pilot configuration
Next topic:
Add actual users to the pilot