300 likes | 484 Views
CON2120: Gaining Victory Over SOA and Application Integration Complexity. Rajesh Raheja Senior Director, Product Management Oracle Fusion Middleware Business Integration. Program Agenda. Overview of SOA and App integration challenges
E N D
CON2120: Gaining Victory Over SOA and Application Integration Complexity Rajesh Raheja Senior Director, Product Management Oracle Fusion Middleware Business Integration
Program Agenda • Overview of SOA and App integration challenges • Successful strategies for managing complexity using SOA governance and architecture (Fusion Applications) • Conclusion
Service-based Integration Challenges Increasing Technical Complexity in Achieving Business Goals 100’s-10,000’s of integration points Inter-dependencies are invisible Tribal knowledge and taxonomy Interface visibility & reuse Time-to-market; agility Control costs / risks Impact of changes; lack of traceability Lack of guidelines for new services Spreadsheets & WIKIs are inadequate Cultural change is hard to manage
Integration Made Easier Enterprise Repository: A Built-In, Automated Catalog of Service Artifacts • Pre-integrated artifact repository with Oracle FMW Stack (and others too) • Automatic artifact collection • Automatic dependency tracking • Transparent, easy to use • Rapid Start results in 30 days Navigating the Repository
Integration Made Easier Foundation Pack: An Accelerator for Canonical and Direct Integrations Foundation Pack • Jump-start Integration Projects • Reduce Integration Risks • Lower Integration Costs Common Business Objects & Services Pre-Defined Reference Process Models Design Patterns & Reference Architecture Integration Methodology Integrated Development Lifecycle Tools Developer Utilities
Enterprise Repository and Foundation Pack Better Together!! • Integration Asset Catalog • Automated dependency tracking • Design-time compliance • Design patterns & Reference architecture • Integration methodology • Developer utilities Developers Architects & Team Leads Integrated lifecycle management tools
Business Innovation Platform for the Enterprise & the Cloud Oracle Applications FusionApplications ISV/Custom Applications Mobile Web Social Oracle Fusion Middleware Business Process Management Content Management Business Intelligence USER ENGAGEMENT Service Integration Data Integration Identity Management Development Tools Cloud Application Foundation Enterprise Management
Oracle Fusion Middleware Business Innovation Platform Web Social Mobile • Complete • Integrated • Best-in-class • Open • On-premise and Cloud User Engagement Business Process Management Content Management Business Intelligence Service Integration Data Integration Identity Management Development Tools Cloud Application Foundation Enterprise Management
Successful Strategies for Managing SOA and Integration Complexity (Fusion Applications)
Key Items to Consider Promote an enterprise integration reference architecture Catalog all assets, asset types and dependencies in a centralized repository Consolidate integration technologies – avoid ‘hammer-nail’ solutions Add controls around design, versioning, deployment and workflow - Implement automated BPM and continuous integration strategies Utilize Business Activity Monitoring for KPI Metrics
Evolution of the Canonical Rationalization of Application Concepts in Fusion Applications Logical Entities 6,000 Tables 20,000 Business Objects 2,000 Data Model must support the “most critical” functionality from PeopleSoft, eBusiness Suite, Siebel, Primavera • Concepts from other applications have been absorbed • Multiple Work Assignments • Overlapping concepts have been reconciled as part of the migration design • Operating Unit and Business Unit • Concepts have been left behind • Smoking History attribute • One logical model to cover: • Services Design • Integration • Migration
Cataloging Content Helps • Single Repository of Business Concepts • Search for existing Business Objects using proper domain level language • Review a whole business area to confirm the concepts that it includes • Only Business Objects that are not redundant, are not ambiguous and are well named and described are registered in the Repository • The registrar has cross product family exposure • Solutions HRR_MEETINGS HRR_MEETING REVIEWEES HRR_DASHBOARDS HRR_MEETING_RVW_CONTENT
Catalog for Visibility into Integration Assets Oracle Enterprise Repository (OER) for Fusion Applications • 1000+ Assets • Web Services • Schema Definition • Composite Services • Business Events • Interface Tables • Flat File Interfaces • eTRM Documentation e.g. • Customization Layers • Flexfields • Flexfields, Lookups, Profile Options • Roles and Reports • Tables, Views, Scheduled Processes • Diagrams: Data Model and Topology • http://fusionappsoer.oracle.com • Categorized by • Product Line Product Family Product • Business Object • Integration Scenario
OER for Fusion Applications Provides End to End Visibility Composite ADF Service BPEL Human Workflow Mediator Business Event Event Subscription ADF SDO Business Rules Composite Service Business Object Web Services Business Process Web Services ADF Service Name = Logical Business Object Event Taxonomy applies to Logical Business Object Composite Taxonomy subscribes To Event Note: LBO name may not be present in all Event taxonomies
Review Service Details and Schema Information Replace ?WSDL with ?XSD&xsdlistto view object schemas
Release 5 Review Web Service Security Requirements
Release 5 Review Service Documentation and Examples
Release 5 Scheduled Jobs for File Based Data Import
Release 5 File Based Data Import Usage Documentation
Release 5 Privileges Required to Run Import Job
Nigel King Vice President, Fusion Applications DevelopmentOracle “Not only are the challenges about integrating separate apps through published interfaces (we have this problem too).... We also have a deeper problem -- that the application concepts must be rationalized. This requires governance and oversight. It is the difference between finding a translator and learning a language.”
Application/Integration Architecture Scott Nieman Enterprise ArchitectLand O’Lakes “Making the asset inter-dependencies visible across the Business, Application, Information and Technical architectures (BAIT) is imperative if you are going to get the integration problem under control. The health of the business demands it.” Information Architecture Business Architecture Technology Architecture People, Process & Tools EA Governance EA Repository Customer Content Oracle Reference Base
The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract.It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.