friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamm_5.4.0.1/rzammxmpbegtomcat.htm

260 lines
19 KiB
HTML
Raw Permalink Normal View History

Add readme and dist folders
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="task" />
<meta name="DC.Title" content="Configure the Apache Software Foundation (ASF) Tomcat Web serving environment" />
<meta name="abstract" content="This example is for users that are not familiar with the Web serving environment. It describes all the steps necessary to get iSeries Access for Web running in an ASF Tomcat web serving environment. It also describes how to verify that the setup is working." />
<meta name="description" content="This example is for users that are not familiar with the Web serving environment. It describes all the steps necessary to get iSeries Access for Web running in an ASF Tomcat web serving environment. It also describes how to verify that the setup is working." />
<meta name="DC.Relation" scheme="URI" content="rzammservxmpbeg.htm" />
<meta name="DC.Relation" scheme="URI" content="../clfinder/finder.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="rzammxmpbegtomcat" />
<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 the Apache Software Foundation (ASF) Tomcat Web serving environment</title>
</head>
<body id="rzammxmpbegtomcat"><a name="rzammxmpbegtomcat"><!-- --></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 the Apache Software Foundation (ASF) Tomcat Web serving environment</h1>
<div><p>This example is for users that are not familiar with the Web serving
environment. It describes all the steps necessary to get iSeries™ Access
for Web running in an ASF Tomcat web serving environment. It also describes
how to verify that the setup is working.</p>
<div class="section">Configuring your Web serving environment consists of these steps: <ul><li>Start the IBM<sup>®</sup> Web
Administration for iSeries interface (also known as IBM HTTP Server
for iSeries).
See step <a href="#rzammxmpbegtomcat__tomstart">1</a></li>
<li>Create an HTTP web server and an ASF Tomcat Web application server. See
step <a href="#rzammxmpbegtomcat__tomcreate">2</a></li>
<li>Configure iSeries Access
for Web. See step <a href="#rzammxmpbegtomcat__tomconfig">3</a></li>
<li>Start the web environment. See step <a href="#rzammxmpbegtomcat__tomstartweb">4</a></li>
<li>Use a browser to access iSeries Access for Web. See step <a href="#rzammxmpbegtomcat__tomaccess">5</a></li>
</ul>
<strong>Steps to configure the Web serving environment: </strong></div>
<ol><li class="stepexpand" id="rzammxmpbegtomcat__tomstart"><a name="rzammxmpbegtomcat__tomstart"><!-- --></a><span>Start the IBM Web Administration for iSeries interface. </span><ol type="a"><li><span>Start a 5250 session to the server.</span></li>
<li><span>Sign on with a user profile that has at least these special
authorities:  *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM.</span></li>
<li><span>Run the following server command to start the web administration
interface job: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)</span></li>
<li><span>Minimize the 5250 session.</span></li>
</ol>
</li>
<li class="stepexpand" id="rzammxmpbegtomcat__tomcreate"><a name="rzammxmpbegtomcat__tomcreate"><!-- --></a><span>Create an HTTP web server and an ASF Tomcat Web
application server:</span><ol type="a"><li class="substepexpand"><span>Open a browser to: http://&lt;<em>server_name</em>&gt;:2001</span></li>
<li class="substepexpand"><span>Log in with a user profile that has, at least these special
authorities:  *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM.</span></li>
<li class="substepexpand"><span>Select <span class="uicontrol">IBM Web Administration for iSeries</span>.</span></li>
<li class="substepexpand"><span>Select the <span class="uicontrol">Setup</span> tabbed page.</span></li>
<li class="substepexpand"><span>Under Common Tasks and Wizards, select <span class="uicontrol">Create HTTP
Server</span>.</span></li>
<li class="substepexpand"><span>The Create HTTP Server page opens. For <span class="uicontrol">Server name</span>,
specify <samp class="codeph">iwatomcat</samp>, then select <span class="uicontrol">Next</span>.</span></li>
<li class="substepexpand"><span>A page opens that prompts for the Server root path. Select <span class="uicontrol">Next</span>. </span></li>
<li class="substepexpand"><span>A page opens that prompts for the Document root path. Select <span class="uicontrol">Next</span>. </span></li>
<li class="substepexpand"><span>The IP Address and Port page opens. For <span class="uicontrol">Port</span>,
specify 2016.</span></li>
<li class="substepexpand"><span>The <span class="uicontrol">Access log</span> page opens. Select <span class="uicontrol">Next</span>.</span></li>
<li class="substepexpand"><span>The <span class="uicontrol">Keep logs</span> page opens. Select <span class="uicontrol">Next</span>.</span></li>
<li class="substepexpand"><span>Select <span class="uicontrol">Finish</span> to create the HTTP server.</span></li>
<li class="substepexpand"><span>The web page is re-displayed.  The Manage/HTTP Servers
tabbed page is active. Under <span class="uicontrol">Server</span>, IWATOMCAT - APACHE
is listed with a status of Stopped.</span></li>
<li class="substepexpand"><span>Under Server Properties, select ASF Tomcat Settings.</span></li>
<li class="substepexpand"><span>The Web page is re-displayed with ASF Tomcat Settings. Specify
the following:</span> <ul><li>Select <span class="uicontrol">Enable servlets for this HTTP server</span>.</li>
<li>De-select <span class="uicontrol">Enable an “in-process” servlet engine</span>.</li>
<li>Select <span class="uicontrol">Enable “out-of-process” servlet engine connections</span>.</li>
<li>Add an entry for Out-of-process workers: <ol type="i"><li>Select <span class="uicontrol">Add</span> under <span class="uicontrol">Out-of- process workers</span>.</li>
<li>For <span class="uicontrol">Hostname:Port</span>, change 8009 to 2017.</li>
<li>For <span class="uicontrol">URLs (Mount points)</span>, specify <samp class="codeph">/webaccess/*</samp>.</li>
<li>Select <span class="uicontrol">Continue</span>. A warning message is displayed
for the worker that was just added.  Ignore the error. The problem will
be resolved when the ASF Tomcat Web application server setup is completed.
Select <span class="uicontrol">OK</span>.</li>
</ol>
</li>
</ul>
</li>
<li class="substepexpand"><span>Select the <span class="uicontrol">ASF Tomcat Servers</span> tabbed
page.</span></li>
<li class="substepexpand"><span>Under <span class="uicontrol">Tomcat Tasks and Wizards</span>, select <span class="uicontrol">Create
ASF Tomcat Server</span>.</span></li>
<li class="substepexpand"><span>The Out-of-Process Engine Creation page opens. for <span class="uicontrol">ASF
Tomcat server name</span>, specify <samp class="codeph">iwatomcat</samp>. Select <span class="uicontrol">Next</span>.</span></li>
<li class="substepexpand" id="rzammxmpbegtomcat__tomvalues"><a name="rzammxmpbegtomcat__tomvalues"><!-- --></a><span>The <span class="uicontrol">Out-of-Process Engine Configuration</span> page
opens. Note the values specified for <span class="uicontrol">Server userid</span> and <span class="uicontrol">ASF
Tomcat home</span>.  These values will be used when iSeries Access
for Web is configured. Select <span class="uicontrol">Next</span>.</span></li>
<li class="substepexpand"><span>The Out-of-Process Communication Settings page opens. Change <span class="uicontrol">Port</span> from
8009 to 2017. Select <span class="uicontrol">Next</span>.</span></li>
<li class="substepexpand"><span>The <span class="uicontrol">Out-of-Process Application Context Definition</span> page
opens.  Select <span class="uicontrol">Add</span>, then specify these values: </span> <ul><li>For <span class="uicontrol">URL path</span>, specify <samp class="codeph">/webaccess</samp>.</li>
<li>For <span class="uicontrol">Application base directory</span>, specify <samp class="codeph">webapps/webaccess</samp>.
  </li>
</ul>
Select <span class="uicontrol">Continue</span>. A warning message is displayed
for the application context that was just added.  This can be ignored.
The problem will be resolved when iSeries Access for Web is configured.
Select <span class="uicontrol">Next</span>.</li>
<li class="substepexpand"><span>The <span class="uicontrol">Out-of-Process Summary</span> page opens.
Select <span class="uicontrol">Finish</span>.</span> You have now created the
HTTP server IWATOMCAT, and an ASF Tomcat Web application server called <samp class="codeph">iwatomcat</samp>.
Minimize the browser window.</li>
</ol>
</li>
<li class="stepexpand" id="rzammxmpbegtomcat__tomconfig"><a name="rzammxmpbegtomcat__tomconfig"><!-- --></a><span>Configure iSeries Access for Web.</span> iSeries Access
for Web provides commands to configure the product. Two different commands
are provided, a CL command and a QShell script command.  Both commands
provide and perform the same function.  Use whichever version you prefer.<ul><li><strong>To use the CL command, follow these steps:</strong><ol type="a"><li>Configure iSeries Access
for Web for your Web application server using the following command:  
<pre>QIWA2/CFGACCWEB2 APPSVRTYPE(*ASFTOMCAT) TCSVRNAME(iwatomcat)
TCHOMEDIR(‘/ASFTomcat/iwatomcat’)TCUSRPRF(QTMHHTTP) </pre>
These
are the parameters used: <dl><dt class="dlterm">APPSVRTYPE</dt>
<dd>Tells the command which Web application server to configure. </dd>
<dt class="dlterm">TCSVRNAME</dt>
<dd>Tells the command the name of the Tomcat Web application server to configure.</dd>
<dt class="dlterm">TCHOMEDIR</dt>
<dd>Tells the command where in the server's file system the Tomcat Web application
server's directory structure is.  This value was displayed in step <a href="#rzammxmpbegtomcat__tomvalues">2.s</a>.</dd>
<dt class="dlterm">TCUSRPRF</dt>
<dd>Tells the command what user profile the Tomcat Web application server
uses.  This value was displayed in step <a href="#rzammxmpbegtomcat__tomvalues">2.s</a>.</dd>
</dl>
For help on this command and the parameters, press F1. <div class="note"><span class="notetitle">Migration Note:</span> <img src="./delta.gif" alt="Start of change" />If you are already using iSeries Access
for Web within another Web application server, refer to <a href="rzammnewconsid.htm">New
Web application server considerations</a>. This topic discusses additional
CFGACCWEB2 command parameters that can be input to migrate user data from
an existing configuration to this new configuration.<img src="./deltaend.gif" alt="End of change" /></div>
</li>
<li>Several messages similar to these will be displayed:   <ul class="simple"><li><tt class="msgph">Configuring iSeries Access for Web. </tt></li>
<li><tt class="msgph">Preparing to perform the configuration changes. </tt></li>
<li><tt class="msgph">Calling WebSphere to perform the configuration changes.</tt></li>
<li><tt class="msgph">iSeries Access for Web command has completed.</tt></li>
<li><tt class="msgph">The WebSphere instance application server must be stopped and
then started to enable the configuration changes.</tt></li>
</ul>
     </li>
<li>Press F3 or Specify when the command completes to exit the display session.</li>
</ol>
</li>
<li><strong>To use the QShell script command, follow these steps:</strong><ol type="a"><li>Start the QShell environment using the following server command: QSH</li>
<li>Make the iSeries Access
for Web directory the current directory.  Run this server command:  
<pre>cd /QIBM/ProdData/Access/Web2/install </pre>
</li>
<li>Configure iSeries Access
for Web portlets using the following command:   <pre>cfgaccweb2 -appsvrtype *ASFTOMCAT –tcsvrname iwatomcat
          -tchomedir /ASFTomcat/iwatomcat –tcusrprf QTMHHTTP</pre>
These
are the parameters used: <dl><dt class="dlterm">-appsvrtype</dt>
<dd>Tells the command which Web application server environment to configure. </dd>
<dt class="dlterm">-tcsvrname</dt>
<dd>Tells the command the name of the Tomcat Web application server to configure.</dd>
<dt class="dlterm">–tchomedir</dt>
<dd>Tells the command where in the server's file system the Tomcat Web application
server's directory structure is.  This value was displayed in step <a href="#rzammxmpbegtomcat__tomvalues">2.s</a>.</dd>
<dt class="dlterm">-tcusrprf</dt>
<dd>Tells the command what user profile the Tomcat Web application server
uses. This value was displayed in step <a href="#rzammxmpbegtomcat__tomvalues">2.s</a>.</dd>
</dl>
For help on this command and the parameters, specify the -?
parameter. <div class="note"><span class="notetitle">Migration Note:</span> <img src="./delta.gif" alt="Start of change" />If you
are already using iSeries Access for Web within another Web application
server, refer to <a href="rzammnewconsid.htm">New Web application server
considerations</a>. This topic discusses additional CFGACCWEB2 command
parameters that can be input to migrate user data from an existing configuration
to this new configuration.<img src="./deltaend.gif" alt="End of change" /></div>
</li>
<li>Several messages similar to these will be displayed:   <ul class="simple"><li><tt class="msgph">Configuring iSeries Access for Web. </tt></li>
<li><tt class="msgph">Preparing to perform the configuration changes. </tt></li>
<li><tt class="msgph">Calling WebSphere to perform the configuration changes.</tt></li>
<li><tt class="msgph">iSeries Access for Web command has completed.</tt></li>
<li><tt class="msgph">The WebSphere instance application server must be stopped and
then started to enable the configuration changes.</tt></li>
</ul>
     </li>
<li>Press F3 when the command completes to exit the QShell session.</li>
</ol>
</li>
</ul>
<ol type="a"><li class="substepexpand"><span>If the command were to fail or indicate an error, refer to the
log files:</span> <dl><dt class="dlterm">/QIBM/UserData/Access/Web2/logs/cmds.log</dt>
<dd>High level, cause and recovery information; translated.</dd>
<dt class="dlterm">/QIBM/UserData/Access/Web2/logs/cmdstrace.log</dt>
<dd>Detailed command flow for IBM Software Service; English only. </dd>
</dl>
</li>
<li class="substepexpand"><span>After successfully configuring iSeries Access for Web, the ASF Tomcat
Web application server must be started to load the changes to its configuration. 
This will be done later.</span></li>
<li class="substepexpand"><span>Signoff the 5250 session window.</span></li>
<li class="substepexpand"><span>Close the 5250 session window.</span></li>
</ol>
</li>
<li class="stepexpand" id="rzammxmpbegtomcat__tomstartweb"><a name="rzammxmpbegtomcat__tomstartweb"><!-- --></a><span>Start the web environment.</span><ol type="a"><li><span>Return to the browser window that is open to the <span class="uicontrol">IBM
Web Administration for iSeries server management</span> page.</span></li>
<li><span>The Manage ASF Tomcat Servers tabbed page should be active.
Under Server is listed IWATOMCAT – ASF Tomcat with a status of Stopped. Select
the green icon next to the Stopped status to start the ASF Tomcat Web application
server. The status is updated to Running.</span></li>
<li><span>Select the HTTP Servers tabbed page.</span></li>
<li><span>Under <span class="uicontrol">Server</span>, select IWATOMCAT - Apache.
The current status of this Apache HTTP server should be Stopped. Select the
green icon next to the status to start the HTTP server. The status is updated
to Running.</span></li>
<li><span>Close the browser window.</span></li>
</ol>
</li>
<li class="stepexpand" id="rzammxmpbegtomcat__tomaccess"><a name="rzammxmpbegtomcat__tomaccess"><!-- --></a><span>Use a browser to access iSeries Access for Web</span><ol type="a"><li class="substepexpand"><span>Open a browser to either of the following addresses to access iSeries Access
for Web:</span> <p>http://&lt;<var class="varname">server_name</var>&gt;:2016/webaccess/iWAHome<br />
http://&lt;<var class="varname">server_name</var>&gt;:2016/webaccess/iWAMain</p>
</li>
<li class="substepexpand"><span>Log in using an i5/OS™ user ID and password. The initial
load of iSeries Access
for Web might take a few seconds.  ASF Tomcat is loading Java™ classes
for the first time.  Subsequent loads of iSeries Access for Web will be faster.</span></li>
<li class="substepexpand"><span>The iSeries Access for Web Home or Main page displays.</span></li>
<li class="substepexpand"><span>Close the browser window.</span></li>
</ol>
</li>
</ol>
<div class="section">By following the above steps, you completed these tasks:<ul><li>Created an ASF Tomcat Web application server named iwatomcat.</li>
<li>Created an HTTP server named IWATOMCAT.</li>
<li>Configured   iSeries Access for Web for the ASF Tomcat Web application
server.</li>
<li>Started ASF Tomcat Web application server and HTTP Web server.   iSeries Access
for Web started when the ASF Tomcat Web application server started.</li>
<li>Verified that iSeries Access for Web can be accessed from a Web
browser.</li>
</ul>
<p><img src="./delta.gif" alt="Start of change" />In this example, only the <span class="cmdname">CFGACCWEB2</span> command
is used to configure iSeries Access for Web. For more information about
using all the iSeries Access
for Web CL commands, use the CL command finder. <img src="./deltaend.gif" alt="End of change" /></p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzammservxmpbeg.htm" title="These examples provide step-by-step instructions for setting up a complete Web serving environment.">Examples for configuring a new Web application server environment</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../clfinder/finder.htm">CL command finder</a></div>
</div>
</div>
<img src="./deltaend.gif" alt="End of change" /></body>
</html>
Reference in New Issue Copy Permalink