Configure a Group administrator

Procedure

Open the configuration file js.conf and enable Group administrators in Process Manager.
1. Set the parameter JS_ENABLE_GROUP_ADMIN=true to enable Group administrators and allow them to operate on flow definitions, flows, jobs, and calendars owned by accounts that are listed in GROUP_MEMBER in lsb.users. The Owner field is also enabled in the Flow Attributes in Flow Editor, and in the Calendar description in Calendar Editor.
2. Restart the Process Manager Server jfd.
```
jadmin stop
jadmin start
```
Configure LSF® user groups to identify the accounts that are the administrators of the user groups and the accounts that are the members.
1. As the LSF administrator, log in to any host in the cluster.
2. Open lsb.users and configure user groups.
  - In GROUP_MEMBERS for the LSF user group, specify the accounts that are members of the user group.
  - In GROUP_ADMINS, specify the accounts that are the group administrators.
  For example, userA and usergroupB are group administrators of flow definitions, flows, jobs, and calendars owned by account ma1, and userD and userE are group administrators of flow definitions, flows, jobs, and calendars owned by accounts ma2 and ma3.
```
Begin UserGroup
GROUP_NAME     GROUP_MEMBER          USER_SHARES        GROUP_ADMIN
ugroup1        (ma1)                   ()               (userA usergroupB)
ugroup2        (ma2 ma3)               ()               (userD userE)
…
End UserGroup
```
3. Save your changes.
4. Run badmin ckconfig to check the new user group definition. If any errors are reported, fix the problem and check the configuration again.
5. Run badmin reconfig to reconfigure the cluster.
6. Run jreconfigadmin to reload LSF user group information in Process Manager and apply changes.
Test your configuration.
1. In Flow Editor, open any flow as a Group administrator.
  For example, Group administrator userA.
2. Submit the flow.
  The owner of the flow is the account that you specified in the Flow Attributes.
  
  For example, if you specified ma1 in the Flow Attributes, and your flow name is Sample, your flow name is ma1:Sample after submission.
3. In Flow Manager, trigger the flow as the Group administrator account.
  For example, as user userA, trigger the flow ma1:Sample. The flow is owned by account ma1.
4. In Flow Manager, operate on the flow as the Group administrator account.
  For example, as user userA, suspend and resume the flow ma1:Sample.
5. View information about who submitted the flow, who triggered the flow, and who is the owner of the flow:
  - In Flow Manager, Runtime Attributes, you can see the triggering user.
  - From the command line, use the command jhist with the -o all or -o operator_name option to view which user owns the flow, submitted the flow, and triggered the flow.