
Deploying the Sample Application Without IntelliStream
This appendix tells you how to deploy the Progress sample application, SportsPro, with WebClient without IntelliStream. 
NOTE:	There is no difference between the SportsPro application in the current version of Progress and the Sports2000 application in previous versions.
These instructions use the following symbols:
	%DLC% represents the Progress installation directory on a particular machine. For example, the instructions might mention %DLC% on the end-user machine.
	%DOCS% represents the Documentation installation directory on a particular machine. This might or might not be the same as %DLC%.
	%ASWORKDIR% represents a Progress AppServers work directory.
	%MYWEBSERVER% represents your Web servers domain name or IP address.
These instructions cover:
1.	Preparing the Web server
2.	Setting up the application on the AppServer machine 
3.	Setting up the application on the Web server machine 
4.	Installing and running the application on the client machine 
B.1		Preparing the Web Server
Preparing the Web server involves:
	Setting up the Java Servlet Engine and the AppServer Internet Adapter
	Setting up MIME types for the application configuration file
B.1.1	Setting Up the Java Servlet Engine and the AppServer Internet Adapter
For instructions on setting up the Java Servlet Engine (JSE) and the AppServer Internet Adapter (AIA) on the Web server, see the chapter on configuration and managing the AppServer Internet Adapter in OpenEdge Application Server: Administration and the Progress Knowledge Center entries on setting up the JSE to work with the AIA. To access these, search the Knowledge Center on JSE and AIA.
B.1.2	Setting Up MIME Types for the Application
Configuration File
On the Web server, set up MIME types for the application configuration file. The technique for doing so depends on your particular Web server. For information on setting up MIME types for a particular Web server, see the Configuring MIME Types for Your Web Server section of Chapter 7, Deploying an Application, in OpenEdge Deployment: WebClient Applications. Also, see the documentation for your Web server.

B.2	Setting Up the Application on the AppServer Machine 
Follow these steps to set up the application on the AppServer machine: 
1 	Verify that a Progress development product has been installed on the AppServer machine and that the person doing the installation, when presented with the Setup Type window, chose the complete installation, as opposed to the typical installation or the
custom installation.
2 	Recursively copy the back-end files of the Sports2000 application from the %DOCS%\src\sports2000\gui directory to the AppServer work directory.
NOTE:	The gui directory contains both back-end and front-end application files.
3 	Create a copy of the sports2000 database on the AppServer machine. The copy can reside anywhere, but note its full path  for example:
d:\wrk91b\sports2000.db
4 	Start a database server for the sports2000 database running on the AppServer machine. Use the Progress Explorer or a proserve command similar to the following:
%DLC%\bin\proserve d:\wrk91b\sports2000.db

5 	Compile the sports2000 back-end application files you copied to the AppServer working directory in Step 2, as follows:
a)	Start a Progress session.
b)	Connect to the sports2000 database.
c)	Use the PRO*Tools PROPATH tool to add the AppServer working directory to the PROPATH.
d)	Start the Application Compiler, select Options Compiler, (optionally) set Minimize R-code Size to Yes, and click OK.
e)	In the Application Compilers main window, click Modify, enter the path of the AppServer working directory, click OK, and compile the application.
6 	Use the Progress Explorer to configure the default asbroker1 AppServer instance, as follows:
a)	In the General Options for Broker tab: 
Change the broker working directory to the AppServer work directory.
In the Appservice Name list, add the service name sports2000partition.
b)	In the General Options for Server tab:
Add the database connection parameter to Server Startup Parameters. For example, if the Sports2000 database resides at d:\wrk91b, add the following parameter:
-db d:\wrk91b\sports2000 
7 	Use the Progress Explorer to configure and start the controlling NameServer instance for the asbroker1 AppServer.
8 	Use the Progress Explorer or the asbman command to start the asbroker1 AppServer instance. For example (using the asbman command):
%DLC%\bin\asbman -name asbroker1 -start

