61 lines
4.7 KiB
HTML
61 lines
4.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="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="concept" />
|
||
|
|
<meta name="DC.Title" content="Application arrangement and architecture" />
|
||
|
|
<meta name="abstract" content="When you design an international application, consider the ways that you can organize and structure your application so that it can be used in an international environment." />
|
||
|
|
<meta name="description" content="When you design an international application, consider the ways that you can organize and structure your application so that it can be used in an international environment." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdevelopingappsdesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsprogrammodsep.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsapppartnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsspecsrefs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdatabasedefs.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbagsarngandarchdsgngd" />
|
||
|
|
<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>Application arrangement and architecture</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagsarngandarchdsgngd"><a name="rbagsarngandarchdsgngd"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Application arrangement and architecture</h1>
|
||
|
|
<div><p>When you design an international application, consider the ways that you can organize and structure your application so that it can be used in an international environment.</p>
|
||
|
|
<p>In particular, consider the following strategies:</p>
|
||
|
|
<ul><li>Separate program modules at appropriate places</li>
|
||
|
|
<li>Name application parts appropriately for a multilingual environment</li>
|
||
|
|
<li>Refer to specifications whenever possible</li>
|
||
|
|
<li>Provide multiple sets of logical files in separate libraries when working with database definitions</li>
|
||
|
|
</ul>
|
||
|
|
<p>The following figure shows you the recommended way to organize the parts of your application.</p>
|
||
|
|
<br /><img src="rbags506.gif" alt="Recommended way to organize application parts." /><br /></div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsprogrammodsep.htm">Program module separation</a></strong><br />
|
||
|
|
You can separate cultural-dependent parts from your running code and set up cultural-dependent environments. You can do this using system values, user profile attributes, job attributes, and object attributes.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsapppartnames.htm">Application part names</a></strong><br />
|
||
|
|
When you want to enable your application for different languages and countries, consider the environments of the target systems in your naming conventions.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsspecsrefs.htm">Specification references</a></strong><br />
|
||
|
|
Define all your fields first in the field reference file of your application and refer to them whenever you can: in the database specifications, in device file specifications, and in the high-level language programs. This technique helps you to define the field specifications once and use them again.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsdatabasedefs.htm">Database definitions</a></strong><br />
|
||
|
|
You define a file to specify certain facts, and the specifications are then used on database files.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsdevelopingappsdesign.htm" title="Your goal in designing international application components is to create components that support national languages independently.">Design globalized applications</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|