Wednesday, October 3, 2012

Oracle Open World day 3

Optimize and Extend Oracle Applications: the path to Fusion Apps
In this session it was discussed what customers could do to make the transformation to Fusion as smoth as posssible. Three key areas where mentioned:

- keep you applications on the latest version
- optimize tools and technologies
- coexistence

If you follow the upgrade path and stays on the latest versions it will be much easier to upgrade. For example, in R12 the Financial architecture (with subbledger accouting etc) is the same as in Fusion.

What you also can do to make the road to Fusion less bumpy is to start use some of the tools and technologies already today. Example of this are Oracle Identity Management (OID, used in Fusion Apps for security), Oracle BI Apps and Oracle BI Publisher. It’s possible to use all of these tools already today in your R12 environment.

One other possibility to get ready for Fusion is to implement new modules using Fusion Apps. If you want to start use the HR module it’s recommended that you implement this is Fusion Apps and let it coexist with you current application version. Another example is Oracle Talent Management Solution, Taleo.

Oracle Fusion Applications: Technical Architecture Deep Dive
The technical architecture of Fusion Applications is still based on the three tier model.

- Client Tier
- Application Tier
- Database Tier

The client tier is what the end user is using to navigate the application. It’s all browser based using any browser or tablet.

The application tier is divided into two sections; Fusion Middleware Services and Fusion Middleware Infrastructure Services. The Fusion Middleware Services includes ADF, Identity Management, SOA etc; the standard technologies that Fusion Apps is built with. Fusion Middleware Infrastructure Services is the part that is Apps specific such as Applcore (way to set up flexfields, generic setup etc), Oracle Enterprise Crawl and Search Framework (used for searches throughout the system to give the user a google like search experience) and Enterprise Scheduler (used for scheduling jobs).

The database tier includes (obvious) the database which have two schemas; the Fusion Apps schema and the Fusion Middleware Schema. This is all stored in the same database.

Fusion Apps Technology Stack includes the following
- Oracle Database
- Oracle Weblogic Server
- Oracle Weblogic Communication Services
- Oracle Identity Management
- Oracle Webcenter
- Oracle Business Intelligence
- Oracle SOA Suite
- Oracle Data Integrator
- Oracle Application Development Framework - ODI
- Oracle Jdeveloper
- Oracle HTTP Server
- Oracle HTTP Server Webgate
- Oracle Web Services Manager Policy Manager
- Oracle Enterprise Content Management Suit
- Oracle Secure Enterprise Serach

One more thing to mention is the four different composers that make it possible to tailor the application in a supported and upgrade safe way. Data Composer (add new objects and attributes), Page Composer (add, remove, show or hide components on a page), Process composer (add or change process steps and rules - BPEL) and the Reports Composer (create and change reports).

PGA Migrates to Oracle Fusion Applications
In this session Oracle and their customer PGA described the experience with upgrading from 11.5.10 to Fusion Apps. PGA was included in the early adopter program as they had a straight forward implementation without any customizations.

- Financials (AP, AR, GL, PO, PA etc)
- 77 legal entities
- 283 companies
- The new solution includes scanning of invoices using the Integrated Imaging Solution
- 1 year project with a 12 people team (6 from Oracle, 6 from PGA)
- The client went live on pre-release 1 (current release is 5)
- On premise installation

Larry talking infront of 10.000 in hall D

View over SF

Example on BAD slide design...

No comments:

Post a Comment