ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamm_5.4.0.1/portconfig.htm

121 lines
8.0 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="reference" />
<meta name="DC.Title" content="Configure iSeries Access for Web in a portal environment" />
<meta name="abstract" content="Installing iSeries Access for Web to the iSeries server does not make it available for use. To use iSeries Access for Web, it must be deployed to the portal environment." />
<meta name="description" content="Installing iSeries Access for Web to the iSeries server does not make it available for use. To use iSeries Access for Web, it must be deployed to the portal environment." />
<meta name="DC.subject" content="iSeries Access for Web, configure" />
<meta name="keywords" content="iSeries Access for Web, configure" />
<meta name="DC.Relation" scheme="URI" content="rzammportenv.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammpxmpbeg.htm" />
<meta name="DC.Relation" scheme="URI" content="porexmpl.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammportcreate.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/cfgaccweb2.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/rmvaccweb2.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammupgrade.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammverifyiaw.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2003, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2003, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="portconfig" />
<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>Configure iSeries Access
for Web in a portal environment</title>
</head>
<body id="portconfig"><a name="portconfig"><!-- --></a>
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Configure iSeries Access
for Web in a portal environment</h1>
<div><p>Installing iSeries™ Access for Web to the iSeries server does not make it available
for use. To use iSeries Access
for Web, it must be deployed to the portal environment. </p>
<div class="section"><div class="note"><span class="notetitle">Note:</span> If you are upgrading iSeries Access for Web from a previous
release, you must still configure iSeries Access for Web to enable the
new functions.</div>
</div>
<div class="section"><h4 class="sectiontitle">Configuration commands</h4>iSeries Access for Web provides
commands to perform and manage the configuration on the server. These commands
must be used to perform actions such as configuring and removing the iSeries Access
for Web configuration within the portal environment.<p>Both CL and script
commands are provided. Providing different types of commands gives you the
flexibility to manage iSeries Access for Web using the interface you are
most comfortable with. The CL and script commands perform identical functions,
they are just invoked differently. The parameters are also identical, but
are input differently. </p>
<p>The CL commands are installed to the library
QIWA2. The script commands are installed to /QIBM/ProdData/Access/Web2/install
and can be used within the QShell environment. </p>
<div class="p">The iSeries Access
for Web CL commands are: <ul><li><strong>CFGACCWEB2:</strong> Deploys the iSeries Access for Web portal application. </li>
<li><strong>RMVACCWEB2:</strong> Removes the iSeries Access for Web configuration.</li>
</ul>
</div>
<div class="p">The iSeries Access
for Web script commands are: <ul><li><strong>cfgaccweb2:</strong> Deploys the iSeries Access for Web portal application. </li>
<li><strong>rmvaccweb2:</strong> Removes the iSeries Access for Web configuration.</li>
</ul>
</div>
</div>
<div class="section"><h4 class="sectiontitle">Command help</h4><p>There are multiple ways to access help
for CL commands. Enter the command name on the command line and press F1.
Alternatively, enter the command name and press F4 to prompt the command,
then move the cursor to any field and press F1 for help on that field. </p>
<p>To
get help on a script command, specify the -? parameter. For example, start
a QShell session by running the command STRQSH, then enter the command /QIBM/ProdData/Access/Web2/install/cfgaccweb2
-?</p>
</div>
<div class="section"><img src="./delta.gif" alt="Start of change" /><h4 class="sectiontitle">Configuration scenarios</h4><p>If you are
not familiar with the portal environment and need to create an HTTP and Web
application server and deploy a portal environment, or if you want to create
a new portal environment for iSeries Access for Web, examples are available to
walk you through the process. </p>
<p>If you are familiar with the portal environment
and already have HTTP and Web application servers created and a portal environment
deployed and ready for use, examples are available that show you how to invoke
the iSeries Access
for Web commands and what to input into the commands.</p>
<img src="./deltaend.gif" alt="End of change" /></div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzammpxmpbeg.htm">Examples for configuring a new portal environment</a></strong><br />
You must setup an HTTP server and portal server before configuring iSeries Access for Web on the iSeries server.</li>
<li class="ulchildlink"><strong><a href="porexmpl.htm">Examples for configuring an existing portal environment</a></strong><br />
These examples provide instructions for configuring iSeries Access
for Web within an existing portal environment. They assume that an HTTP server
and Web application server exist and that WebSphere<sup>®</sup> Portal has been deployed.
Before using these examples, ensure you have completed the plan, install,
and configure checklist. </li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzammportenv.htm" title="Find out how to configure, customize, use, and save iSeries Access for Web in a portal environment.">iSeries Access for Web in a portal environment</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzammverifyiaw.htm" title="Follow these instructions to install iSeries Access for Web on the server.">Install iSeries Access for Web</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzammportcreate.htm" title="When configuring iSeries Access portlets for WebSphere Portal, default WebSphere Portal pages can be created and populated with the iSeries Access portlets. The default pages created consist of a main page entitled &#34;My iSeries&#34; and multiple sub-pages under the main page. The sub-pages group similar functional portlets on the same page.">Create pages</a></div>
<div><a href="rzammupgrade.htm" title="This topic contains information about upgrading iSeries Access for Web from a previous release.">Upgrade considerations</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../cl/cfgaccweb2.htm">CFGACCWEB2 CL command</a></div>
<div><a href="../cl/rmvaccweb2.htm">RMVACCWEB2 CL command</a></div>
</div>
</div>
<img src="./deltaend.gif" alt="End of change" /></body>
</html>