Oracle fusion soa operations and configuration

oracle fusion soa operations and
configuration
CONTACT US:

MAGNIFIC TRAINING
INDIA +91-9052666559

USA : +1-678-693-3475
info@magnifictraining.com
www. magnifictraining.com

© 2011/12/13 Oracle Corporation – Restricted Distribution

1

Disclaimer Notice
The following is intended to outline Oracle 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.

Slide 2

Agenda
• Improving Transparency, Performance, and Enabling Civic
Engagement Through Intergovernmental Collaboration and
Innovative Technology
– From the customers’ viewpoint, David will share recent NIEM*
successes, along with the technical and political challenges along
the way. Being both a strong proponent of open source and having
developed a number of world leading solutions himself prior to
joining Oracle, he presents an objective perspective of what it takes
to effectively leverage SOA to achieve intergovernmental
collaboration objectives and successfully roll out new services
– Open Data; what you need to know
– Open Source; what you can deliver today
– Innovations; what we are working on
• What this all means: better services and economic opportunities
for citizens
*NIEM – National Information Exchange Model


3

Technology Landscape
• Open Data
– Open Data Introduction, Solution Architecture and Tools

• Information Alignment
– Dictionaries - Key Technology and Foundation Pillar

• NIEM Development Life Cycle
– NIEM Concepts, Tools and Adoption, SOA

• Summary
– Opportunities for Government



4

Vision and Potential; EU and Japan
◆ Not only further development of IT industry, initiatives seek to create…
① New business created by the integration of IT & data and existing industries

② New business created by the integration of different industries through IT & data
New Business using IT & data
Narrow
IT Industry

Expanding into
multiple
industries and
business areas

As real world data is
added, the amount of
available information
increases
significantly

New Business created by
the integration of IT and
existing industries
Construction
Equipment
Automobiles

Energy

Medical
Equipment

Robots

Agriculture

Healthcare

Retail

New Industries created by
the integration of different
industries through IT and data
Energy×Automobiles
×Transportation System

Healthcare×Agriculture


Source: http://semanticommunity.info/@api/deki/files/21578/BrandNiemann02122013.pptx

Robots×Retail×City Planning

55

5

Japan – DATA METI Plan
As part of approach to develop “Leading-Edge Integrated Industries”, METI
intends to actively release public data in formats that facilitate reuse under
the clear set of reuse rules.
Examples of Public
Data

Geological Map

＜Stimulate the Economy＞
・Develop Information Service
・Edit & Process the raw data
→Create additional value

Revitalize
economic and
industrial
activities

Citizens

Deliver Better
Service

Economic Statistics

・Develop Applications

Business Operator

・Create useful Websites

METI

Provide
Raw Data

・Build business online systems

Source: http://semanticommunity.info/@api/deki/files/21578/BrandNiemann02122013.pptx

6

USA - Background
"Open Data is the new default…
anywhere, anytime on any
device, and everything should be
APIs"

Steven VanRoekel

Federal CIO – Whitehouse Digital
Strategy Architect

Along with its Open Data Policy, the White House unveiled May 9
Project Open Data, a GitHub-hosted tool kit it hopes will be the
living, breathing implementation arm of its policy
Behind the hype and technology what is really being achieved?

7

Decoding the Digital Strategy

• What exactly are Open Data APIs?
• How can Oracle solutions support them?

• What does a solution architecture look like?
• How does this align with NIEM*?
• What technology pillars and tools are there?

© 2012/13 Oracle Corporation – Restricted Distribution

8

Open Data APIs explained
• A way, via the internet, to securely deliver

information between entities and systems
• API – Application Programming Interface
• Security is supported along with roles and
permissions for requestors, e.g.
– Public information – such as road works, health services, voting

– Private information – patient data, student data, company data


9

Example – Chicago Pharmacy Vaccines Search
http://www.verifyxml.org

1. Socrata data
extract
2. MySQL
database
3. Glassfish
4. Open-XDX
5. Prime Faces
6. Hosting site

Combines: rapid development paradigm; open data approach;
open source tools; RESTful web services; community based
resources and delivery; NIEM-aligned information feeds.

10

