Preparing to deploy IAG client components online
Applies To: Intelligent Application Gateway (IAG)
Whale Communications Intelligent Application Gateway (IAG) 2007 client endpoint components are installed on client endpoints using online installation mode if component installation is enabled on the trunk for the site to which the client endpoints connect. Component installation is enabled when the setting Disable Component Installation and Activation is not checked in the Session tab of the trunk properties. For more information, see Managing client endpoints during an IAG session.
Online installation mode is suitable for end-users who have ActiveX download rights in Windows Internet Explorer and are logged in with power-user or administrator privileges. In this mode, as soon as users try to access the site, before logging in, IAG downloads the Whale Component Manager onto their endpoints. Once the Component Manager is installed on the client endpoint, it determines the need for the installation of the rest of the components each time the user accesses the site, and it installs them as follows:
By default, the following components are installed automatically:
Attachment Wiper
Client Trace utility
Endpoint Detection
If required, you can configure other components that will be installed automatically.
The rest of the components are installed as required. For example: when the user accesses a non-Web application for the first time, the Component Manager installs the SSL Wrapper component.
Modifying the list of automatically installed components
Add components to the default list of components that Component Manager installs automatically on the endpoint computer as follows:
To add components to the list of automatically installed components
On the IAG server, access the following custom folder:
…\Whale-Com\e-Gap\von\InternalSite\inc\CustomUpdate
If this folder does not exist, create it.
Under the folder you accessed in step 1, do one of the following:
If you want the changes that you make to affect all trunks, create the following file
InstallXml.inc
If you want the changes that you make to be applied to a specific trunk, create the following file:
<
Trunk_Name><Secure(0=no/1=yes)>InstallXml.inc
For example: for an HTTPS trunk named “MyTrunk”, create the file
mytrunk1InstallXml.inc
If such a file already exists, use the existing file.
Copy the following lines into the file you created in step 2:
<%
Response.write "<Component Name=""SSL Wrapper"" ID=""1"" Install=""1"" />"
Response.write "<Component Name=""Network Connector"" ID=""17""
Install=""1"" />"
if uninstall_lln = "0" and remove_lln = "0" then
Response.write "<Component Name=""Socket Forwarding"" ID=""8""
Install=""1"" />"
Response.write "<Component Name=""Socket Forwarding activation: Basic""
ID=""33"" Install=""1"" />"
Response.write "<Component Name=""Socket Forwarding activation: Extended""
ID=""65"" Install=""1"" />"
Response.write "<Component Name=""Socket Forwarding activation: VPN""
ID=""129"" Install=""1"" />"
end if
%>
Comment out the lines that are not applicable by adding ' at the beginning of the line, where:
The following line adds the SSL Wrapper component to the list of automatically installed components:
Response.write "<Component Name=""SSL Wrapper"" ID=""1""
Install=""1"" />"
The following line adds the Network Connector component to the list:
Response.write "<Component Name=""Network Connector""
ID=""17"" Install=""1"" />"
The following line adds the Socket Forwarding component to the list:
Response.write "<Component Name=""Socket Forwarding"" ID=""8"" Install=""1"" />"
In addition, the following lines enable the Socket Forwarding activation mode:
Basic mode:
Response.write "<Component Name=""Socket Forwarding
activation: Basic"" ID=""33"" Install=""1"" />"
Extended mode:
Response.write "<Component Name=""Socket Forwarding
activation: Extended"" ID=""65"" Install=""1"" />"
VPN mode:
Response.write "<Component Name=""Socket Forwarding
activation: VPN"" ID=""129"" Install=""1"" />"
Make sure the required Socket Forwarding Activation mode is enabled; if the component is used by multiple applications, in various Activation modes, make sure all the applicable modes are enabled.
When users next access the site, the automatic component installation includes the additional components you defined here.