web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Chapter 4 Chapter4Web components Important This section provides information about the web components which are included in the BES AppServer Edition, and can be optionally installed (Web Services pack (VisiExchange) component) as part of VisiBroker Edition. For more information, go to the BES Installation Guide. For documentation updates, go to www.borland.com/techpubs/bes. Apache web server implementation The BES implementation of the open-source Apache web server version 2.0 (an httpd server) is HTTP 1.1-compliant and is highly customizable through the Apache modules. Apache configuration The Apache web server comes pre-configured and ready-to-use when it is initially started. Many modules are dynamically loaded during the Apache startup. You can later customize its configuration for the IIOP connector, clustering, failover, and load balancing with one or more web container(s). You can use the Management Console to modify the configuration file, or you can use the directives in the plain text configuration file: httpd.conf. By default, the Apache httpd.conf file is located in the following directory: /var/domains//configurations// mos//conf Otherwise, for the location of the httpd.conf file, go to the configuration.xml file located in: /var/domains//configurations/ and search for the Apache Managed Object, apache-process httpd-conf sub-element attribute: httpd-conf= For more information about the Apache Managed Object elements and attributes, go to the BDOC Reference, Managed Object elements and attributes section. Chapter 4: Web components 29
Apache web server implementation For information about configuring the httpd.conf file for the IIOP connector/redirector, go to Chapter 5, “Web server to web container connectivity.” Apache configuration syntax Note When you edit the httpd.conf file, you must adhere to the following configuration syntax guidelines: ■ ■ ■ ■ ■ ■ The httpd.conf files contain one directive per line. To indicate that a directive continues onto the next line, use a back-slash “\” as the last character on a line. No other characters or white space must appear between the back-slash “\” and the end of the line. Arguments to directives are often case-sensitive, but directives are not casesensitive. Lines which begin with the hash character “#” are considered comments. Comments cannot be included on a line after a configuration directive. ■ Blank lines and white space occurring before a directive are ignored, so you can indent directives for clarity. For additional information on the Apache web server configuration options and general directive usage, go to the Apache Software Foundation web site at: http:// www.apache.org, or go to the Java API Reference. Running Apache web server on a privileged port Processes which access privileged ports on UNIX hosts must have appropriate permissions; the process must be started with the permissions of user root. Typically, only some processes in a particular configuration need to be started with root permissions. The setuser script helps configure BES to allow Apache web server start as root or with root permissions. Before starting the configuration, gather the following information about the system on which Apache is installed: 1 BES installation directory 2 User and group names for the account that the Agent should become after shedding its root UID, that is, the installation owner. 3 User and group names for the system root account (typically root/sys) The following steps describe the procedure for configuring the Apache web server to run on port 80. 1 Ensure that the Management Hub and the configuration containing the Apache web server are not running. 2 Enable multi-user mode on the BES installation. a b c Edit the property agent.mum.enabled.root.mo=true in /var/domains/base/adm/properties/agent.config Become root. Run the setuser script: setuser -u -g +m 30 BES Developer’s Guide
- Page 1 and 2: Developer’s Guide Enterprise Serv
- Page 3 and 4: Contents Chapter 1 Introduction to
- Page 5 and 6: Entity beans . . . . . . . . . . .
- Page 7 and 8: Chapter 23 Using JMS 209 Configurin
- Page 9 and 10: Entity Bean Properties (applicable
- Page 11 and 12: Figures 0.1 Borland Enterprise Serv
- Page 13 and 14: BES Products and Editions overview
- Page 15 and 16: Documentation conventions Important
- Page 17 and 18: Contacting Borland support World Wi
- Page 19 and 20: BES services overview Figure 0.1 Bo
- Page 21 and 22: The Partition and its services ■
- Page 23 and 24: Borland Enterprise Server and J2EE
- Page 25 and 26: 14 BES Developer’s Guide
- Page 27 and 28: Creating Partitions Creating Partit
- Page 29 and 30: Running Partitions Table 3.1 Option
- Page 31 and 32: Configuring Partitions You can also
- Page 33 and 34: JMX support in Partitions ■ ■ A
- Page 35 and 36: JMX support in Partitions Figure 3.
- Page 37 and 38: Thread pools Partition properties r
- Page 39: 28 BES Developer’s Guide
- Page 43 and 44: Borland web container implementatio
- Page 45 and 46: Borland web container implementatio
- Page 47 and 48: Borland web container implementatio
- Page 49 and 50: Smart Agent implementation Smart Ag
- Page 51 and 52: 40 BES Developer’s Guide
- Page 53 and 54: Apache web server to Borland web co
- Page 55 and 56: Apache web server to Borland web co
- Page 57 and 58: Apache web server to Borland web co
- Page 59 and 60: Large data transfer Downloading lar
- Page 61 and 62: Large data transfer Uploading large
- Page 63 and 64: IIS web server to Borland web conta
- Page 65 and 66: IIS web server to Borland web conta
- Page 67 and 68: IIS web server to Borland web conta
- Page 69 and 70: Session management with JSS If an i
- Page 71 and 72: Managing and configuring the JSS Co
- Page 73 and 74: The Borland IIOP connector BES supp
- Page 75 and 76: Setting up your web container with
- Page 77 and 78: 66 BES Developer’s Guide
- Page 79 and 80: Web-enabling your CORBA server Impo
- Page 81 and 82: Configuring your Apache web server
- Page 83 and 84: Configuring your Apache web server
- Page 85 and 86: Web Services and Partitions ■ ■
- Page 87 and 88: Web Service providers Java:RPC prov
- Page 89 and 90: How Borland Web Services work
Chapter<br />
4<br />
Chapter4Web components<br />
Important<br />
This section provides information about the <strong>web</strong> components which are included in the<br />
BES AppServer Edition, and can be optionally installed (Web Services pack<br />
(VisiExchange) component) as part of VisiBroker Edition. For more information, go to<br />
the BES Installation Guide.<br />
For documentation updates, go to www.borland.com/techpubs/bes.<br />
Apache <strong>web</strong> <strong>server</strong> implementation<br />
The BES implementation of the open-source Apache <strong>web</strong> <strong>server</strong> version 2.0 (an httpd<br />
<strong>server</strong>) is HTTP 1.1-compliant and is highly customizable through the Apache<br />
modules.<br />
Apache configuration<br />
The Apache <strong>web</strong> <strong>server</strong> comes pre-configured and ready-to-use when it is initially<br />
started. Many modules are dynamically loaded during the Apache startup. You can<br />
later customize its configuration for the IIOP connector, clustering, failover, and load<br />
balancing with one or more <strong>web</strong> container(s). You can use the Management Console<br />
to modify the configuration file, or you can use the directives in the plain text<br />
configuration file: httpd.conf.<br />
By default, the Apache httpd.conf file is located in the following directory:<br />
/var/domains//configurations//<br />
mos//conf<br />
Otherwise, for the location of the httpd.conf file, go to the configuration.xml file located<br />
in:<br />
/var/domains//configurations/<br />
and search for the Apache Managed Object, apache-process httpd-conf sub-element<br />
attribute:<br />
httpd-conf=<br />
For more information about the Apache Managed Object elements and attributes, go to<br />
the BDOC Reference, Managed Object elements and attributes section.<br />
Chapter 4: Web components 29
Change language