Release 10.1A: OpenEdge Deployment:
WebClient Applications

> ## Hosting on a Web server

> If you deploy your application component files or external installer on a Web server, there are a number of other tasks that you must perform and considerations you must make. The following sections provide information about:

> - Case sensitivity on UNIX Web servers

> - Executable directories

> - Authentication options on Microsoft Internet Information Server (IIS)

> - Configuring MIME types for your Web server

> ##### Case sensitivity on UNIX Web servers

> Web servers that use the UNIX operating system, such as Apache, are case-sensitive. Therefore, the letter case of installation filenames on the Web server and those in your application configuration file must match or a run-time error will occur.

> ##### Executable directories

> Do not place a Web installer in an executable directory on your Web server. Otherwise, when a user’s browser accesses the installer executable, the installer attempts to execute on the Web server instead of downloading and executing on the user’s system. This results in a server run-time error.

> You can prevent this on an iPlanet Web Server or Netscape Enterprise Server by setting the Web server to download all executable files referenced from a browser instead of executing them. For more information, visit the iPlanet Web site to read the article on setting your Web server to let users download executable files. Otherwise, see your Web server documentation for information on how to plan the content of your directories (or to create virtual directories) so they do not allow local execution of files referenced by the user’s browser.

> ##### Authentication options on Microsoft Internet Information Server (IIS)

> If you are configuring Internet Information Server, select only the Basic (Clear Text) authentication option in the WWW Services Properties for the Web server. If the Windows Challenge/Response authentication option is selected, end users who are not running Internet Explorer receive an authentication dialog box that they cannot satisfy. This prevents them from starting an installation. As a result, end users can never run their application over the Web.

> Note: Basic authentication uses a well-known encryption algorithm for user names and passwords that provides minimal security.

> ##### Configuring MIME types for your Web server

> When the user attempts to access the application, the Web page that you provide references the configuration file for the application. Before your user’s browser can open the configuration file using WebClient Initializer, it must recognize a MIME type for the configuration file. To accomplish this, you must configure your Web server to associate the configuration file extension with its MIME type.

> The method used for configuring your Web server depends on the type of Web server you use. For each Web server, however, you must specify the extension and MIME type for the configuration file types, as follows:

> - MIME types — `application/progress-wcappcab`

> - File type extension — `prowcapc`

> The following sections provide instructions for configuring the MIME type on OpenEdge-supported Web servers.

> Note: If an Internet Service Provider (ISP) hosts your Web installation, you must provide it with this configuration file MIME type information required to configure the Web server properly.

> ##### Apache Web server

> | To register the MIME types for all directories on the server, do one of the following:

> - Add the following line to the `srm.conf` file:

>     addtype application/progress-wcappcab prowcapc

> - Add the following line to the `mime.types` file:

>     application/progress-wcappcab prowcapc

> If you are using a dedicated Web server, rehash/recycle to register this information.

> ##### Sun One Web Server/iPlanet Web Server/Netscape Enterprise Server

> For a Sun Web server, you must change the association of `.exe files` in addition to adding the definition for `application/progress-wcappcab`.

> | To configure MIME types on Sun One/iPlanet/Netscape:

> 1. Open the Administration Server.

> 2. Select a server and choose the Manage button.

> 3. Choose Preferences Mime Types.

> 4. Add the new content-type definition application/progress-wcappcab, and associate it with the file suffix prowcapc.

> 5. Edit the magnus-internal/cgi MIME type definition, and remove exe from the list of associated extensions.

> 6. Edit the application/octet-stream MIME type definition, and add exe to the list of associated extensions.

> 7. Complete the Administration Server steps to save and apply your changes so the Web server recognizes the changes to the MIME type definitions.

> ##### Microsoft Internet Information Server (IIS)

> The IIS server stores its MIME types in the Windows registry. You register the MIME type for the application configuration file using the `iis_wc.reg` registry file.

> You can find this file in the following location in your OpenEdge installation:

>     OpenEdge_install_dir\webinstall\webclient\web_image

> | To merge the MIME type entries from this file into the registry and configure the Web server:

> 1. Copy the `iis_wc.reg` file to your Web server.

> 2. To register the MIME type, do one of the following on the Web server:

> - Select `iis_wc.reg` in the Windows Explorer, right-click, and select Merge. This imports the contents of the file into the registry.
> - Double-click the file in the Windows Explorer. This imports the contents of the file into the registry.
> 3. Restart your Web server to register these changes.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095