To implement an Authentic Browser project, you will need one server machine, and one or more client machines that are connected to the server.
The Authentic Browser server carries out the following functions:
•The server stores files related to the Altova Authentic XML document that is to be edited. These files are:
1. The XML Schema (XSD) on which the editable XML document is based;
2. The XML document to be edited;
3. The SPS or PXF file that controls the layout and input mechanisms of the XML document in Authentic View.
•The server stores the HTML Page for Authentic Plug-in. This HTML page is the access point for Authentic View editing. It contains instructions to access the XML document, and it serves as a container for the Authentic View window in which the XML document is loaded and edited. To access this page, its URL is typed into client browsers.
•If you are deploying the Enterprise edition of Authentic Browser, then the Enterprise license must be stored on the server. Enterprise licenses are issued for one or more specified servers.
•If on-demand installation of the Authentic Browser plug-in is planned, the server stores the Authentic Browser extension package/s (CAB, XPI, and/or CRX file/s) for the download and installation of the plug-in on client machines. (Otherwise, the plug-in is installed directly in client browsers.)
The steps required to prepare the server are described in the section, Server Setup.
An XML document can be viewed and edited in Altova's Authentic View if the XML document has an SPS or PXF file assigned to it. Authentic View editing is carried out on client machines, which must be set up as follows:
•Each client must have one of the following browsers installed: Internet Explorer 5.5 or higher (32-bit and 64-bit), Firefox (32-bit)
•Additionally, each client machine must have Internet Explorer 5.5 or higher installed on it. This is because the Authentic View interface (which will be displayed within the browser window) is generated using Internet Explorer.
•Unless on-demand installation has been planned, the Authentic Browser plug-in must be directly installed on client browsers.
The steps required to prepare clients are described in the section, Client Setup.
After the server and clients have been prepared as described above, the user enters the URL of the HTML page for Authentic Plug-in in the client browser. If the plug-in has not already been installed in the client browser, the HTML page can contain instructions to perform an on-demand installation of the plug-in in the client browser.
Once the plug-in is installed on the client, code in the HTML page causes an Authentic View editing window to open within the browser window. The XML document to be edited is loaded into the Authentic View window from the server and the user can start editing it and saving changes directly to the XML document.