Oracle Open Data Solution – Open-XDX
• Open-XDX is an all new component designed to deliver
rapid Open Data APIs
• Integrates into Oracle Fusion Middleware foundation
and Database products
• Uses XML configuration templates and code-less
methods and open source NIEM tools
• Allows plug-and-play delivery for Oracle customers and
applications


11

Example – Military Applicant Onboarding
• Need to examine the applicants health history and
particularly prescriptions
• 1 in 5 high schoolers today are abusing prescriptions
• Drug use leads to at-risk military personnel from intheatre adverse reactions and post-traumatic stress
• Nationally States are looking to share pharmacy
records to reduce prescription abuse, pill mills and
rogue doctors
• In California 80% of prescriptions are for non-residents
• DOJ / BJA PMIX program – Prescription Medication
Information eXchange – using NIEM


12

Requisite Onboarding Flow Process


13

Medical Authority Role

Combines: SOA; BPM; Semantic tools; Secure web services; community
based resources and delivery; NIEM-based information exchanges.

14

PMIX Background

Scale of the exchange challenge

15

Integrated Location Intelligence

Location
information
integrated with
BI to allow
analysis of
incident
patterns, geogr
aphical hot
spots.
.

Draw line around
an area of interest
and highlight all
cases in area, and
drill into details of a
specific incidents.


16

Example – Government Financial Transparency

Coming soon:
PeopleSoft data
integration via
Open-XDX APIs…

http://www.checkbooknyc.com/spending_landing/yeartype/B/year/114
17

Sharing Source Code - GitHub

https://github.com/VerifyXML

18

Applicability to Government Challenges
• Cost of building information exchanges
– Reduction of development sunk costs through minimizing coding tasks
– Allowing rapid prototyping and proof of concepts (agile development)
– Flexibility - dynamic adaptable templates instead of rigid fixed code
– Reuse – templates for common systems / solutions easily shared and adapted

• Government transparency and public information sharing
– Structured content from data stores – e.g. election results reporting, monthly cost
reports, scheduled road maintenance; obvious metadata and semantics

– Simple search requests on data – e.g. part numbers, codes, licenses lookup
– Not intended for unstructured and textual content document delivery

• Practical real world data sharing anywhere
– Direct simple tool with short learning curve and plug and play deployment


19

Dictionaries - Key Technology and Foundation Pillar
NIEM Past and NIEM Future
Lessons Learned

NIEM + INFORMATION
ALIGNMENT

Who steers NIEM currently?
Founders and Voting Members
• Dept of Justice
• Dept of Homeland Security
• Dept of Health and Human Services
Ex-Officio Members
• Global Justice Information
Sharing Initiative
• Office of Management and Budget
• Program Manager, Information
Sharing Environment (ISE)
• NASCIO
Partners
• Terrorist Screening Center
• Dept of Defense / Dept of Navy
• Dept of State, Consular Affairs (invited)


21

DoD NIEM Adoption
DoD Chief Information Officer Teri Takai :

NIEM military domain “will support
development of information exchange
specifications across the full range of
military operations.”
NIEM will be used unless component can
show compelling reasons

Lt. Gen. Mark Bowman, Joint Chiefs of Staff CIO/J6

22

National Information Exchange Model (NIEM)
 Created a centralized organization to promote
standardization of information exchange for cross
jurisdictional information sharing.

1 Centralize - Joint DOJ /
DHS / HHS program +
DoD

 NIEM’s governing structure is comprised of
Federal, State, Local, Tribal and private organizations.
NIEM is managed at an executive level by the
Department of Homeland Security (DHS), Department
of Justice (DOJ), and Department of Health and
Human Services (HHS) + DoD


23

FEDERAL AGENCY COMMITMENTS

AGENCY
Department of Agriculture
Department of Defense
Department of Education
Department of Energy
Department of Health and Human Services
Department of Homeland Security
Department of Housing and Urban Development
Department of Justice
Department of Labor
Department of State
Department of the Interior
Department of the Treasury
Department of Transportation
Department of Veterans Affairs
Environmental Protection Agency
General Services Administration
National Aeronautics and Space Administration
National Archives and Records Administration
National Science Foundation
Nuclear Regulatory Commission
Office of the Director of National Intelligence
Social Security Administration
Geospatial Line of Business
Grants Management Line of Business
Financial Management Line of Business
Human Resources Line of Business

