admin Comment(0)

Senior Director, Product Management, Oracle Fusion Middleware, Oracle · Foreword by Adam 88 Oracle Fusion Middleware 11g Architecture and Management need to download and use the RCU to create the schemas required by SOA. Master All Aspects of Oracle Fusion Middleware Management Govern a unified Oracle Fusion Middleware 11g Architecture and Management ebook by Reza. Editorial Reviews. About the Author. Reza Shafii is a Senior Principal Product Manager within Oracle Fusion Middleware 11g Architecture and Management (Oracle Press) eBook: Reza Shafii, Stephen (Oracle Press); Due to its large file size, this book may take longer to download Send a free sample.

Language: English, Spanish, Indonesian
Country: Paraguay
Genre: Environment
Pages: 463
Published (Last): 11.11.2015
ISBN: 449-9-20187-866-4
ePub File Size: 18.31 MB
PDF File Size: 16.28 MB
Distribution: Free* [*Free Regsitration Required]
Downloads: 39952
Uploaded by: CHERRY into practice with the help of Oracle Fusion Middleware 11g . We hope these Markus Zirn is Vice President of Product Management for Oracle Fusion Hamza Jahangir is a director of Enterprise Architecture at Oracle , and is . Chapter 3: Code-free Application Extensions and Integrations. PDF [(Oracle Fusion Middleware 11g Architecture and Management)] [Author: Reza Shafii] [Aug] Read Online Download PDF [(Oracle. 10 unique architecture patterns powered by Oracle Fusion Middleware in this Oracle book and eBook.

All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle.

How to Insert a Record To insert a record, perform the following steps: Ensure that you have the cursor positioned on a blank record by performing one of the following steps: Enter the data into the relevant items.

Enter the search criteria to retrieve the appropriate record. Scroll through the records, and stop at the record that is to be updated. Update the record. How to Delete a Record To delete a record, perform the following steps: Scroll through the records, and stop at the record that is to be deleted. Delete the record by performing one of the following actions: Deletes Updates Inserts Memory Making Changes Permanent As previously stated and as depicted by the slide graphics, changes are retained in memory.

To make any inserts, updates, or deletes permanent, you must save commit them to the database. To do this, perform one of the following actions: Discarding Inserts, Updates, and Deletes To discard any inserts, updates, or deletes, you must clear the records roll back instead of saving. Exiting a Run-Time Session You exit the run-time session by performing one of the following actions: By default, you cannot exit the form while you have unsaved updates, inserts, or deletes.

Reza Shafii (Author of Oracle Fusion Middleware 11g Architecture and Management)

You need to either save or undo the changes before you can exit. Example The following is the SQL statement in error and its corresponding error: The following concepts were covered in this lesson: You supply the search criteria. You supply no search criteria. Overview This practice covers the following topics: Overview In this practice session, you start an instance of the Forms managed WebLogic Server to function as a Web server on your local machine.

You run the course application in a browser and execute both unrestricted and restricted queries. You navigate through the application and use it to insert, update, and delete records. Using this knowledge, you can plan and implement the structure of your Forms applications. This is the application-building component of Oracle Forms Developer. You can use Forms Builder to design and store the definitions of form, menu, and library documents. While in the Forms Builder, you can invoke the other component, Forms Compiler.

You must run the Forms Builder component in a graphical user interface GUI environment in order to use its graphical design facilities. After your form is built, use the Forms Compiler. This reads the definition of your module and creates an executable run file. You can also enter these commands on the command line. For example: Commands for invoking the product components vary according to platform.

The files used at run time must already have been compiled by the Forms Compiler component. To test your applications, you can also access Forms Services directly from Forms Builder by setting certain preferences, as described later in this lesson. A module is a major component of your application and is the basis for storage and ownership. A module owns the objects that it contains.

A Forms Developer module can be of the following types, as pictured in the graphics in the slide: As the main component of an application, the form module presents the objects and data that users can see or interact with. Data items in a form are arranged into records. A menu module can consist of a hierarchy of menus, each with selectable items. Forms Builder provides the default menu for every form.

The default menu includes commands for all basic database operations, such as insert, delete, query, and so on. If your application has specific requirements that are not met by the default menu, you can create a custom menu module.

You can use a menu module with multiple forms. An object library is a collection of form objects that you can use in other modules. You can create it to store, maintain, and distribute standard objects that can be reused across the entire development organization.

You can build an application from multiple form modules, menu modules, and library documents as needed. Key Features With Forms Builder you can: You can use Forms Builder to quickly develop form-based applications for presenting and manipulating data in a variety of ways.

Users of Forms Builder applications can: Object Navigator The interface components of the Forms Builder tool help to provide the flexibility and productivity of the Oracle Forms development environment. The Object Navigator, pictured in the screenshot in the slide, is a hierarchical browsing and editing interface.

You can use the Object Navigator to locate and manipulate application objects quickly and easily. Features include: All other nodes and the objects they contain are indented to indicate that they belong to these higher-level nodes.

Property Palette All objects in a module, including the module itself, have properties that you can see and modify in the Property Palette, shown in the screenshot in the slide.

Layout Editor Forms Builder Components: Layout Editor The Layout Editor, shown in the screenshot, is a graphical design facility for creating and arranging interface items and graphical objects in your application. You can use the tool palette and the toolbar available in the Layout Editor to design the style, color, size, and arrangement of visual objects in the application.

The layout can include graphical objects and images. Code objects in Forms Developer include event triggers, subprograms functions and procedures , menu item commands, menu startup code, and packages. Or — Toolbar: Click Connect. When you invoke Forms Builder, a Welcome dialog box appears.

If you click Cancel to dismiss the dialog box, you see the Object Navigator and an empty new module. If you build applications that access database objects, you must connect to a database account from the Forms Builder. Connect to a database if you need to: Enter the database user and password in the Connect dialog box. If not connecting to the default database, provide the necessary connect string or database alias. Oracle Forms Builder automatically displays the Connect dialog box if you try to perform a task that requires connection.

However, menus appear with the same look and feel of your native GUI interface. Feature Description Underline Shortcut key: They can consist of many types of objects, some of which are visible to the user at run time. The three major objects in a form, as shown in the graphics in the slide, are: These are interface objects that present data values to the user or enable the user to interact with the form, depending upon the item type.

There are several types of items. Items are logically grouped into blocks and visibly arranged on canvases. A block is the intermediate building unit for forms. Each form consists of one or more blocks. A block is the logical owner of items, and each item in a form belongs to a block. Items in one block are logically related for example, they may correspond to columns in the same database table or may need to be part of the same navigation cycle. Blocks, therefore, provide a mechanism for grouping related items into a functional unit for storing, displaying, and manipulating records.

A form module can have several canvases such as the pages of a paper form. A canvas can display items from one or more blocks. To see a canvas and its items, you must display the canvas in a window.

A window can have more than one canvas. By default, all canvases in a form appear in the same window which could mean you see only one canvas at a time , but you can assign separate windows for each canvas so that several canvases can be viewed at once. Items in one block do not need to be physically grouped.

They can span many canvases and windows. A canvas is similar to a picture portrait, and a window is similar to a picture frame. Just as you need a picture frame to display a picture portrait, you need a window to display a canvas and its contents. Each item has a sequenced position within its block, and each block has a sequenced position in the form. When a user requests to move to the next item in a block, focus will be set on the next item in sequence, wherever that may be.

Default navigation follows the order of items in a block as listed in the Object Navigator, but you can change this. If the next item is on a different canvas, as shown in the slide, Forms displays that canvas automatically. Similarly, users can request to move to the next block or previous block. If the first item in this block resides on another canvas, that canvas is displayed automatically. If you can already see the item that you want to move to, you may click it.

You can also program mechanisms into the application to enable navigation in other ways. Data Blocks When you build database applications with Forms Builder, many of the blocks will be data blocks. A data block is associated with a specific database table or view , a stored procedure, a FROM clause query, or transactional triggers. If it is based on a table or view , the data block can be based on only one base table, even though the data block can be programmed to access data from more than one table and data sources.

By default, the association between a data block and the database enables the user to automatically access and manipulate data in the database. However, to access data from other tables nonbase tables , you need to write triggers. The graphics in the slide depict the following: Base table source 2.

Single-record data block 3. Trigger access 4. Nonbase table source 5. Multirecord data block 6. Record Oracle Fusion Middleware 11g: These items are data items or base-table items. At run time, you can use standard function keys, buttons, menu options, or standard toolbar options to initiate query, insert, update, or delete operations on base tables, and the subsequent commit of the transaction. Control Blocks A control block is not associated with a database, and its items do not relate to any columns within any database table.

Its items are called control items. For example, you can create many buttons in your module to initiate certain actions, and you can logically group these buttons in a control block. Master Versus Detail Blocks To support the relationship between data blocks and their underlying base tables, you can define one data block as the detail child of a master parent data block. This links primary key and foreign key values across data blocks, and synchronizes the data that these data blocks display.

Forms Builder automatically generates the objects and code needed to support master-detail relationships. As the designer, you need only request it. If your application requires it, you can also create independent data blocks in which there is no relationship between the two data blocks. Single-Record Versus Multirecord Blocks You can design a data block to show one record at a time single-record block or several records at once multirecord block.

Usually, you create a single-record data block to show master block data and a multirecord data block to show detail block data. In either case, records in a data block that are currently not visible on the screen are stored in a block buffer. With more than one data block, you can do the following: You can have one base table per data block.

You can create a large form module with many data blocks, similar to the one shown in the left side of the slide. Alternatively, you can create several smaller form modules with fewer data blocks in each, as shown by the graphic in the right side of the slide.

Generally, a modular application with several smaller form modules has the following characteristics: Here are some points to consider when grouping data blocks in the application: The data blocks cannot be linked by the standard interblock relations.

Navigation between data blocks is handled by default functionality. Navigation between data blocks of different forms is programmed by the designer although mouse navigation to visible items can be automatic.

Triggers can be written at form, block, or item level in a Forms module. A form module is made up of one or more blocks. A data block is based on a database object, such as a table or a view. A data block can contain both data items, which represent columns in the base table, and control items. The dashed lines in the slide represent the relationships between database objects table and column and Forms objects block and item. To be visible to the end user, each item in a block must appear on a canvas.

A frame can be created to arrange data block items on the canvas. Program Units: To be visible to the end user, each canvas must appear in a window. A form module can have one or more canvases and windows.

They are discussed in more detail in later lessons. These associations are shown in the slide by the dotted lines connecting items with canvases and frames and also connecting canvases with windows. There are four tabs in the Preferences dialog box. The screenshot shows the General tab and the preferences that you can set there. To see a description of each preference, click Help in the Preferences dialog box or press the Help key F1 for Windows.

In addition to session preferences, you can also set run-time preferences that apply to running your form from within the builder. To modify preferences, perform the following steps: Specify any options that you require. Click OK to save the changes or Cancel to cancel the changes.

The following table describes one preference on each of the tabs: This option enables you to avoid issuing separate Compile and Run commands each time you modify and run a form.

Subclass Subclassing Path Options for keeping or removing the subclassing path Wizards Welcome Dialog Check box to suppress or display the first Welcome dialog box. There are several similar check boxes. Runtime Array Processing Determines whether Forms Builder processes groups of records at a time, reducing network traffic and increasing performance Oracle Fusion Middleware 11g: The name of the preference file varies on different platforms.

If the preference file already exists, Oracle Forms Developer merges its changes with the existing file. This does not affect preferences for Reports. Each option in the preference file is prefixed by the tool name to which it belongs. Oracle Reports Developer reads the preference file whenever you invoke Reports Builder. The preferences file is an editable text file. If possible, however, you should use the Preferences dialog box to alter the options.

Join Kobo & start eReading today

The graphics in the slide show how to change a preference in the dialog box and the effect it has on the cauprefs. The following table describes the Help menu options in Forms Builder: The Contents tab, shown in the screenshot at the left of the slide, provides access to a variety of manuals and references. There are also Index and Search tabs. Forms on OTN The latest product information on Oracle Technology Network, shown by the middle screenshot in the slide About Form Builder Shown at the bottom right of the slide, this is a separate window that shows product components and their version numbers.

When you are connected to a database server, it also displays similar information for server-side product components. These environment variables must be set on the machine where Forms Builder is installed. For example, on Windows, you set them in the Windows Registry. Java class files: Forms Builder needs access to certain Java classes for some of its features, such as Help, the debugger, and the Java importer. Icon files: Forms Builder enables you to create buttons with iconic images.

You can use. Valid values are ico the default , gif, or jpg. Although you can use. By default, when you run a form from Forms Builder, the parameters that are passed in the URL are hidden. OBR stands for one button run, a term used for running a form from within Forms Builder by clicking the Run Form button. These have default values, all of which you can modify in your own environment for different applications.

Setting Search Paths for Run Time Forms uses some environment variables set on the middle-tier computer to search at run time for files such as forms, menus, and libraries. This enables you to build applications that are portable across platforms and directory structures by avoiding hard-coded paths in file references.

Forms searches the following paths in order until the required file is found: Settings in this file override system settings for running a Forms application. You can also override these settings at run time in the file that controls the Forms run-time environment, which is the default.

Using the Forms environment file makes it easier to deploy the application on any platform.

Fusion 11g free and oracle middleware ebook download architecture management

You can specify which file to use as the environment file in the Forms configuration file, formsweb. You can also set parameters to control which form to run, the user ID, aspects of the Java client and the HTML file that contains the Java applet, and many other settings. The default. In addition to the format masks a developer might explicitly define, Forms Builder uses several of its own internal masks. You can use the following environment variables to specify the values for these internal masks: Each database session within a Forms application has a single database date format mask.

This mask potentially, a set of masks is used to convert a user-entered string into a native format date value. This forces the user to enter values into date items with no format mask in the format exemplified by The RRRR token enables years between and to be entered with the century omitted. This mask converts dates displayed in output, such as lists of values: This mask converts dates displayed in error messages: This makes it easy to test your application in a three-tier environment, with all components appearing and behaving as they would for a user of the application.

By default, the testing occurs on the development computer where Forms Builder is installed, using the default settings in the Forms Servlet configuration file, with no parameters passed on the URL. The screenshots show from top to bottom: Build Applications with Oracle Forms 3 - 35 Testing a Form with the Run Form Button continued You can modify this three-tier testing environment in the Preferences dialog box by performing the following steps: Click the Runtime tab.

Note that it is typically on the same machine where you are running Forms Builder. You can also use the config parameter to specify a named configuration in the Forms Web configuration file formsweb. Set the Web Browser Location needed only if you want to run in a different browser than the default for your machine. If you close the browser without first exiting the form, your session may hang. You will notice this because you may not be able to recompile the same form, but will receive the error: Unable to create form file.

If this happens, you can open Task Manager and end the frmweb process manually. Forms Builder enables screen-based queries, inserts, updates, and deletes of data. A data block is the logical owner of items. Items in one data block do not need to be physically grouped. Items in one data block can span several canvases.

Overview In this practice, you become familiar with Oracle Forms Builder by performing the following tasks: You also run forms from within Forms Builder by using the Run Form button. Each module comprises data blocks that are built using table specifications from the database. This lesson shows you how to create a basic form module and its data blocks.

You also learn how to deploy a form module. Apply standards. Fine tune layout. Set object properties. Add code. Designing Form Modules Test the form module. Create an empty module. Designing Form Modules The following actions, along with the tools that are typically used to perform them, are part of creating a form module although all actions may not be performed for every module: Action Forms Builder Tool Create an empty module.

Object Navigator Create data blocks and items and arrange the items on a canvas. Object Library Fine tune the layout. Layout Wizard or Layout Editor Set object properties. Property Palette Add code. Run Form button Oracle Fusion Middleware 11g: Creating a New Form Module There are several ways to create a new form module. This takes you to the Forms Builder Welcome page that is shown in the slide unless you have changed the Preferences to not display it.

Now perform one of the following steps: Then follow the Layout Wizard steps. This takes you to the Forms Builder Object Navigator automatically creating an empty form module. Objects within a form, and the module itself, have properties that define their behavior.

You can see the properties of an object and their values in the Property Palette of the object. The screenshots show all the properties of a form module as displayed in the Property Palette. To open the Property Palette of an object, perform one of the following steps: A brief description of a selected property appears at the bottomof the palette. To obtain more detailed online Help for any of the properties, select the property and use the Help key F1 , to display a description of that property.

The Property Palette features a toolbar at the top, along with a search box enabling you to easily locate any property. The properties are divided into categories that you can expand or collapse. The properties affect the general behavior of the form and the objects within it.

Properties for a form module include the following: The screenshots show the module name selected in the Object Navigator and the Property Palette synchronized to display the properties of that selected module. The Property Palette shows the Name property, where you can change the name of the form module. It also shows the Coordinate System property with a More button displayed in the value space. Clicking the button invokes the Coordinate Info dialog box, where you can change the Coordinate System properties.

7- oracle fusion middleware 11g build applications with oracle forms vol 1 (1).pdf

Property Description Name Specifies the internal name of the form module, as it appears in the Object Navigator Coordinate System Defines the units used to measure objects in the form and their positions Oracle Fusion Middleware 11g: This name is displayed in the Object Navigator and in the Property Palette. You should change the default name to a meaningful name in either of the following places: Follow Oracle naming rules. Do not give two objects of the same type the same name.

The name cannot include Oracle or Forms Builder—reserved words. The Coordinate System unit for a form can be one of the following: Units are character cells default size taken from the default font settings.

The default unit is point Real. This means that object positions and sizes within the form are measured by this unit.

Points provide fine alignment and consistency across different platforms and video devices. Create a data block with associated data source quickly and easily.

Lay out data block contents for visual presentation. Now that you know how to create a new form module, you need to create new data blocks within it. Block creation involves creating the data block and then laying out its contents for visual presentation. You can create a data block manually or by using the Forms Builder wizards. In this lesson, you learn how to create a new data block based on a database table, using the Data Block Wizard and the Layout Wizard.

The slide shows a magic wand, symbolizing a wizard. Recall that a data block can be based on a table or view, a stored procedure, a FROM clause query, or a transactional trigger. In this course, you use database tables as the source. This requires that you first connect to the database, which you are prompted to do if you use the Data Block Wizard without first connecting.

Connecting to the database was covered in the previous lesson. Launch Layout Wizard. Lay out data block contents. Using the Wizards to Create a Data Block The slide shows the process of creating a new data block by launching the Data Block Wizard, entering the data source, launching the Layout Wizard, and laying out the contents of the data block. You can invoke either wizard in reentrant mode.

Data Block Wizard The Data Block Wizard enables you to create or modify data blocks quickly and easily for use in your application. The wizard can automatically generate code to enforce integrity constraints in the database. Layout Wizard Although the Data Block Wizard enables you to create a new data block easily with its associated data sources, it does not deal with the visual presentation of objects included in the data block.

After you create the data block, you need to lay out its contents for user interaction.

11g architecture ebook download free management middleware oracle fusion and

To accomplish this task quickly and easily, use the Layout Wizard. The wizards are not the only way to perform a task such as building a data block, but they are usually the simplest. You can build a block manually instead of using the wizards. Invoke online Help. Save without exiting.

Save and exit. Previous screen Next screen Available only in reentrant mode Tabbed interface: If you click Next or Back before entering all necessary information for a particular wizard page, the wizard prevents you from navigating to another page. Similarly, if you have not entered all necessary information when you click Apply or Finish, the wizard automatically takes you to the page where you can finish entering the required information. In reentrant mode, which enables you to modify existing blocks or layouts, the wizards have a tabbed interface that enables you to quickly navigate to the section you want to modify.

The screenshots show the Tools menu, the context menu, the Data Block Wizard option, and the toolbar. Type Page Data Block Wizard: The Data Block Wizard consists of several pages.

To create a new data block, you must interact with each page. Welcome Page Click Next to continue. Type Page shown in the screenshot Choose between one of two data source types: Table Page Data Block Wizard: Table Page On the Table page shown in the screenshot: Enter the table or view name for the data source name, or click Browse and select a name from a dialog box.

Click Refresh to display a list of columns in the selected table or view. If you are not connected to the database, the Connect box is displayed. Select the columns you want to include in the data block. To select more than one column, press and hold Ctrl and then select the columns.

Click the double-right arrow or the double-left arrow to include or exclude all columns, or click the right arrow or the left arrow to include or exclude selected columns only. Select the Enforce data integrity check box if you want the wizard to enforce the database integrity constraints.

If there is at least one other existing block in the current module, the next page that displays is the Master-Detail page, where you can associate the new data block with other master data blocks. Finish Page Data Block Wizard: Click Finish to create the new data block and immediately invoke the Layout Wizard. You have the option of exiting the Data Block Wizard at this stage, without immediately invoking the Layout Wizard.

If you do so, you can either lay out the data block manually or invoke the Layout Wizard at a later time to lay out the items of a data block. Launching the Layout Wizard To launch the Layout Wizard to create a new layout, perform one of the following steps: The screenshot at the top of the slide shows the last page of the Data Block Wizard that can optionally launch the Layout Wizard.

The other screenshots show invoking the Layout Wizard from Tools menu, the context menu, and the toolbar. Canvas and Data Block Pages Use the Layout Wizard to lay out the data block items for visual presentation quickly and easily.

The Layout Wizard consists of several pages.

You must interact with each page. Canvas Page 1. Select New Canvas from the Canvas pop-up list to get a new canvas on which to display the data block items. Select Content as the canvas type in the Type pop-up list. Data Block Page shown in the screenshot 1. Select the items that you want to display in the data block frame.

Click the double-right arrow or double-left arrow to include or exclude all items, or click the right arrow or the left arrow to include or exclude selected items only. You can also drag selected items from one list to another. To lay out the items in a particular sequence, drag the items into that sequence.

You can use the Item Type pop-up list to select a type for each item. The default type is Text for each item. An item type can also be changed later to something else, such as a pop-up list or a radio group. Items and Style Pages Items Page Specify prompt text and display width and height for each display item. Style Page Select a layout style for your frame. Your options are: Records and Finish Pages Records Page shown in the screenshot 1.

Enter a title in the Frame Title field. Enter the number of records that you want to display at run time in the Records Displayed field. Enter the physical distance in the coordinate system unit of the form between records if you are displaying more than one record at a time. You can select the Display Scrollbar check box to display a scroll bar next to the frame common for multirecord data blocks.

Finish Page Click Finish to create a new frame and lay out the selected items for the new data block. The Layout Wizard steps are complete. After you complete the Layout Wizard steps, you can view the layout in the Layout Editor, where you can customize or modify the layout if necessary.

These values can be modified to change the behavior of the form. In addition, Forms Builder may create triggers to validate user input if you select the Enforce data integrity check box on the Table page of the Data Block Wizard.

Templates typically include generic objects, such as graphics, toolbars, and program units. You can define standard window layouts, standard toolbars, and other common objects that you want to include in new forms.

Creating a Form Based on a Template To create a form based on a template, perform one of the following: After choosing to use a template, Forms Builder presents you with a file dialog where you can browse to the form you want to use as a template. Both of these options display the Save As dialog box for the initial save. In the dialog box, do the following: Enter a file name. Navigate to the directory where you want to save the file. Click Save. The screenshots show the menu option, the toolbar, and the Save As dialog box.

This saved definition of a form in the file system is not executable, and can be opened only by Forms Builder. When you execute a Save command, only the current module is saved. Compiling a form or menu module creates the needed executable file. There are several ways to compile a form: Each of these options is depicted in the screenshots in the slide. Compiling and saving are two independent tasks. Performing one does not automatically accomplish the other.

Action Type of Compilation 1. Explicit 2. Launch the Forms Compiler component from the command line or the Windows Run dialog box frmcmp. Explicit 3. Launch the Forms Compiler component from the Windows Start menu.

Explicit 4. Set the Build Before Running preference. Implicit Oracle Fusion Middleware 11g: The executable application files. The graphics in the slide show the various file types. Move module files to middle tier. Generate module on middle tier.

Run in browser using Forms Services on middle tier. This machine may be running on a different platform; if so, you need to recompile the module after you transfer it to the middle tier. You can use an FTP utility to move the. If the platform is the same as your development platform, you can move the. If it is a different platform, you can invoke the Forms Compiler on the middle tier to recompile the module files, as shown in the slide.

After the executables have been placed on the middle tier, you can invoke the application in a browser, using a URL that points to the Forms Servlet on the middle-tier Web server. Producing Text Files and Documentation The files normally produced by saving and generating modules are in binary format. To convert a binary file to text, perform the following: This opens the Convert dialog box.

In the Convert dialog box: To produce documentation for your module, perform the following: Select the module to be documented in the Object Navigator. You can also produce documentation in other ways not covered in this course: Overview In this practice, you create a new form module.

You create a single-block form that displays a single record. Forms Developer gives you the ability to quickly define additional data blocks and to define relations between the new blocks and any existing blocks in the form. This lesson shows you how to create a master-detail form and how to modify a data block and its layout.

Each data block can stand alone or be related to another data block. The slide shows the following: The master data block is based on the table with the primary key, and the detail data block is based on the table with the foreign key.

A master-detail relationship equates to the one-to-many relationship in the entity relationship diagram. A Detail Block Can Be a Master You can create block relationships in which the detail of one master-detail link is the master for another link. Examples The following are examples of the master-detail structure: Master-Detail Page You can build a master-detail form module either by creating a relation between a master and detail block explicitly or by using the Data Block Wizard to create it implicitly.

Follow the same steps as before to create a new data block in the Data Block Wizard until you come to the Master-Detail page, shown in the slide. On this page, select the Auto-join data blocks check box and click Create Relationship. If the Auto-join data blocks check box is not selected, the Data Block dialog box is displayed with a list of all data blocks in the form without any foreign key constraint names. Master-Detail Page continued 4.

Select a master data block in the Data Block dialog box and click OK. The wizard automatically creates the join condition between the detail and master data blocks in the Join Condition field and displays the name of the master data block in the Master Data Blocks field. If the Auto-join data blocks check box is not selected, the wizard does not automatically create the join condition between the detail and master data blocks.

You must use the Detail Item and Master Item pop-up lists to create a join condition manually. Click Next, and then complete the Data Block Wizard steps.

The master data block must exist in the form module before you create the detail block. You can also create a relation by invoking the Data Block Wizard in reentrant mode. This object is called a relation.

The following tasks occur automatically: The screenshot shows the following objects that are created in the Object Navigator for a relation: Explicit Relations If a relation is not established when default blocks are created, you can create your own. To explicitly create a relation, perform the following steps: Select the Relations node under the master block entry in the Object Navigator.

Click the Create icon. The New Relation window is displayed. Specify the name of the detail block. Choose your master delete property. Choose your coordination property. Specify the join condition. The new relation, new triggers, and new program units are highlighted in the Object Navigator. Do not precede names with colon. The example shows the condition: Cannot delete master record if detail records exist Running a Master-Detail Form Module When you run your master-detail form module, you will find that: You can change the above behavior by modifying the relation object properties.

Only master is deleted Cascading: Master and all details are deleted Non Isolated: If no detail record, master is deleted Non Isolated: For example, you can delete all corresponding line items when an order is deleted. The graphics show what happens to master and detail records with different settings of the Delete Record Behavior property, as described in the text beside each graphic. Although deleting with the cascading property may remove many detail records, the commit message shows only the number of records deleted from the master block.

Property Value Use Non Isolated Prevents the deletion of the master record when detail records exist; the master record is deleted only if no detail records exist Cascading Deletes the detail records when a master record is deleted Isolated Deletes only the master record Oracle Fusion Middleware 11g: The screenshots show the block-level triggers in the Object Navigator when the Delete Record Behavior property is set to: For example, you can defer querying the line items for an order until the operator navigates to the item block.

Coordination Property Use Default depicted in first slide graphic Forces coordination of blocks to occur whenever the master record is changed by a user or a trigger Deferred with Automatic Query depicted in second slide graphic Postpones potentially expensive detail query processing until the cursor visits the related blocks Deferred without Automatic Query depicted in first third graphic Allows entry of additional query criteria in the detail block before querying Prevent Masterless Operations Ensures that the detail block cannot be queried or used to insert records when a master record is not displayed Oracle Fusion Middleware 11g: Select frame or object in the Layout Editor, or data block or frame in Object Navigator.

Change property values. Modifying the Structure of a Data Block After you create a data block, you may want to customize or modify it by performing one of the following: Use reentrant mode to modify the data block, even if the block was not originally created with the Data Block Wizard.

To invoke the Data Block Wizard in reentrant mode, perform the following steps: Select the frame or a component of the block in either the Object Navigator or the Layout Editor. Invoke the Data Block Wizard by performing one of the following steps, depicted in the screenshots: Change values. Modifying the Layout of a Data Block You may want to customize or modify the layout of the data block items on the canvas.

You can do this by performing one of the following steps: Use reentrant mode to modify the layout of items in an existing frame, even if the frame was not originally created with the Layout Wizard.

Select the appropriate frame in the Object Navigator under the Canvases node or in the Layout Editor. Before you reenter the Layout Wizard, it is important to select the correct frame in the Object Navigator or the Layout Editor.

If you overlook this when you reenter the Layout Wizard, you may create an additional frame instead of modifying the current frame. Either method takes you to the Data Block page in the Layout Wizard. Use Next and Back as you do when not in reentrant mode, or go directly to a certain page by clicking its tab. Overview In this practice, you create a new form module that displays the master-detail information.

Create a third data block that is not related to any other block in the form module. Use the Forms Builder wizards to create all three data blocks. You also learn how to include blocks that are not associated with the database. You can modify data block and layout properties through the reentrant wizards, as explained in the previous lesson.

If the object appears on a canvas, you can modify properties by using the graphical Layout Editor. You can set individual properties for each Forms Builder object in its Property Palette. The wizards, the Layout Editor, and the Property Palette all depict object properties. Changes made in one tool are reflected in the others. Property Palette 2. Reentrant layout wizard 3. Layout Editor You can use the Property Palette to control the behavior and appearance of any Forms Builder object with a greater degree of granularity.

In the Property Palette, you can fine-tune objects that you have initially created in the wizards or the Layout Editor. When an object is first created, it is automatically assigned several property values by default. You can change these property values in the Property Palette. To display the Property Palette of an object, use one of the following methods: From the pop-up menu, select the Property Palette option, as shown in the second screenshot.

Press F1. Property Palette: Features The following are the features of the Property Palette: The screenshots show each of these features of the Property Palette and the Help window for a particular property. Feature Description Property list Displays a two-column list of names and values of properties that are valid for a particular object. Properties are grouped under functional headings or nodes. You can expand or collapse a node by using the plus and minus icons beside the node name.

Find field Enables you to quickly locate a particular property. The Search Forward and Search Backward buttons enhance your search. Toolbar Consists of a series of buttons that provide quick access to commands Help Enables you to obtain description, usage, and other information about any property by pressing F1 with the property selected Oracle Fusion Middleware 11g: Properties are manipulated differently, depending on the property type.

The following is a summary of the controls that are used in the Property Palette: Property Control Description Text field A Text field is displayed where the current property can be set by entering a text value.

For longer text values, an iconic button also appears, enabling you to open a text editor, as shown in the top-left screenshot in the slide. Pop-up list This appears where a fixed set of values, such as Yes or No, is allowed for the property. Click the down arrow to open the list, as shown in the bottom- left screenshot, and then select a value.

Click the button in the property value column to invoke an LOV, as shown in the screenshot at the right of the slide. More button Use this when more complex settings are needed. Click More to open the extra dialog box, similar to the example in the screenshot at the top-left of the slide. The following is a summary of these icons and their description: After you activate the Property Palette, its window remains open until you close it. The window automatically displays the properties of each object you visit in the Layout Editor or the Object Navigator.

This is because, by default, the list of properties in the Property Palette is synchronized whenever you select an object. Icon Description Circle Specifies that the property value is the default value Square Specifies that the property value has been changed from the default Arrow Specifies that the property value is inherited Arrow with a cross Specifies that the property value was inherited but has been overridden Oracle Fusion Middleware 11g: Overview A visual attribute is a named set of properties defining: Overview Visual attributes are the font, color, and pattern properties that you set for form and menu objects.

The screenshots show dialogs boxes for setting font, fill color, and fill pattern. You can create a named set of such properties; this named set is called a Visual Attribute, which is another object that you can create in the Object Navigator with properties such as font, color, and pattern combinations. Set the Visual Attribute Type property of the Visual Attribute to Title if you plan to apply it to objects such as frame titles, or to Prompt if it is used for prompts.

Otherwise, set Visual Attribute Type to Common, which is the default. Every interface object in a Forms application has a property called Visual Attribute Group, which determines how the individual Visual Attribute settings of an object are derived. Blocks have a Current Record Visual Attribute Group property that defines the Visual Attribute to be used for the current record in the block.

Register for an account and access leading-edge content on emerging technologies.

Related Interests

Register now. Packt Logo. My Collection. Deal of the Day Create dynamic dashboards to bring interactive data visualization to your enterprise using Qlik Sense. Sign up here to get these deals straight to your inbox. Find Ebooks and Videos by Technology Android.

Packt Hub Technology news, analysis, and tutorials from Packt. Insights Tutorials. News Become a contributor. Categories Web development Programming Data Security. Subscription Go to Subscription. Subtotal 0. Title added to cart. Subscription About Subscription Pricing Login. Features Free Trial. Search for eBooks and Videos. Oracle Fusion Middleware Patterns. Are you sure you want to claim this product using a token? Harish Gaur et al. September Quick links: What do I get with a Packt subscription?

What do I get with an eBook? What do I get with a Video? Frequently bought together. Learn more Add to cart. Paperback pages. Book Description In today's business environment, the needs of Enterprises are rapidly changing and these changes demand an unprecedented level of adaptation and innovation. Table of Contents Chapter 1: Chapter 2: Process-driven SOA Development. Chapter 3: Code-free Application Extensions and Integrations.

Programming code-free application extensions and integrations—the platform. Beyond the travel authorization solution—an approach for other applications. Chapter 4: Chapter 5: Chapter 6: Chapter 7: Building Intelligent Processes with Insight-driven Agility.

Business Intelligence meets Service-Oriented Architecture. Business Scenario: Insightful processes for vehicle remarketing at Motability Operations. Chapter 8: Building Enterprise 2. Wind River's Enterprise 2. Chapter 9: Chapter Rocky road: A trucking company's outdated infrastructure. Authors Harish Gaur. Markus Zirn. Srikant Subramaniam. Nam Doan-Huy. YiHong Xu. Narshimha Rao Kondapaka. Melody Wood.

Ross Sharman. Juliana Button. Matt Miller. Mark Simpson. Kiran Dattani. Milind Pandit. Nikhilesh Chitnis. Sandeep Banerjie. Mark Farabaugh. Sri Ayyeppen. John Chung. Mike Blackmore. Hamza Jahangir. Basheer Khan. Rex Thexton. Nishidhdha Shah. Read More. Read More Reviews. Recommended for You. Oracle Service Bus 11g Development Cookbook.

A Hands-On Tutorial. All Rights Reserved. Contact Us. View our Cookie Policy. We understand your time is important.