1.3 Configuring the Mobility Administration Console

You can change the configuration of the Mobility Administration Console to meet your administrative needs.

1.3.1 Adjusting the Mobility Administration Console Polling Rate for Groups of Users

The Mobility Administration Console locates GroupWise groups based on their group_name.post_office.domain location in your GroupWise system.

When you add a group of users to your Mobility system, the group’s existing members are added to the group as displayed in the Mobility Administration Console. Subsequently, the Mobility Administration Console polls for updates to group membership. This ensures that the group membership that is displayed in the Mobility Administration Console always matches the membership in the GroupWise system.

By default, the Mobility Administration Console polls the user source for changes in group membership every 1800 seconds (30 minutes).

In the Mobility Administration Console, click Config > User Source.
Adjust the poll rate as needed to synchronize the group membership in the Mobility Administration Console with current group membership in the GroupWise system.
Click Save to save the new setting(s).
Restart the Mobility Service:
```
gms restart
```

1.3.2 Using the Mobility Administration Console with a Single Sign-On Solution

If you are using a single sign-on solution such as NetIQ Access Manager or KeySheild SSO, the Mobility Administration Console does not require authentication when you are already logged in to the single sign-on solution.

For Access Manager, no extra configuration is required.
For KeyShield SSO, you must provide Keyshield SSO settings on the Single Sign-On page in the Mobility Administration Console. For more information, see KeyShieldSSO.

1.3.3 Adding GroupWise Users as Mobility Administrators

By default, when you use GroupWise as your Mobility system’s user source, you must log in to the Mobility Administration Console using the root user name and password.

You can configure the Mobility Service to allow specific users to log in using their GroupWise user name and password. Then the root user name and password can continue to be used as well.

In a terminal window on the Mobility server, become root by entering su - and the root password.
Change to the following directory:
```
/etc/datasync/configengine
```
Open the configengine.xml file in a text editor.

Add the following section:

<gw>
   <admins>
       <username>GroupWise_Username</username>
       <username>GroupWise_Username</username> 
   </admins>
   <enabled>true</enabled>
</gw>

Replace GroupWise_Username with the appropriate GroupWise user name. You can add as many GroupWise users as needed.

Save the configengine.xml file, and then exit the text editor.
Restart the Mobility Service to put the new settings into effect:
```
gms restart
```