USE OF NIEM
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Committed to Use
Further Evaluation Required
Committed to Use
Committed to Use
Committed to Use
Will Not Use
Committed to Use
Will Not Use
Committed to Use
Committed to Use

24

The NIEM Framework
NIEM connects communities of people who share a common need to
exchange information in order to advance their missions, and provides a
foundation for seamless information exchange between federal, state,
local, and tribal agencies. Much more than a data model, NIEM offers an
active user community as well as a technical and support framework.
Community

Technical Framework

Support Framework

Formal Governance
Processes

Data Model

Tools for Development
and Discovery

Online Repositories

XML Design Rules

Established
Training Program

Mission-Oriented Domains

Development Methodology

Implementation Support

Self-Managing
Domain Stewards

Predefined
Deliverables (IEPD)

Help Desk &
Knowledge Center

The NIEM Data Model
NIEM’s data model is a set of common, controlled, and approved XML
data structures and definitions vetted through the Federal, State,
Local, Tribal and Private Sectors.

Data elements are organized into core and
domain-specific components
Core components are
used by multiple
domains and can be
described by structure,
semantics, and
definition universally

Domain-specific
components are
continually updated by
subject matter experts
that are actual NIEM
participants and
industry experts for
their particular domain

NIEM Naming and
Design Rules (NDR)
specify how each of
these components are
defined and utilized

NIEM’s Domains View

NEWEST DOMAINS
NIEM Government Resource
Management Domain

NIEM Health Domain
NIEM Human Services Domain

DOMAINS IN PLANNING
NIEM Agriculture
NIEM Education
NIEM Transportation

27

NIEM Past and Present Challenges
• Vertical domain vocabulary for DHS and DOJ
• One dozen domain dictionaries
• Technology limited - built using XSD schema
• Core components highly contextual to DHS/DOJ
• Surprisingly – no actual logical models of information!
• Gap with semantic technologies integration
• Limited data content rules and code lists
• Mapping automation support missing
• Multi-year development life cycles


28

SOA View - Information Sharing Stack and Rules
NIEM: rules important; not just
data

Business
Process,
Enrichment,
Routing
Rules

Privacy and Policy
Automation
Identity and
Access
Management
Routing / Process
Flow
Standardized
Metadata

Validation
Rules


Privacy and
Policy
Automation
Rules

Common
Vocabulary

Identity,
Access
Control,
Classifications
Rules

29

NIEM is still improving…
•
•
•
•

Collections of complex XML Schema
Verbose components
Embedded context in names
Currently facing significant scaling challenges
– Inconsistencies; too much manual management; slow lifecycles

• Dictionary technology incubating
• Enhanced code lists mechanism incubating
• UML profile is evolving initiative with OMG
– Attempt to marry modelling techniques and XSD Schema syntax

• Policy and Security mechanisms incubating
• Need to embrace enabling tools for rapid expansion of
domains and community collaboration


30

The 8 “D”s and NIEM

• Design
• Develop
• Deploy
• Document
• Dictionaries
• Discovery
• Differentiate
• Diagnose

NIEM IEPD Process

Repeatable, Reusable Process

(Exchange Specification Lifecycle)
*IEPD - Information Exchange Package Documentation


31

Integrating into your existing processes and control
• Critical to manage and steer use of NIEM
• Ensure business outcomes match requirements
• Lessons learned with NIEM
– The earlier in the software development process that NIEM is
introduced the better the overall outcomes
– Each step has deliverables – business plan, delivery
architecture, data model, alignment reports, schema, test results
that can be monitored in your SDLC*
– Monitoring products reinforces reuse as best practice
– Tools essential in review processes

• Collaboration tools can coordinate artifacts across
projects and participants
• Test bed tools and open APIs reduce integration
*SDLC – Software Development Life Cycle
alignment costs

32

Dictionaries: Key Pillar of Information Sharing
Components
1

Canonical XML Components Dictionary

Canonical
Dictionary
Collections

XML
User Inserts

2

Relationship
Lookups

Component Associations and Couplings

Navigation
and Query
Tools

Domains Reuse Library
3

Exchange Templates and Rules

