Try OpenEdge Now
skip to main content
WebClient Applications
Deploying the Sample Application with IntelliStream : Setting up the application on the AppServer machine

Setting up the application on the AppServer machine

This section provides information about applications on AppServer machines.
Note: This example assumes that the AppServer machine is the same as the development machine on which you prepare the front-end and back-end application code. For this reason, this machine must be a Windows machine.
To set up the application on the AppServer machine:
1. Verify that an OpenEdgedevelopment product is installed on the AppServer machine. The person doing the installation, when presented with the Setup Type window, must choose the complete installation, as opposed to the typical installation or the custom installation.
2. Verify that an AppServer was installed and configured on the AppServer machine.
3. Create the WebClient application root directory, the symbol for which is %APPROOTDIR%. The application root directory can reside anywhere, but note its path.
4. Recursively copy the source-code files of the Sports2000 application from the %DOCS%\src\sports2000\gui directory to %ASWORKDIR%.
Note: The gui directory contains both back-end and front-end application files. %ASWORKDIR% is where the entire application is compiled, though only the back-end r-code (.r) files are run from this directory.
5. Create a copy of the Sports2000 database on the AppServer machine. The copy can reside anywhere, but be sure to note its path.
6. Start an OpenEdge session and do the following:
a. Connect to the Sports2000 database, entering its path, which you noted in Step 5.
b. Use the PROPATH Editor to add the AppServer work directory to the PROPATH.
c. In the Application Compiler, go to Options > Compiler, change Minimize R-code size to YES, change Generate MD-5 to YES, and click OK. In the main window, click Modify. In the File Specification window, enter the AppServer's working directory, click OK, and compile the application.
7. Recursively copy the directories in the following table as specified, creating the destination subdirectory as necessary:
Recursively copy directory . . .
To location . . .
8. Copy the files in the following table as specified, creating the destination subdirectory as necessary:
Copy file . . .
To location . . .
9. Use a text editor to modify the appsrvtt.d file, which you copied in the previous step , as follows:
a. In appsrvtt.d, search for the following string:
b. In the string, change yourservername to the domain name of the Web server running the AIA. For example, if the domain name of the Web server running the AIA is http://testhost, modify the string to appear as follows:
c. Save appsrvtt.d.
10. Use the WebClient Application Assembler as follows:
a. From the main menu, select File > Open , and open %APPROOTDIR%\sportspro.wcp.
b. On the General tab, change the path of the application root directory to its actual path on the AppServer machine. The default value is d:\demo91c\sportspro.
c. On the same tab, click on the Locator button. The Configuration File Locator Definition window appears. In this window, change the URL to the host name of the server hosting the configuration file, which defaults to http://yourhostname.
d. In the Codebase Locator Definition window (main menu Deployment > Locators > Codebase), change the URL to the host name of the server hosting the codebase, which defaults to http://yourhostname.
e. On the Options tab, check the System Tasks toggle box and click System Tasks Definition. The System Tasks Definition window appears.
On the Shortcut tab, check the Application Shortcut toggle box and click the ellipsis (...) button next to the Icon field. The Open window appears.
Manipulate the Open window to select the progress.ico file, which you copied to %APPROOTDIR% in the previous step.
On the Files tab, select the file d:\demo91c\sportspro\csspin32.ocx and click Remove. Then, add the file %APPROOTDIR\csspin32.ocx. Finally, confirm the Application Specific toggle box is checked.
f. Save sportspro.wcp.
g. In the Generate window (main menu Deployment > Generate), then choose Regenerate Latest Version. In the Output Directory field, enter the name of the directory where you want the generated files to be placed; that is, the value of %OUTDIR%. Finally, click OK.
The WebClient Application Assembler creates the application configuration file and the cabinet files and places them into the output directory you specified.
11. Use OpenEdge Management or OpenEdge Explorer, or the proserve command to start a database server for the sports2000 database running on the AppServer machine. For example, if the sportspro2000 database resides at %APPROOTDIR%\databases, use a command like the following:
%DLC%\bin\proserve %APPROOTDIR%\databases\sports20000.db
12. Use OpenEdge Management or OpenEdge 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 (%ASWORKDIR%), and add the service name sports2000partition to the Appservice Name list.
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 %ASWORKDIR%\databases, enter the following string:
-db %ASWORKDIR%\databases\sports2000
13. Use OpenEdge Management or OpenEdge Explorer, or the asbman command to start the asbroker1 AppServer instance. For example (using the asbman command):
%DLC%\bin\asbman -name asbroker1 -start