R12 d49656 gc10-apps dba 04

Editor's Notes

• #2: Schedule: Timing Topic 60 minutes Lecture 0 minutes Practice 60 minutes Total
• #3: <Course name> <Lesson number> - Instructor Note : The Applications technology stack refers to the whole range of components that constitute an Applications installation, whereas the Applications Technology layer is a collection of utility products whose functionality is applicable to all Oracle Applications modules.
• #4: <Course name> <Lesson number> - Overview This module covers the different tiers and components of Oracle Applications Release 12. Some will be described in greater detail than others.
• #5: <Course name> <Lesson number> - Multi-tier Architecture In the multi-tier model, functions of the Oracle Applications architecture are distributed among multiple levels, or tiers . Although many machines may be used in an installation, scalability is derived from the logical division of processing capabilities across three distinct levels: the desktop (or client) tier, the application (or middle) tier, and the database tier. The tiers referred to are virtual, and do not represent physical machines. Each tier can consist of one or more machines (often called nodes ). This is particularly true of the application tier, where the various servers (groups of processes that run on a single machine and provide a particular functionality) are often divided between several machines. Equally, a node can accommodate more than one tier. For example, the database server can reside on the same node as one or more of the servers in the application tier.
• #6: <Course name> <Lesson number> - Desktop Tier The client interface is provided through either the newer HTML interface or the traditional Forms interface. The HTML interface products require only a Web browser on the desktop tier. For the Forms interface products, an additional component, the Forms Client Applet, is used in conjunction with the Web browser. The Forms Client Applet downloads the necessary JAR files on demand, and they are cached locally for future use.
• #7: <Course name> <Lesson number> - Forms Client Applet The Forms Client Applet is a general-purpose presentation applet that supports Oracle Applications products that use the Forms interface, including those with customizations and extensions. The Forms Client Applet is packaged as Java Archive (JAR) files, which contain all Java classes typically required to run Oracle Applications forms. The Forms Client Applet displays Oracle Applications screens, and supports field-level validation, multiple coordinated windows, and data entry aids such as lists of values (LOVs). The Forms Client Applet sends user requests to the forms server, and handles responses such as screen updates. Required and commonly used JAR files are downloaded from the Web server at the beginning of the client’s first session. Afterwards, they remain in the client’s local disk cache, ready for future sessions. When updated versions of the JAR files are installed on the application tier, they are automatically downloaded to the desktop via the Java-enabled Web browser. Less commonly used JAR files are downloaded on demand.
• #8: <Course name> <Lesson number> - Desktop Java Client The Forms client applet must run within a Java Virtual Machine (JVM) on the desktop client. The Sun J2SE Plug-in component allows use of the Oracle JVM on web clients, instead of the browser's own JVM. This component is implemented as a browser plug-in. In the traditional, Forms-based Oracle Applications environment, the JVM was run as part of the standard Applications sign-on process. Now, with the move to a mainly HTML-based environment, the JVM (now the J2SE Plug-in) is only invoked when a user chooses to access functions that require it, such as running a form. If the J2SE Plug-in has not been installed, the browser prompts the user to download the required installation executable. The slide shows the Java console, which can be displayed by selecting “Show console” on the “Advanced” tab of the J2SE plug-in control panel. This can be useful in diagnosing problems with JAR file downloads. Instructor Note: The J2SE plug-in replaces Oracle JInitiator, which was used to provide a JVM in Release 11 i .
• #9: <Course name> <Lesson number> - Application Tier The application tier, sometimes referred to as the middle tier, hosts the various services and servers that implement and execute the business logic, and mediates communications between the desktop tier and the database tier. The following services and servers make up the application tier: Web Services Forms Services Concurrent Processing Server At present, Web Entry Point Services, Web Application Services, and Root Services must all be installed on the same node. Instructor Note: Release 12 introduces a number of significant changes to the way Applications services are implemented. For further details, see Oracle MetaLink Note 406558.1, Configuring Applications Node Services in Oracle Applications Release 12 .
• #10: <Course name> <Lesson number> - Load Balancing The application tier supports load balancing among many of the servers to provide high availability, fault tolerance, reliability and scalability. Wherever possible, you should use the same platform (such as Linux) for all application tier machines. Do not attempt to use a mixture of UNIX and Windows machines. As well as having to manage patches for the disparate platforms, there are technical limitations. Instructor Note : Load balancing is covered in more detail in the module Advanced Configuration Options .
• #11: HTML-Based Applications The HTML-based applications (formerly known as Self-Service Applications) have the following characteristics: • Do not use Oracle Forms for the interface • Are designed in pure HTML and JavaScript • Dynamically generate HTML pages by executing Java code • Use a metadata dictionary for flexible layout • Operate by direct connection to the Web server
• #12: <Course name> <Lesson number> - Oracle Applications Framework The Oracle Applications Framework is the development platform for HTML-based applications. It consists of a Java-based application tier framework and associated services, designed to facilitate the rapid deployment of HTML-based applications. The Framework-based applications logic is controlled by procedures that execute through the Java servlet engine, which is provided by the Apache JServ module. The servlet engine uses the metadata dictionary in constructing the Framework UI.
• #13: <Course name> <Lesson number> - Oracle Applications Framework Components AOL/J (AOL Java) provides the Oracle Applications Framework with underlying security and Applications Java services. It provides the Oracle Applications Framework with its connection to the database and with application-specific functionality, such as flexfields and attachments. BC4J (Business Components for Java), included in Oracle JDeveloper, is used to create Java business components for representing business logic. It also provides a mechanism for mapping relational tables to Java objects and allows the separation of the application business logic from the UI. The Java controller processes the programmatic UI definition. The Apache JServ module provides the Java servlet engine, which uses the metadata dictionary to construct the Framework UI. The HTML UI generator, UIX.
• #14: <Course name> <Lesson number> - Oracle Applications Framework Processing With Oracle Applications Framework, an HTML-based Applications module uses the following access path: The user clicks on the hyperlink of a function from a browser. The browser makes a URL request to the Web listener. AOL/J validates user access to the page. The page definition is loaded from the Metadata Dictionary on the database tier into the application tier (Metadata UI Definition). The BC4J objects that contain the applications logic and access the database are instantiated. The Java Controller programmatically manipulates the page definition as necessary, based on dynamic UI rules. UIX (HTML UI Generator) interprets the page definition, creates the corresponding HTML in accordance with UI standards, and sends the page to the browser.
• #15: <Course name> <Lesson number> - Java Servlet Access with HTML Applications When using a JavaServer Page (JSP), the HTML interface module uses the following access path: The user clicks the hyperlink of a function from a browser. The browser makes a URL request to the Web listener. The Web listener contacts the servlet engine (JServ) where it runs a JSP. The JSP obtains the content from the Applications tables and uses information from the metadata dictionary to construct the HTML page. The resulting HTML page is passed back to the browser via the Web server.
• #16: <Course name> <Lesson number> - Forms Services The Forms services component hosts the Oracle Applications forms and the Forms runtime engine. Acting as the engine of the Oracle Applications Forms-based interface, the Forms services component mediates the communication between the desktop client and the Oracle database server. It manages the display of information in the client browser, and also updates the database as necessary. Where applicable, the Forms services component caches data and provides it to the client as needed. For example, this feature is used when scrolling through multiple order lines that cannot be displayed on a single screen. By default, Forms services in Oracle Applications Release 12 are provided by the Forms listener servlet, a Java servlet that delivers the ability to run Oracle Forms applications over HTTP or HTTPS connections. It hosts the Oracle Applications forms and associated runtime engine, mediating the communication between the desktop client and the Oracle database server, displaying client screens, and initiating changes in the database according to user actions.
• #17: <Course name> <Lesson number> - Forms Services Architecture The Forms services architecture is essentially a three-tier architecture: The Forms client applet is located on the desktop. The user passes information to the application tier by entering text in a field or clicking a button. The application tier hosts the user interface logic that determines the response needed when a user initiates an action. For example, this may be to open a new window, run a query, or populate a related field. The database tier hosts the database and data-intensive logic. It is contacted to retrieve data not already cached on the application tier, or where additional processing is needed. In this configuration, where all logic is located on the servers, software updates need only be performed in one data center, and are immediately accessible to users via a LAN, WAN, or even a dial-up connection. To minimize network traffic, the Forms client applet is downloaded automatically the first time a user accesses Oracle Applications. The applet is then stored on the desktop, so does not need to be downloaded with each subsequent connection to Oracle Applications.
• #18: <Course name> <Lesson number> - Low Network Traffic Forms listener servlet can communicate with the desktop client using these network protocols: • Standard HTTP network connection • Secure HTTPS network connection • TCP/IP connection By default Oracle Applications Release 12 utilizes Forms listener servlet mode. However, socket mode is still fully supported, and its use may be required in a WAN environment, to optimize performance. Instructor Note: For further details of socket mode, see Oracle MetaLink Note 384241.1, Using Forms Socket Mode with Oracle E-Business Suite Release 12.
• #19: <Course name> <Lesson number> - Low Network Traffic Once a connection is made, many operations can be performed on the client either without contacting the Forms services at all, or with minimal interaction. For example, if a user is entering data for specific field items, there is no need to update an entire screen when only a few fields are updated. In this scenario, only the changed fields are updated with the new values. Consequently, this is much more efficient than a full screen painting application. Instructor Note : Network features are covered in more detail in the module Advanced Configuration Options .
• #20: <Course name> <Lesson number> - Concurrent Processing Server Most user interactions with Oracle Applications data are conducted via the HTML interface or the Forms interface. However, some reporting and updating programs may need to be run either periodically or on an ad hoc basis. As these programs may require a large number of computations, they are run in the background at a time, and with a priority, such that the work of interactive users is not impeded. Such programs are run on the Concurrent Processing server. You submit a request to run a concurrent program through an Oracle Applications form. The request inserts a row into a database table, specifying the program to be run. Concurrent managers read the applicable requests in the table and start the relevant concurrent programs. Note: Log and output files from concurrent programs are generated on the Concurrent Processing server. These should be monitored for errors, and archived or deleted when no longer needed. Failure to do so will eventually result in a shortage of disk space.
• #21: <Course name> <Lesson number> - Report Review Agent The log or output file that results from a concurrent request is sent to a utility known as the Report Review Agent , which passes a file containing the entire report to the Forms services, which passes the report back to the user’s browser one page at a time.
• #22: <Course name> <Lesson number> - Accessing Concurrent Processing Output 1. The Concurrent Processing server communicates with the data server using Oracle Net. 2. The resultant concurrent program log or output file from a request is passed back as a report to the Report Review Agent. 3. The Report Review Agent passes a file containing the entire report to the forms server. 4. The Forms Services component passes the report back to the user’s browser one page at time. Profile options can be used to control the size of the files and pages passed, to suit report volume and available network capacity.
• #23: <Course name> <Lesson number> - Administration Server The term Administration server is a historical one: there is no such component in the Release 12 architecture. By default, any application tier node can be used to carry out the following operations: Applying database patches to Oracle Applications - Most patches consist of files and scripts that update the file system and database objects. You use the AutoPatch utility (adpatch) to perform these updates. AutoPatch may also be used to apply cumulative patches such as minipacks and maintenance packs. Maintaining Oracle Applications data - Some features require regular maintenance to ensure that the system is operating optimally. The AD Administration utility (adadmin) enables you to carry out this and other file system and database maintenance tasks.
• #24: <Course name> <Lesson number> - Database Tier The database tier contains the Oracle database server, which stores all the data maintained by Oracle Applications. The database also stores the Oracle Applications online help information. The database server does not communicate directly with desktop clients, but rather with the servers on the application tier, which mediate communication between the database server and the clients.
• #25: <Course name> <Lesson number> - Oracle Homes The Applications Release 12 architecture utilizes three ORACLE_HOMEs: The 10g Release 2 (10.2) Database Server ORACLE_HOME replaces the Oracle9 i ORACLE_HOME used in Release 11 i . The Application Server 10.1.2 ORACLE_HOME (sometimes referred to as the Tools, C, or Developer ORACLE_HOME) replaces the 8.0.6 ORACLE_HOME in Release 11 i . The Application Server 10.1.3 ORACLE_HOME (sometimes referred to as the Web or Java ORACLE_HOME) replaces the iAS ORACLE_HOME in Release 11 i . Instructor Note : This is a key change from Release 11i .
• #26: <Course name> <Lesson number> - Oracle Homes The slide summarizes the Oracle Home architecture in Release 12. Instructor Note : This Oracle Home reorganization represents a significant change to the architecture. For more details, see Chapter 2 of Oracle Applications Concepts.
• #27: <Course name> <Lesson number> - Oracle Applications Technology Layer The Oracle Applications technology layer is an integrated collection of components whose functionality is applicable to all Oracle Applications modules. Components in the Oracle Applications technology layer include: Applications DBA (AD) Application Object Library (FND) Applications Utilities (AU) Workflow (WF) Alert (ALR) OA Framework (FWK) Oracle XML Publisher (XDO)
• #28: <Course name> <Lesson number> - Oracle Applications DBA (AD) The Applications DBA product provides a set of tools for administration of the Oracle Applications file system and database. AD tools are used for installing, upgrading, maintaining, and patching the Oracle Applications system. The AD utilities include: AD Administration - Performs general maintenance tasks for Oracle Applications. AD Merge Patch - Merges multiple patches into a single, integrated patch. AutoConfig - Manages configuration changes in an Oracle Applications system. AutoPatch - Applies patches and adds new languages and products to an Oracle Applications system. Rapid Clone - Used to clone an Oracle Applications system. Rapid Install - Sets up a fully configured Oracle Applications system, including the latest certified technology stack and all patches, minipacks, and other updates.
• #29: <Course name> <Lesson number> - Oracle Application Object Library (FND) The Oracle Application Object Library is a key component of the Applications technology layer. It consists of a collection of reusable code, programs, and database objects that provides common functionality across all products. Oracle Application Object Library offers many features to facilitate system administration. These include: Security setup and maintenance features. Management of concurrent processing. Uniformity between products of flexfield processing and procedures for report submission. Capability to allow the creation of custom programs that interact with the base Applications modules.
• #30: <Course name> <Lesson number> - End User Features Oracle Application Object Library includes several features that help provide uniformity of function across the various Applications products: Standard user interface - The Application Object Library supports the integration of Oracle Applications by providing standardized functionality and capabilities across all products so that the look and feel do not vary from product to product. Shared flexfield value sets - Flexfields allow the entry of certain important information to be standardized across all products. One example is the Accounting flexfield, which is used by Financials products and Manufacturing products. Standard Report Submission (SRS) - The procedure to submit a background report to the concurrent manager using SRS is the same regardless of the product that owns the report. SRS takes advantage of shared flexfield value sets. Applications Online Help - The presentation of Applications Online Help is also standardized across all products and accessed through a browser. Profile options - Applications Object Library allows you to configure Oracle Applications easily by setting certain profile options.
• #31: <Course name> <Lesson number> - Developer Features Application Object Library provides many features for developers creating custom forms, reports or programs that interface with Oracle Applications. GUI and coding standards - The same coding and Graphical User Interface (GUI) standards used by Oracle Applications developers are available to custom developers. Standard Report Submission - Custom reports can be integrated into Standard Report Submission so that they can be submitted and monitored using the same procedures as other Oracle Applications reports. Developers can set up certain menus and responsibilities to access custom reports or standard objects. Flexfield development - Flexfields used in custom forms can take advantage of existing flexfield capabilities such as value sets, validation, and security rules. Custom menus and responsibilities - Custom menus and responsibilities can be seamlessly integrated with Oracle Applications. Detailed information on custom features for developers is available in the Oracle Applications Developer’s Guide.
• #32: <Course name> <Lesson number> - System Administration Features Oracle Application Object Library provides many features to simplify administration of Oracle Applications, enabling the system administrator to carry out routine tasks quickly and easily. These features include the ability to: Set up new users - Register new Oracle Applications users and give them access to only those forms, functions, and reports they need to do their jobs. Manage and control security - Decide which users have access to each product, and within a product, which forms, functions, and reports a user can access. Audit user activity - Monitor what users are doing and when. Choose who to audit and what type of data to audit. Set user and system profiles - A profile is a set of changeable options that affects the way Oracle Applications looks and behaves. A system administrator can set profile values at the site, application, responsibility, and user levels. Manage concurrent processing - A system administrator can monitor and control concurrent processing using various interfaces, including forms and Oracle Applications Manager (OAM). Instructor Note : These topics are covered in detail in the Oracle Applications System Administration classes, such as R12 System Administration Fundamentals.
• #33: <Course name> <Lesson number> - Application Object Library Security Application Object Library controls access to the data in Oracle Applications via user sign-ons and responsibilities. Each user must have a user name and password to gain access to Oracle Applications. A responsibility is a level of authority in Oracle Applications that lets Applications users access only those functions and data appropriate to their role in the organization. Responsibilities allow access to a specific product, operating unit, set of books and a restricted list of windows, functions, reports, and groups of products, or data groups. The forms available from the navigation menus vary by responsibility. For example, the Purchasing User navigation menu does not include all the forms that are available to the Purchasing Super User navigation menu. When you install Oracle Applications, a standard Applications user called SYSADMIN is created for you. Several default responsibilities are also created. Since the SYSADMIN sign-on is automatically assigned the System Administration responsibility, you can use SYSADMIN to create new user sign-ons and assign them to responsibilities. You can also create any custom responsibilities you need.
• #34: <Course name> <Lesson number> - Oracle Applications Utilities (AU) The Applications Utilities (AU) component is used to maintain the Oracle Applications system. AU hosts a collection of files copied from other products. This allows generating on-site classes of files such as Forms and reports, or running reports invoked by the reports server from a standard, shared location. Generating forms or reports may require access to shared PL/SQL libraries, so these files are copied to AU_TOP as well.
• #35: <Course name> <Lesson number> - Oracle Applications Framework (OAF) OA Framework is a Java and XML-based development method used in Oracle E-Business Suite to develop HTML-based applications. OA Framework pages are based around the Model-View-Controller (MVC) design strategy that mixes declarative (XML-based) and programmatic (Java-based) components to create a complete web-based application. OA Framework pages are developed using a version of Oracle's JDeveloper 10g tool specifically tailored for use with Oracle E-Business Suite. While the Java-based components of OA Framework pages are stored in the file system, the declarative XML-based UI is stored in the Metadata Store (MDS). By storing the XML data centrally (in MDS) and hierarchically (in XML), OA Framework allows page attributes to be modified and changed easily, via Personalizations. Instructor Note : In older versions of Oracle E-Business Suite, the equivalent declarative data was maintained by the AK component. AK was superseded by OA Framework for several reasons: it did not provide a tool (such as JDeveloper) for creating and maintain its metadata; it used a proprietary definition (AK-specific, compared to Java and XML); and was not scalable (AK-specific, compared to Personalizations).
• #36: <Course name> <Lesson number> - Oracle Workflow Oracle Workflow provides an infrastructure for the enterprise-wide communication of data related to defined business events, providing the capabilities needed to: Manage enterprise business processes that may span trading partners Support standard and personalized business rules Streamline and automate transaction flows Manage exceptions without manual intervention Oracle Workflow lets you model and maintain your business processes using a graphical workflow builder. You can model and automate sophisticated business processes, defining processes that can loop, branch into parallel flows and rendezvous, decompose into sub-flows, branch on task results, time out, and more. Acting as a system integration hub, Oracle Workflow can apply business rules to control objects and route them between applications and systems. It extends the reach of business process automation throughout an enterprise and beyond, to include any email user, web user, or system, enabling people to receive, analyze, and respond to notifications needing their attention. Users can respond to a notification via any standard email system or standard Web browser.
• #37: <Course name> <Lesson number> - Oracle Alert (ALR) Oracle Alert (ALR) allows you to email system notifications to users when an exception or event occurs. Some products are delivered with predefined alerts, which can be used to notify users about specified database exceptions as they occur, and perform routine tasks automatically according to a schedule you define. For example, you can configure Oracle Alert to send an email to key database administrators when a tablespace in the Oracle Applications database does not have adequate free space.
• #38: <Course name> <Lesson number> - Oracle XML Publisher (XDO) XML Publisher is a Java-based product based on the Worldwide Web Consortium (W3C) Extensible Stylesheet Language (XSL). Specifically, XML Publisher utilizes the XSL-FO standard to transform XML data into a formatting object (FO). Oracle XML Publisher uses data definitions and templates to produce output reports in the desired format. A data definition is a data source (or a combination of data sources) that either is XML or can produce XML. Examples of definitions include output from concurrent programs and Web services. A template is a report definition, which sets out how a report should look. Key features of XML Publisher include: Provides a template-based, easy-to-use publishing solution for end-users Allows users to employ familiar desktop tools to create and maintain reports in their preferred format, and then use XML Publisher to convert them to the XSL-FO format Offers a variety of options for published documents, such as multiple output formats, multiple languages, and multiple delivery options Uses the Oracle database for storage Instructor Note : The non-Applications version of XML Publisher is now known as BI Publisher. However, the Applications version currently retains the older name. This is expected to change in a future release.
• #39: <Course name> <Lesson number> - System Administration and OAM Oracle Applications Manager (OAM) is a sophisticated tool that supports managing and monitoring an Oracle Applications system from an HTML-based central control console. Among other tasks, Oracle Applications Manager can help you to: • Configure and administer your system • Diagnose and correct problems • Manage patches • Monitor and tune performance • Monitor system security OAM is built into Oracle Applications and available as standard. You can also license the optional Application Management Pack for Oracle E-Business Suite. For further details, see OracleMetaLink Note, 394448.1, Getting Started with the Application Management Pack for Oracle E-Business Suite .
• #40: <Course name> <Lesson number> - Key Changes This slide recaps the main changes to the Applications technology stack in Release 12. Instructor Note : T he move from Oracle JDeveloper 9i to 10g is significant for developers, in the context of Oracle Applications Framework.
• #41: <Course name> <Lesson number> -
• #42: <Course name> <Lesson number> -