Managing the Microsoft ActivSync application in IAG SP2

Applies To: Intelligent Application Gateway (IAG)

Application-Specific Settings

In order to enable access to Microsoft ActiveSync on handheld devices from Whale Communications Intelligent Application Gateway (IAG) 2007, configure a Webmail trunk, and in the Webmail Application page of the reate New Trunk wizard, select the application Microsoft ActiveSync. When creating the trunk, note the following:

  • Since ActiveSync uses basic authentication only, it is highly recommended that you define the Microsoft ActiveSync trunk as an HTTPS trunk. If you use an HTTP trunk, users credentials will not be secured.

  • In the Authentication and Application Login pages of the Create New Trunk Wizard, the authentication server you select must be the authentication server that is used by the Exchange server, that is, the domain that is defined in ActiveSync on the handheld device.

  • Most default trunk settings should not be changed. The settings you can optionally change include:

    • Is SSL option, relevant for HTTPS trunks. This option is activated either in the Application Server page of the Create New Trunk Wizard, or in the Application Server area of the IAG Configuration console.

    • Permitted Authentication Attempts and Block Period authentication-related parameters.

    • Custom hooks.

Activating custom hooks

There are two hooks that you can use with the ActiveSync trunk, to be run at different stages of the Login process, as follows:

  • At the beginning of the login process. This hook can be used, for example, to override original request parameters.

  • At the end of the login process. This hook can be used, for example, to analyze the authentication results.

To activate a custom hook

  1. On the IAG server access the following folder: …\Whale-Com\e-Gap\Von\InternalSite\inc\CustomUpdate. If it does not exist, create it.

  2. Create a file containing the required script, as follows:

    For a hook to be run at the beginning of the login process, create

    a file named: <Trunk_Name><Secure(0=no/1=yes)>ActiveSyncLoginStart.inc

    For example: for an HTTPS trunk named “Handheld”, name the

    file Handheld1ActiveSyncLoginStart.inc

    For a hook to be run at the end of the login process, create a file

    named: <Trunk_Name><Secure(0=no/1=yes)>ActiveSyncLoginEnd.inc

  3. In the IAG Configuration console, activate the configuration.

    The action you defined in the hook will be run when end-users access the Microsoft ActiveSync application.