Oracle Forms Developer and Reports Developer Release 6i: Guidelines for Building Applications A73073-01 |

Library | Service | Contents | Index

# 1
Managing Your Applications

One of the most important aspects of application development is managing the modules that make up an application. Large applications can consist of literally thousands of modules, and millions of lines of code. In addition, modules which are important to the project as a whole but which are not compiled into the application itself (such as design specifications, test scripts, and documentation) must also be tracked and maintained.

This chapter explains how to use Forms Developer and Reports Developer to help you manage the application development process.

#####

Section | Description
--- | ---
Section 1.1, "The Software Development Lifecycle: An Overview" | Briefly covers the major milestones of application development and discusses Project Builder within that framework.
Section 1.2, "Managing Project Documents During Design and Development" | Discusses how to manage documents during development of an application.
Section 1.3, "Managing Project Documents During the Test Phase" | Discusses how to ensure that your QA group tests the correct configuration of project documents during the test phase.
Section 1.4, "Managing Project Documents During the Release Phase" | Discusses how to ensure that an installable version of your application is delivered to your customers.
Section 1.5, "Deploying Completed Applications" | Discusses how to turn your own application into one that is installable by the Oracle Installer.

## 1.1 The Software Development Lifecycle: An Overview

Application development typically occurs in four phases:

- Design. The initial specification for the application is developed. This specification can be based on a variety of sources: customer feedback, input of project management or development team members, requests for enhancement, necessary bug fixes, or systems analysis.

- Develop. Individual modules are created or modified, possibly incorporating a wide variety of languages, tools, or platforms.

- Test. The modules are tested. This generally occurs in two stages: unit test and system test. Unit test is testing at a modular or functional level; for example, testing UI elements such as menus or buttons. System test tests the integration of major portions of the code; the backend with the UI, for example.

- Deploy. The modules are packaged together in an installable form and delivered to customers.

#### Figure 1-1 The phases of the development lifecycle: input and deliverables

As the application grows in size and complexity, the four phases are repeated iteratively, and the amount of information produced (actual code, bug reports, enhancement requests, etc.) grows. Yet all input and deliverables for all phases must be tracked and maintained to ensure the integrity of the final deliverable: the application your customer installs.

This chapter discusses how to use Forms Developer or Reports Developer to manage your application's code base and maintain version integrity.

### 1.1.1 Using Project Builder to implement a management strategy

In any development project, management tasks can be split roughly into two categories:

- Project management, which includes allocating the necessary equipment, budget, and person-hours of work necessary to complete the development of the application.

- Software configuration management, which includes assigning modules to developers, determining dependencies among modules, maintaining the code under development, and version control.

Project Builder, a component of both Forms Developer and Reports Developer, enables you to simplify your software configuration management tasks so you and your team can focus on your primary objectives: designing, coding, and testing applications.

### 1.1.2 About Project Builder

To help simplify your software management tasks, Project Builder provides the means for you to:

- Associate modules with an application or component of an application.

- Automate actions based on file types.

- Create dependencies between modules and indicate how changes cascade; in other words, show which modules need to be recompiled based on changes to other modules.

- Assign default connection strings to modules.

- Designate which modules are to be included in the final install set.

- Share projects and subprojects among team members and port them to different environments.

- Invoke other tools from the Project Builder user interface.

These features are described in detail in Section 1.1.3, "Exploring Project Builder benefits". If you're unfamiliar with Project Builder terminology, however, it's a good idea to read through Section 1.1.2.1, "Understanding Project Builder terminology" before proceeding. This section defines some basic terms which provide the context for a discussion of Project Builder's features.

#### 1.1.2.1 Understanding Project Builder terminology

Project Builder is based upon the concepts of projects and subprojects:

- Projects are collections of pointers to the modules and files that are part of your application.

- Subprojects are projects contained within other projects, providing a finer level of organizational granularity. Often the organization of files into subprojects mirrors the organization of files into subdirectories, but this is not a requirement.

In addition to projects and subprojects, these terms are also central to a solid understanding of Project Builder:

- Types. A type is the basis of every item, and controls the actions that are available in Project Builder. Project Builder types recognize their associated file types primarily by default extension; for example, .TXT for text files. Project Builder predefines types for many commonly used files, such as forms documents (FMB), text files, and C source files. You can also use the Type Wizard to define types for other applications.

- Project items. The components that make up a project are known as items. An item is simply a description of a file that is part of a project. Each item is fully described in the associated Property Palette, which lists the item's type, location in the file system, size, and when it was last modified. The actions and macros (see below) for the item are also defined.

  It is important to remember that an item is not the file itself; rather, it is a description of the file. So, when you delete an item from a project, you are simply telling Project Builder that the file is no longer part of the project. The file itself is not deleted.

- Actions. Actions are command strings that apply to files of a given type; for example, the Edit action for a text item may be the command string that invokes Notepad or WordPad.

- Macros. Macros are variables you can use to modify actions. A macro may be either a constant or a simple expression (which, in turn, may contain other constants and/or expressions). For example, Project Builder inserts all the information you've specified for connecting to a database into the ORACONNECT macro, which is included in all commands that might require you to connect. The information in the macro is then inserted into the action so you can log on automatically.

  Just as you might use environment variable in scripts or batch files to conveniently modify a script's actions without editing the script itself, so you can use macros to customize actions without having to edit the action themselves. For example, you might define a macro to determine whether to compile your application in Debug mode or Optimized mode. In preparation for building the deployment version of the application, you would simply change one macro definition to switch off Debug, rather than having to find and modify every type whose Build command made use of the Debug flag.

