The Web-to-Host Wizard creates a hierarchical file structure. The site folder is at the top level. It contains one or more launch folders, that contain launch pages, that contain the code necessary to start the BlueZone sessions.
When you start the Web-to-Host Wizard for the first time, there are no configured sites, launch folders, or sessions.
The following steps provide a high-level overview of the Web-to-Host Wizard order of operation.
Create a site.
For example, on a Microsoft IIS web server, if you created a site named MySite, a folder is created in the following location:
C:\inetpub\wwwroot\MySite\
Refer to Sites for more information.
Create a launch folder.
When you create a launch folder, the Wizard creates the launch folder in the site folder. For example, if you create a launch folder named MyLaunchFolder in the MySite site, a folder is created in the following location:
C:\inetpub\wwwroot\MySite\MyLaunchFolder\
When a launch folder is created, the Wizard copies all of the files from the site \template folder to the launch folder.
Refer to Launch folders for more information.
Add sessions.
launch_x.htm
Launch page used for ActiveX browsers, such as Internet Explorer.
launch_jws.htm
Launch page used for browsers that do not support ActiveX, such as Microsoft Edge, Google Chrome, and Mozilla Firefox.
The Wizard uses the values you supplied and converts them to parameters that are written to the launch pages.
In the ActiveX launch page (launch_x.htm) the Wizard modifies the existing object tag, which contains all of the parameters and values necessary to start the emulation sessions that have been configured on this web page.
In the Java Web Start launch page (launch_jws.htm) or the BlueZone Web Start launch page (launch_bws.htm), the Wizard modifies the existing page.json file, which contains all of the parameters and values necessary to start the BlueZone emulation client sessions that are configured in the Wizard.
Refer to Sessions for more information.