Status: Verified
GOAL:
How to Use Progress 9.1x WebClient Across a LAN with No Web Server
GOAL:
How to use WebClient with No Web Server
GOAL:
How to setup Webclient using a File Server
GOAL:
How to setup Webclient using an Intranet
GOAL:
How to setup WebClient to run from a local drive
FACT(s) (Environment):
Progress 9.1x
FIX:
To change an existing Webclient application to deploy across a LAN the following must be changed:
1. Generate a new version of the Webclient containing File references instead of URL references.
2. Modify the Appservtt.d file
3. Obtain the intranet folder from the Progress Installation CD.
4. Modify the bootstrap.htm file
5. Modify the webclient.htm file
1. Open the WebClient project file (.wcp file) in the WebClient Application Assembler and make the following changes:
a. Under the General tab change the Configuration File URL: to point to the location of where the prowcapc file will reside on the File Server.
Do not include the filename. This directory structure does not need to exist at the time of the generation. In the below example H: is the mapped drive that the clients will access.
Example: Configuration File URL: file://H:\Deploy\
b. Under the Component tab change the Codebase URL to the directory location of the .cab files on the File Server.
This is the file location of where the *.cab files will reside on the file Server. This directory structure does not need to exist at the time of the generation. In the below example H: is the mapped drive that the clients will access.
Example: Codebase URL: file://H:\Deploy\
c. Under the WebClient tab change the WebClient Install URL:
Example: WebClient Install URL: H:\Deploy\
d. Generate a New Version of the WebClient Application to obtain a updated *.prowcapc file.
The PATHs specified in each of the text boxes must be accessible from the end-user machine.
2. Modify the appsrvtt.d created in the Output directory of the Generated application.
In the appsrvtt.d file make the following modifications:
Change: "http://yourservername/aia/Aia?AppService=sports2000partition" to ""
3. Obtain the intranet folder from the Progress Installation CD. The Progress installation CD provides the WebClient image files for an Intranet deployment under WebInstall\WebClient\Intranet. This is the image that is used to perform Intranet installations
a. Copy the files contained in the Intranet folder to the file server that will host the installation. The drive where the files reside must be a mapped drive. The URL will reference the mapped drive (FILE://M/directory path)
4. Modify the bootstrap.htm file on the File Server to point the URL location to your *.prowcapc and Webclient.htm file using using directory pathing.
For example the bootstrap.htm document.location.href tag is directed to the *.prowcapc file located on the File server. The window.location tag points to the webclient.htm file located on the file server:
//. Reference a prowcapp file to invoke prowcini.exe
// NOTE: MODIFY THIS URL TO POINT TO YOUR .prowcapc FILE.
document.location.href = "H:/Deploy/sportspro.prowcapc";
}
else
{
// Start install process for Web Client
// NOTE: MODIFY THIS URL TO POINT TO THE WebClient Install page
window.location = "H:/Deploy/webclient.htm";
5. Make the following modifications to the webclient.htm located on the File Server to ensure the install is done as a File Server install.
a. Under the function StartInstall () { uncomment out the following line:
ether.SetProperty("ProwcappURL", "<URL to your .prowcapc file>")
b. Change the ProwcappURL to point to the *.prowcapc file located on the file server. For Example:
// ether.SetProperty("ProwcappURL", "H:/Deploy/sportspro.prowcapc")
At the bottom of the webclient.htm file make the following changes:
c. Comment out the OBJECTID line that is used for an InterNET install by adding backslashes "//" to the beginning of the line, For Example:
<!-- THE OBJECT TAG BELOW IS FOR USE WITH THE INTERNET -->
//<OBJECT ID="playerIE" align=baseline height=1 width=1 classid="CLSID:90C9629E-CD32-11D3-BBFB-00105A1F0D68" codeBase="http://www.installengine.com/engine/isetup.cab#Version=6,30,100,1255" ></OBJECT>
d. UnComment the OBJECTID line that is used for INTRANET installs by removing the <! -- --> surronding the OBJECT ID, For Example:
<!-- TO DO: *** THE OBJECT TAG BELOW IS FOR USE WITH AN INTRANET -->
<OBJECT ID="playerIE" align=baseline height=1 width=1 classid="CLSID:90C9629E-CD32-11D3-BBFB-00105A1F0D68" codeBase="isetup.cab#Version=6,30,100,1255" ></OBJECT>
e. Uncomment the Applet code at the end of the page for Applet for use with the Intranet, For Example remove the <!-- --> from the <SCRIPT language=JavaScript> tag:
<SCRIPT language=JavaScript>
if (chkBrowser()=='nav406up')
// THIS APPLET CODE IS FOR USE WITH THE INTERNET
//document.write('<APPLET CODE="iSetupApplet.class" NAME="SetupPlayer" ARCHIVE="isapplet.jar" CODEBASE="http://www.installengine.com/applet"> <PARAM Name="iSetupVer" Value="6,30,100,1255"></APPLET>');
// THIS APPLET CODE IS FOR USE WITH AN INTRANET
document.write('<APPLET CODE="iSetupApplet.class" NAME="SetupPlayer" ARCHIVE="isapplet.jar" CODEBASE="."> <PARAM Name="iSetupVer" Value="6,30,100,1255"></APPLET>');
//-->
// THIS APPLET CODE IS FOR USE WITH AN INTRANET
document.write('<APPLET CODE="iSetupApplet.class" NAME="SetupPlayer" ARCHIVE="isapplet.jar" CODEBASE="."> <PARAM Name="iSetupVer" Value="6,30,100,1255".></APPLET>');
.