12.11.2014 Views

web server - Borland Technical Publications

web server - Borland Technical Publications

web server - Borland Technical Publications

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Apache <strong>web</strong> <strong>server</strong> implementation<br />

For information about configuring the httpd.conf file for the IIOP connector/redirector,<br />

go to Chapter 5, “Web <strong>server</strong> to <strong>web</strong> container connectivity.”<br />

Apache configuration syntax<br />

Note<br />

When you edit the httpd.conf file, you must adhere to the following configuration<br />

syntax guidelines:<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

The httpd.conf files contain one directive per line.<br />

To indicate that a directive continues onto the next line, use a back-slash “\” as the<br />

last character on a line.<br />

No other characters or white space must appear between the back-slash “\” and the<br />

end of the line.<br />

Arguments to directives are often case-sensitive, but directives are not casesensitive.<br />

Lines which begin with the hash character “#” are considered comments.<br />

Comments cannot be included on a line after a configuration directive.<br />

■<br />

Blank lines and white space occurring before a directive are ignored, so you can<br />

indent directives for clarity.<br />

For additional information on the Apache <strong>web</strong> <strong>server</strong> configuration options and general<br />

directive usage, go to the Apache Software Foundation <strong>web</strong> site at: http://<br />

www.apache.org, or go to the Java API Reference.<br />

Running Apache <strong>web</strong> <strong>server</strong> on a privileged port<br />

Processes which access privileged ports on UNIX hosts must have appropriate<br />

permissions; the process must be started with the permissions of user root. Typically,<br />

only some processes in a particular configuration need to be started with root<br />

permissions. The setuser script helps configure BES to allow Apache <strong>web</strong> <strong>server</strong> start<br />

as root or with root permissions.<br />

Before starting the configuration, gather the following information about the system on<br />

which Apache is installed:<br />

1 BES installation directory<br />

2 User and group names for the account that the Agent should become after shedding<br />

its root UID, that is, the installation owner.<br />

3 User and group names for the system root account (typically root/sys)<br />

The following steps describe the procedure for configuring the Apache <strong>web</strong> <strong>server</strong> to<br />

run on port 80.<br />

1 Ensure that the Management Hub and the configuration containing the Apache <strong>web</strong><br />

<strong>server</strong> are not running.<br />

2 Enable multi-user mode on the BES installation.<br />

a<br />

b<br />

c<br />

Edit the property<br />

agent.mum.enabled.root.mo=true<br />

in<br />

/var/domains/base/adm/properties/agent.config<br />

Become root.<br />

Run the setuser script:<br />

setuser -u -g +m<br />

30 BES Developer’s Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!