210 lines
13 KiB
HTML
210 lines
13 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 1: Set up Application Administration" />
|
|
<meta name="abstract" content="This scenario describes how to plan and configure a system to be administered through Application Administration. It demonstrates how you can control access to applications by limiting users to applications and functions that are specific to their job duties." />
|
|
<meta name="description" content="This scenario describes how to plan and configure a system to be administered through Application Administration. It demonstrates how you can control access to applications by limiting users to applications and functions that are specific to their job duties." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaj3scenario.htm" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="scenario1" />
|
|
<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 1: Set up Application Administration</title>
|
|
</head>
|
|
<body id="scenario1"><a name="scenario1"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Scenario 1: Set up Application Administration</h1>
|
|
<div><p>This scenario describes how to plan and configure a system to be
|
|
administered through Application Administration. It demonstrates how you can
|
|
control access to applications by limiting users to applications and functions
|
|
that are specific to their job duties.</p>
|
|
<div class="section"><p>Suppose that your company has a server (Server001) in a network
|
|
that runs the following client applications:</p>
|
|
</div>
|
|
<div class="section"> <dl><dt class="dlterm">Manufacturing application</dt>
|
|
<dd>A client interface with these administrable functions: <ul><li>Inventory Management</li>
|
|
<li>Order Fulfillment</li>
|
|
</ul>
|
|
</dd>
|
|
<dt class="dlterm">Finance application</dt>
|
|
<dd>A client interface with these administrable functions: <ul><li>Accounts Receivable</li>
|
|
<li>Budgeting</li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<div class="section"><p>Users access the server by using iSeries™ Access for Windows<sup>®</sup> and iSeries Navigator.
|
|
You must determine which applications you want to administer through Application
|
|
Administration. Then you must evaluate what type of access your users require
|
|
for each function. </p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Step 1: Plan your Application Administration strategy</h4><dl><dt class="dlterm">Which applications to administer?</dt>
|
|
<dd>Server001 has two, and only two, distinct groups of users: users of the
|
|
Manufacturing application, and users of the Finance application. The manufacturing
|
|
users should not have access to the Finance application, and Finance users
|
|
should not have access to the Manufacturing application. In addition, each
|
|
group has different access settings to the various iSeries Navigator functions. Because
|
|
of this, you need to register iSeries Navigator, the Manufacturing
|
|
application, and the Finance application on Server001. iSeries Access for Windows and
|
|
its administrable functions (iSeries Navigator) are automatically registered when
|
|
you install Application Administration so you do not need to register iSeries Navigator. </dd>
|
|
<dt class="dlterm">What type of access do you want users to have to the administrable functions
|
|
of those applications?</dt>
|
|
<dd>All users that use the Manufacturing application belong to a user group
|
|
that is called MFGUSER. All manufacturing team leaders also belong to a user
|
|
group that is called MFGLEAD. All users that use the Finance application belong
|
|
to a user group that is called FINANCE. Now that you have determined the user
|
|
groups, you can give the users of the applications on Server001 access to
|
|
the following: <dl><dt class="dlterm">Manufacturing application</dt>
|
|
<dd> <dl><dt class="dlterm">Inventory Management</dt>
|
|
<dd>Only Judy, Natasha, Jose, and Alex require access to this function.</dd>
|
|
<dt class="dlterm">Order Fulfillment</dt>
|
|
<dd>All manufacturing team leaders require access to this function, except
|
|
Alex.</dd>
|
|
</dl>
|
|
</dd>
|
|
<dt class="dlterm">Finance application</dt>
|
|
<dd> <dl><dt class="dlterm">Accounts Receivable</dt>
|
|
<dd>All members of FINANCE require access to this function.</dd>
|
|
<dt class="dlterm">Budgeting</dt>
|
|
<dd>All members of FINANCE require access to this function.</dd>
|
|
</dl>
|
|
</dd>
|
|
<dt class="dlterm">iSeries Navigator</dt>
|
|
<dd> <ul><li>All manufacturing users require access to Basic Operations.</li>
|
|
<li>All finance users require access to Basic Operations, Database, and File
|
|
Systems.</li>
|
|
<li>All system administrators require access to all iSeries Navigator functions.</li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
<div class="note"><span class="notetitle">Note:</span> The administrators on this server do not require access
|
|
to the Manufacturing application or the Finance application. All administrators
|
|
have all object system privilege.</div>
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Step 2: Set up your Application Administration strategy</h4><p>Given
|
|
the information you compiled in planning your Application Administration strategy,
|
|
configure the access settings for each application's administrable function
|
|
as follows:</p>
|
|
<dl><dt class="dlterm">Manufacturing application</dt>
|
|
<dd><strong>Inventory Management</strong> <ol><li>From the <span class="uicontrol">Application Administration</span> dialog, go
|
|
to the <span class="uicontrol">Client Applications</span> page.</li>
|
|
<li>Expand <span class="uicontrol">Manufacturing application</span>.</li>
|
|
<li>For Inventory Management, deselect <span class="uicontrol">Default Access</span>.</li>
|
|
<li>Click <span class="uicontrol">Customize</span>. This opens the <span class="uicontrol">Customize
|
|
Access</span> dialog.</li>
|
|
<li>In the <span class="uicontrol">Access</span> field, deselect <span class="uicontrol">All object
|
|
system privilege</span>.</li>
|
|
<li>Expand <span class="uicontrol">All Users</span> in the <span class="uicontrol">Users and Groups</span> list
|
|
box.</li>
|
|
<li>Select Judy, Natasha, Jose, and Alex from the list of all users and click <span class="uicontrol">Add</span> to
|
|
add them to the <span class="uicontrol">Access Allowed</span> list.</li>
|
|
<li>Click <span class="uicontrol">OK</span> to save the access settings.</li>
|
|
<li>For Order Fulfillment, deselect <span class="uicontrol">Default Access</span>.</li>
|
|
<li>Click <span class="uicontrol">Customize</span>. This opens the <span class="uicontrol">Customize
|
|
Access</span> dialog.</li>
|
|
<li>In the <span class="uicontrol">Access</span> field, deselect <span class="uicontrol">Users
|
|
with all object system privilege</span>.</li>
|
|
<li>Expand <span class="uicontrol">All Users</span> in the <span class="uicontrol">Users and Groups</span> list
|
|
box.</li>
|
|
<li>Select Alex from the list of all users and click <span class="uicontrol">Add</span> to
|
|
add him to the <span class="uicontrol">Access Denied</span> list.</li>
|
|
<li>Expand <span class="uicontrol">Groups</span> in the <span class="uicontrol">Users and Groups</span> list
|
|
box.</li>
|
|
<li>Select MFGLEAD from the list of groups and click <span class="uicontrol">Add</span> to
|
|
add the group to the <span class="uicontrol">Access Allowed</span> list.</li>
|
|
<li>Click <span class="uicontrol">OK</span> to save the access settings.</li>
|
|
</ol>
|
|
</dd>
|
|
<dt class="dlterm">Finance application</dt>
|
|
<dd><strong>All functions</strong> <ol><li>From the <span class="uicontrol">Application Administration</span> dialog, go
|
|
to the <span class="uicontrol">Client Applications</span> page.</li>
|
|
<li>Expand <span class="uicontrol">Finance application</span>.</li>
|
|
<li>For Accounts Receivable, deselect <span class="uicontrol">Default Access</span>.</li>
|
|
<li>Click <span class="uicontrol">Customize</span>. This opens the <span class="uicontrol">Customize
|
|
Access</span> dialog.</li>
|
|
<li>In the <span class="uicontrol">Access</span> field, deselect <span class="uicontrol">Users
|
|
with all object system privilege</span>.</li>
|
|
<li>Expand <span class="uicontrol">Groups</span> in the <span class="uicontrol">Users and Groups</span> list
|
|
box.</li>
|
|
<li>Select FINANCE from the list of groups and click <span class="uicontrol">Add</span> to
|
|
add the group to the <span class="uicontrol">Access Allowed</span> list.</li>
|
|
<li>Click <span class="uicontrol">OK</span> to save the access settings.</li>
|
|
<li>Repeat these steps for Budgeting.</li>
|
|
</ol>
|
|
</dd>
|
|
<dt class="dlterm">iSeries Navigator</dt>
|
|
<dd><strong>Basic Operations</strong> <ol><li>From the <span class="uicontrol">Application Administration</span> dialog, go
|
|
to the <span class="uicontrol">iSeries Navigator</span> page.</li>
|
|
<li>For Basic Operations, select <span class="uicontrol">Default Access</span> and <span class="uicontrol">All
|
|
Object Access</span>.</li>
|
|
<li>Click <span class="uicontrol">OK</span> to save the access settings.</li>
|
|
</ol>
|
|
<p><strong>Database</strong></p>
|
|
<ol><li>From the <span class="uicontrol">Application Administration</span> dialog, go
|
|
to the <span class="uicontrol">iSeries Navigator</span> page.</li>
|
|
<li>For Database, deselect <span class="uicontrol">Default Access</span>.</li>
|
|
<li>Click <span class="uicontrol">Customize</span>. This opens the <span class="uicontrol">Customize
|
|
Access</span> dialog.</li>
|
|
<li>In the <span class="uicontrol">Access</span> field, select <span class="uicontrol">Users with
|
|
all object system privilege</span>.</li>
|
|
<li>Expand <span class="uicontrol">Groups</span> in the <span class="uicontrol">Users and Groups</span> list
|
|
box.</li>
|
|
<li>Select FINANCE from the list of groups and click <span class="uicontrol">Add</span> to
|
|
add the group to the <span class="uicontrol">Access Allowed</span> list.</li>
|
|
<li>Click <span class="uicontrol">OK</span> to save the access settings.</li>
|
|
</ol>
|
|
<p><strong>File Systems</strong></p>
|
|
<ol><li>From the <span class="uicontrol">Application Administration</span> dialog, go
|
|
to the <span class="uicontrol">iSeries Navigator</span> page.</li>
|
|
<li>For File Systems, deselect <span class="uicontrol">Default Access</span>.</li>
|
|
<li>Click <span class="uicontrol">Customize</span>. This opens the <span class="uicontrol">Customize
|
|
Access</span> dialog.</li>
|
|
<li>In the <span class="uicontrol">Access</span> field, select <span class="uicontrol">Users with
|
|
all object system privilege</span>.</li>
|
|
<li>Expand <span class="uicontrol">Groups</span> in the <span class="uicontrol">Users and Groups</span> list
|
|
box.</li>
|
|
<li>Select FINANCE from the list of groups and click <span class="uicontrol">Add</span> to
|
|
add the group to the <span class="uicontrol">Access Allowed</span> list.</li>
|
|
<li>Click <span class="uicontrol">OK</span> to save the access settings.</li>
|
|
</ol>
|
|
<p><strong>All other iSeries Navigator functions</strong></p>
|
|
<ol><li>From the <span class="uicontrol">Application Administration</span> dialog, go
|
|
to the <span class="uicontrol">iSeries Navigator</span> page.</li>
|
|
<li>For each function, deselect <span class="uicontrol">Default Access</span> and
|
|
select <span class="uicontrol">All Object Access</span>.</li>
|
|
<li>Click <span class="uicontrol">OK</span> to save the access settings.</li>
|
|
</ol>
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<div class="section"><p>Now, you have used the Local Settings within Application Administration
|
|
to set up an environment that restricts user access to specific functions.
|
|
If you want to set up an administration system for Central Settings, continue
|
|
to <a href="rzaj3scenario2.htm#scenario2">scenario 2</a> which explains
|
|
how to use the Central Settings in your Application Administration strategy.</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> |