Template

Catalog

Automatic Rendering Tools
4

W3C Schema and Model Representations

Schema

5

Delivery Control, Messaging, Security

XML
Models

Component
s

Deployment Environments and Middleware

Testing Workbench, Rules Engine, Data Samples, Integration ETL

6

Implementation Artifacts and Examples

33

Developing domain dictionaries (EIEM)
• Allows domains to manage their components libraries
• Provides consistency for project development teams
– Sets of NIEM consistent XML exchange components
– Aligned to enterprise data stores
– Optimized for reuse and interoperability

• Save time and effort across the enterprise
– Perennial question for developers – when should I use NIEM
components, and when our own local ones?
– Are there components already available for that purpose?

• Provide formal mechanisms and procedures to share
components and collaborate across SDLC process
• Provide external parties consistent data views
*EIEM – Enterprise Information Exchange Model


34

EIEM/BIEC
• Business Information Exchange
Components (BIEC)
– NIEM-conforming XML schema data
component definition that meets a
particular recurring business
requirement for an enterprise

• Enterprise Information Exchange
Model (EIEM)
– NIEM-conforming schemas that define
data components to be reused in
IEPDs developed by an enterprise;
collection of enterprise BIECs
organized into a subset and one or
more extension schemas

Available Dictionary Tools
• CAM toolkit provides a rich set of tools to create and
manage dictionaries
– Bottom up harvesting of existing information assets
– Top down modelling and engineering
– Reuse scoring and comparison reporting

• Dictionary aligned with UN/CEFACT CCTS work
– Supports concepts and model
– Component renamer supports NIEM Naming and Design Rules

• Practical solution - supports desktop tools
– Support for Excel spreadsheet importing and exporting
– Can generate UML models
– Works with simple Mindmap rendering

• Dictionary Collections
– Create collaborative shared sets of dictionaries

36

Dictionary Management / Acquisition


37

Value Proposition

• Allow business data analysts to focus on
information needs and build data exchanges
• Aligns information with industry standards and
enterprise information stores
• Ensures consistent usage and definitions using
profile of syntax-neutral terms and constructs
• Components can be derived from existing
domain schema and data structures
• Supports providing sharing and collaboration
services
• Allows development of supporting analytics tools

38

The Vision

XML
Technologies

UML
Technologies

W3C Schema
Tools

NIEM
Components in
Neutral
Dictionary
Representation

Semantic
Representations

Rules
Technologies
HTML 5
rendering tools
Security
solutions

Middleware
solutions

39

NIEM Concepts, Tools and Adoption
Information Exchange Life Cycle (IEPD)

NIEM DEVELOPMENT

National Information Exchange Model (NIEM)
Tools for enabling

1 interoperability

Provides the tools for
enabling interoperability
at the data layer within
and across systems
supporting information
sharing, while
preserving investments
in current technology
and optimizing new
technology
development.

COMPLEXITY
multiple
disconnected
components +
closed coded

41

