Release 12.1
Part Number E12893-04
Contents
Previous
Next
| Oracle E-Business Suite System Administrator's Guide - Configuration Release 12.1 Part Number E12893-04 | Contents | Previous | Next |
Important: This information is provided for backward compatibility only.
The Oracle Self-Service Web Applications, including Self-Service Expenses, Self-Service Human Resources, Internet Procurement, Internet Receivables, Self-Service Time, Web Suppliers, iStore, iPayment, iSupport, iMarketing, and eTravel from Oracle, extend the functionality of Oracle E-Business Suite by adding a browser-based, walk-up-and-use functionality that supplements Oracle E-Business Suite.
The Oracle Self-Service Web Applications can be either inquiry or transactional. Inquiry modules read but do not update the Oracle E-Business Suite database; transactional modules update the database.
The architecture consists of the following components:
A web browser
Oracle HTTP Server, powered by Apache
HTML documents
Java Server Pages, JavaBeans and Servlets
The following definitions will help you to understand the big picture of Oracle Self-Service Web Applications.
The Oracle HTTP Server (powered by Apache) is based on the open source HTTP server created by the Apache Software Foundation. Information on the Apache Server can be found at http://www.apache.org. This provides the communication services of Oracle Internet Application Server (iAS). The Apache Server is modular. In addition to the standard Apache modules (often referred to as mods) the Oracle HTTP Server adds a number of Oracle specific modules, along with an extension to the functionality of several of the standard mods. Theses include mod_cgi, mod_ssl, mod_jserv and mod_perl.
The industry standard technique for running applications on a web server. Oracle HTTP Server supports this standard.
A format for encoding hypertext documents that may contain text, graphics, and references to programs, and references to other hypertext documents. HTML is a subset of Standard Generalized Markup Language (SGML).
A protocol used to request documents from the web server.
A reusable Java class which has specific naming conventions for its methods and variables. JavaBean components can be used to perform well-defined tasks, such as connecting to a database, maintaining client information, or rendering a screen page.
Javascript is a scripting language that adds significant power to HTML files without the need for server-based CGI programs.
JSPs allow for the embedding of servlet code within HTML pages. The operation of JSPs is similar to that of server-side includes.
A small, "pluggable" extension to a server that will enhance the server's functionality. Java servlets are a key component of server-side Java devlopment.
An Apache module that provides for the execution of Common Gateway Interface (CGI) applications through the invocation of an operating system shell that runs the application and uses the CGI to deliver data to the application..
An Apache module that routes all servlet requests to the Apache JServ Servlet engine. The servlet engine provides the runtime environment to execute servlets. The servlet engine executes from within a Java Virtual Machine (JWM) running on the same node, or a different node, to the Apache HTTP Server. Each JVM has one servlet engine but the number of servlet engines is not proportional to the number of JServ processes. As the mod_jserv and Apache JServ servlet engines are different processes, potentially running on different machines, a protocol called Apache JServ Protocol (AJP) is used for communication.
For more information on the AJP Protocol refer to http://java.apache.org/jserv/protocol/AJPv11.html
An active data dictionary that employs the Oracle Forms-based interface. The data dictionary stores specific information about Self-Service Web Applications data, including prompts, language, navigation, and security.
The client user interface component. The browser you use must support tables and frames and be Javascript enabled. The embedded Javascript coding provides a mechanism for client side caching of user-entered data during a transaction, and simple client side validation of user-entered data. Execution of simple Javascript code logic at the client side results in reduced network traffic between the web browser client and the web server.
Workflows can be defined for business flows so users can be sent automatically all the information they need to make a decision and have other business processes run automatically based upon their responses.
Workflows are defined using the Workflow Builder, a Windows GUI interface that enables users to design the business process, the activities, items, messages and lookup lists, and roles (the approval chain). This workflow is then integrated into the business transaction process. For Web Employees, it is integrated with the requisition approval process.
Notifications generated in the workflow chain can be viewed with the Oracle Self-Service Web Applications or a Workflow-supported email system.
Oracle Self-Service Human Resources includes a predefined workflow process to generate offer letters.
All workflow processes are customizable.
For more information, see the Oracle Workflow documentation.
This is an Oracle Forms-based data dictionary used to define flow content. When users query for data, information is displayed on a web page, complete with hypertext links that enable the user to drill down to more detailed information. The pages that are linked in this way constitute a flow, alternatively referred to as an inquiry. Using the Web Applications Dictionary, you specify the content of, and links between the pages that make up a flow. Specifically, you can specify:
HTML page format (headers, text, tables)
Object content by associating with Applications Business Views or PL/SQL
Business Flows among Objects (hypertext links)
Page Content (fields, selection criteria)
Web Applications Dictionary also serves as a real time execution engine to retrieve information from the database. Oracle Self Service applications reference the data dictionary at run time to retrieve data from the database and generate dynamic HTML pages.
The Web Applications Dictionary provides a means of defining business flows which can then be web-enabled. All inquiry flows were built using Web Applications Dictionary. These can be customized as needed.
The Web Applications Dictionary is part of Oracle E-Business Suite, Release 12 and is part of the “AK Common Modules". Once installed, it is accessed in the same manner as all of the core Oracle E-Business Suite.
See: Web Applications Dictionary Overview.
When you invoke an OSSWA function that displays information as dynamically generated web pages, the following sequence of events takes place:
The user clicks the hyperlink of a function on an OSSWA menu. A URL embedded in the HTML source code is accessed from the browser that calls for a Java servlet.
The Oracle HTTP Server, powered by Apache, routes the request to mod_jserv.
mod_jserv takes requests and forwards them to Apache Jserv, the servlet engine.
The servlet engine generates the response, communicating with the database as required. If the servlet needs to execute any Java Server Pages (JSP) it will contact Oracle JSP. Oracle JSP is a translator and runtime environment for JSPs. Oracle JSP can run as a standalone translator or as part of a servlet engine, to dynamically compile JSPs as required.
The response is returned to mod_jserv.
The HTTP Server returns the response to the client.
The Web Application Dictionary is an active data dictionary that enables you to define applications for the web, and generate many of the application's characteristics at runtime. The data dictionary stores key information about your application, including appearance, language, security requirements, navigation, and data. Because this information is stored in an active data dictionary, you can create an inquiry application for the web specifically designed to meet your business needs.
An Oracle Forms user-interface is provided for you to enter your application's characteristics in the active data dictionary. Through this user-interface, you can customize existing inquiry applications for the web, or create new ones without programming effort. You can create applications that are customizable, extensible, and multilingual.
With Oracle Web Application Dictionary you can:
Develop applications for the web without programming
Generate the application web pages at runtime
Register your application definition in an active data dictionary
Customize and extend existing applications, and maintain your customizations
Seamlessly integrate Oracle E-Business Suite data and company intranet content
Completely reconcile company transactions through a web inquiry interface
Graphically illustrate your application data relationships using Object Navigator
Below are some terms used with the Web Applications Dictionary.
A database view.
A reusable field used in a web inquiry application. For example, customer name and customer number are both attributes. An attribute is not associated with data. For example, the customer name attribute can be reused anytime a customer name field is displayed on a web inquiry screen.
A reusable field that results when you associate an attribute with an object.
A logical grouping of data. For example, customer information can be grouped in one region and shipping information can be grouped in another region. A region also represents a section of a web page.
A reusable field that results when you associate an attribute or object attribute with a region.
The steps above show one way of creating a flow using the Web Application Dictionary. However, there are additional optional screens that are provided as well, specifically the Assign Regions screen and its related screen. You can use the Assign Regions screen to assign an object attribute to many regions at once. You can optionally navigate to this screen from the Object Attributes window using the Multiple Assignments button.
Important: The Attribute Values window is not applicable to the Web Application Dictionary. The Attribute Navigation button in the Regions window causes the Attribute Values window to be displayed
Three Common Modules folder windows display different fields, depending if you use Oracle Product Configurator, Oracle Self-Service Web Applications, or both. Use the MODE parameter in the Form Functions window to set which mode to use, Product Configurator or Applications for the Web (Self-Service Web Applications).
If your site uses only one mode, set the MODE parameter at the site level. If your site uses both modes, set the MODE parameter at the user level.
To set the folder mode:
Log in to Oracle E-Business Suite, choose the System Administrator responsibility, and Open the Form Functions window.
For the Object Workbench, Define Regions, and Define Attributes window, set the MODE parameter to one of the following:
WEBAPPS if you are using Oracle Self-Service Web Applications.
CONFIGURATOR if you are using Oracle Product Configurator.
For example, if you are using the Product Configurator, set:
MODE="CONFIGURATOR"Note: The MODE parameter can be set at either the site or user level. If your site uses both Product Configurator and Self-Service Web Applications, set MODE at the user level according to how each user uses these windows.
This section contains tasks using the Web Application Dictionary.
You must define an object for each database view to be used in your flow. This function registers the view in the Web Application Dictionary.
Note: You can only define one object per database view.
Before defining an object, create views to use in your web inquiry.
In the Web Application Dictionary, navigate to the Objects folder window.
Enter an object name.
Select an application.
Select a database object, i.e., a database view.
Choose the Object Attributes button to define the attributes for the database object.
Choose the Unique Keys button and define the primary and unique keys for the database object.
Enter the primary key.
Save your work.
Choose the Foreign Keys button to define foreign keys for the database object.
Associate defined attributes with one or more objects (database views) to create object attributes.
Note: Uniform Resource Locator (URL) attributes must be object attributes.
Note: If you are updating existing assignments and you change a long label, you are prompted if you want to change the label for all related object attributes and region items. If you choose OK, all related labels are changed.
Prerequisites to this task are:
Define objects.
Define the attributes to assign to objects.
Navigate to the Object Attributes folder window.
Select an existing attribute name to assign to an object.
Optionally, select a database view column name corresponding to the object attribute.
Enter a long label for the object attribute. The default is the label used when the attribute was defined, but can be overridden.
Note: The remaining data in the Object Attributes folder window defaults from when you defined the attribute. You may override these defaults.
Choose the Create Attributes button to create additional attributes. When you close the Attributes window, you are prompted to add the attributes you just created to your object attributes.
Choose the Multiple Assignments button.
Enter all the regions that you want the current object attribute assigned to.
Attributes can be defined and then assigned to one or more objects.
Note: If you are updating existing attributes and you change a long label, you are prompted if you want to change the label for all related object attributes and region items. If you choose OK, all related labels are changed.
Navigate to the Attributes folder window. Do this by choosing the Create Attributes button from the Object Attributes folder window.
Enter an attribute ID, the internal name for this attribute.
Enter an application to associate with the attribute.
Enter a user–friendly attribute name to be used in lists of values.
Enter a long label for the attribute. The default is the attribute name. This is the attribute prompt in your web inquiry application.
Optionally, indicate how the text should appear on the browser: bold, italic, and so on.
Select a vertical alignment: Top, Center, or Bottom.
Select a horizontal alignment: Left, Center, or Right.
Enter the datatype for the attribute.
Enter the display length for the attribute value.
Optionally, enter a free–form description for the attribute.
For each object, a unique primary key must be defined. A primary key ensures that each row of data can be uniquely identified and cannot be duplicated.
Prerequisites for this task are:
Define objects.
Define attributes.
Define object attributes.
In the Web Application Dictionary, navigate to the Unique Keys window by choosing the Unique Keys button from the Objects folder window.
Enter a name for the unique (primary) key.
Enter at least one unique key column sequence. The sequence determines the order the specified columns are evaluated.
The combination of primary keys and foreign key relationships determine the navigation through your web flow. That is, if your flow must have navigation from one region to another based upon the same object, a foreign key must be defined for that object.
The prerequisites of this task are:
Define objects.
Define attributes.
Define object attributes.
Define Unique Key(s).
In the Web Application Dictionary, navigate to the Foreign Keys window by choosing the Foreign Keys button from the Objects folder window.
Enter the foreign key.
Select the parent object (database view).
Enter the referenced key. This is the unique (or primary) key of the parent object.
Optionally, enter a description for the relationship.
Optionally, enter the inverse relationship.
Optionally, enter a description for the inverse relationship.
Enter the foreign key column.
Enter the referenced key column.
Repeat the last two steps until all referenced key columns have been assigned.
Regions can be defined and then assigned to one or more pages.
You can define regions that do not display. Such regions serve as a way of navigating from one object to another.
Before performing this task, define your objects.
Navigate to the Regions folder window.
If you want to copy an existing region to then modify and save as a new region, choose the Copy button. Enter a new application name, region ID and region name.
If you are creating a new region from scratch, enter the ID for the region.
Enter a user–friendly region name.
Enter the application associated with the region.
Select the object name associated with the region.
Select a region style: Single–row, Multi–row.
If you selected Single–row in the previous step, enter the number of columns (a field and its label) to display in the region before the line wraps.
Optionally, enter a free–form description for the region.
Use the Region Items button to navigate to the Region Items window.
Region items are attributes or object attributes that are placed within a region. These are typically the attributes that you want to display in the region. However, there are exceptions to this.
Prerequisites to this task are:
Define attributes to associate with regions.
Define objects.
Define object attributes to associate with regions.
Define regions.
In the Web Applications Dictionary, navigate to the Region Items folder window. Do this by selecting a region in the Regions window and choosing the Region Items button.
Select the attribute type, either attribute or object attribute, to associate to a region. An attribute is usually reserved for use with a button.
Select the name of an existing attribute or object attribute.
Enter a display sequence for the region item.
This determines the order of the region items, whether they display or not. If you do not want a region item displayed, select the Hidden item style in the next step.
Select an item style, either Button or Text.
Note: The Checkbox, Hidden, and Poplist item styles are not supported.
Optionally, indicate whether the region item can be queried.
Optionally, indicate whether the underlying column of the region item should determine the order in which data is displayed, and whether that order is ascending or descending.
This generates a web query form.
Copyright © 1994, 2010, Oracle and/or its affiliates. All rights reserved.