Kbase P102773: How to make WebSpeed to work with short urls
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/19/2009 |
|
Status: Unverified
GOAL:
How to make WebSpeed to work with short urls
FACT(s) (Environment):
OpenEdge 10.x
IIS 5.1
IIS 6.0
Windows XP
Windows Server 2000
Windows Server 2003
FIX:
1. Control Panel -> Administrative Tools -> Internet Information Services
2. Locate the "Default Web Site" and right-click onto it choosing "Properties"
3. Choose "Home Directory" tab
4. Unless is already set, then choose Execute permissions: Scripts Only
5. Click onto the "Configuration" button (if it is not enabled, then you have to first click onto the button <Create> above it, to create application name.)
6. In the "Application Configuration" dialog click onto the button <Add>
7. Choose the executable to be your cgiip.exe in the OpenEdge installation directory e.g.:
"C:\Progress\bin\cgiip.exe" -i wsbroker1
Extension: .ssp
Verbs: All Verbs
Enable "Script engine"
Disable "Check that file exists"
Click <OK>
Now you have set that all the files with the extension .ssp will be mapped by the web server to the WebSpeed messenger using wsbroker1 (you can change this if needed).
8. Open the Windows Explorer and copy file
%DLC%\src\web\objects\web-util.p into the
%WRKDIR%\web\objects\web-util.p
where %DLC% is your OpenEdge installation directory and
%WRKDIR% your WebSpeed working directory.
9. Modify that copied file in the following way:
Locate the "run-web-object" internal procedure and right after
the definitions of the variables add the following code:
IF pcFileName EQ "" THEN
DO:
IF NUM-ENTRIES(SCRIPT_NAME,"/") = 2 THEN
DO:
ASSIGN
pcFilename = SCRIPT_NAME
pcFilename = REPLACE(pcFileName,"/","") .
END.
ELSE
ASSIGN
pcFilename = SCRIPT_NAME
SCRIPT_NAME = "/" + ENTRY(2,SCRIPT_NAME,"/")
pcFilename = SUBSTR(pcFilename,2,LENGTH(pcFileName)) .
END.
This code will prevent the error message :
Unable to find web object ''
10. Start your WebSpeed broker and web server and test with the URL: http://hostname/workshop.ssp
You should see the workshop page although the 2 left frames will not be rendered correctly - this is nothing to worry about as the workshop code contains absolute paths.
11. When you test the following URL:
http://hostname/webtools/session.ssp
the page will work fine in IIS 6.0, but it will produce the error 500 on the IIS 5.1 web server. This has to do with the way how these 2 web servers are parsing the URL. IIS 6.0 looks into the entire URL and as it sees the .ssp it immediately forwards the request to the messenger (to which the .ssp is mapped). On the other hand, IIS 5.1 tries to locate 'webtools' directory under its root directory (C:\Inetpub\wwwroot by default) and as it can't find it causes this error. Therefore, for the IIS 5.1 you need to create this directory:
C:\Inetpub\wwwroot\webtools
It doesn't need to contain the actual WebSpeed file, but it needs to be there in order for the web server to be able to perform mapping.