• Managing Developer/2000 Applications
    The Software Development Lifecycle: An Overview 
    The Developer/2000 management strategy 
    About Project Builder 
    Understanding Project Builder terminology 
    How Project Builder affects existing development roles 
    Exploring Project Builder benefits 
    Associating modules with an application 
    Automating actions based on file types
    Creating dependencies between modules
    Assigning default connection strings to modules
    Designating which modules are to be included in the final install set
    Sharing and porting project and subproject registry files
    Accessing other Developer/2000 and third party tools
    Using source control packages with Developer/2000
• Managing Project Documents During Design and Development 
    Installing Project Builder 
    Installing the project and user registries 
    Creating a project 
    Creating a project: Project Administrator 
    Creating a project: Team members 
    Working with projects and project documents 
    Working with projects: Project Administrator 
    Working with project documents: Team members 
    Managing projects and project documents across multiple
• platforms 
    Managing projects across multiple platforms: Project
• Administrator 
    Managing project documents across multiple platforms: Team members
• Managing Project Documents During the Test Phase
  1.3.1 On the development side
  1.3.1.1 The test phase: Project Administrator
  1.3.2 On the test side
  1.3.2.1 The test phase: Testers
  1.4 Managing Project Documents During the Release Phase
  1.4.1 On the development side
  1.4.1.1 The release phase: Project Administrator
  1.5 Deploying Completed Applications
  1.5.1 Before You Begin
  1.5.1.1 Terminology
  1.5.1.2 The Oracle Installer files
  1.5.1.3 The contents of the DEPLOY directory
  1.5.2 Making your application an installable product
  1.5.2.1 Deploying your application on Windows
  2 Deploying Applications on the Web
  2.1 Understanding the Developer/2000 Server
  2.1.1 Introduction to the Developer/2000 Server
  2.1.1.1 The best of the Web and client/server
  2.1.1.2 Three-tiered architecture
  2.1.2 Benefits of the Developer/2000 Server
  2.1.3 Form Builder Web architecture
  2.1.3.1 About the Forms Client
  2.1.3.2 About the Forms Server
  2.1.4 Running Form Builder applications on the Web
  2.1.4.1 Security and encryption
  2.1.5 Report Builder Web architecture
  2.1.5.1 Static Reporting with the Web Wizard
  2.1.5.2 Scheduling Reports with the Reports Server
  2.1.5.3 Dynamic Reporting with the Web Cartridge or CGI
  2.1.6 Graphics Builder web architecture
  2.1.6.1 About the Graphics Client and Graphics Server
  2.1.6.2 About the Graphics Client
  2.1.6.3 About the Web server with Oracle Web Request Broker module
  2.1.6.4 About the Graphics Server
  2.1.6.5 Call and response: Graphics Client and Graphics Server
  2.1.6.6 About display instances and session IDs
  2.1.6.7 About using Graphics Builder parameters in URLs
  2.2 Setting Up the Developer/2000 Server
  2.2.1 Configuring the Forms Server
  2.2.1.1 Step 1: Generating and deploying .FMX files
  2.2.1.2 Step 2: Starting and stopping the Forms Server Listener
  2.2.1.3 Step 3: Making applications available to end users
  2.2.1.4 Step 4: Configuring the Forms Client
  2.2.2 Setting up load balancing
  2.2.2.1 Configuring your Web cartridge for load balancing
  2.2.2.2 Installing the Metrics Server and Clients
  2.2.2.3 Modifying your cartridge base HTML file
  2.2.2.4 Starting the Metrics Server
  2.2.2.5 Starting the Metrics Clients
  2.2.3 Troubleshooting your Form Builder configuration
  2.2.4 Configuring the Reports Server
  2.2.4.1 Step 1: Setting up the Reports Server
  2.2.4.2 Step 2: Setting up the Reports Web Cartridge or Web CGI 2.2.4.3 Step 3: Specifying URL run requests
  2.2.4.4 Step 4 (Optional): Using the URL mapping feature
  2.2.4.5 Step 5: Deploying reports on the Web