Application Development


Appendix D . Deployment Checklist for Two-tier Applications


Directory Structure for Two-tier Applications

Distribute the files and libraries used by your Panther application in a single directory, call it the application directory. The directory should include such things as your application's executables and Panther-specific libraries. In addition, it should include the following subdirectories:


Checklist for Deployment

The tables in this section list the components you should include in a distribution for the specific platform. Depending on your particular application, there might be other considerations and files which you might include. Those considerations are covered later in this chapter.

Preparing a Windows Distribution

Table D-1 lists the files and libraries required on a Windows installation. The table also includes where these files can be found in the Panther distribution. In general, you should make copies of those files as opposed to using the originals. In all likelihood, your Panther application has been using the components it needs while you've been developing it. This list will serve as a means of making certain all the pieces you need are deployed to the application users.

Table D-1 Checklist for contents of a Panther application for Windows

File/Library Found in Panther Description

application directory contents:

² cktbl32/64.dll

util

Panther-specific DLL

² database DLLs

util

Support Panther database drivers—Informix, ODBC, Oracle, Sybase

² *.ini

config

Initialization file prol5w32.ini

² libsti32/64.dll

util

Panther-specific DLL

² libsti.ini

config

Graph-specific initialization file (copy this file to the Windows directory)

² prorun32/64.exe

util

Runtime executable (rename for your application)

² wecjlib.dll

util

Panther-specific DLL

config directory contents:

² client.lib includes:

client screens

Panther screens that make up the user interface

smwzmenu

Binary menu script file; include if client screens created with screen wizard use the prototype menu bar/toolbar

smwizard.bin

JPL module made public by client screens created by the screen wizard

JPL modules

JPL code used by client screens

Graphics files

Image files (such as *.ico, *.bmp, *.jpg) referenced on client screens and/or toolbars

styles.sty

Transaction manager styles file for your application

*cmap.bin

config

Binary configuration map file (maps Panther fonts to Windows-specific fonts, etc.).

*key.bin

config

Binary key files for mapping physical keys to Panther logical keys. Omit this file from the library if end-users can modify key mapping on installation.

msgfile.bin

config

Contains messages and information used by Panther

smjgbls

config

Defines all Panther global constants

² *.fnt

config

Graph-specific fonts referenced in graphs in your application

² grafcap

config

Initialization file for graph support

² prorun5.lib

config

Panther's runtime support library

² prorw5.lib

config

Panther's runtime library for reports

² *keys

config

ASCII key file for mapping physical keys to Panther logical keys. Required if key mapping is user configurable; include key2bin utility as well.

² smvars.bin

config

Binary environment setup file

Preparing a UNIX Distribution

Table D-2 Checklist for contents of a Panther application for UNIX/Motif platforms

File/Library Found in Panther Description

application directory contents:

² Prolifics

config

Resource file for Motif (installation should copy Prolifics to the home directory of each user)

² prorun

util

Client executable (rename for your application); required only if supporting UNIX clients

config directory contents:

² client.lib includes:

Required only if supporting UNIX clients

client screens

Panther screens that make up user interface

smwzmenu

Binary menu script file; include if client screens created with screen wizard use the prototype menu bar/toolbar

smwizard.bin

JPL module made public by client screens created by the screen wizard

JPL files

JPL files used by client screens

Graphics files

Image files (e.g., *.xbm, *.xpm, *.bmp, *.jpg) referenced on client screens and/or toolbars

styles.sty

Transaction manager styles file

*cmap.bin

config

Binary configuration map file (maps Panther fonts to Motif-specific fonts, etc.).

*key.bin

config

Binary key files for mapping physical keys to Panther logical keys. Omit this file from the library if end-users can modify key mapping on installation.

msgfile.bin

config

Contains messages and information used by Panther

smjgbls

config

Defines all Panther global constants

*vid.bin

config

For character-mode only. Binary files that describe terminal capabilities and attributes to Panther. Omit this file from the library if end-users can modify video specifications on installation.

² *.fnt

config

Graph-specific fonts referenced in graphs in your application; required if supporting UNIX clients

² gdsp

util

Graph support utility

² grafcap

config

Initialization file for graph support

² prorun5.lib

config

Panther's runtime support library

² prorw5.lib

config

Panther's runtime library for reports

² smvars.bin

config

Binary environment setup file. Copy and modify for your application.

² swsdrvr

util

Graph support utility