Scenario 2: Set up an administration system for Central Settings

In scenario 1, you set up Application Administration on a system to administer who has access to specific manufacture and finance applications. By defining the system as an administration system, you can administer Central Settings. These settings allow you to use the advanced settings that allow you to control sign on, connections, language, environments, service, password information, and to determine automatically if new plug-ins are available. In addition, you will also be able to control access to several additional functions of iSeries™ Access for Windows^®.

Step 1: Plan your administration system strategy

Which users do you want to administer?

Since all users have specific access settings for various functions, you need to administer all users so the access settings are enforced. Otherwise, all users would have access to all functions.

Do you want all users who install using the modified installation image to use a specified administration system?

The only server available to the manufacturing and finance people is Server001. This server contains every user's advanced settings, so when users install, you want them to automatically use Server001 as their administration system. Since this is the only administration system in their environment, you will specify Server001 as the installation image administration system.

How often do you want to validate the client-side cache to ensure that the client's settings match the settings stored on the administration system?

The Central Settings will not change often after they are initially set up, but any changes should be distributed to all iSeries Access for Windows clients in your network within a week. Because of this, you should set the scan frequency to Once every seven days.

Which iSeries Access for Windows applications that are managed through Central Settings should be available to users and groups?

You want all centrally managed applications available to all users and groups except the Remote Command-Command Line administrable function.

Which advanced settings should be mandated versus suggested?

You want to make sure all users are signing on to the system using their default user ID (prompting as needed) and that a warning message is sent to them before their password expires. Therefore, sign on information and password expire warning will be mandated. This will ensure that the user does not change these two settings. All other advanced settings will be in a suggested state so the system administrator can suggest a value but the user will still be able to modify it.

Step 2: Set up your administration system

Define the administration system

These steps outline what actions you must take to actually administer functions on an administration system:

1. Right-click Server001 and select Properties.
2. Select the Administration System page.
3. Select Administration System.
4. Select Number of days for the scan frequency and specify 7 days.
5. Select Administer users by default.
6. Click Set Installation Image Administration System.
7. Specify the location of the installation image or click Browse to locate the installation image.
8. Specify Server001 for the administration system.
9. Click OK to close the Set Installation Image Administration System dialog.
10. Click OK to close the Properties dialog.

Set the Central Settings

These steps outline what actions you must take to set the advanced settings for the administration system:

1. Right-click Server001.
2. Select Application Administration > Central Settings.
3. Deselect Remote Command-Command Line Default Access.
4. Deselect Remote Command-Command Line All Object Access.
5. Click Advanced Settings. . . .
6. Select the Passwords page.
7. Select Warn users before server password expires.
8. Specify 10 days so users are sent warning messages 10 days prior to expiration.
9. Click the padlock in front of this value to mandate it. (The padlock should be closed.)
10. Select the Connections page.
11. Select Use default user ID, prompt as needed.
12. Click the padlock to mandate this value. (The padlock should be closed.)
13. Leave all other advanced settings as suggested values. The padlocks for these setting should be open.
14. Click OK to close theAdvanced Settings dialog.
15. Click OK to close the Application Administration dialog.

Now, you have set up an administration system that contains the Central Settings. Within the Central Settings, you were able to adapt the advanced settings to meet your company's needs.