HTML Page for Authentic Plug-in
The HTML Page for Authentic Plug-in carries out the following important functions:
1.The first time that the HTML Page for Authentic Plug-in is opened on a client, code within the HTML page causes the Authentic Browser plug-in to be downloaded from the server to the client and installed on the client. This code has to be written correctly to identify the correct file on the server. The format of the file that is downloaded (CAB, XPI, or CRX) will depend on the client's browser. The code will also be different because Internet Explorer and Firefox process code differently than each other.
2.Code within the HTML page sets up the Authentic View interface within the browser window, including the dimensions of the Authentic View interface, and the locations of the XML, XSD, and SPS files.
3.It specifies the XML file to edit, as well as the schema file and SPS on which the XML file is based.
4.It contains, within HTML SCRIPT elements, definitions for subroutines and the handling of events. For example, it can be specified what action to carry out when a button in the HTML page is clicked. See Internet Explorer Example 1: Simple and Firefox Example 1: Simple for examples.
|Note:||If you are deploying the Enterprise edition of Authentic Browser, then the HTML page must be installed on the server for which the Enterprise license has been registered.|
Embedding Authentic Browser
To use the Authentic Browser plug-in, an object that identifies the plug-in must be embedded in the HTML page that downloads the plug-in. This is done using the following HTML elements and attributes:
•Internet Explorer: <OBJECT clsid=“clsid:<CLSID>”/>
•Firefox: <embed type=”<MIMEType>”/>
For information on what CLSID and MIME type values to use, see Authentic Browser Versions.
The sub-sections of this section describe how the functions listed above are to be implemented in the HTML page. These sections are organized at the first level by browser-type because of the different ways used to download the Authentic Browser DLL for particular browsers:
•Licensing for Enterprise Edition describes the licensing mechanism for the Enterprise Edition of Authentic Browser
•Internet Explorer describes how to download a CAB file (having a .cab extension) via an HTML OBJECT element.
•Firefox describes how to download an XPI file (extension .xpi) via an HTML EMBED element.
•Independent browsers describes how to determine the browser type making the request and how to then download the correct plug-in version for that browser.
In these sub-sections, you will find descriptions and examples of how the HTML OBJECT , EMBED, and SCRIPT elements are to be used, as well as examples of complete HTML pages that invoke the Authentic Browser plug-in. For information about individual objects, see the respective Object descriptions in the Reference section.