Kbase 19711: How to Set Up Apache Webserver for Webspeed
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
How to configure Apache webserver for Webspeed on UNIX
GOAL:
Details of the files involved during the configuration of an Apache Web server.
GOAL:
How to configure cgiip with apache web server
FACT(s) (Environment):
Progress 9.0x
OpenEdge 10.x
UNIX
Apache
FIX:
This is only a guide, and includes information about the ubroker.properties file to help Technical Support Engineers and users configure and test WebSpeed on UNIX platforms. The solution assumes a Progress installation already existing on this UNIX machine. It assumes everything (transaction server, name server, messenger, and web server)is on the same machine.
Follow these steps:
1) Install Apache Web server according to the Apache
instructions.
2) Edit the httpd.conf file in the conf directory under the
Apache installation.
Apache Version 1.3.9 has an installation bug that
comments out the location of the Server name line. The line
appears as:
# ServerName starbuck.
Remove the pound sign (#).
By default, the Apache Web server runs on port 80. If your
Web server runs on a port other than 80 (for example
8088), you must specify this port in the httpd.conf file:
#
# Port: The port to which the standalone server listens.
For # ports < 1023, you will need httpd to be run as root
initially.
#
Port 8088
Check whether DocumentRoot is pointing to the directory out of which you will serve your documents.
Check whether ScriptAlias has mapped /cgi-bin/ to your web server install directory/cgi-bin
3) Note the cgi-bin directory in the Apache installation. Apache
only supports cgi and therefore creates this directory and the
alias for the directory during installation. Copy wspd_cgi.sh
from the bin directory of the Progress installation to this
Apache cgi-bin area.
It is a sample script file used to call the WebSpeed
messenger.
4) The Apache Web server must be able to locate the static files
for Progress WebSpeed Workshop and other WebSpeed application
files. The alias WebSpeed31x (x stands for A,B,C or D depending on version) must be created. This should be
done near the /icons alias, for example:
Alias /webspeed31D/ "/usr1/besg/progress/91d/webspeed/"
<Directory "/usr1/besg/progress/91d/webspeed">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
NOTE: The above example is shown for the webspeed 3.1D. If it is another version the alias convention should be to make the "webspeed" word without the quotes in LOWER case and the alpha letter on the major version release on the alphanumeric portion should be in UPPER case. For instance, the alias for OpenEdge 10.0B WebSpeed should look like "webspeed100B" without the decimal and the quotes.
5) Start the Apache Web server using the command apachectl start.
Start from the bin directory of the apache installation.
If the Web server doesn't start, check the log files in the
logs directory of the Apache installation.
6) You start three processes: the AdminServer, the
NameServer, and the WebSpeed broker (which will then start
the agents).
AdminServer starts by default on port 20931 with the command
proadsv -start. If you must change the port it starts on, you
must specify this when starting AdminServer with a command
like:
proadsv -start -port 3333
Be aware that the NameServer, NS1, will start when the
AdminServer is started unless this is changed in the
ubroker.properties file). If the AdminServer won't start,
check the log files in the work directory,
AdminServerSystemOut.log, and admserv.log.
The Progress NameServer and WebSpeed broker must be configured
in the ubroker.properties file. The file includes a section
with sample definitions for a NameServer NS1
([NameServer.NS1]) and a WebSpeed broker wsbroker1
( [UBroker.WS.wsbroker1] ).
NS1 default starts on port 5162 and wsbroker1 starts on port
3055. If you must change these ports, do it in those
specific areas of the ubroker.properties file.
Once configured, NS1 i.s started with the command:
nsman -name NS1 -start
wsbroker1 is started with the command:
wtbman -name wsbroker1 -start
If the NameServer and WebSpeed brokers do not start, check the
log files in the work directory:
NS1.ns.log, wsbroker1.server.log > wsbroker1.broker.log
NOTE: AdminServer supports the managing of WebSpeed,
therefore the NameServer and WebSpeed brokers are associated
with the AdminServer. If you start AdminServer on a port other
than the default, you must specify the port number when
starting the NameServer and WebSpeed broker, similar
to this command:
nsman -name NS1 -start -port 3333
By default, the WebSpeed Messenger Administration (WSMAdmin)
capability is set to off for security reasons. When debugging,
turn it on for the Messenger you are working with, in this
case cgi. You must add the line:
AllowMsngrCmds=1
in the following area:
#
# WebSpeed CGIIP Messenger Properties
#
[WebSpeed.Messengers.CGIIP]
AllowMsngrCmds=1
controllingNameServer=NS1
msngrExecFile=$DLC/bin/cgiip
msngrScriptFile=$DLC/bin/wspd_cgi.sh
7) To ensure everything is configured properly, go to the URL
'http://hostname' and try to access the Apache Web server.
NOTE: If you started your Web server on a port other than 80,
the URL must change to 'http://hostname:portnumber.'
There, you should see the Web server home page information.
Query the AdminServer, the NameServer, and the WebSpeed broker
with the commands:
proadsv -query (optional: -port 3333)
nsman -name NS1 -query (optional: -port 3333)
wtbman -name wsbroker1 -query (optional: -port 3333)
Now go to 'http://hostname/cgi-bin/wspd_cgi.sh?WSMAdmin.'
This uses the wsbroker1 broker defined in the
ubroker.properties file and allows you to do a number of
configuration checks.
Add /WService=servicename to the URL if you use a broker other
than wsbroker1..