B.3	Setting Up the Application on the Web Server Machine
Follow these steps to set up the application to launch from your Web server machine:
1 	Recursively copy all files from %DOCS%\webinstall\sports2000\web_image directory to the sports2000 subdirectory of the Web server document root directory.
2 	Copy all files from %DLC%\webinstall\webclient\web_image directory to the Web server document root directorys webclient subdirectory.
3 	In the Web server document root directorys Webclient subdirectory, edit the webclient.htm file to automatically install the application automatically just after installing WebClient. To do this:
a)	Uncomment the lines that invoke the One-Click application install directly. (Keep commented the lines that invoke the WebClient initializer.)
b)	Change <URL to your One-Click application installer directory> to http://%MYWEBSERVER%/sports2000. 
c)	Change <URL to your .prowcapc file> to http://%MYWEBSERVER%/sports2000/sports2000.prowcapc. 
For example:
ether.SetProperty(ApplicationURL, http://pctest/sports2000);
ether.SetProperty(ProwcappURL, http://pctest/sports2000/sports2000.prowcapc);
These changes let you install WebClient and the Sports2000 application on the client machine.
4 	In the Web server document root directorys sports2000 subdirectory, make the following changes:
a)	Edit the bootstrap.htm file, replacing the document.location.href and window.location URLs to match the location of your configuration and webclient.htm files, respectively.
For example:
document.location.href = "http://pctest/sports2000/sports2000.prowcapc";
window.location = "http://pctest/webclient/webclient.htm";
b)	Edit the sports2000.htm file, uncommenting the line containing the prowcapc entry, and including the domain name or IP address of your Web server and the name of your application configuration file.
For example:
ether.SetProperty("ProwcappURL",
"http://pctest/sports2000/sports2000.prowcapc");
5 	Use the WebClient Application Assembler PRO*Tool to generate a customized sports2000.prowcapp file. To do this:
a)	Copy %DOCS%\webinstall\sports2000\sports2000.wcp to any directory.
b)	Open the file with the Application Assembler. 
c)	Modify the following URLS: the URL of your configuration file specified in the Configuration File Locator Window, the URL of the WebClient install on the WebClient tab, and the URL for your application install specified on the Options tab.
d)	From the Application Assemblers main menu, choose Deployment Generate. Enter an output directory and a version name (for example, v1) and click OK to generate a new configuration file.
e)	Copy the configuration file to the Web server document root directorys sports2000 subdirectory.
6 	Configure (if not already configured) and start an instance of the AppServer Internet Adapter to run as a Java servlet in the Java Servlet Engine and to access the AppServer served by asbroker1. 
For instructions on setting up the Java Servlet Engine (JSE) and the AppServer Internet Adapter (AIA) on the Web server, see the chapter on configuration and managing the AppServer Internet Adapter in the OpenEdge Application Server: Administration and the Progress Knowledge Center entries on setting up the JSE to work with the AIA. To access these, search the Knowledge Center on JSE and AIA.
B.4	Installing and Running the Application on the Client Machine 
Follow these steps to install and launch the application on the client machine: 
NOTE:	Normally Step 1 would not be necessary. But since it was impossible to predict the name of your server, the appservtt.d file, which contains the connection URL and which is included in the installation materials, has been set to YourServername.
1 	Edit the hosts (winnt\system32\drivers\etc\hosts) file on the client machine to add an entry containing the IP address and host name of your server. The entry might appear as follows:
173.16.114.111	     YourServername      
2 	Open a Web browser (Internet Explorer or Netscape Version 4 or newer) and go to one of the following URLs:
http://%MYWEBSERVER%/sports2000/bootstrap.htm
or
http://%MYWEBSERVER/sports2000/sports2000.prowcapc
For example:
http://pctest/sports2000/bootstrap.htm.
3 	Install WebClient and the Sports2000 application by following the instructions and accepting the defaults.
NOTE:	The sample applications SmartB2B and SonicMQ buttons invoke options not yet implemented.