CAM Toolkit (http://www.cameditor.org)
•
•
•
•
•
•

Minimal learning curve for practitioners
Provide technology neutral methods, tools and techniques
Leverage visual metaphors – WYSIWYG
Business Rule Validation
Conformance Test Suites
SQL data mapping / XML generation (code-free methods)

SIMPLICITY
integrated
components +
visual metaphors +
open source
• Creates technical artifacts needed for a NIEM IEPD
• Deliver the NIEM domain and core component sets in format
that can be quickly adapted and reused

42

CAMeditor.ORG Project Statistics
SNAPSHOT OF
PROJECT ACTIVITIES
130,000+ CAMeditor.org
page visits to site

165+ countries have
downloaded tools;
30% of visitors are from
U.S.;
700+ downloads weekly

2000+ student views of
online video training
resources

8 languages now
available

www.cameditor.org
www.niemtrainingvideos.org

43

Summary

GOVERNMENT
OPPORTUNITIES

Key Technology Needs
• Delivering on the Open Data Digital Strategy Vision for government
• Open Standards and Open Source based
• Plug and play with code-free templates and rapid development
• Supports NIEM and Open XML exchanges
• Leverages deployed technology today
• Workflow integration
• Dictionary component management
• Secure messaging delivery and partner management
• Delivered across-platform and device
• End-to-end security & governance

45

Opportunities / Challenges
• Open Data movement – delivering on promise of

government transparency
• Enabling next generation digital economy and
information sharing

• Providing improvements and efficiencies for intragovernment information sharing
• Integration into SOA delivery stack
• International collaboration on information standards


46

Open XDX - Conceptual Overview
Data Exchange

Control template contains information of
the exchange structure design and DB
mapping rules of data tables and columns

Existing
Information
Databases

SQL

SQL

Template
Structure

JDBC
connection

Rules

Rapid

DB Mappings

Deploy

Open-XDX

Configuration

Parameters

RESTful Webservice (WADL)
or
SOAP (WSDL)

Open
Data XML Packaging

©2012 Oracle Corporation

Payload
XML/JSON Send

Delivery
Service

API

47

NIEM IEPD / Exchange Delivery Lifecycle

Dictionaries

Requirements

Discovery

Updates

Design
Diagnose

Drag and Drop
Visual
Designer

Develop

XML
Samples

Exchange

1

Templates

Production

Differentiate

Results

Deploy

XSD
Schema

Document

NIEM IEPD
Reports

2

3

Validated

XMI / UML
Models

Templates /
Schema


Document
ation

4

Required
IEPD artifacts

5

48

IEPD Delivery Tasks / Tools Matrix

Exchange Schema Development
Canonical Model Development / Generation
Exchange Schema Generation
NIEM Compliance Checking / Reporting
WSDL / JAXB Binding Generation
Operation Message Test Case Generation
Production Services Message Generation
SQL Schema Mapping
NIEM IEPD Artifact Generation
- Cross-reference spreadsheet
- UML model
- Business Rules Report
- XSD schema package
Conformance Test Suite
Run time XML instance validation

CAM
X
X
X
X
X

CAMV

Open-XDX
(OPX)

X
X
X

X
X
X
X
X
X
X
X

In order to be NIEM-conformant, the IEPD must adhere to:
1.
NIEM Conformance Document
2.
NIEM Naming and Design Rules (NDR) v1.3
3.
NIEM Model Package Description (MPD) Specification v1.0


49

XML Technology Components
NIEM: need to manage
complete aspects of exchange
delivery, not just the structure
and content data model


50

Swim Lane View
UML Technologies
UML
XMI

W3C Schema
XSD

Patterns

Associations
Stereotypes
Inheritance

This is what NIEM exchanges
are delivered with on-the-wire!

Namespace

Enumerations
Cardinality
Facets

XML Technologies
XML

HTML

XQuery
XPath

XSLT

Web

Elements

JavaScript

JSON

Attributes

REST

Content

Complex Types

SQL
SOAP

Objects
Audience:

Audience:

Audience:

Audience:

Data Modellers / Designers

Software Developers and
Middleware Engineers

General content delivery
and applications; content
engineers; rules
representation systems;
multimedia delivery;
geospatial systems

Web
application
developers

Open-XDX

51

Dictionaries Semantics Approach

• Abstract dictionary representations with strong
semantics, rules and code lists support
• Schema, models, documentation are generated from
dictionary definitions automatically
• Contextual mechanisms allow linear number of true
core components – not exponential growth
• Easier for practitioners to leverage with more
predictable and repeatable results
• Enable domain use horizontally across government
• ETL mapping automation support

• Continuous collaboration environment

52

General Ledger – RICE Objects

General Ledger Open Interfaces
General Ledger Standard Reports Overview
General Ledger Screens Overview
Developing new forms and reports
Modification of existing forms and reports
Registration of forms and functions


53

Should you require any further
information please do not hesitate to
contact us

http://www.oraclecourseonline.com
-oracle fusion soa online training
contact us:
info@magnifictraining.com or +919052666559
By Real Time Experts from Hyderabad,
Bangalore
,India,USA,Canada,UK, Australia, South
Africa.


55

Oracle fusion soa operations and configuration

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (12)

En vedette

En vedette (8)

Similaire à Oracle fusion soa operations and configuration

Similaire à Oracle fusion soa operations and configuration (20)

Dernier

Dernier (20)

Oracle fusion soa operations and configuration

Notes de l'éditeur