- Global registry. The Global Registry contains the pre-defined Project Builder types.

- User registry. Each user has a user registry in which to define new types, redefine existing types, and modify or create actions or macros.

- Project registry file. The project registry file contains information necessary to track a project, including pointers to modules contained within the project, default connection strings, and a pointer to the "home" directory for the project.

The Project Builder interface provides three tools for manipulating the items that make up a project:

- The Project Navigator furnishes a familiar "navigator" or "explorer" style interface with which you can view the modules in your application. In addition, you can use Project Builder's filtering capabilities to display only the modules you want to see. You can also launch editing tools directly from the Project Navigator.

- The Property Palette enables you to examine and modify the properties of selected items.

- The Launcher, a secondary toolbar, provides another means of accessing development tools. You can even add buttons to the Launcher and associate them with your favorite third-party tools.

Figure 1-2 depicts all three of these tools.

#### Figure 1-2 The Project Builder user interface

#### 1.1.2.2 How Project Builder affects existing development roles

Certain roles must be filled to keep the application development effort going smoothly. Some, such as project manager, development manager, and team leader, are common roles within development groups and require no definition. However, with Project Builder one new role exists--that of project administrator.

A project administrator is charged with creating projects and making them available to developers. The project administrator maintains the Global Registry and modifies it as necessary, exporting the changes to the developers on the team. He or she may also export the project information to different environments, such as test environments, or other platforms for cross-platform development.

The work the project administrator does when managing projects may affect the roles of the following team members:

- Developers

- Source control administrator

- Testers (QA)

- Releaser

Of course, the precise duties of each team member vary from development group to development group. A team member may also take on more than one role; for example, a team leader may also be a project administrator, or a developer may be in charge of source control.

### 1.1.3 Exploring Project Builder benefits

Now that you are familiar with basic Project Builder terminology (see Section 1.1.2.1, "Understanding Project Builder terminology"), let's examine the benefits Project Builder provides.

#### 1.1.3.1 Associating modules with an application

You can associate all of the modules in an application with the application itself simply by adding the modules to the same project. This allows you to track a large application as a single entity, determine the dependencies between modules, and so on.

#### 1.1.3.2 Automating actions based on file types

Project Builder ships with an extensive list of types, to which are assigned default actions (such as Open, Edit, or Print). When you select a module, then click the right mouse button, a pop-up menu displays the actions associated with that type. By default, the actions included in a type definition apply to all modules of that type in a project. You can also modify and add to these actions.

Actions are simply command strings. One benefit to defining actions with the actual command strings (besides simplicity, of course) is that an action can be associated conceptually with several different types. For example, editing a Word document requires a different tool than editing a text document, yet conceptually the two edits are very similar. Project Builder can associate an Edit command with many different types, using a different command string for each. In this way, a single command executes an appropriate action no matter what type of module you're working with.

#### 1.1.3.3 Creating dependencies between modules

Knowing which modules depend on which other modules is necessary to determine when modules need to be recompiled as a result of a change. It's also the key to managing the impact of changes; for example, if a library changes, which forms are now out-of-date?

Project Builder includes the dependencies for module types in their type definitions. Thus, it can recognize dependencies between existing modules in a project. Since it can also track modifications to modules, it automatically recompiles changed modules and the modules dependent on them.

In fact, Project Builder can recognize dependencies that do not yet exist within the project and create markers for them. These markers are called implied items. For example, suppose your project contains an .FMB file, defined by the Project Builder type "Form Builder document." The "Form Builder executable," or .FMX file, may not exist--you may not have generated it yet. But Project Builder knows the existence of this .FMX file is implied by the existence of the .FMB file, and creates an implied item to mark it.

To determine the existence of an implied item, Project Builder correlates the value of the property Deliverable Type for each defined type with the input items, or source, required for the Build From <type> action for each defined type. In our example above, the Deliverable Type property for the "Form Builder document" type is defined as "Form Builder executable," or .FMX.The Build From <type> action defined for a Form Builder executable is "Build From FMB". This means .FMB files are the input items for creating .FMX files, and, conversely, .FMX files are targets for .FMB source.

The chain of implied items can consist of multiple files. For example, suppose you add a C source file to a library file. In this case, Project Builder adds modules of whatever other types are necessary to get a complete path of Build From <type> actions from one file type to the other (like an object file).

While Project Builder detects dependencies only between compilable modules and their resultant executables, you can set dependencies manually by adding modules to a project below the item dependent on them. For example, if an .FMB is dependent on a PL/SQL library, you can add the .PLL to the project below the .FMB, and Project Builder will recognize the dependency.

#### 1.1.3.4 Assigning default connection strings to modules

With Project Builder, you can define all of your most-used connection strings and store their definitions under the Connections node. You can then assign a connection to a module by dragging the connection from the Connections node and dropping it on the module. When you need to edit that module--for instance, a form--you can select the form in the Project Navigator and choose Edit from the pop-up menu. Project Builder automatically opens Form Builder and connects to your database for you.

#### 1.1.3.5 Designating which modules are to be included in the final install set

Project Builder makes it easy to determine and track the modules that will be included in your final install package (for example, .EXE files, .DLL files, and .HLP files).To earmark a file for delivery, set the Deliver File property to Yes. When you're ready to create an install package, you can use the Delivery Wizard to package all modules for which the Deliver File property is set to Yes into a single unit.

Note: You can set the Deliver File property for a type or for individual project items.

#### 1.1.3.6 Sharing and porting project and subproject registry files

Project Builder enables you to export the information about a project to other team members and to other platforms. Information about types, actions, macros, and project registry files--including all the customizations you've made--can be written to a text-based export file which you can then import to other environments and other platforms. This enables cross-platform development and testing.

