Kbase 19198: V8.2 Client Packaging
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  14/10/1999 |
|
V8.2 Client Packaging
PC Platforms
Version 8.2 of Progress provides 32-bit executables for both gui and
character mode for 32-bit Windows platforms (Win95 and WinNT).
PRODUCT | DB | COMPILE | LOAD | InterFace
| Conn | | df d |
==============+======+=========+========+==========
ProVision | L/R | Y | Y Y | GUI*
4GL | L/R | Y | Y Y | GUI*
Personal DB | L | -rx |-rx N | GUI*
Cl. Networking| R | -rx |-rx N | GUI*
Char. Client | (1) | LIC | LIC | CHAR
Query/RESULTS | (2) | (3) |-rx N | GUI*
Report Builder| (2) | (4) |N/A N/A| GUI
L Local
R Remote
* These licenses can also have a character mode interface by adding
the Win32 Character Client. In 8.2, character mode is ordered as
a separate piece. There's no extra charge for character mode --
we just want to be able to track how many customers want it.
(1) Must be combined with a development or deployment license for
connectivity
(2) Must purchase Client Networking or Personal DB for connectivity
(3) Only procedures that don't update DB
(4) Can compile RB reports
-rx Compiles only encrypted code with -rx startup parameter or loads
df with -rx startup parameter
LIC The answer depends on the license it's combined with. Yes, if
combined with a development license No, if combined with a
deployment license
Development -vs- Deployment Licenses:
=====================================
ProVision and the 4GL license are referred to as development licenses
because you can develop applications with them. The 4GL license just
provides the Procedure Editor for doing development work. The
ProVision license also provides the Procedure Editor, but it includes
other tools to help with development such as the UIB, the debugger and
the reporting tools.
Client Networking and Personal DB are referred to as deployment
licenses.
Notes on DB Connections
=======================
Local means connecting to a database in single-user mode. This type
of license is sometimes referred to as stand-alone.
Remote means connecting to a database that has had a server started in
multi-user mode.
Results and Report Builder can be purchased as separate licenses, but
they are also included in the Provision package. When they're part of
ProVision, they can make either local or remote connections to a
database.
When purchased as separate licenses, they must be purchased and
installed with a deployment license (either Client Networking or
Personal DB) in order to be able to connect to a database. If a
customer wants a Query/Results license to be able to access both local
and remote data, they would need three components: Query/Results,
Client Networking and Personal Database. The same is true for Report
Builder.
Local Server
------------
· Development licenses come with the ability to start a local server
(using the executable _mprosrv.exe) which will allow multiple local
sessions to connect to a database. Only sessions running on the PC
where _mprosrv.exe is running can connect to the db.
· Note: In previous releases, local servers were started with a
special executable (wproserv.exe) and used a special protocol (-N
wipc). In 8.2 we replace wproserv.exe with the standard server
executable _mprosrv.exe. No protocol should be specified when you're
starting a local server in 8.2.
· The idea behind this is to give developers the ability to test
multi-user applications on a stand-alone PC. (This is sometimes
referred to as "beach" development-- a developer can take her laptop
to the beach and still write/test a multi-user application.) There is
information on this in the System Administration Guide.
Notes on Compiling Issues
=========================
Client Networking and Personal Database are sometimes referred to as
"runtime" licenses. (In Version 6 of Progress there was a license
type called Runtime.) They are deployment licenses that get sold as
ways to provide the Progress "engine" the ability to run precompiled
applications. However, they can compile encrypted source code. A
special startup parameter is needed to turn on the ability to compile
encrypted source code: -rx. This is the parameter that also enables
the option in the Data Dictionary that lets you load .df (data
definition) files.
On the development side, an additional Progress product is required
for encrypting source code. It's called Developers Toolkit. It is
not part of the Provision License. See the Product Configuration
Guide for a description of Developers Toolkit. See Kbase number 14068
(QBW: encrypt) for some important information on how to deploy
encrypted source code.
The two runtime licenses (Client Networking and Personal DB) include
the Report Engine, so that they can run programs that use reports
developed with Report Builder.
Kbase number 16291 has useful information about errors customers might
see with respect to their compile capabilities.
Packaging Issues That are Important When Installing
===================================================
The media we ship (the CD-ROM) contains all the files needed for any
of the licenses for a particular version of Progress. (This was not
true in Version 6.) The serial number and control codes entered
dictate what the license type is and what files get installed for the
license. This fact can come in handy if a customer forgets to order
something (for example, they ordered only Query/Results and they need
to get Client Networking too). They just need to get a serial number
and control codes for the piece they are missing. They do not need to
be shipped new media. However, there will be charges for purchasing
an additional license-- Sales Administration handles those details.
Tech Support cannot place an order for an additional license. There
won't be an additional charge if they want to add the Win32 Character
client to what they have, but Sales Admin will still need to place the
order.
When query/results is ordered with client networking, those two
products need to be installed together. In order for products to work
together, they need to be listed in the same progress.cfg file. The
way to achieve that is by installing them together. The same sort of
thing holds true for Report Builder and the Win32 character client.
In 8.2, the user is forced by the install program to put everything
that is the same version in the same directory.
Checking on What License(s) a Customer Has
==========================================
The serial numbers, names of the products and other useful information
about licenses that a customer has installed are stored in a file
called progress.cfg that is put by default in the DLC directory.
There is also an executable called showcfg.exe in the DLC\bin
directory that will display the contents of progress.cfg.
In Version 8.2, the showcfg command is a windows command and there is
an icon in the Progress Program group and also an icon in the
PRO*Tools menu bar that will execute the showcfg command. The icon in
the Progress Group is labeled Progress Config. Both icons have a
large blue lower case i. There is also a DOS version of the showcfg
command if you want to run from the DOS prompt. The executable name
for that is showcfgd.exe.
Kbase number 16249 has information on errors customers might see if
they don't have the correct product for what they're trying to do.
VZA (Oct 06 1999)