Citrix
Include legacy content

Archive: How to Enable File Type Association with Access Gateway Enterprise Edition

  • CTX116253
  • Created On  Mar 28, 2008
  • Updated On  Feb 04, 2010
  • Article
  • Topic : Other
This article is no longer maintained, its content refers to a discontinued product and may be out of date. Refer to the Discontinued Product Lifecycle or Active Citrix Product pages for more information on support schedules.

Summary

This article describes how to enable the File Type Association feature with Citrix Access Gateway Enterprise Edition.

Background

The File Type Association feature associates file extensions with specific applications that are published on a XenApp server (previously known as Citrix Presentation Server). When a user clicks on a link to a file containing an associated file extension, the file opens as a published application opposed to opening locally on the client device.

Requirements

• Access Gateway Enterprise Edition 8.1 or later

• Web Interface 4.5 or later

• XenApp 4.x or later

File Type Association also requires several files to be updated on either version of Web Interface prior to using the feature. The updated files are attached to this article.

Procedure

Web Interface 4.5 and 4.6 steps:

1. Create a Web Interface site. This site can be in Direct or Advanced Access Control mode.

2. Inside the WI_mods.zip file attached to this article are three folders: FTA_patch_WI4.5, FTA_patch_WI4.6, and FTA_patch_WI5.0. The FTA_patch_WI4.5 folder contains files specifically for Web Interface 4.5. The FTA_patch_WI4.6 folder contains files specifically for Web Interface 4.6. The FTA_patch_WI5.0 folder contains files specifically for Web Interface 5.0. Download and extract the folder that corresponds to the version of Web Interface you are using.

3. Copy the modified app_data, auth, and site directories to your Web Interface site. These updated directories overwrite existing directories with the same name. The new directory structure does not affect other Web Interface sites on your Web Interface server.

4. Copy the modified web.config file to your Web Interface server. The default location for this file is <root directory>\Inetpub\wwwroot\Citrix\AccessPlatform. This overwrites the existing web.config file.

Web Interface 5.0 and 5.0.1 steps:

1. Create a Web Interface site. This site can be in Direct or Advanced Access Control mode.

2. Copy the modified app_data, app_code, and site directories to your Web Interface site. These updated directories overwrite existing directories with the same name. The new directory structure does not affect other Web Interface sites on your Web Interface server.

3. Locate the web.config file in your Web Interface site directory. The default location for this file is <root directory>\Inetpub\wwwroot\Citrix\XenApp.

4. Open web.config with a text editor such as notepad.

5. Locate the following lines:

<location path="site/launch.ica">
        <system.web>
            <httpHandlers>
                <add verb="*" path="*.ica" type="System.Web.UI.PageHandlerFactory"/>
            </httpHandlers>
        </system.web>
    </location>

    <location path="site/launch.rad">
        <system.web>
            <httpHandlers>
                <add verb="*" path="*.rad" type="System.Web.UI.PageHandlerFactory"/>
            </httpHandlers>
        </system.web>
    </location>

6. Replace with the following line:

<location path="site/contentLaunch.ica">
        <system.web>
            <httpHandlers>
                <add verb="*" path="*.ica" type="System.Web.UI.PageHandlerFactory"/>
            </httpHandlers>
        </system.web>
    </location>

    <location path="site/contentLaunch.rad">
        <system.web>
            <httpHandlers>
                <add verb="*" path="*.rad" type="System.Web.UI.PageHandlerFactory"/>
            </httpHandlers>
        </system.web>
    </location>

Save the changes you made to web.config

Access Gateway steps:

1. Create a new virtual server or use an existing virtual server and bind authentication policies as needed.

2. Create a new session policy and session profile. The session profile must point to the Web Interface site you modified in the steps above. Below is an example of a session profile that points to a Web Interface site. In this example, Compact is specified in the Web Interface Portal Mode field. This setting should match what you have configured on your Web Interface server. Turn ICA Proxy mode to OFF so Web Interface applications will enumerate in the default Homepage.

3. Bind the session policy to the virtual server.

4. Create a traffic policy. The traffic policy must include expressions that contain the file extension for any file type you want to associate with the File Type Association feature. The traffic policy should look similar to the following example.

In this example, the ICA client installed on the user’s workstation initiates an ICA session to the XenApp server when a user attempts to open a Word document with a .doc file extension.

5. Bind the traffic policy to the virtual server.

XenApp steps:

1. Examine the properties of the published applications you want to use with the File Type Association feature. The file extension you want to use with File Type Association should be enabled under the published application’s content redirection properties. In the following example, the Word application has been published and all of its file extensions have been enabled for the File Type Association feature:

2. Click Apply and then click OK to close the properties window.

3. You have now associated certain file extensions with specific published applications. The File Type Association feature should now be enabled and functional with Access Gateway Enterprise Edition.

Test File Type Association Functionality:

1. Create a Word document (if you have enable FTA for Word) and copy it to the Web root of your Web Interface server. The default Web root is <system drive>\inetpub\wwwroot.

2. On the Access Gateway, create a bookmark that points to the Word document (i.e. http://<ip of your Web Interface server/yourWorddocument.doc). Bookmarks are found under the Resources node in the Access Gateway admin console. Enable the option Use Access Gateway as a reverse proxy.

3. Bind the bookmark to your virtual server.

4. Save your configuration.

5. Open a browser and log on to the virtual server.

6. The Homepage should enumerate along with Web Interface published applications in the left frame.

7. The bookmark you created should appear in the center frame.

8. Click on the bookmark and an ICA session should initiate.


Share your comments or find out more about this topic

Citrix Forums

Languages

N/A

| Terms of Use | Privacy | Governance