#### 1.1.3.7 Accessing other product components and third party tools

You can access other tools from the Project Builder user interface through several means:

- Actions, which you access by selecting a module in the Project Navigator and clicking the right mouse button. A pop-up menu displays all the actions associated with the selected item; the actions listed invoke whatever tools are specified in the command strings. You can also double-click an item in the Project Navigator to invoke its default action.

- The Build, Deliver, and source control actions, which launch whatever tools are associated with them.

- The Launcher toolbar, which launches many components such as Form Builder, Report Builder, and Graphics Builder. You can also add your own buttons to the Launcher toolbar and associate them with your favorite third-party tools.

#### 1.1.3.8 Using source control packages

Both Forms Developer and Reports Developer provide interfaces to these source control packages:

- PVCS from Intersolv

- Clearcase from PureAtria

- Versions, the source control component of StarTeam, from StarBase

You can also use other source control tools by modifying the source control actions provided with Project Builder to point to them.

Since a variety of source control packages are available and can be used with Forms Developer and Reports Developer, specific instructions for source-controlling your projects are beyond the scope of this chapter.However, general guidelines will be provided where applicable.

## 1.2 Managing Project Documents During Design and Development

Much has been written about the importance of design in the success of an application.Deliverables during the design phase can include design documents and specifications, meeting minutes, UI prototypes, results from customer surveys (if the application is new), user tests and lists of enhancement requests (if the application is to be revised)--all documents that can be added to and tracked within a project.

This means the project administrator for the development effort should be identified early in the design process and begin creating the project immediately. (See Section 1.1.2.2, "How Project Builder affects existing development roles" for information on the role of the project administrator.) This section describes the role of the project administrator and the members of the development team in setting up Project Builder to manage a project during the design and development phase.Specifically, this section addresses:

- Installing Project Builder

- Creating a project

- Working with projects and project documents

- Managing projects and project documents across multiple platforms

Note: The steps involved in accomplishing simple tasks with Project Builder are in the Project Builder online help and are not included in this chapter.

### 1.2.1 Installing Project Builder

Project Builder is automatically installed to ORACLE_HOME\PJ10.Noteworthy files found in this directory are:

- Global Registry file (TYPESnn.UPD), where nn indicates the national language

- Default user registry files (PJUSERnn.UPD), where nn indicates the national language

Perhaps the most important issue to address during Project Builder installation is how you want to make these various files available to team members. Section 1.2.1.1, "Installing the project and user registries" discusses your options.

#### 1.2.1.1 Installing the project and user registries

Project Builder depends on native file sharing protocols for its security. This can make project files vulnerable to accidental changes, which is something to keep in mind as you decide how to configure the Global Registry and user registries. Table 1-1 lists the available options.

##### Table 1-1 Registry installation options

Option | Pros | Cons | Recommendation
--- | --- | --- | ---
Install Project Builder with the Global Registry on a shared network drive and the user registries on local machines. | If your team is networked, developers can access a single copy of the Global Registry. This ensures that all versions of the Global Registry in use are up-to-date. | If all team members have write access to the Global Registry, it can be accidentally overwritten. | To prevent the Global Registry from being accidentally overwritten, install it in a directory to which only you have write access.
Install Project Builder with copies of the Global Registry available to each team member, in addition to their own user registries. | You can propagate updates to the Global Registry simply by making a copy of the changed file available to your team members (if they are on the same platform). | The individual Global Registries are not safe from accidental overwrites or deletions. | Use Project Builder's Export facility to propagate changed registry files instead of providing copies. A more rigorous process may help discourage a casual attitude toward registry files.
Install Project Builder with the Global Registry and a single user registry shared among team members. |  | The types, actions, projects, and project modules are at risk for conflicting modifications. | Don't choose this option. But if you must, have members of your development team edit only the modules, not the project itself.

### 1.2.2 Creating a project

This section focuses on the creation of a single project for distribution to a team of developers. However, this may not be the best option for your group. If the application being developed is very large or if components are to be split up among team members, you may choose to create several separate, smaller projects, the contents of each determined by the responsibilities of each developer or group of developers.

If you decide to distribute a single project, note that Project Builder projects will accept pointers to modules that do not exist in the specified location. (You can determine whether a module exists by examining its information in the Property Palette; Time created/modified and File size (bytes) are blank if the module does not exist). This means you can distribute a single large project without requiring all team members to have all modules available.

Creating a project is an ongoing task that requires the participation of both the project administrator as well as each member of the development team. This section describes the responsibilities unique to each role.

#### 1.2.2.1 Creating a project: Project Administrator

As project administrator, your role goes beyond creating a project registry file and deciding what to include in the project. Whether you use the Project Wizard provided by Project Builder to create the project, or create a project registry file and manually edit the various properties, prior planning is highly recommended before you complete the following tasks:

1. Create the project:

   1. Set up the project's directory structure.

   2. Add modules.

   3. Establish default actions, macros, and connection strings.

   4. Set necessary dependencies manually.

2. Work with the source control administrator to set up a concurrent source control project.

   1. Define new types and edit existing ones.

   2. Customize actions and macros.

   3. Create reusable connections.

