Kbase 4907: How to Deploy a Fast Track Database and Application
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
How to Deploy a Fast Track Database and Application
910628-cmb01
INTRODUCTION:
=============
This Product Services Technical Support Knowledgebase entry
describes the steps to deploy a FAST TRACK database.
WHY YOU NEED TO DO THIS:
========================
You need to consider the FAST TRACK deployment options when
you make your application (PROGRESS and FAST TRACK) available
to your customers.
PROCEDURAL APPROACH:
====================
1. End-User Platform
When you deploy an application, be aware of differences
between the source and target operating systems. This is
an especially important consideration when naming files. For
example, DOS uses filenames with a maximum of eight character
(with a three character extension), while UNIX and VMS
allow much longer filenames.
Before you can run an application on an end-user platform,
you must compile the application code on a platform that
has the same operating system and hardware.
2. PROGRESS Product Considerations
To compile and run a deployed application on another computer
system, the end-user must have one of the following versions
of FAST TRACK:
* Full FAST TRACK
* FAST TRACK Query/Report
* FAST TRACK Run-Time
PROGRESS Query/Run-Time cannot compile applications that update
the database. PROGRESS Run-Time does not have the capability to
compile procedures.
3. Encryption Considerations
If you are sending encrypted code to the end-user platform, make
sure that you encrypt all of the include (.i) files in the FAST
TRACK subdirectories (menu, qbf, maint, form, report). Otherwise,
the end-user will receive a run-time error when they try to
execute the application.
FUNCTIONALITY OF COMPILED END-USER FAST TRACK APPLICATIONS
Product Combination Limitations
-----------------------------------------------------------------------
PROGRESS Application Development None
System
-----------------------------------------------------------------------
PROGRESS 4GL/RDBMS No FAST TRACK menus, Run-Time
security, output control, QBF
views and joins.
-----------------------------------------------------------------------
PROGRESS 4GL/RDBMS and None
PROGRESS FAST TRACK
-----------------------------------------------------------------------
PROGRESS 4GL/RDBMS and None
PROGRESS FAST TRACK Run-Time
-----------------------------------------------------------------------
PROGRESS Query/Run-Time No FAST TRACK menus, Run-Time
security, output control, QBF
view and joins.
-----------------------------------------------------------------------
PROGRESS Query/Report None
-----------------------------------------------------------------------
PROGRESS Query/Run-Time and None
PROGRESS FAST TRACK
-----------------------------------------------------------------------
PROGRESS Query/Run-Time and None
PROGRESS FAST TRACK Run-Time
-----------------------------------------------------------------------
PROGRESS Run-Time No QBF qualifications, QBF views
or joins, new include files, FAST
TRACK menus, Run-Time security,
and output control.
-----------------------------------------------------------------------
PROGRESS Run-Time and No QBF qualification, new include
FAST TRACK Run-Time files, or page size in output
control.
-----------------------------------------------------------------------
FAST TRACK/PROGRESS Product Matrix
----------------------------------
Applications generated by FAST TRACK can be run by:
* PROGRESS Run-Time
* PROGRESS Query/Run-Time
* PROGRESS 4GL/RDBMS
You can use reports, QBF procedures, and forms generated with FAST
TRACK on any PROGRESS database that contains the appropriate data
files. Report code, however, cannot access FAST TRACK's run-time
security and output device control options.
Here are some quidelines for developing FAST TRACK applications for
PROGRESS Run-Time.
* No QUERY command in QBF Procedures.
* You cannot change include files associated with
output devices, either with the Report Writer's
ASK option or via the UPDATE OUTPUT DEVICES option
on the Maintenance menu. You must recompile new
include files.
* The end-user cannot change a report's page size.
For example, the Report Writer's ASK option does
not prompt for a page size on a PROGRESS Run-Time
system.
DEPLOY APPLICATION (DUMP OPTION)
------------------------------------
STEP 1: Choose the Deploy Application option from the FAST TRACK
Maintenance Menu. Type D to dump the application.
STEP 2: Choose the type of objects to dump from the Choose Objects
menu.
STEP 3: Choose the object(s) to dump.
STEP 4: Specify a deployment directory for each type of object
deployed.
STEP 5: Specify whether or not you want to dump .r code along with the
.p code.
Deployment Directory
--------------------
Store your dumped reports, menus, screens and QBF's in different
subdirectories, because the report and QBF dump procedures can create
files with the same names.
On UNIX and VMS systems, ensure that you have adequate permission to
create files and write files to existing directories. If, during the
deployment process, you discover you do not have adequate permission,
press CONTROL-C to cancel deployment.
Before dumping you application, make sure that you have enough space to
proceed. When you dump your application, you are essentially copying
all of your procedures and FAST TRACK data files to your deployment
directories.
DUMPING MENUS
-------------
After you select the menus to dump, FAST TRACK prompts you for a
deployment directory.
The default Menu Deployment directory is MENUDEP.
The deployment process copies all menu related files to the deployment
directory. These consist of procedure (.p) and include (.i) files.
If you choose to deploy compiled (.r) files, it copies them too.
In addition, the deployment directory contains the following data
files:
_menu.d
_choice.d
_menprog.d
If you dump submenus, reports, and QBF procedures associated with your
selected menu, the data files for each of the associated items will
appear in the MENUDEP deployment directory. If you have separate
application subdirectories for you report, qbf, menu, forms, and other
types of procedures, you must create that same directory structure
within the deployment directory BEFORE deploying your application. For
example, if your application has the following subdirectories:
APPLICATION DIRECTORY
:
-----------------------------------------------------------
: : : :
reports forms qbfs menus
The Menu Deployment directory MENUDEP should have the following
structure:
APPLICATION DIRECTORY
:
-----------------------------------------------------------
: : : : :
reports forms MENUDEP qbfs menus
:
:
-----------------------------------------------------------
: : : :
reports forms qbfs menus
DUMPING REPORTS
---------------
After you select the reports to dump, FAST TRACK prompts you for a
deployment directory.
The default Report Deployment directory is REPDEP.
The deployment process copies all report related files to the
deployment directory. These consist of procedure (.p) and include
(.i) files. If you choose to deploy compiled (.r) files, it copies
them too. In addition, it copies the following report-related data
files to the deployment directory:
_fdef.d _form.d
_ragg.d _repexp.d
_report.d _rgroup.d
_rlevel.d _row.d
_rqual.d _repprog.d
If you have a separate application directory for your reports, you
must create that directory within the deployment directory BEFORE
you deploy your application.
DUMPING QBFs
------------
After you select the QBFs to dump, FAST TRACK prompts you for a
deployment directory.
The default QBF Deployment directory is QBFDEP.
The deployment process copies all QBF related files (and any files for
QBF screens) to the deployment directory. These consist of procedure
(.p) and include (.i) files. If you chose to deploy compiled (.r)
files, it copies them too. In addition, the process copies the
following QBF-related data files to the deployement directory
_form.d
_fdef.d
If you have a separate application directory for your qbfs, you must
create that directory within the deployment directory BEFORE you
deploy your application.
Note: In addition to dumping QBF objects, QBF deployment dumps all
screen objects used to generate the QBF. If all your screens
are associated with a QBF, you do not need to dump the screens
separately using the Screen deployment option.
DUMPING FORMS
-------------
The default Screen Deployment directory is FORMDEP.
The deployment process copies all FAST TRACK form procedure files to
the deployment directory. These consist of form (.f) files. In
addition, it copies the following screen related data files to the
deployment directory:
_fdef.d
_form.d
If you have a separate application directory for your forms, you must
create that directory within the deployment directory BEFORE you deploy
your application.
SIX STEPS TO LOAD A COMPILED APPLICATION
1. Prepare end-user platform for the application.
2. If you deployed pieces of your application into different
directories, set up the same directory structure.
3. Extract application from distribution media.
4. Start up FAST TRACK with the application database and access the
FAST TRACK Maintenance Menu.
5. Deploy Application (LOAD) the source and object code.
6. Set up printers and security with "Run-Time Security" and "Update
Output Devices".
SEVEN STEPS TO LOAD AN UNCOMPILED APPLICATION
1. Prepare end-user platform for the application.
2. If you deployed pieces of your application into different
directories, set up the same directory structure.
3. Extract application from distribution media.
4. Start up FAST TRACK with the application database and access the
FAST TRACK Maintenance menu.
5. Deploy Application (LOAD) the source code.
6. Compile Application.
7. Set up printers and security with "Run-Time Security" and "Update
Output Devices".
PREPARING THE END-USER PLATFORM
Before you install your application, ensure that the environment
on the target system is set up properly.
Consider the following directory structure in the MENUDEP deployment
directory:
menudep
:
-----------------------------------------------------------
: : : :
reports forms qbfs menus
You should make the same directory structure in your new application
directory on the end-user platform. For example:
new application directory
:
-----------------------------------------------------------
: : : : :
reports forms MENUDEP qbfs menus
Once you have set up the environment of the target system, copy the
deployment dump files from the delivery media to the application
deployment directory (MENUDEP) on the target system.
THE FTLOAD UTILITY
------------------
The FTLOAD utility is designed to convert a PROGRESS (Version 4.2E or
higher) database to a FAST TRACK database. The ftload software is
packaged with FAST TRACK and installed in the main FAST TRACK
Maintenance menu, which is your entry point into FAST TRACK when you
deploy an application.
To run FTLOAD on UNIX, DOS, or OS/2 enter:
ftload <database-name>
To run FTLOAD on VMS enter:
@FTLOAD <database-name>
To run FTLOAD on BTOS/CTOS enter:
fast track convert database
FAST TRACK Convert Database
Database Name <database-name>
If the database is not a FAST TRACK database, FAST TRACK displays the
following message:
This is not a FAST TRACK database.
Do you wish to convert it (y
)?
Type 'y' to convert the specified database. Otherwise type 'n'.
A prompt appears for you to confirm that you have done a backup of your
system. Type 'y' to confirm, or 'n' to exit. When FTLOAD finishes
converting your database, it displays the following message:
Successful FAST TRACK conversion completed.
Then, FTLOAD executes and displays the FAST TRACK Maintenance Menu.
From there, you can load your application.
DEPLOY APPLICATION (LOAD OPTION)
--------------------------------
STEP 1: Choose the Deploy Application option from the FAST TRACK
Maintenance menu. Type L to load application (note that the
default is D).
STEP 2: Choose the object(s) to load from the Choose Objects Menu.
STEP 3: Specify a deployment directory for each type of deployed
object.
STEP 4: Specify an application directory for each type of deployed
object.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
FAST TRACK User's Guide, Chapter 7
Progress Software Technical Support Note # 4907