Try OpenEdge Now
skip to main content
WebClient Applications
Deploying an Application : Customizing deployment configurations : Defining a custom deployment configuration

Defining a custom deployment configuration

Before running the WebClient Deployment Packager, determine the correct values for your custom deployment configuration, and make sure that the source .prowcapc file is accessible.
To run the WebClient Deployment Packager:
1. Choose WebClient Deployment Packager from the PRO*Tools palette; or execute the following command from either <OpenEdge-install-dir>\bin, or the directory where you unzipped
prowcappmgr.exe -deploy
The WebClient Deployment Packager window appears:
2. Create a new custom deployment configuration, or open an existing one.
3. You can save the deployment configuration to a .wcd file at any time. If the configuration has not been saved previously, you see a standard Save As dialog that enables you to name the file with a .wcd extension and to specify its location.
4. Most of the Deployment Packager fields get their initial values from the source .prowcapc file. Enter new values as appropriate for the custom deployment configuration. See the Defining applications in WebClient Application Assembler and the online help for more information.
Your .prowcapc file and your application .CAB files must be either both signed or both unsigned. The application will not run if there is a mismatch. Therefore, you must be sure that the security setting for your new .prowcapc file matches that of the .CAB files. The value that you specify in the Current security field applies only to the new .prowcapc file; it does not affect the .CAB files. The value (Signed or Unsigned) that the Deployment Packager shows for the Original.prowcapc file typically reflects the status of the .CAB files, as well as that of the source .prowcapc file, so you should usually match that setting. If the security settings do not match when you validate or generate the new configuration, a warning is displayed.
5. After defining the custom deployment configuration, save your changes and generate the new .prowcapc file, as explained in the Generating the .prowcapc file. Optionally, you can validate the configuration in a separate operation before generating the new file. (Before executing a Generate operation, the Deployment Packager automatically performs the same validation.)
* Security considerations