Kbase P85219: How to setup cgiip.exe messenger and/or cgiip.wsc script with IIS 6.0
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/07/2009 |
|
Status: Verified
GOAL:
How to setup CGI messenger with IIS 6.0
GOAL:
How to configure CGI messenger with with IIS 6.0
GOAL:
How to setup cgiip.exe messenger
GOAL:
How to configure cgiip.exe messenger
GOAL:
How to setup cgiip.wsc script
GOAL:
How to configure cgiip.wsc script
GOAL:
How to configure WebSpeed messenger on windows 2003?
FACT(s) (Environment):
Windows 2003
IIS 6.0
WebSpeed 3.1D
WebSpeed 3.1E
OpenEdge 10.x
FIX:
Setting up cgiip.exe with IIS 6.0:
-------------------------------------
1. Make sure the cgiip.exe is in the [IIS Installation Drive]:\inetpub\scripts directory, or any folder of your choice. Also, a virtual directory (any name of your choice) is created that is mapped with the [IIS Installation Drive]:\inetpub\scripts folder or the folder you placed the cgiip.exe messenger in.
2. Check to make sure that the virtual directory has the read, run script and execute privileges set. The physical directory where the messenger resides, also needs to have IUSR_<machine_name> user with read and execute privileges granted.
3. In the IIS console (right mouse click on the my computer icon in the desktop > select manage > expand the tree for the Services and Applications > expand the tree for the Internet Information Service), select or highlight Web Service Extensions.
4. Click on the Add a new web service extension..., under the extension name you can add any name you like. You can type "WS CGI Messenger" for instance. Click the Add button to select the cgiip.exe messenger from [IIS Installation Drive]:\inetpub\scripts or where ever the messenger is which is related to the virtual directory. Check the box that says "Set the extension status to allowed".
Setting up cgiip.wsc with IIS 6:
-----------------------------------
A: Follow the step number 1 and 2 above. Make sure you add cgiip.wsc along with cgiip.exe in the [IIS Installation Drive]:\inetpub\scripts folder. Follow the step 3 above. If you already have the web service extension created, you can edit the existing properties and add another required file the same as step 4. After you added the cgiip.exe it should look like the following:
[IIS Installation Drive]:\inetpub\scripts\cgiip.exe
If the IIS Installation Drive is "C", it should look like:
C:\inetpub\scripts\cgiip.exe
Add "%s %s" followed by an space but without the double quote. The entry should look like the following:
C:\inetpub\scripts\cgiip.exe %s %s
Click OK buttons to get out of the configuration.
B: In order to map the .wsc extension in the web server, right mouse click on the default web site > select Properties > select Home Directory tab > Click on the configuration button in the Application settings section > In the Application configuration Configuration window, select Mappings tab > Click "Add" button > browse the "Executable", cgiip.exe, from [IIS Installation Drive]:\inetpub\scripts folder. Place a double quote around the whole path and type "%s %s" followed by an space without the quotes. If the IIS Installation Drive is on "C" drive, the entry should look like the following:
"C:\inetpub\scripts\cgiip.exe" %s %s
Type .wsc in the Extension input box. The "All verbs" and the "Script engine" should be checked. Click OK out of the properties. Restart the web server.
Notes:
- To restart IIS6, go to IIS admin, select the IIS on the right, right click -> all tasks -> restart IIS
- Make sure the local path of the directory containing the .wsc script file does not contain spaces.
This must happen in order for the configuration to take effect