Kbase 19717: How to Setup Netscape WebServer with WebSpeed 3.x
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
How to Setup Netscape WebServer for webspeed messenger.
FACT(s) (Environment):
WebSpeed 3.x
FIX:
This document is being written to describe which files are involved
during the configuration of an Netscape (iPlanet) web server 4.x for use with WebSpeed 3.x. For Netscape/iPlanet 6.x information, please refer to changes at the end. It is meant only to be a guide. It includes
information about the ubroker.properties file to help a (more windows
literate) TSE to configure and test WebSpeed on a UNIX platform. It
assumes that a Progress installation exists on this UNIX platform
before starting and also assumes that everything is on the same
machine. Netscape supports CGI and NSAPI so both are discussed here.
STEPS
[PART I- Configure Netscape ]
1. Install the Netscape Web server according to the Netscape
instructions. At the time of this writing, the version was 4.1. This
version includes a gui interface for managing the Web server. During
installation, you are asked for a port number for the AdminServer for
the gui interface as well as a port number for the web server. It's
a good idea to write these down.
2. If you are NOT configuring Netscape for use with NSAPI, skip to
step 3. First, edit the "obj.conf" file that is in the install
directory/https-hostname/conf directory. You will need to add the
following information
NOTE before Adding
Be sure these lines are the LAST 2 Init fn lines and let the first line wrap, do not hit return
(Assuming webspeed is installed at /dlc directory, tailor shlib setting to your own installation.)
ADD
---
Init fn=load-modules shlib="/dlc/bin/wsnsa.dll" funcs=WSNSAinit, WSNSAdefault,WSNSAshutdown,WSNSAwebspeedCheck
Init fn=WSNSAinit
NOTE before Adding
Add this line (FIRST in the NameTrans lines):
Also add this line (FIRST in the Service Method lines):
ADD
---
NameTrans fn=WSNSAwebspeedCheck
Service method=(GET|POST|HEAD) fn=WSNSAdefault
You also need to edit the "start" file in the install directory/https-hostname directory to include the values for DLC and WRKDIR such as:
ADD
---
DLC=/dlc; export DLC
WRKDIR=/usr1/progress/wrk; export WRKDIR
3. If you are NOT configuring Netscape for use with CGI, skip to
step 4. You will see that there is no cgi-bin directory in the
Netscape installation. It supports cgi, however you need to create a
directory (and the alias to use it). Create the cgi-bin directory in
the install-directory and copy wspd_cgi.sh from the bin directory of
the Progress installation to this cgi-bin area. It is a sample script
file used to call the messenger.
4. You must first start the AdminServer using the "start" command.
This must be done before you can start the Netscape Web server. This
can be done from the install directory/https-admserv directory. You must be logged in as root. From a browser, use the
url:http://hostname:portnumber, where portnumber is the port number
you gave during installation for the AdminServer. You'll see your
server name there and you can click the manage button.
5. The Web server must be able to locate the static files for WebSpeed Workshop and other WebSpeed application files. If you did not choose to copy these files to the web server document root directory during the Progress installation you need to create the alias webspeed3x to point to their location. Click the Content Mgmt tab and then the Additional document directories button on the left. Add /webspeed3x to the end of the URL prefix and then specify the location of the files such as /usr1/progress/9x/webspeed.
6. If you are NOT configuring Netscape for use with CGI, skip to
step 7. You need to add the cgi-bin alias. Click the programs tab.
Add cgi-bin to the end of the url prefix and then the location of your
cgi-bin directory below that.
7. Now, you can start the Web server. Click on the Preferences tab and click the server on button. If it does not start, check the log
files. They are in the install-directory/https-hostname/logs
directory.
[PART II - Configure WebSpeed with Netscape.]
The AdminServer starts by default on port 20931 with the command
proadsv -start (optional: define -port)
The NameServer, NS1, will by default autostart when the AdminServer
is started, unless otherwise change within ubroker.properties file.
The NameServer and WebSpeed brokers need to be configured in the
ubroker.properties file. There is a section with sample definitions
for a name server NS1 ( [NameServer.NS1] ) and a WebSpeed broker
wsbroker1 ( [UBroker.WS.wsbroker1] ). NS1 will start by default on
port 5162 and wsbroker1 will start on port 3055. If you need to
change these ports, do so in these specific areas of the
ubroker.properties file.
Once configured, start NameServer and WebSpeed broker (s).
NS1 can be started using the command
nsman -name NS1 -start (optional: define -port)
wsbroker1 can be started using the command
wtbman -name wsbroker1 -start (optional: define -port)
Note if any component is not starting, please check appropriate
log files for more information. Query each component to make sure
that they can be accessed.
After all components have been configured correctly, verify that the
Netscape Web server can be accessed referencing; http://hostname.
Remember, if you've started your Web server on a port other than 80,
then change the URL to "http://hostname:portnumber".
Query the AdminServer, NameServer and also the WebSpeed broker (s) using the commands:
proadsv -query (optional: define -port)
nsman -name NS1 -query (optional: define -port)
wtbman -name wsbroker1 -query (optional: define -port)
[PART III - Verify the following can be accessed]
For CGI use http://hostname/cgi-bin/wspd_cgi.sh?WSMAdmin. This will use the wsbroker1 broker defined in the ubroker.properties file and will allow you to do a number of checks to be sure things are configured correctly. Add /WService=servicename if you want to use a
broker other than wsbroker1.
For NSAPI use http://hostname/wsnsa.dll/WService=wsbroker1?WSMAdmin.
This will use the wsbroker1 broker defined in the ubroker.properties
file and will allow you to do a number of checks to be sure things are
configured correctly.
To configure CGIIP, go to AdminServer, click on Class Manager button, go to Programs tab, Select CGI Directory option on the left, and map URL prefix /cgi-bin to install directory/cgi-bin.
To map workshop WebSpeed direcotory, go to Content Mgnt tab, and pick up additional document root directory option..