Progress
on the Web
IntelliStream
When you use IntelliStream, the WebClient Application Assembler generates all the deployment files necessary to install and run your application. In addition, when you make changes to your application, use the WebClient Application Assembler to easily generate the files you need to update your application.
You take advantage of the IntelliStream features by defining application components. To define a component, your compiled application code must be available to your development machine. In addition, you must package the compiled application code to reflect how you want to deploy the application. For example, you must add your
.r
code to the.pl
files you want, and all the files must reside in the same directory structure that you intend to use on your end users machine. Therefore, you must be able to access these files using the WebClient Application Assembler’s Add Files to Component dialog box. For more information about developing your application and compiling your code, see Developing the Application."Application Components
Components are essential to taking advantage of the IntelliStream feature. Components are collections of one or more files grouped together based on related functionality and are put into a compressed
.CAB
file for deployment. Components are used to deliver the application files and should meet the following requirements:
- Code organized into a component should be functionally related because the component is automatically installed as a unit to an end user’s machine. Components can be installed as follows:
- You can have only one At Startup
component. The At Startup component is downloaded before the application runs the first time. This is usually the main code used to start the application and code needed by all users. You identify this unique component by choosing the At Startup option when you define the component in the WebClient Application Assembler’s Component Definition dialog box.
- Components should be self contained so that all procedures that call each other are together. If you have a procedure that is called from many parts of your application, you might want to include this procedure in the At Startup component so it is available to all other components.
For more information about components, see, the "Running the WebClient Application Assembler" section, the WebClient Application Assembler help, "Designing the Application," and "Developing the Application".
System Tasks
System files, such as
.dll
files, or application-specific files that require special processing, such as updates to the registry, must be defined as System Tasks using the Options tab in the WebClient Application Assembler. Files specified using the Options tab, are automatically added to the At Startup component.Progress 4GL Install Procedure
You can augment the IntelliStream install capabilities with a 4GL install procedure. This procedure is specified using the Options tab in the WebClient Application Assembler. This procedure and any code that it requires must be put in the At Startup component. WebClient runs this procedure at the end of its installation tasks. If you use a 4GL install procedure, you can also provide an 4GL install uninstall procedure that runs at the end of the uninstall tasks. For more information about using Progress 4GL installers, see the "Options Tab" section.
Uninstall
IntelliStream includes an uninstaller that removes your application and its registry entries from your end user’s machine.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |