You can assign users to be superusers (or Process Portal administrators).
A superuser can view, edit, and delete all spaces and pages, can manage
and create templates, and can change ownership of a space by changing
the owner ID.
Before you begin
Before you complete this task, you
must have completed the following tasks:
About this task
Assign the superuser role by using the following application
server security role: Admin. Using this method
gives you flexibility in assigning the role to any number of your
organization's existing groups and users. It doesn't require
the creation of an administrators group in the user registry for the
sole purpose of acting as the focal point for the superuser.
If
you already have a Business Space superuser
assigned from an earlier version than V7.5, you can modify the superuser
by user group instead. See Assigning the superuser by user group.
Procedure
- If you are setting up administrators with the superuser
role for the first time, complete the following steps.
- Log in to the administrative console for your product.
- Click and select one of the following
applications:
- mm.was_node_server (for
a stand-alone server environment)
- mm.was_cluster (for
a network deployment environment)
- Click Security role to user/group mappings.
- Select the row for the Admin role,
and click the Map Users button or the Map
Groups button to map either users or groups to the Admin
role.
- Click Save.
- Restart the server.
- If you previously assigned superusers based on user groups,
and you want to switch to this simpler way to manage superusers by
role, complete the following steps.
- Open the configuration file.
- For a stand-alone server: profile_root\BusinessSpace\node_name\server_name\mm.runtime.prof\config\ConfigService.properties
- For a cluster: deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\config\ConfigService.properties
- Change the following property values in the configuration
file as shown:
com.ibm.mashups.adminGroupName
= {com.ibm.mashups.J2EERole.Admin}
com.ibm.mashups.widget.attributes.configure.groups=
- Run the updatePropertyConfig command
in the wsadmin environment of the profile.
Important: For Windows, the value for the propertyFileName parameter
must be the full path to the file, and all backslashes must be double,
for example: AdminTask.updatePropertyConfig('[-serverName server_name -nodeName node_name -propertyFileName
"profile_root\\BusinessSpace\\node_name\\server_name\\mm.runtime.prof\\config\\ConfigService.properties"
-prefix "Mashups_"]').
- For a stand-alone server:
The following example uses Jython:
AdminTask.updatePropertyConfig('[-serverName server_name -nodeName node_name
-propertyFileName "profile_root\BusinessSpace\node_name\server_name
\mm.runtime.prof\config\ConfigService.properties" -prefix "Mashups_"]')
AdminConfig.save()
The
following example uses Jacl:
$AdminTask updatePropertyConfig {-serverName server_name -nodeName node_name
-propertyFileName "profile_root\BusinessSpace\node_name\server_name
\mm.runtime.prof\config\ConfigService.properties" -prefix "Mashups_"}
$AdminConfig save
- For a cluster:
The following example uses Jython:
AdminTask.updatePropertyConfig('[-clusterName cluster_name -propertyFileName
"deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\
config\ConfigService.properties" -prefix "Mashups_"]')
AdminConfig.save()
The following example uses Jacl:
$AdminTask updatePropertyConfig {-clusterName cluster_name -propertyFileName
"deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\
config\ConfigService.properties" -prefix "Mashups_"}
$AdminConfig save
- Restart the server.
- Use the previous procedure to assign users to the Business Space superuser roles.