79 lines
5.9 KiB
HTML
79 lines
5.9 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="Packaging and installation process" />
|
|
<meta name="abstract" content="Consider running code, translated textual data, and installation documents when packaging applications. This topic lists some suggestions for simplifying the packaging and installation of your application." />
|
|
<meta name="description" content="Consider running code, translated textual data, and installation documents when packaging applications. This topic lists some suggestions for simplifying the packaging and installation of your application." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdevelopingappsprocess.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagssubsystemsandnls.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagslingandcultdevdes.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsuserprofilenamecon.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsnatlangdefaultsysval.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsjoblibrarylist.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdevelopingappsdeliver.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="rbagspackandinstallprocess" />
|
|
<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>Packaging and installation process</title>
|
|
</head>
|
|
<body id="rbagspackandinstallprocess"><a name="rbagspackandinstallprocess"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Packaging and installation process</h1>
|
|
<div><p>Consider running code, translated textual data, and installation
|
|
documents when packaging applications. This topic lists some suggestions for
|
|
simplifying the packaging and installation of your application.</p>
|
|
<ul><li>Store the running code and textual data separately.</li>
|
|
<li>Package the textual data so that customers receive only the textual data
|
|
in the languages that are ordered. (If the textual data for all languages
|
|
is sent to all customers, it will waste system resources and lead to maintenance
|
|
problems.)</li>
|
|
<li>Provide comprehensive installation documents (translated to the language
|
|
of the person installing the product) to avoid unnecessary operator-related
|
|
problems and also to avoid the wrong impression right at the beginning that
|
|
the application is not reliable. <p>Installation documentation should cover
|
|
the following topics:</p>
|
|
<ul><li>What is needed to install and run the application, such as hardware and
|
|
software requirements.</li>
|
|
<li>How to install the application, and how to recover when things go wrong.</li>
|
|
<li>What changes need to be made regarding: <ul><li>Subsystem definitions</li>
|
|
<li>Device descriptions</li>
|
|
<li>User profiles</li>
|
|
<li>System values</li>
|
|
<li>Library lists</li>
|
|
</ul>
|
|
</li>
|
|
<li>What are the application limitations?</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsdevelopingappsprocess.htm" title="Before you invest your time and money into the development of globalized applications, you will benefit from a planning process that gives you an opportunity to consider how you can efficiently and effectively serve your users. The information in this topic will help you develop such a plan.">Goals and processes</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rbagssubsystemsandnls.htm" title="A subsystem is a single, predefined operating environment through which the server coordinates the work flow and resource use.">Subsystems</a></div>
|
|
<div><a href="rbagslingandcultdevdes.htm" title="These control language (CL) command parameters can be used to change cultural and linguistic conventions for some display and printer devices.">Device descriptions</a></div>
|
|
<div><a href="rbagsuserprofilenamecon.htm" title="The user profile name identifies the user to the server. This user profile name is also known as the user ID. It is the name that the user types in the User prompt on the Signon display.">User profile name considerations</a></div>
|
|
<div><a href="rbagsnatlangdefaultsysval.htm" title="System values are the default values for jobs and functions on the system.">Default system values for national language versions</a></div>
|
|
<div><a href="rbagsjoblibrarylist.htm" title="The language used for textual data (displays, messages, printed output, and online help information) is controlled by the library list for the job.">Job library list</a></div>
|
|
<div><a href="rbagsdevelopingappsdeliver.htm" title="As you prepare to deliver your globalized application, you should consider how globalization issues might affect the ways that your customers install and use your application.">Deliver globalized applications</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |