101 lines
5.8 KiB
HTML
101 lines
5.8 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Administer HTTP transports for the Web container with the administrative console</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h3><a name="appsvrtrans"></a>Administer HTTP transports for the Web container with the administrative console</h3>
|
||
|
|
|
||
|
|
<p>Components of WebSphere Application Server - Express uses HTTP transports to communicate with each other. Your application also uses HTTP transports to receive and reply to client requests.</p>
|
||
|
|
|
||
|
|
<p>In WebSphere Application Server - Express, version 5.1, HTTP transport functionality is a supported internal Web server that you can use in a production environment. You do not need to configure a separate HTTP server instance for your application server. However, it is recommended that you use a separate HTTP server instance, because other Web servers can offer advanced functionality and improved performance.</p>
|
||
|
|
|
||
|
|
<p>Before you decide which type of transport to use, consider the following limitations of the internal HTTP transports:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Internal transports do not support Simple Network Management Protocol (SNMP).</li>
|
||
|
|
<li>Existing Common Gateway Interface (CGI) support must be implemented as servlets. That is, you must convert any existing CGI programs to servlets.</li>
|
||
|
|
<li>Internal transports do not support session affinity for workload balancing.</li>
|
||
|
|
<li>Because static content can not be served directly by an external HTTP server, overall application server performance can be adversely affected.</li>
|
||
|
|
<li>Web servers generally are more susceptible to security exposures than application servers are. If a production environment includes an external Web server and an application server running on two separate machines, many of the Web server's security exposures can be limited to the machine where the Web server runs. However, if you use the internal HTTP transport, the internal HTTP transport always runs on the same machine as the application server. As a result, a security exposure in the Web server can expose both the Web server's and application server's environments.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>You can use the administrative console and wsadmin to configure HTTP transports for your application server.</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><a href="#acappsvrtrans">Use the administrative console to configure HTTP transports</a></li>
|
||
|
|
<li><a href="#wsaappsvrtrans">Use wsadmin to configure HTTP transports</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p><strong><a name="acappsvrtrans">Use the administrative console to configure HTTP transports</a></strong></p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><a href="acstart.htm">Start the administrative console</a>.</li>
|
||
|
|
<li>Expand <strong>Servers</strong> and click <strong>Application Servers</strong>.</li>
|
||
|
|
<li>Click the name of your application server.</li>
|
||
|
|
<li>On the application server's page, click <strong>Web Container</strong>.</li>
|
||
|
|
<li>On the Web Container page, click <strong>HTTP transports</strong>.</li>
|
||
|
|
<li>Add, modify, or remove an HTTP transport.
|
||
|
|
<ul>
|
||
|
|
<li>To add a new HTTP transport, follow these steps:
|
||
|
|
<ol type="a">
|
||
|
|
<li>Click <strong>New</strong>.</li>
|
||
|
|
<li>Configure the HTTP transport settings.</li>
|
||
|
|
<li>Click <strong>Apply</strong> or <strong>OK</strong>.</li>
|
||
|
|
</ol></li>
|
||
|
|
<li>To modify an HTTP transport, follow these steps:
|
||
|
|
<ol type="a">
|
||
|
|
<li>Click the host name for the transport that you want to modify.</li>
|
||
|
|
<li>Make your changes.</li>
|
||
|
|
<li>Click <strong>Apply</strong> or <strong>OK</strong>.</li>
|
||
|
|
</ol></li>
|
||
|
|
<li>To remove an HTTP transport, follow these steps:
|
||
|
|
<ol type="a">
|
||
|
|
<li>Select the transport that you wanto to remove.</li>
|
||
|
|
<li>Click <strong>Delete</strong>.</li>
|
||
|
|
</ol></li>
|
||
|
|
</ul></li>
|
||
|
|
<li><a href="acsave.htm">Save the application server configuration</a>.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<p><strong><a name="wsaappsvrtrans">Use wsadmin to configure HTTP transports</a></strong></p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><p>On the CL command line, run the STRQSH (Start Qshell) command.</p></li>
|
||
|
|
|
||
|
|
<li><p>Run the cd command to change to the directory that contains the wsadmin tool:</p>
|
||
|
|
<pre>cd /QIBM/ProdData/WebASE51/ASE/bin</pre></li>
|
||
|
|
|
||
|
|
<li><p><a href="wsarun.htm#start">Start wsadmin</a>.</p></li>
|
||
|
|
|
||
|
|
<li><p>At the wsadmin prompt, run this command to identify the application server and assign it to the server variable:</p>
|
||
|
|
<pre>set server [$AdminConfig getid /Cell:<em>myCell</em>/Node:<em>myNode</em>/Server:<em>myAppSvr</em>/]</pre>
|
||
|
|
<p>where <em>myCell</em> is the name of the cell that contains your application server, <em>myNode</em> is the name of the node that contains your application server, and <em>myAppSvr</em> is the name of your application server.</p></li>
|
||
|
|
|
||
|
|
<li><p>Run this command to identify the Web container for the application server and assign it to the wc variable:</p>
|
||
|
|
<pre>set wc [$AdminConfig list WebContainer $server]</pre></li>
|
||
|
|
|
||
|
|
<li><p>Run these commands to list all of the transports that belong to the Web container and assign it to the transports variable:</p>
|
||
|
|
<pre>set transportsAttr [$AdminConfig showAttribute $wc transports]
|
||
|
|
set transports [lindex $transportsAttr 0]</pre>
|
||
|
|
<p>These commands return the transport objects from the transports attribute in a list format.</p></li>
|
||
|
|
|
||
|
|
<li><p>Run this command to identify the transport to be modified and assign it to the transport variable:</p>
|
||
|
|
<pre>set transport [lindex $transports 0]</pre></li>
|
||
|
|
|
||
|
|
<li><p>Run this command to modify the address attribute to change the host and port:</p>
|
||
|
|
<pre>$AdminConfig modify $transport {{address {{host {myHost}} {port 9081}}}}</pre></li>
|
||
|
|
|
||
|
|
<li><p>Run this command to save your changes:</p>
|
||
|
|
<pre>$AdminConfig save</pre></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|