128 lines
8.7 KiB
HTML
128 lines
8.7 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Scenario 2: Set up an administration system for Central Settings" />
|
||
|
|
<meta name="abstract" content="This scenario is based on the same setup as scenario 1, but it also demonstrates how to define the system as an administration system, which contains Central Settings." />
|
||
|
|
<meta name="description" content="This scenario is based on the same setup as scenario 1, but it also demonstrates how to define the system as an administration system, which contains Central Settings." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaj3scenario.htm" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="scenario2" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Scenario 2: Set up an administration system for Central Settings</title>
|
||
|
|
</head>
|
||
|
|
<body id="scenario2"><a name="scenario2"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario 2: Set up an administration system for Central Settings</h1>
|
||
|
|
<div><p>This scenario is based on the same setup as scenario 1, but it
|
||
|
|
also demonstrates how to define the system as an administration system, which
|
||
|
|
contains Central Settings.</p>
|
||
|
|
<div class="section"><p>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. <span><img src="./delta.gif" alt="Start of change" />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<sup>®</sup>.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Step 1: Plan your administration system strategy</h4><dl><dt class="dlterm">Which users do you want to administer?</dt>
|
||
|
|
<dd>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. </dd>
|
||
|
|
<dt class="dlterm">Do you want all users who install using the modified installation image
|
||
|
|
to use a specified administration system?</dt>
|
||
|
|
<dd>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.</dd>
|
||
|
|
<dt class="dlterm">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?</dt>
|
||
|
|
<dd>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 <span class="uicontrol">Once every seven days</span>.</dd>
|
||
|
|
<dt class="dlterm">Which iSeries Access
|
||
|
|
for Windows applications
|
||
|
|
that are managed through Central Settings should be available to users and
|
||
|
|
groups?</dt>
|
||
|
|
<dd>You want all centrally managed applications available to all users and
|
||
|
|
groups except the Remote Command-Command Line administrable function.</dd>
|
||
|
|
<dt class="dlterm">Which advanced settings should be mandated versus suggested?</dt>
|
||
|
|
<dd>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.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Step 2: Set up your administration system</h4><dl><dt class="dlterm">Define the administration system</dt>
|
||
|
|
<dd>These steps outline what actions you must take to actually administer
|
||
|
|
functions on an administration system: <ol><li>Right-click <span class="uicontrol">Server001</span> and select <span class="uicontrol">Properties</span>.</li>
|
||
|
|
<li>Select the <span class="uicontrol">Administration System</span> page.</li>
|
||
|
|
<li>Select <span class="uicontrol">Administration System</span>.</li>
|
||
|
|
<li>Select <span class="uicontrol">Number of days</span> for the scan frequency and
|
||
|
|
specify <kbd class="userinput">7 days</kbd>.</li>
|
||
|
|
<li>Select <span class="uicontrol">Administer users by default</span>.</li>
|
||
|
|
<li>Click <span class="uicontrol">Set Installation Image Administration System</span>.</li>
|
||
|
|
<li>Specify the location of the installation image or click <strong>Browse</strong> to
|
||
|
|
locate the installation image.</li>
|
||
|
|
<li>Specify <span class="uicontrol">Server001</span> for the administration system.</li>
|
||
|
|
<li>Click <span class="uicontrol">OK</span> to close the <span class="uicontrol">Set Installation
|
||
|
|
Image Administration System</span> dialog. </li>
|
||
|
|
<li>Click <span class="uicontrol">OK</span> to close the <span class="uicontrol">Properties</span> dialog.</li>
|
||
|
|
</ol>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Set the Central Settings</dt>
|
||
|
|
<dd>These steps outline what actions you must take to set the advanced settings
|
||
|
|
for the administration system: <ol><li>Right-click <span class="uicontrol">Server001</span>.</li>
|
||
|
|
<li>Select <span class="menucascade"><span class="uicontrol">Application Administration</span> > <span class="uicontrol">Central Settings</span></span>.</li>
|
||
|
|
<li>Deselect Remote Command-Command Line Default Access.</li>
|
||
|
|
<li>Deselect Remote Command-Command Line All Object Access.</li>
|
||
|
|
<li>Click <span class="uicontrol">Advanced Settings. . . </span>.</li>
|
||
|
|
<li>Select the <span class="uicontrol">Passwords</span> page.</li>
|
||
|
|
<li>Select <span class="uicontrol">Warn users before server password expires</span>.</li>
|
||
|
|
<li>Specify <kbd class="userinput">10 days</kbd> so users are sent warning messages
|
||
|
|
10 days prior to expiration.</li>
|
||
|
|
<li>Click the padlock in front of this value to mandate it. (The padlock should
|
||
|
|
be closed.)</li>
|
||
|
|
<li>Select the <span class="uicontrol">Connections</span> page. </li>
|
||
|
|
<li>Select <span class="uicontrol">Use default user ID, prompt as needed</span>.</li>
|
||
|
|
<li>Click the padlock to mandate this value. (The padlock should be closed.)</li>
|
||
|
|
<li>Leave all other advanced settings as suggested values. The padlocks for
|
||
|
|
these setting should be open.</li>
|
||
|
|
<li>Click <span class="uicontrol">OK</span> to close the<span class="uicontrol">Advanced Settings</span> dialog. </li>
|
||
|
|
<li>Click <span class="uicontrol">OK</span> to close the <span class="uicontrol">Application Administration</span> dialog.</li>
|
||
|
|
</ol>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>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.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaj3scenario.htm" title="These scenarios show how one can apply Application Administration to their company's strategy. These scenarios explain a particular company's plan and how to execute their plan through Application Administration.">Scenarios: Application Administration</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|