Kbase P76789: How to configure Sun One Webserver 6.0 with OpenEdge 32 bit WSNSA messenger?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/30/2008 |
|
Status: Verified
GOAL:
How to configure Sun One Webserver 6.0 with OpenEdge 32 bit WSNSA messenger?
GOAL:
How to configure Sun One Webserver 6.1 with OpenEdge 32 bit WSNSA messenger?
GOAL:
How to configure Sun One (formally, iplanet ) Webserver 6.0 with OpenEdge 32 bit WSNSA messenger?
GOAL:
Where do I download Sun One Web Server 6.0 sp5?
GOAL:
How do I install and configure Sun One webserver 6.0 SP5 with webspeed?
FACT(s) (Environment):
OpenEdge 10.x
WebSpeed 3.x
iPlanet 6.0
FIX:
1. Preinstallation tasks
First, you have to download the Sun One webserver SP05 installation file from http://wwws.sun.com/software/download/products/3e3add06.html, then uncompress / untar the file into a temporary directory.
2. Installation
*** For more information about the installation process, refer to documentation at http://docs.sun.com/db/coll/S1_ipwebsrvree60_en.
To execute the installation:
a- Run ./setup
b - Follow the menu instructions.
3. To set up the NSAPI messenger:
a) go to install directory/https-hostname/config
b) Edit magnus.conf and add these line (Be sure they are the LAST 2 Init fn lines. Let the first line wrap - do not hit return):
Init fn=load-modules shlib="/dlc/bin/wsnsa.dll" funcs=WSNSAinit,
WSNSAdefault,WSNSAshutdown,WSNSAwebspeedCheck
Init fn=WSNSAinit
Note: the path for shlib depends on where your installation of messenger is.
c) Edit obj.conf and add
NameTrans fn=WSNSAwebspeedCheck
Also add this line (FIRST in the Service Method lines):
Service method=(GET|POST|HEAD) fn=WSNSAdefault
d) Edit the start file in the install directory/https-hostname directory to include the values for DLC and
WRKDIR such as:
DLC=/dlc; export DLC
WRKDIR=/usr1/progress/wrk; export WRKDIR
Note: DLC should be tailored to your messenger installation directory
4. Configure messenger's ubroker.properties file. Make sure the controlling name server is pointing to correct name server or the broker information is set up if name server is not used.
5. From the browser:
http://host:port/wsnsa.dll/WService=wsbroker1/ping
http://host:port/wsnsa.dll/WService=wsbroker1/workshop
** http://host:port/wsnsa.dll?WSMAdmin