3. Make the project available to team members.

   The next few topics provide recommendations for completing each of these tasks.

   ##### 1.2.2.1.1 Step 1: Creating the project

   The Project Wizard provides an easy-to-use interface for creating a project. You can also create a new project without the Project Wizard (using the New Project tool on the toolbar) and set project properties in the Property Palette.

   At its simplest, a new project is a default project registry file primed with information about the Global Registry, but little else. Project Builder needs a bit more information before it can keep track of your project, as discussed in the next few topics.

   Step 1a: Set up the project's directory structure

   The directory structure of a project can have far-reaching consequences. For example, suppose a project contains modules that are located in a directory that's not a child of the project directory. Now suppose you create actions that search for and modify project modules. How will you find the "orphan" modules? Create alternate actions with hardcoded paths? Not portable. Search from the root? Not efficient.

   Recommendations:

   - Place modules in the project directory or in a directory that's a child of the project directory (a good choice when adding subprojects).

   - As much as possible, organize your projects and subprojects so that they mirror your actual directory structure.

   The standard methods for adding modules to a project are the Add Files to Project and Add Directory dialogs. Note that the dialogs always insert the full path unless the module you want to add is in the project directory; then a relative path name is used.

   Step 1b: Add modules

   Once you have planned the directory structure, you can add modules to the project.

   Recommendation: Use subprojects whenever possible to help organize your project. But don't simply group together all forms or all reports. Group the modules into components; for example, you might create a subproject for all the modules in a large form, including .FMB files, .FMX files, PL/SQL libraries, menus, bitmaps, icons, etc. This enables you to more easily create some necessary dependencies not detected by Project Builder.

   Step 1c: Establish default actions, macros, and connection strings

   This step involves making site-specific edits to actions and macros; for example, changing build actions to use the compilers and compiler options that are standard at your site. If you have not already done so, you can also create connection strings for commonly used databases containing test data or necessary tables.

   Step 1d: Set necessary dependencies manually

   Project Builder can recognize some dependencies between modules (it knows that .FMX files are built from .FMB files, which are built from .FMT files), but only the dependencies it can deduce by cross-referencing the Deliverable Type and the Build From <type> actions.

   Other dependencies may exist as well: dependencies on PL/SQL libraries, menus, icons, and so on. You can tell Project Builder about these dependencies by creating entries for the modules on which a module is dependent below the item for the dependent module, as shown in Figure 1-3, "Manually added dependencies".

   #### Figure 1-3 Manually added dependencies

   This figure illustrates NAVWIZ.FMB's dependency upon WIZARD.PLL, NAVIGATE.PLL, and NAVWIZ.MMB.

   ##### 1.2.2.1.2 Step 2: Work with the source control administrator

   After you create your project, you're ready to introduce a source control package. Many third-party source control packages also implement the concept of projects.

   Recommendation: Work with your source control administrator to set up a source control project that mirrors your development project in Project Builder.

   When setting up a project to source control a complex application, remember to include the non-obvious modules as well. For example, when checking in a form, don't forget menus, PL/SQL libraries, user exits, icons, or special fonts you use. Applications running on Windows may use OCX or ActiveX controls that should be source-controlled as well.

   ##### 1.2.2.1.3 Step 3: Make the project available to team members

   Once you've done the preliminary work of creating the project and establishing source control, it's a good idea to export all project information to a project export file and notify team members of its location. They can then import the project.

   It is possible to notify team members of the location of the actual project registry file, but remember that Project Builder uses your operating system's own security features to protect your project modules from being deleted or overwritten. Simple deletes and overwrites are possible. To maintain the integrity of your projects, follow Project Builder's own process for updating projects, and always import and export modifications to the project instead of simply distributing changed registry files.

   When you notify your team members of the location of the project export file, you should also notify them of the directory structure you've set up so they can mirror that structure on their development machines. The easiest course for setting up the project is to have all team members map the project location to the same project directory on their machines, since mappings to different project locations would require separate copies of the project registry file with different values for the Project Location: Q:\myproj, R:\, etc.

   Team members can then check out the modules they have been assigned.

   #### 1.2.2.2 Creating a project: Team members

   After the project administrator has completed the tasks described in Section 1.2.2.1, "Creating a project: Project Administrator", project team members can fine-tune the work. If you are a project team member, you can expect to:

   1. Set up your directory structure and import the project

   2. Customize your user registry

      1. Define new types and edit existing ones

      2. Customize actions and macros

      3. Create re-usable connections

   3. Check out your assigned modules

   ##### 1.2.2.2.1 Step 1: Set up your directory structure and import the project

   When your project administrator informs you that the project is available, it's time to import the project information and set up your working directories with the modules you've been assigned.

   Recommendation: File management is easier if you set up your directory structure to mirror what your project administrator has already created for the project.

   ##### 1.2.2.2.2 Step 2: Customize your user registry

   One of the first things to do when setting up a project is to customize your user registry.

   Step 2a: Define new types and edit existing ones

   If you want to add modules to your project that are of a type not represented in the Global Registry, you can use the Type Wizard to define your own type in your user registry and assign actions, macros, and so on to it.

   In addition, you may want to override a default command or macro for a particular type in the Global Registry. An easy way to accomplish this is to copy the type in the Global Registry, paste it into your user registry, and edit it. Now, all modules of that type in your project will inherit the modifications from the type in the user registry.

   Recommendation: Notify your project administrator when you modify a global type by copying it into your user registry and editing it. Such a modification might be useful to the whole team.

   Step 2b: Customize actions and macros

   While you can customize the actions and macros associated with the types you add to your user registry, it's important to remember that you can modify actions and macros at other points in the Project Builder hierarchy as well. Where you edit the item depends on the extent of the influence you want your change to have.

   The following table lists all the locations you might find an action or macro, the scope of that action or macro, and what can override it.

   #####

   An action or macro assigned to: | Affects: | Unless overridden by:
   --- | --- | ---
   Global Registry | All items of type(s) to which it is assigned in all user registries and projects beneath the Global Registry. | Actions or macros in a user registry, project, subproject, or item.
   User registry | All items of type(s) to which it is assigned in all projects beneath the user registry. | Actions or macros in a project, subproject, or item.
   A project | All items of type(s) to which it is assigned in the project. | Actions or macros in a subproject or item.
   A subproject | All items of type(s) to which it is assigned in the subproject. | Actions or macros in an item.
   An item | Itself only. | Cannot be overridden.

   Step 2c: Create reusable connections

   If you have your own set of tables with data you've created for testing purposes, you can add your own connections to the list provided by the project administrator. Once you've created the connections, you can assign a connection to a module by selecting the connection's item in the Project Navigator, dragging it to the project file entries, and dropping it on the item for the module you've chosen. Now, when you select an action that opens a tool requiring a database connection, Project Builder logs on for you.

   ##### 1.2.2.2.3 Step 3: Check out your assigned modules

   Once you have your directory structure in place and the project imported, you can populate your workspace with the modules you've been assigned. The source control commands Check In, Check Out, and Source Control Options, accessible from the File'AdministrationFile->Administration menu, are associated with actions defined for each type. This means you can modify the actions, if necessary, to affect the results of the commands--though this is not recommended for source control.

   ### 1.2.3 Working with projects and project documents

   When the project enters the development phase, maintaining the integrity of the project becomes increasingly important.

   Recommendation: Only the project administrator should make changes to the project that affects multiple team members (such as modifying the Global Registry or adding new subprojects containing new modules).

   #### 1.2.3.1 Working with projects: Project Administrator

   While the application is in development, as project administrator your role is to maintain and support the project. In addition, you might be in charge of managing development deliverables, or working with a development manager to do so. You might need to:

   - Add new modules and dependencies

   - Export modifications to the project registry file

   - Apply version labels

   ##### 1.2.3.1.1 Adding new modules and dependencies

   Sometimes new modules must be added to a project after its initial creation, and dependencies added manually. The process for doing so is the same as when creating the initial project. For more information, see Section 1.2.2.1.1, "Step 1: Creating the project".

   ##### 1.2.3.1.2 Exporting modifications to the project registry file

   Once you've added the new modules and made the necessary changes, you can export the changes and make them available to members of your team. The process for doing so is the same as when exporting the initial project. For more information, see Section 1.2.2.1.1, "Step 1: Creating the project".

   ##### 1.2.3.1.3 Applying version labels

   Although you can try to keep various revisions synchronized with each other (for example, through a nightly check-in), often development on one module will be completed while another needs bugs fixed or headers changed. Synchronous revisions are generally impractical.

   A better method is to synchronize versions by applying a symbolic version label to the group of revisions that mark the achievement of a significant milestone. Most major source control tools enable you to apply a symbolic label to a source control project.

   #### 1.2.3.2 Working with project documents: Team members

   When your project is set up and your modules have been assigned, you can use Project Builder to:

   - Edit modules

   - Add modules and dependencies manually

   - Build your project

   - Check modules in and out

   ##### 1.2.3.2.1 Editing modules

   Recommendation: The most efficient way to use Project Builder to edit modules is to customize the actions associated with the types of modules you'll be editing so they invoke the tools you want to use with the options you need. In addition, be sure to associate a connection string with either the individual module or the project. Then you can drag the connection from its location in your user registry and drop it on the module or project item. Once your modules are prepared in this fashion, choosing a pop-up menu item or double-clicking on a project item opens your module in the correct application. If necessary, you'll already be logged on.

   You can also use the Launcher to access development tools. The Launcher is shipped with toolbar buttons already set for the Forms Developer or Reports Developer tools, but you can add a third-party tool by creating a button and associating it with an executable.

   Note: If you invoke a tool via the Launcher and then open a module, the tool will not be aware of any associated connection strings. You will need to log on to the database manually.

   ##### 1.2.3.2.2 Adding modules and dependencies manually

   See Section 1.2.2.1.1, "Step 1: Creating the project", or contact your project administrator.

   ##### 1.2.3.2.3 Building your project

   The Build commands--Build Selection, Build Incremental, and Build All--are available from the Project menu. They are also associated with an action--in this case, the Build From <type> action.

   This means you can select a single command for any different module type and the module will be compiled according to the definition of the Build From <type> action--not for that particular type, but for the target you actually want to build.

   For example, the Build From <type> action for an .FMX file invokes the Form Generator and creates the .FMX file from the corresponding .FMB.What the Build command compiles is the .FMB, but how it compiles the .FMB is determined by the action associated with the .FMX that results.

   You can modify the results of the Build commands by modifying the definition of the Build From <type> action for the corresponding target.

   Choose Build Selection to compile selected modules, or force a compile of all compilable modules by choosing Build All. Because Project Builder can detect when modules are out-of-date and need to be recompiled, you can compile only out-of-date modules by selecting the item for the project containing them, then choosing Build Incremental.

   Note: The Build commands are also available from the pop-up menu.

   ##### 1.2.3.2.4 Checking modules in and out

   If modules need conversion for source control (for instance, the source control only works on text and your modules are binary), you can edit the Check file into RCS action to automate the conversion to text before check-in.

   You can also edit the Check file out of RCS action in a similar fashion to convert the text-based source controlled version of the module back to binary.

   ### 1.2.4 Managing projects and project documents across multiple platforms

   Many applications today run on multiple platforms, with development taking place on a variety of platforms as well. Chapter 5, "Designing Portable Applications" can help you ensure that the application underlying your project is portable.

   To ensure that your project is portable, too, Project Builder supports development on several major platforms. To do so, it must ship with a Global Registry that reflects the platform; in other words, the types defined must be found on that platform, and the actions and macros must be written according to the syntax rules of that platform. This means the Global Registry, and, by extension, all user registries and project registry files, are not portable.

   However, you can export information about a project to a text file and import the text file to another platform, as discussed in Section 1.1.3.6, "Sharing and porting project and subproject registry files".

   #### 1.2.4.1 Managing projects across multiple platforms: Project Administrator

   If you are the administrator of a project undergoing development on multiple platforms, you can expect to:

   - Branch off a source control project to contain the code for the platform

   - Export projects and project information to alternate platforms

   ##### 1.2.4.1.1 Branching off a source control project to contain the code for the platform

   Work with your source control administrator to create a branching source control project that enables your team members to isolate the code for the new platform.

   ##### 1.2.4.1.2 Exporting projects and project information to alternate platforms

   Creating an export file for the purpose of distributing a project to another platform is no different from creating an export file to distribute to team members on the same platform. The export file created by Project Builder is a text file, easily transferred to the alternate platform.

   #### 1.2.4.2 Managing project documents across multiple platforms: Team members

   The role of a team member working on development on an alternate or secondary platform is actually quite similar to the role of a team member developing on the base platform. However, there is one major difference: when you receive a project already created on a different platform, you can expect to:

   - Revise customized actions and macros to conform to platform requirements

   ##### 1.2.4.2.1 Revising customized actions and macros to conform to platform requirements

   Equivalent versions of pre-defined actions and macros, where they exist, are provided by Project Builder for all supported platforms. However, if some actions have been customized or new actions created, you will either need to edit the actions to make them work on the new platform or create equivalent new actions.

   ## 1.3 Managing Project Documents During the Test Phase

   Though the test phase is often thought of as separate and distinct from the development effort--first you develop, then you test--testing is a concurrent process that provides valuable information for the development team.

   There are at least three options for integrating Project Builder into the test phase:

   - Your testers do not install Project Builder. You use Project Builder functionality to compile and source-control the modules to be tested and hand them off to the testers, whose process remains unchanged.

   - The testers import the same project or projects that the developers use.

   - You create a project based on the development project but customized for the testers (for example, it does not include support documents, specs, or source), who import it.

   Recommendation: A combination of the second and third options works best. Associating your application with a project can be useful during the testing phase, as well. You can create actions to automatically run test scripts or add script types and make them dependent on the modules they are to test.

   During unit test, testers can use the same project or projects as the developers, if the project is organized by functional units, or separate projects have been created for functional units.The project or projects can also be exported, so unit test can take place in a variety of environments and on a variety of platforms.

   System test might require a new, stripped-down version of the development projects that includes only the modules being tested, especially if you need to concatenate several smaller projects.

   ### 1.3.1 On the development side

   The goal of the development group in this phase of the process is to provide the test group with the modules to be tested in as smooth a manner as possible.

   #### 1.3.1.1 The test phase: Project Administrator

   The tasks involved in creating and exporting a project for testing purposes are the same as the tasks required when creating and exporting a project to a development team:

   - Create a test project based on deliverable modules (optional)

   - Create the test version

   - Export the project to different test environments

   ### 1.3.2 On the test side

   Although members of the test team generally are not responsible for any modifications to the modules of an application, they do have input (modules to test) and deliverables (fully-tested modules and lists of bugs uncovered during the testing phase).

   Project Builder can help the test team keep track of its input and deliverables in the same way it helps development team members.Testers can add scripts and logs to a project, modify actions to include debugging options, and add subprojects containing testing information.

   #### 1.3.2.1 The test phase: Testers

   If you have decided to use Project Builder to help test your application, you'll need to do some preparatory work that is very similar to that of the developers when they are first setting up their projects.You may need to:

   - Import the test project and set up the testing environment

   - Add test scripts and test data to the project

   - Modify actions and macros to facilitate testing

   ##### 1.3.2.1.1 Importing the test project and setting up the testing environment

   The process of importing a test project and setting up a testing environment is the same as the process for importing a project and setting up the environment for development.See Section 1.2.2, "Creating a project", for more information.

   ##### 1.3.2.1.2 Adding test scripts and test data to the project

   You may need to add some items, such as test scripts, to the project.In addition, you may need to add connection strings to database accounts containing test data.

   Remember that you can automate the running of test scripts just as you can automate actions associated with the modules in your application.

   ##### 1.3.2.1.3 Modifying actions and macros to facilitate testing

   If actions specifying "run with debugging" have not already been provided, you can either modify existing actions to include a debug flag, or create new actions.

   ## 1.4 Managing Project Documents During the Release Phase

   When your application has been thoroughly tested and is ready to release, Project Builder can help you simplify the process of delivering the application to customers.

   ### 1.4.1 On the development side

   During the release phase, the development group passes the tested and verified versions of all modules necessary for installation to the releaser.Because Project Builder marks all modules to be included in the final application and associates special commands with them, this hand-off can be automated in the same fashion as other processes, such as compiling your project and source controlling it.

   #### 1.4.1.1 The release phase: Project Administrator

   Once your project has been thoroughly tested and is ready for release, you have one remaining task: package the project.

   ##### 1.4.1.1.1 Packaging the project

   Project Builder provides the Delivery Wizard to help you package your applications as installable components, as well as to:

   - Copy or FTP your completed project to a staging area.From the staging area, you can copy or archive your files to a distribution medium, or make them available internally.

   - Generate the necessary scripts so your project is installable on Windows 95 and NT through the Oracle Installer.You can even package the Forms Developer or Reports Developer runtime environments with your project, so your users can install the entire package--your application, plus the required runtime environment--from a single invocation of the Oracle Installer.

   - Run a customized Deliver action to TAR or ZIP your files.

   The modules actually packaged by the Delivery Wizard are determined by the value of the Deliver file property associated with each item (Yes to include the module in the package, No to leave it out).

   ## 1.5 Deploying Completed Applications

   After you have packaged your application, you're ready to make it available to your customers.In addition to installing your application, your customers will also need to use the Oracle Installer to install the Runtime environment on which your application depends.To simplify the installation process for your customers, both Forms Developer and Reports Developer provide the Oracle File Packager, with which you can make your own application installable with the Oracle Installer on Windows NT and Windows 95.When you've completed the steps in this section, your customers can install everything they need--your application, plus the required Runtime environment(s)--using a single mechanism.

   ### 1.5.1 Before You Begin

   Before discussing how to package your application, it's a good idea to familiarize yourself with the terminology and background information relevant to the installation/packaging process:

   - Section 1.5.1.1, "Terminology"

   - Section 1.5.1.2, "The Oracle Installer files"

   - Section 1.5.1.3, "The contents of the TEMPLATES directory"

   #### 1.5.1.1 Terminology

   This table defines some important terms for the installation/packaging process:

   #####

   Term | Definition
   --- | ---
   Stage (or staging) area | The area on your PC or network where files and installation scripts are prepared, then copied to the distribution media.
   Distribution media | The set of media (for example, tapes, CDs, or diskettes) from which users install your application.
   Installable component | Any product (for example, Forms Runtime, GUI Common Files, and so on) that has its own set of Oracle Installer files (MAP, VRF, INS, and DEI).
   Product file (PRD file) | A file that lists all installable components in a given staging area.
   Oracle File Packager | A wizard that creates the product file and all the Oracle Installer files (MAP, VRF, INS, DEI) needed to make your Windows application installable through the Oracle Installer.

   #### 1.5.1.2 The Oracle Installer files

   The Oracle Installer files control how and where an application is installed (and de-installed) on a user's machine.While the Oracle File Packager creates the Oracle Installer files for you, you may have to make some slight modifications manually. If you just want to look at some sample installer files, take a look at:

   \TEMPLATES\RELEASE\YOURAPP

   \FORMSAPP

   FORMSAPP.MAP
   FORMSAPP.VRF
   FORMSAPP.INS
   FORMSAPP.DEI

   \DEV2KAPP

   DEV2KAPP.MAP
   DEV2KAPP.VRF
   DEV2KAPP.INS
   DEV2KAPP.DEI

   All of these files are text files and should be viewable and editable in a text editor.

   ##### 1.5.1.2.1 The PRD file

   The PRD file lists all the installable components in a given staging area. It also identifies the base filename and location for the Oracle Installer files of each component.In other words, the PRD lists all the files that appear in the Available Products pane of the Oracle Installer. Its name reflects the platform it describes; e.g., WIN95.PRD and NT.PRD.There is one PRD file per staging area, per platform.

   #####

   Column Name | Description
   --- | ---
   #### | Product number.You shouldn't have to modify this.
   Product | A unique name used to identify your application.
   Parent | Leave as "root".
   Filename | Base filename of your MAP, VRF, INS, and DEI installation scripts.
   Version | Version number of your application.
   Interface Label | Name of your application as it appears in the Available Products window of the Oracle Installer.
   Location | Relative path to the directory that contains the installation script files (MAP, INS, VRF, and DEI) and all the files that make up your application.
   Size | Total size of the installable component.Set automatically by the CHECKMAP utility.
   Visible? | Makes the component visible (or not) in the Available Products window of the Oracle Installer.
   Selected? | Makes the component selected (or not) in the Available Products window of the Oracle Installer.
   Open? | Used for parent/child components.You should not need to modify this field.
   Description | Describes your application.
   Volume | Should match what appears in the Filename field.Not used for CD or LAN installations.

   ##### 1.5.1.2.2 The MAP file

   The MAP file is a table that lists all the files that make up your application.

   #####

   Column Name | Description
   --- | ---
   Source | File to be copied to the user's machine.
   Destination | Directory to which the file is copied.
   Group | Program group that will hold the program item(s).
   Item | Name of the item or icon as it appears in the menu.
   Command | Command that is executed when the item or icon is invoked.Appears in the format: command line working_directory alternate_icon Working_directory and alternate_icon are optional, however, if "command line" appears alone, it must end with a semicolon.

   Note: Group, Item, and Command are required only for applications that appear in the Start menu.To see an example of how these fields are filled in, use your OS search capabilities to locate DEVDEM60.MAP, the map file for the Forms and Reports Developer demos. (If you can't find it, you may have to install "Forms Developer [or Reports Developer] Demos and Add-ons" from your Oracle distribution media.)

   ##### 1.5.1.2.3 The VRF file

   The VRF file VeRiFies that all the correct dependencies are identified and installed. For example, by specifying that your application depends on Forms Runtime, your application's installation process will automatically detect whether Forms Runtime is already present on a user's machine.If it is not, Forms Runtime will be installed.

   The VRF file also prompts the user for information, such as where the product should be installed.In addition, the VRF file sets up the user's environment, defining such things as environment variables in the Windows registry.

   ##### 1.5.1.2.4 The INS file

   The INS file INStalls the files that make up an installable component, sets any needed environment variables, and registers the product with the Oracle Installer.It works in coordination with the MAP file and the VRF file.

   ##### 1.5.1.2.5 The DEI file

   The DEI file DEInstalls the files that make up an installable component.It also removes environment variables and unregisters the component after successful deinstallation.It works in coordination with the MAP file.

   #### 1.5.1.3 The contents of the TEMPLATES directory

   The TEMPLATES directory provides everything you need to set up and customize your own staging area. Available on your Oracle distribution media, the TEMPLATES directory contains:

   - The RELEASE subdirectory, which serves as a starting point for creating your own staging area.

   - RELEASE\INSTALLR\INSTALL\WIN95.PRD, a PRD file that lists the installable components for Forms, Reports, and Graphics Runtime environments on Windows 95:

     - Required Support Files

     - System Support Files

     - GUI Common Files

     - Tools Utilities

     - Forms Runtime

     - Reports Runtime

     - Graphics Runtime

   - RELEASE\INSTALLR\INSTALL\NT.PRD, a PRD file that lists the installable components for Forms, Reports, and Graphics Runtime environments on Windows NT (see the previous bullet for a components list).

   ### 1.5.2 Making your application an installable product

   This section contains instructions for creating a one-step or a multi-step installation process for your customers:

   - One-step process: Your customers install your application and the Runtime environment they need from a single PRD file.Another way to think of this is that your customers install everything they need--your application, plus the required Runtime environment(s)--from a single invocation of the Oracle Installer.

   - Multi-step process: Your customers install applications from many different staging areas, each of which has its own PRD file. This approach works well if you need to distribute many Forms Developer or Reports Developer applications, or if the required Runtime environment is already available to your customers from a common area.

   Whichever process you choose, to make your application installable with the Oracle Installer, you will:

   - Copy the TEMPLATES\RELEASE directory from the Oracle distribution media to your machine to serve as a starting point for your own staging area.

   - Use the Oracle File Packager to create the PRD, MAP, VRF, INS, and DEI files you need to make your application installable through the Oracle Installer.

   - Copy your files from your development area to the staging area.From there you can copy the files to your distribution media.

   The rest of this chapter contains specific instructions for completing these tasks.

   #### 1.5.2.1 Deploying your application on Windows

   If your application is installable on Windows 95 and NT, you can use the Oracle File Packager to create the Oracle Installer files and to copy your files from your development area to the staging area. The following steps address both one-step and multi-step installations.

   Step 1: Install the Oracle File Packager

   1. From TEMPLATES\OISFP10 (on your Oracle distribution media), click SETUP.EXE to invoke the Oracle Installer.SETUP.EXE detects which operating system is running and launches the appropriate Oracle Installer.

   2. Select Oracle File Packager from the list of installable products.

   3. Complete the installation process as prompted.

   Step 2: Prepare your staging area

   1. Copy TEMPLATES\RELEASE to a drive on your PC or a networked drive.

   2. Create a subdirectory for your application under TEMPLATES\RELEASE\FORWIN95, even if your application is targeted for the NT environment.

      If you are staging more than one application, create a subdirectory for each.

   Step 3: Move your files to the staging area and create the Oracle Installer files.

   Repeat this step for each staging area you established in Step 2.

   1. From the Start menu, select Oracle for NT or Windows 95, then select Oracle File Packager.

   2. Follow the steps presented in the Oracle File Packager, using the online help to assist you.

   Notes:

   - The internal string you specify in Step 3 is prepended to your Oracle Installer files (MAP, INS, VRF, and DEI).

   - When prompted for the Staging Area Location, specify the subdirectory under TEMPLATES\RELEASE\FORWIN95.

   Step 4: Merge your PRD file with NT.PRD and WIN95.PRD

   This step creates a one-step installation process.If you're creating a multi-step installation, go to Step 5.

   1. Copy the line from your own application's PRD file and paste it into RELEASE\INSTALLR\INSTALL\WIN95.PRD and/or RELEASE\INSTALLR\INSTALL\NT.PRD.

   Step 5: Modify the Oracle Installer files

   1. If you want your application to appear as an icon in the Start menu, add the Group, Item, and Command fields to the MAP file(s) for your application(s). To see an example of how to fill in these fields, use your operating system's search capabilities to find the Oracle Demos MAP file, DEVDEM60.MAP.

   2. If you wish to establish some dependencies for your application, add them to the VRF file.

      For example, if you establish Forms Runtime as a dependency for your application, the installation process will automatically detect whether Forms Runtime is already present on a user's machine. If it is not, Forms Runtime will be installed.

   3. In each staging area, click SETUP.EXE to bring up the Oracle Installer. Examine the files listed in the Available Products pane. If you do not want a file to appear in this pane--for example, a file has already been established as a dependency in the VRF file and does not need to be installed explicitly--edit the staging area's PRD file and change the file's "Visible?" value to false.

   Step 6: Test your installation

   Test your installation on a "clean" machine (a machine with no previously-installed products) that is representative of the projected end-user environment. Do not rely on tests conducted on a developer's machine--that machine may already have files such as icons or libraries that you inadvertently omitted from your map file, or registry settings that were not included in your INS file. This is one of the most common causes of installation problems.

   1. Install your application and make sure it installs the components it should.

   2. Launch the application to make sure it runs correctly.

   3. Test removing your application using the Oracle Installer.

   Step 7: Copy the staging area to your distribution media

   When you are ready to copy your application to CD, tape, diskette, or another medium--or simply to a LAN or other networked machine--be sure you include the entire staging area--that is, TEMPLATES\RELEASE in its entirety. If you include only your subdirectory, the required runtime environment(s) will not be accessible.

| Copyright © 2000 Oracle Corporation. All Rights Reserved. |
Library | Service | Contents | Index