52 lines
3.7 KiB
HTML
52 lines
3.7 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>Overview of WebSphere Application Server - Express architecture</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h2><a name="overarch"></a>Overview of WebSphere Application Server - Express architecture</h2>
|
||
|
|
<img src="rzamy513.gif" align="right" width="359" height="329" alt="Architecture of WebSphere Application Server - Express" border="0">
|
||
|
|
|
||
|
|
<p>This image shows the high-level architectural components of WebSphere Application Server - Express for iSeries.</p>
|
||
|
|
|
||
|
|
<p>The architecture of WebSphere Application Server - Express consists of these software components:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><p><strong>WebSphere subsystem</strong>
|
||
|
|
<br>The WebSphere Application Server - Express subsystem, QASE5, contains the jobs that pertain to WebSphere Application Server - Express. In addition to the jobs running in the QASE5 subsystem, your applications may also use jobs running in other subsystems.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Application server</strong>
|
||
|
|
<br>The application server provides the runtime environment for server-side Java components (such as servlets and JavaServer Pages). An application server contains the following architectural components:</p>
|
||
|
|
<ul>
|
||
|
|
<li><p><strong>Web container</strong>
|
||
|
|
<br>The Web container runs within the application server and handles requests for servlets, JavaServer Pages files, and the Web applications that contain them.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Name server</strong>
|
||
|
|
<br>The Java Naming and Directory Interface, or JNDI, is used to provide access to Java components within a distributed computing environment. The WebSphere Application Server - Express name server provides the implementation of the JNDI service. You can bind WebSphere Application Server - Express resources to JNDI names, which allows applications to access resources such as data sources and mail providers.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Security server</strong>
|
||
|
|
<br>The WebSphere Application Server - Express security server provides security infrastructure and mechanisms to protect sensitive application resources and administrative resources and to address enterprise end-to-end security requirements on authentication, on resource access control, on data integrity, confidentiality, and privacy, and on secure interoperability.</p></li>
|
||
|
|
</ul><p></p></li>
|
||
|
|
|
||
|
|
<li><p><strong>HTTP server</strong>
|
||
|
|
<br>The HTTP server receives requests for server-side components (such as servlets and JavaServer Pages) and passes the requests to WebSphere Application Server - Express through an interface called the WebSphere plug-in. WebSphere Application Server - Express supports these HTTP servers:</p>
|
||
|
|
<ul>
|
||
|
|
<li>IBM HTTP Server for iSeries (powered by Apache)</li>
|
||
|
|
<li>Lotus Domino HTTP Server</li>
|
||
|
|
</ul><p></p></li>
|
||
|
|
|
||
|
|
<li><p><strong>WebSphere plug-in</strong>
|
||
|
|
<br>WebSphere Web server plug-ins enable the Web server to communicate requests for dynamic content, such as servlets, to the application server. WebSphere Application Server - Express ships two plug-ins; one for IBM HTTP Server for iSeries (powered by Apache) and one for Lotus Domino HTTP Server. The plug-ins use a configuration file to determine whether a request should be handled by the Web server or the application server. For example, the plug-in forwards servlet requests to the application server. If you are using the HTTP server to serve HTML files, then the plug-in forwards HTML requests to the HTTP server.</p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|