Post on 05-Dec-2014
description
Overview
Personal Home Page
E-Business Login
Launching Professional Interface
Concurrent Requests
Workflow
Troubleshooting
PHP ConnectionsApplication Server Data Server
WebApplications
Dictionary
Listener
Data
StoredProcedures
BrowserBrowser
PL/SQLCartridge
Client
Application Server Data Server
WebApplications
Dictionary
Listener
Data
StoredProcedures
BrowserBrowser
PL/SQLCartridge
Client
PHP Connections
OverviewPersonal Home Page
E-Business Login
Launching Professional Interface
Concurrent Requests
Workflow
LDAP
Troubleshooting
E-Business Login Leverages Oracle Applications
Framework architecture Enables language selection
based on installed languages prior to login
Defaults to E-Business Suite Home Page
Provides profile option to use the “old” Personal Home Page, if required
E-Business Login
Requires no additional setup Allows “Old” PHP to be seen by setting the value of the
“Self Service Personal Home Page Mode” profile to “Personal Home Page”
Defaults the SSO Login screen for installations with the stand alone 11.5.9 SSO patch
Implementation & Support
HTML Homepage and Navigator
Provides a single, unified application index inclusive of Oracle Applications Forms, JSP and OA Framework pages
Launches Oracle Forms, JSP’s, and OA Framework pages seamlessly from Navigator
Starts Form sessions automatically if required
HTML Homepage and Navigator
Enables users navigating through different forms/ responsibilities to reuse the same Forms session instead of opening multiple sessions
Retains one Forms session open on your PC at any given time for a given database
Removes initial SOCKET_LISTENER_PORT Profile (defaulted to 6945) dependency through the application of Patch # 2924292
Implementation & Support
New Seeded Responsibilities Functional Administrator (FA)
Similar to existing System Administrator who manages the business functionality of the E-Business Suite
Tailored for administrators who know how the business is run and how to tune the business from the administration consoles
Allows for management of Grants, Lookups, Messages and Profiles using OA Framework HTML User Interface
New Seeded Responsibilities (Cont’d)
Functional Developer (FD) Responsible for customizing
programs and User Interfaces Similar to existing Application
Developer role but FD’s use only the functions in the OA Framework HTML User Interface
Allows for management of Objects, Lookups, and Messages using OA Framework HTML User Interface
Security Grants Provides a new model of security that “grants” permissions
to users independent of the Navigation Menu structure. Extends Oracle Application’s native security policies to
accommodate customer specific security requirements
Security Grants Features two models:
Data Security Grants which determine what “Actions” (Permission Sets) can be performed by “Whom”, (User, Group, Responsibilities) on which “Objects”
Function Security Grants which determine what “Actions” (Functions) can be performed by “Whom”, (User, Group, Etc.)
Note: Function Security Grants represent actions that can be performed on the system in general.
Security Grants
Security Grants Details
Freely define Function Security Grants There are limits to the definition of Data Security Grants
given the limited uptake of this new feature (e.g. Projects, Oracle Sales Online, Tasks)
Data Security Grants are the future and teams will be required to uptake in future releases
Secures specific instances of data not menus
Implementation & Support
Self-Service Interface
Launching Self-Service
When a user clicks on a self-service responsibility, it sends a request to Apache. Apache in turn either passes the request to mod_plsql or the Jserv (external process).
If using Jserv (as most pages do anymore), Jserv executes the JSP. If the JSP needs connectivity to the database, it makes a thin client connection to the DB.
Launching Self-Service (cont)
Jserv is controlled by files in the following location: $IAS_TOP/Apache/Jserv/etc/
jserv.conf
jserv.properties
zone.properties
Launching Self-Service (cont)
From the jserv.properties file, the Jserv knows where to get the DBC file. This is typically $FND_TOP/secure
The DBC file contains all the information on how to connect to the DB, as well as other configuration details (connection pooling, etc.)
Launching Self-Service (cont)
As long as Jserv is functioning correctly, a page will be built and sent back to Apache, who passes it on to the browser.
Note: Some Jserv sessions are stateful, others are released as soon as data is fed to Apache.
ServletEngine
Self Service Web Connections
Application Server Data Server
WebApplications
Dictionary
Listener
DataJSP
BrowserBrowser
Client
ServletEngine
Application Server Data Server
WebApplications
Dictionary
Listener
DataJSP
BrowserBrowser
Client
Self Service Web Connections
Application Server Data Server
WebApplications
Dictionary
Listener
Data
BrowserBrowser
Client
Workflow
Servlet Engine
JSP
JSP
Se
rvle
t En
gin
e
CSS
BC4J
Web beans
Self Service Web Connections
Self-Service Architecture
JSP
Serv
let
En
gin
e
Web beans
BC4J
CSS
Industry standard UI technologyCommon HTML components used throughout ApplicationsBusiness logic encapsulated in View Objects and Entity Objects
Style sheets allow easy UI changes
OverviewPersonal Home Page
E-Business Login
Launching Professional Interface
Concurrent Requests
Workflow
LDAP
Troubleshooting
Professional Interface
Professional Interface
Data Server
Java Server Pages (JSP)
Forms
Reports
Discoverer
Concurrent Manager
Browser PL/SQL Gateway
Servlet Engine
Web
Lis
ten
er
ApplicationApplicationLogicLogic
Forms Server
Data ManagerData Managerandand
PL/SQL EnginePL/SQL Engine
Application Executable
User InterfaceUser InterfaceLayerLayer
SQL*Net
Web Browser Database
AutomaticallyDownloaded
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
Oracle Developer Server
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
User InterfaceUser InterfaceLayerLayer
FMX File
Java Apple
t
Forms Server Architecture
Oracle DeveloperOracle Developer
BrowserBrowser Internet Application Server
Internet Application Server1) HTTP Request
2) Return HTML File: <applet...>
Starts Java
Java Class Loader
Java Class Loader
3) Request Applet
Load-cached applet
4) Return Applet (in JAR file)
Starts Applet
Forms Client Applet
Forms Client Applet
socket
socket
5) Request Forms Connection
Forms ServiceForms Service
HTTP Listener
HTTP Listener
Forms Runtime Engine
Forms Runtime Engine
Creates
socket
6) Initial Window then
Ongoing Forms Session
Forms Server
Listener
Forms Server
Listener
Initiating A Client Session
Forms Server Architecture
Data ServerData
ServerForms Forms ServerServer
Browser running Forms
java applet
Browser running Forms
java applet
Java code downloaded as neededApplet cached on client
Forms Network Traffic
Browser running Forms
java applet
Browser running Forms
java applet
Data ServerData
ServerForms Forms ServerServer
LAN,WAN, orDial-up
Forms Network Traffic
Browser running Forms
java applet
Browser running Forms
java applet
Data ServerData
ServerForms Forms ServerServer
Many UI operations handled on the client
One round trip per field navigation
Forms Network Traffic
Browser running Forms
java applet
Browser running Forms
java applet
Data ServerData
ServerForms Forms ServerServer
Compact,differential runtime messages
Forms Network Traffic
Data ServerData
ServerForms Forms ServerServer
Browser running Forms
java applet
Browser running Forms
java applet
HTTP orHTTPS protocol
Forms Server Scalability
Data ServerData
Server
Forms Forms ServerServerForms Forms
ServerServerForms Forms ServerServerForms Forms
ServerServerForms Forms ServerServerForms Forms ServersServers
Browser running Forms
java applet
Browser running Forms
java applet
36
Load Balancing Forms ServersMetrics ServerMetrics Server
Metrics ClientMetrics Client
Forms ClientForms Client
1Connection
Request2
HTML Returned
3Reads HTML
and connects to Forms Server on
least-loaded system
Load Information
Load Information
Load Information
Metrics ClientMetrics Client
Metrics ClientMetrics Client
Forms Server Load Balancing
• Metrics server records the number of active processes
• Dynamic HTML points user to least loaded host
Metrics Server
Apps Server 3
Globalization/Localization
Forms Server Failover Capabilities
Apps Server 3
“Apps Server 3 not available”
Apps Server 2
• Metrics server monitors availability of other application servers
• Dynamic HTMLre-routes user to another server
Metrics ServerGlobalization/Localization
Launching Help
If the user selects the “copy file” option Jinit spawns a new web browser window. Browser contacts Apache to run a PL/SQL
procedure. This procedure builds a webpage that consists
of 3 frames Search Navigator Search Results
Overview
Personal Home Page
E-Business Login
Launching Professional Interface
Concurrent Requests
Workflow
Troubleshooting
Launching a Request
Concurrent Requests are the way that the Apps accomplish:
Batch Jobs Dataloads Posting Etc
Reporting Reports 6i FSG Etc.
Launching a Request
Kicking off a request is easy. User navigates to the “Submit Requests”
screen. Select the request Enter the parameters (date range, etc.) Save changes
Record is written to FND_CONCURRENT_REQUESTS table
Launching a Request (backend)
What happens behind the scenes is a little more tricky.
Conflict Resolution for a request is either handled by ICM or CRM.
The CRM will check the request to see if it is in conflict with anything
If no conflicts, the request gets queued on a manager.
Launching a Request (backend)
If the request gets queued on a manager The manager loads the files that are needed to
run that request. Requests can be: Host commands Reports runtime SQL files SQL*Loader files Etc.
Viewing Request Output
When the request completes, a user can view the output in their professional interface
The user clicks on the “View Output” button and the report output is displayed on the screen.
In addition, the user can select “copy file” and the file is downloaded to the browser in form of a txt file.
Viewing Request Output (backend)
When a user clicks “View Output”
Jinit sends the request to the Forms Server. Forms Server instantiates a connection to the
FNDFS listener FNDFS listener is a standard database listener.
($TNS_ADMIN/$ORACLE_SID) The Listener spawns an FNDFS process
Viewing Request Output (backend)
FNDFS reads the file, and sends it back through a network pipe.
FNDFS is somewhat interactive, as it paginates the output, and can deliver a partial file or a complete report.
Viewing Request Output (backend)
If the user selects the “copy file” option Jinit spawns a new web browser window. Browser contacts Apache to run the
FNDWRR.exe CGI. FNDWRR.exe works as a pass-through to
FNDFS As soon as the file is delivered, FNDFS goes
away, and FNDWRR.exe loses authentication.
TCF Connections
TCF stands for Thin Client Framework
Apps has a service called the TCF socket server. This process is used for UI components to connect to server components.
Apps uses this framework for server processes that are not forms server related, but still have a server component.
TCF Connections (cont)
TCF connections are started by the jinitiator initializing an applet that is not forms server related.
This applet in turn communicates with the TCF socket server. The TCF server initializes whatever java processes are needed to fulfill the request.
Since the TCF is Java based, it’s configuration is in the $FND_TOP/secure/ dbc file.
TCF can run http/https and socket. The difference between TCF and Forms is that TCF always runs as a standalone process.
Overview
Personal Home Page
E-Business Login
Launching Professional Interface
Concurrent Requests
Workflow
Troubleshooting
Workflow
Workflow is a generic service that can be triggered by nearly anything occurring in the apps.
Workflow processes can be run by calling the workflow APIs directly or through the concurrent manager job “Workflow Background Process” This job is scheduled as per business needs
Workflow (continued)
Workflow response processing Workflow Notification Mailer
Started through OAM Processes messages that come via MAIL
protocol Keeps track of Processed, Unprocessed, and
Discarded messages. Runs as a Concurrent Manager service.
Workflow (continued)
Business Event System Run through Advanced Queues Uses Savepoints, so not appropriate for
triggers Workflow background engine picks up the
queued message and processes Workflow tables must be cleaned daily as
the volume can grow quite large
RolesUsers
Directory Services
Notification Services
Send
Respond
Forward
Cancel
Query
Oracle Workflow Enabled Application
Oracle Server
Engine
Execution
Definition
Administration
Monitoring
Query
WorkflowBuilder
WorkflowLoader
WorkflowDefinition
Files
WorkflowDevelopment
Client
Oracle Portal
NotificationMailer
ApplicationServer
WebNotification
Worklist
WebMonitor
WebAnalysis
Tools
Browser Client
MailApplications
Workflow Components
Rule-Based Workflow Engine
Manages the Execution of a Business Process
Immediate and Background Operation
Generates a Complete Audit Trail Delivers Notifications When Human
Activities are Required Oracle9i Transactional Integrity
Guarantees Consistency Between Application and Workflow State
Server-Side Architecture Ensures Optimal Performance
o7
Oracle Oracle WorkfloWorkflo
ww
Oracle9iOracle9i
OracleApplications
Release 11i Order Management Workflow
EndHeader levelInvoice - Order
Book - Order,Manual
Close - OrderEnter
Order Header Flow - Generic with Header Level Invoicing
Unreserve
Close - LineCreate Supply -Line
Schedule - Line Header LevelInvoice - Line,
Deferred
Enter - Line EndShip - Line,Manual
Order Line Flow - Generic with Header Level Invoicing
Notifications
Oracle server
Notification System
NotificationWorklist
Web Client
Oracle Workflow Worklist
OracleInternet
Messaging
SMTP
MAPI
Oracle Workflow Notification Mailer
VariousMail
Applications
• Netscape Messenger• Lotus Notes• Microsoft Exchange• Unix Sendmail• Others
HTML Plain text
Participating in a Workflow
Receiving Notifications from a Workflow Most E-mail Systems Pagers Phones Web Notifications Faxes or Printers
Electronic Notifications
Sending Notifications to a Workflow Individuals/Groups/Positions
Multiple mechanisms Web Any E-Mail System Pagers/Phones
Self Service Notifications
Extended HTML Extended HTML message formatsmessage formats
Make a decision Make a decision via online via online
inquiryinquiry
Email Notifications
Extended HTMLExtended HTMLmessage formatsmessage formats
Make a decision Make a decision via Email via Email
attachmentattachment
Email Notifications
Automatic Automatic generation of generation of
response templateresponse template
Oracle Workflow Monitor Graphically Monitor and Administer Workflow
Transactions. Java Applet Runs in a standard Web Browser
View and Analyze Transaction History Retry or Skip any Activity Rewind and Rerun any Process Available to End Users and Administrators
Summary of Key Activities Decision Makers in the Process Current Process Owners
Oracle Workflow Monitor - Summary
DBMS
Call Workflow API’s
New Requisitionentered
Alert or Triggeroutput variables
WorkflowAttributes
DBMS
Functions
PL/SQLStored Procedures
Workflow Process
Attributes Functions
NotificationMailer
Oracle Alert
DB Trigger
Forms Trigger
Messages
Advanced Queue IntegrationAdvanced Queue Integration
Workflow
WorkflowEngine
BackgroundEngine
Advanced QueueWF Outbound
WF Inbound
WF Deferred
Oracle Server
External Inbound
External Outbound
External Process
External System
Overview
Personal Home Page
E-Business Login
Launching Professional Interface
Concurrent Requests
Workflow
Troubleshooting