Release 10.1A: OpenEdge Reporting:
Query/Results Administration and Development

> ## The deployment report

> As you build a Results application, Results creates and maintains a deployment report. The deployment report lists all of the databases, procedure files, ASCII files, and graphics files that are part of your application in Results. These are the files that you must deploy to install your application in end-user environments.

> The name of the deployment report consists of the first five characters of the current `QC7` file followed by .txt. Results creates the deployment report in the same directory as the `QC7` file. Example 4–1 shows an example of a deployment report for a simple Results application.

> Example 4–1: sport.txt
>     # Progress RESULTS Deployed Application FileList
>     # This reports does not provide Public Query Directory Information

>     baseResourceFile= aderes/results.l
>     configurationFile:ascii= sports.qc7
>     configurationFileAltSrc:featureFile= sportf.p
>     configurationFileAltSrc:menuFile= sportmt.p
>     database:1= sports
>     defaultIcon:Graph= C:/PROSPRT/GRAPH-D.BMP
>     defaultIcon:Graph= C:/PROSPRT/GRAPH-I.BMP
>     defaultIcon:Graph= C:/PROSPRT/GRAPH-U.BMP
>     featureFileSrc:Cmprint= C:\PROSPRT\CMPRINT.P
>     featureFileSrc:Graph= C:\PROSPRT\PRSGRAPH.P
>     integrationPointSrc:define= C:\PROSPRT\PRSDEF.P
>     integrationPointSrc:direct= C:\PROSPRT\PRSDIR.P
>     integrationPointSrc:field= C:\PROSPRT\PRSFLD.P
>     integrationPointSrc:login= C:\PROSPRT\PRSLOGN.P
>     integrationPointSrc:logo= C:\PROSPRT\PRSLOGO.P
>     integrationPointSrc:menu= C:\PROSPRT\PRSSEC.P
>     integrationPointSrc:sens= C:\PROSPRT\PRSMNU.P
>     integrationPointSrc:table= C:\PROSPRT\PRSTBL.P
>     integrationPointSrc:where= C:\PROSPRT\PRSSEL.P
>     logoIcon= C:/PROSPRT/PROSPRT.ico

> Each file entry in the deployment report has a label that identifies how the file is integrated into Results.

> ##### Deployment file list

> The following list identifies and describes the deployment report labels:

> `baseResourceFile`

> The relative pathname of the `results.l` file. Deploy this file only if you altered it to define export formats, page sizes, and label formats.

> `configurationFile:`asci``

> The pathname of the `QC7` file.

> `configurationFileAltSrc:`featureFile``

> The pathname of the feature definition file. This file loads the feature definitions for your application into Results. Results generates a compiled, optimized version of this file for the fastload system. You can set the name of this file with the Query Customize Deployment menu option.

> `configurationFileAltSrc:`menuFile``

> The pathname of the menu definition file. This file loads the menu system and tool bar configuration for your application into Results. Results generates a compiled, optimized version of this file for the fastload system.

> `database:`n``

> The name of a database referenced in the query configuration file. The deployment report contains an entry for each database referenced in the query configuration file. The `n` represents the number of the database in the order of listing in the query configuration file. In most cases, the application databases already exist in the user environment.

> `defaultIcon:`featureName``

> The pathname of an icon specified for a programmer-defined feature. The `featureName` parameter is the name of the feature associated with the icon. The deployment report typically has three defaultIcon entries for each new feature to identify graphics files associated with the three states of the icon: up, down, and insensitive. The following excerpt from a deployment report shows the graphics files associated with a feature called Graph:

>     defaultIcon:Graph= C:/PROSPRT/GRAPH-D.BMP
>     defaultIcon:Graph= C:/PROSPRT/GRAPH-I.BMP
>     defaultIcon:Graph= C:/PROSPRT/GRAPH-U.BMP

> `featureFileSrc:`featureName``

> The pathname of a source procedure file associated with a programmer-defined feature. The featureName parameter is the name of the new feature. The following excerpt from a deployment report shows the procedure file associated with a feature called Cmprint:

>     featureFileSrc:Cmprint= C:\PROSPRT\CMPRINT.P

> The deployment report contains a featureFileSrc entry for each programmer-defined feature.

> `integrationPointSrc:`intPoint``

> The pathname of a source procedure file associated with an integration point. The intPoint parameter is an identifier for an integration point. These are the valid identifiers and the names of the corresponding integration points:

> - define — Initialize Vars and Interface
> - direct — Query Directory Switch Program
> - field — Field Security
> - login — Login Program
> - logo — Logo Screen
> - menu — Feature Security
> - sens — Menu Item Override
> - table — Table Security
> - where — Table Selection Security

> The deployment report contains an integrationPointSrc entry for each integration point that has an assigned integration procedure.

> `logoIcon`

> The pathname of a graphics file defined as the application icon for Results in the window system.

> The following section lists additional files that do not appear in the deployment report, but are potential candidates for deployment as part of a Results application.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095