67 lines
5.2 KiB
HTML
67 lines
5.2 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="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="topic" />
|
||
|
|
<meta name="DC.Title" content="Scenario: Journal management" />
|
||
|
|
<meta name="abstract" content="Provides the steps that a fictitious company, JKL Toy company, takes as it implements journal management on its iSeries server." />
|
||
|
|
<meta name="description" content="Provides the steps that a fictitious company, JKL Toy company, takes as it implements journal management on its iSeries server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijklprod.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijklint.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijkldev.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzai8/rzai8backupscenario.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirscenarios.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakijournalscenario" />
|
||
|
|
<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: Journal management</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakijournalscenario"><a name="rzakijournalscenario"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: Journal management</h1>
|
||
|
|
<div><p>Provides the steps that a fictitious company, JKL Toy company,
|
||
|
|
takes as it implements journal management on its iSeries™ server.</p>
|
||
|
|
<p>Sharon Jones, the system administrator for the JKL Toy Company, is responsible
|
||
|
|
for backing up their servers and making sure that their servers can be recovered
|
||
|
|
in the event of a natural disaster or system failure. As security officer,
|
||
|
|
she is also responsible for ensuring the security of the servers.</p>
|
||
|
|
<p>The JKL Toy Company has a network that consists of a development server,
|
||
|
|
a production server, and an http server. Click on a server on the diagram
|
||
|
|
below for a description of the system and the journaling strategy Sharon uses.<br /><img src="rzaki501.gif" alt="" /><br /> </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijklprod.htm">JKLPROD</a></strong><br />
|
||
|
|
JKLPROD is the system that JKL uses for all of their customer orders and where their business applications are installed (inventory control, customer orders, contracts and pricing, accounts receivable). The information about this server is extremely critical to their business and changes often.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijklint.htm">JKLINT</a></strong><br />
|
||
|
|
JKLINT is the system that JKL uses for their Web site and e-mail. While this data is critical to their business, it is fairly static.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakijkldev.htm">JKLDEV</a></strong><br />
|
||
|
|
JKLDEV is JKL's development server. Though it does not require 24x7 availability, the data on it represent many person hours of work by the developers. Therefore it is important that in the event of a crash, the system be brought to a current state. Also, since it is a development server, changes to the data occur often.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakijrnkickoff.htm" title="Use local journal management to recover the changes to an object that have occurred since the object was last saved, as an audit trail, or to help replicate an object. Setting up journaling locally is a prerequisite for other iSeries functions such as Remote journal management and Commitment control. Use this information to set up, manage, and troubleshoot journaling on a local server.">Local journal management</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="../rzai8/rzai8backupscenario.htm">Scenario: Backup using BRMS</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="rzakirscenarios.htm" title="These scenarios describe the possible ways that JKL Toy Company can use remote journal management. JKL Toy Company uses the server JKLINT as their web server.">Scenarios: Remote journal management and recovery</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|