Generating the .prowcapc file

When you are ready to store your custom deployment configuration in a new .prowcapc file, you can do so in the following modes:

  • Interactive mode — Starts the generation process from the Deployment Packager main window.
  • Batch mode — If Progress Developer Studio for OpenEdge is installed, you can execute a command-line script that performs the operation without user interaction.

In both cases, the Deployment Packager writes a log of the operation in the output directory where it creates the .prowcapc file. The log file has the same name as the .prowcapc file, but with a .log extension.

Interactive mode

Open the .wcd file and choose Deploy > Generate, or click
on the toolbar. The Deployment Packager validates the configuration, as described in the preceding section.

If there are no errors, the Deployment Packager displays a prompt that lists the changes you have made—that is, differences between the original configuration and the new one—as well as any warnings. At this point, you have the option of continuing or canceling the operation. After reviewing the information, click Yes to generate the new .prowcapc file, or click No to abort the operation.

When you click Yes, the Deployment Packager generates the new .prowcapc file in the specified output directory. The filename matches the value of the Application Name field.

Upon completion, a message identifies the new .prowcapc file (or indicates the errors that prevented successful generation of the file). It also identifies the log file for the operation.

Batch mode

If Progress Developer Studio for OpenEdge is installed, you can use the bprowcappdep.bat script in <OpenEdge-install-dir>\bin to generate the .prowcapc file.

Note: Progress Developer Studio for OpenEdge is not available to users of the standalone Deployment Packager tool extracted from the prowcdp.zip file.

You execute the script passing it the path to the deployment configuration (.wcd) file, for example:

bprowcappdep c:\WebClient\deployment\MyApp.wcd

Unless the validation process encounters errors (in which case the operation terminates), generation of the .prowcapc file proceeds with no option to cancel. Messages that precede the actual start of the generation process, including error notifications and warnings, are written to the console window; they do not appear in the log file. Therefore, when using the bprowcappdep.bat script, you should redirect the screen output to a file or take other steps to make sure you do not overlook important messages.