JetNet/Oracle Tuxedo Guide

Appendix F. Deployment Checklist for JetNet

Directory Structure for JetNet 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:

bin directory for UNIX only—Includes JetNet administrative executables. Required for three-tier processing.
configuration directory—Includes the runtime components that make up your application, such as your application libraries and those files that are specific to running your application.
library directory for UNIX only—Includes JetNet shared libraries. Required for three-tier processing.
locale directory—Includes the routines used by JetNet. Required for three-tier processing.
udataobj directory—Includes files used by JetNet. Required for three-tier processing.

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 F-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 or 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 F-1 Checklist for contents of Panther Windows applications**
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 files. `prol5w32/64.ini`, `jetman.ini` if using the JetNet manager.
`jetman.exe`	`util`	JetNet manager executable; required only if running the manager
`libsti32/64.dll`	`util`	Panther-specific DLL
`libsti.ini`	`config`	Graph-specific initialization file (copy this file to the Windows directory)
`libxml2.dll`	`util`	Needed if XML files are to be imported.
`msvcr80.dll`	`util`	Microsoft Visual C++ 2005 runtime DLL. Needed if the Redistributable Package will not be installed.
`PanPDF32/64.dll`	`util`	Needed if PDF reports will be created.
`projpeg.dll`	`util`	Needed to process JPEG images.
`promfc32/64.dll`	`util`	Contains status line and frameset code.
`prores32/64.dll`	`util`	Panther Windows resource DLL
`prorun32/64.exe`	`util`	Runtime executable (rename for your application)
`rwres32/64.dll`	`util`	Report Writer Windows resource DLL
`wbuft.dll`	`util`	JetNet library
`wtuxws.dll`	`util`	JetNet library
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
`common.lib includes:`
`wincmap.bin`	`config`	Binary configuration map file (maps Panther fonts to Windows-specific fonts, etc.).
`jif.bin`		Binary service and queue definition file
`winkeys.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
`*.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
`winkeys`	`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
`symbold,` `symbols1`	`config`	Font files for graphs, if used in application
locale\C directory contents:
		Routines used by JetNet
`gp_cat`	`locale\C`
`langinfo`	`locale\C`
`libwsc_cat`	`locale\C`
`trpc_cat`	`locale\C`
udataobj directory contents:
`tpadm`	`udataobj`	JetNet-specific file
`usysfl32`	`udataobj`	JetNet-specific file
`usysflds`	`udataobj`	JetNet-specific file

Preparing a UNIX Distribution

**Table F-2 Checklist for contents of Panther UNIX/Motif applications**
File/Library	Found in Panther	Description
application directory contents:
`broker.bin`		JetNet configuration file
`progserv`	`util`	Conversion server executable (rename for your application); required only for 2- to 3-tier converted applications
`progserv.env`	`config`	Conversion server environment definition file; required only for 2- to 3-tier converted applications
`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
`proserv`	`util`	Standard server executable (rename for your application)
`proserv.env`	`config`	Standard server environment definition file
`rbboot`	`util`	Utility to start JetNet and boot application servers
`rbcfinfo`	`util`	Used by `rbconfig`
`rbconfig`	`util`	Command-line utility for creating a JetNet configuration file
`rblisten`	`util`	Utility allows application servers to run on multiple ma chines.
`rbshutdown`	`util`	Utility to shutdown JetNet and application servers
bin directory contents:
		JetNet administrative executables
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
`common.lib` includes:
`*cmap.bin`	`config`	Binary configuration map file (maps Panther fonts to Motif-specific fonts, etc.).
`jif.bin`		Binary service and queue definition file
`*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
`*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
`server.lib` includes:		Not required for two-tier applications
service components		Screens that are defined as service components for use on a server
`smwizsrv.bin`	`config`	JPL module made public by service components created by the screen wizard
JPL modules		JPL code used by service components
`smvars.bin`	`config`	Binary environment setup file. Copy and modify for your application.
`swsdrvr`	`util`	Graph support utility
`library directory contents:`		JetNet shared libraries and platform-specific shared libraries. Platform-specific libraries have a unique extension; refer to your platform documentation to determine the extension. For example, for Solaris, the file extension is .so and for HPUX on PA-RISC, it is .sl.
`libbuft.pltExt`	`lib`
`libfml.pltExt`	`lib`
`libfml32.pltExt`	`lib`
`libgp.pltExt`	`lib`
`libnwi.pltExt`	`lib`
`libnws.pltExt`	`lib`
`libqm.pltExt`	`lib`
`libtmib.pltExt`	`lib`
`libtux.pltExt`	`lib`
`libtux2.pltExt`	`lib`
`libusort.pltExt`	`lib`
`libwsc.pltExt`	`lib`
`libwsh.pltExt`	`lib`
locale/C directory contents:
		Routines used by JetNet
`CMDTUX_CAT`	`locale/C`
`GP_CAT`	`locale/C`
`LIBTMIB_CAT`	`locale/C`
`LIBTUX_CAT`	`locale/C`
`TMADMIN_CAT`	`locale/C`
`WSNAT_CAT`	`locale/C`
udataobj directory contents:
`mib_views.V`	`udataobj`	JetNet-specific file
`tmib_views.V`	`udataobj`	JetNet-specific file
`tpadm`	`udataobj`	JetNet-specific file