Kbase P178609: What changes are allowed through the WebClient Deployment Packager?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/12/2010 |
|
Status: Unverified
GOAL:
What changes are allowed through the WebClient Deployment Packager?
GOAL:
What changes can be made to the WebClient deployment using the .wcd file (WebClient Deployment Packager)?
FIX:
You can change the following elements of the application definition in the WebClient Deployment Packager:
1 Application name.
2 WebClient install URL.
3 Configuration file URL and associated security information.
4 Codebase URL and associated security information.
5 Digital signature information for the .prowcapc file.
6 URLs for Web-enabled external install and upgrade programs.
You cannot use the Deployment Packager to modify the content of the application itself.
1. Prowcapc File ? This field initially shows the path to the source .prowcapc file
from which the deployment information was extracted, and it is a read-only field
until you save the deployment configuration to a .wcd file. Unless the file is removed
from that location before you generate your new .prowcapc file, there is no need to
change this field. However, the file must be available at the specified location when
you generate the new .prowcapc file, so that the Deployment Packager can make a
copy of it as the target for your changes. If the original source file is moved, change
the path in this field to the new location. Click the ellipsis (...) button for a standard
file browser.
2. Output Directory ? Enter the directory path where you want the new .prowcapc
file to be generated. Click the ellipsis (...) button for a standard file browser.
3. Application Name ? The initial value is from the source file (that is, the value
entered in the Application field on the Application Assemblers' General tab, and
matched by the file name of the .prowcapc file). The Deployment Packager uses the
value of this field as the name of the new .prowcapc file that it creates in the
specified output directory. You can change the name if you wish; if you do, the
Deployment Packager will warn you when you validate or generate the new
configuration that the name does not match the original.
4. Startup Parameters ? The application startup parameters specified on the
Application Assembler?s General tab appear as the initial value. You can change
them as appropriate.
5. WebClient Install URL ? This field identifies the Internet location from which
WebClient can be downloaded. The WebClient Initializer goes to this location when
attempting to upgrade the WebClient version. The initial value is the URL entered
on the WebClient tab of the Application Assembler.
6. Configuration File URL? This field identifies the location where the WebClient
Initializer looks for the .prowcapc file. The initial value is the URL entered on the
General tab of the Application Assembler. To change this value and the associated
connection and authentication options, click the Locator button to open the
Configuration File Locator Definition dialog box.
7. Codebase URL? This field identifies either an Internet server or an AppServer that
hosts your application code (.CAB) files. The initial value is the URL entered on the
Component tab of the Application Assembler. To change this value and the
associated authentication options, click the Locator button to open the Codebase
Locator Definition dialog box.
Web-enabled External Installer ? The Install URL and Upgrade Install URL
fields identify the Internet locations of programs for installing and upgrading the
application. The initial values are those entered on the Options tab of the Application
Assembler. You can enter new values if appropriate.
After defining the custom deployment configuration, save your changes and generate the new
.prowcapc file in either interactive or batch mode:
Interactive mode
Open the .wcd file and choose Generate or click the button on the toolbar.
If there are no errors, the Deployment Packager displays a prompt that lis.ts the changes you
have made, and gives you 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 name of this file 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 you have installed OpenEdge Studio, you can use the bprowcappdep.bat script to generate
the .prowcapc file without running the Deployment Packager interactively. This file is installed
in OpenEdge-Install-Directory\bin. (It is not available to users of the standalone
Deployment Packager tool extracted from the prowcdp.zip file.)
You execute the script with a single argument, the path to the deployment configuration (.wcd)
file. For example:
The validation and generation are performed as in interactive mode, with an important
exception: 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.