This document provides an approach to simplify designing in a license constrained world by identifying usage scenarios for Oracle middleware products. It begins with disclaimers and background information on the licensing documentation. Key aspects discussed include terminology, the license picture, what qualifies as an Oracle product, and OTN licensing. Examples of usage scenarios are then provided for AIA, SOA Suite, ODI, and Informatica-based integrations. Diagram keys are also explained to help interpret the licensing validity of each scenario.

1. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 1)
Phil-at-mp3monster.org
www.mp3monster.org
‘An Approach to making it easer to
design in a License constrained World’

2. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 2)
Phil-at-mp3monster.org
www.mp3monster.org
Disclaimer
• As the subject of licensing can be legally very
sensitive …
– The following presentation is the opinion of the presenter
only
– The viewers expressed here are not representative of any
employer or client
– The contents of this presentation do not constitute a legal
understanding,
– Neither can the presenter or any employer or client accept
any liability for the accuracy of the information presented

3. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 3)
Phil-at-mp3monster.org
www.mp3monster.org
Background
• This deck looks at the approach in terms of Oracle products, but the ideas should be largely
portable to any vendor.
• The Licensing documentation of what can and cannot be done with Oracle middleware is
complex.
• Therefore to simplify understanding we have identified and produced a series of use cases
that demonstrate what can and can not be done that allows devs/designers to work without
needing to refer to 1 or 2 individuals
• In addressing the licensing considerations we’ve been able to lay on top some Architectural
Governance
• What you’ll see …
– Our master document has some pre-amble this explained here, and elements included
(explain vs show because of commerciality)
– Look at a few examples (a subset) of the master document…
• In many respects these are like Design Patterns and Use Cases, except …
– Patterns help solve common problems
– These are more, can I use this ‘design pattern’
– This can also feel like Use Cases as well
– So to avoid loaded terms what we have are ‘Usage Scenarios’

4. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 4)
Phil-at-mp3monster.org
www.mp3monster.org
Terminology – For This document &
Interpretation
• 1st Step qualify our terminology for the document e.g.
– 3rd Party Applications are non Internal & Non Oracle solutions
used by the company
– Company retained apps – are those solutions built by us that
reside outside of the Oracle ecosphere
– OBIEE = BI Platform (BI server, presentation server, scheduler and
publisher)
– OBIA = Pre-packaged ETL, RPD (meta data file which defines the
physical layer (OBAW schema), business model mapping layer and
presentation layer) and web catalogue code sets (reports,
dashboards etc.)
• 2nd some terms in the legal Oracle docs can be ambiguous or even
conflict with the technology application e.g. Composite (SCA or
deployable package)
• If nothing else – be consistent even if you are consistently wrong (if
you get into a dispute over wording then you can’t be accused of
deliberate misinterpretation in some places)

5. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 5)
Phil-at-mp3monster.org
www.mp3monster.org
License Picture
• The overall picture is driven by several overlapping documents that could appear to be
contradictory.
• Documents do have precedence to resolve conflicts (priority in descending order). These are:
1. Customer Ordering Document (referred to as COD in this document)
• Commercially Sensitive
2. Oracle License and Services Agreement (referred to as OLSA in this document)
• Commercially Sensitive
3. Oracle – Applications Licensing Table (referred to as ALT in this document)
• Available from http://www.oracle.com/us/corporate/pricing/application-licensing-table-070571.pdf
3. Oracle Fusion Middleware Licensing Information 11g Release (11.1.1) (referred to as FMLI in this
document)
• Document Reference E14860-03
• Available from http://docs.oracle.com/cd/E12839_01/doc.1111/e14860/title.htm
4. Oracle Global Technology Pricelist (referred to as GTP in this document)
• Available from http://www.oracle.com/us/corporate/pricing/technology-price-list-070617.pdf

6. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 6)
Phil-at-mp3monster.org
www.mp3monster.org
What Qualifies as an Oracle Product (within the
current organisation approved tech stack for
middleware)
• We identified for the core document a common parlance for the Oracle Products as
they have some varying name e.g. OEM, Seibel UCM
• Differentiate Technology Licensed vs Product licensed e.g.
– The various Licensing documents refer to Eligible products. This is defined by the
products (not technology licensed items) in the customer Ordering Document(s)
• We also provide a detailed list of products licensed that can be cross referenced –
helpful if you have multiple purchases
• Makes the following content easier

7. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 7)
Phil-at-mp3monster.org
www.mp3monster.org
OTN Licensing
• Many vendors offer a service like Oracle Technology Network (OTN) where
you can download products, with license constraints.
• All Oracle products can be retrieved through the Oracle Technology Network
(OTN) which offers a licensing statement at the time of download – this
license constraint means for us:
– Oracle OTN licenses should be avoided,
– they are limited licenses to use Oracle programs only for the purpose of
prototyping , testing and demonstrating an application and not for any
other purpose,
– the OTN license is restricted to one computer only and can only be used
by one person in the operating environment.
– No support is provided by Oracle to any OTN licensed download.

8. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 8)
Phil-at-mp3monster.org
www.mp3monster.org
SOA Suite Licensing Differentiators
Product Name Description
SOA Suite for Oracle Middleware An unrestricted deployment of SOA
Suite
Identified COD p3
SOA Suite for Oracle Middleware for
Oracle Applications
SOA Suite with licensing constraints
Identified in ALT not in COD
SOA Suite for Non Oracle Middleware For running SOA suite on top of
another app Server – for example
WebSphere
Where there are subtle differences in products, or product naming can cause
confusion an approach such as this within the context material can help …
There are some subtleties in the SOA Suite naming which are clarified here for
future reference as it impacted initial assessments.

9. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 9)
Phil-at-mp3monster.org
www.mp3monster.org
Diagram Key
• Block colour is primary indicator
• Text Colour differentiates variations
• Note Custom SOA Composite is a composite not used in a custom
PIP context (i.e. only uses SOA Suite and has no connection to AIA
Foundation Pack)
• Alternate Paths are shown by
• Oracle Product – black & white text to help illustrate multiple
products
Oracle
Product
Custom PIP
Retained
Application
Oracle
Product
Licensed
PIP
3rd Party
Application
Custom
SOA
Composite
• Shaded background colour indicates deployment location. By
default it is assumed deployment location is inline with
architectural guidance, so deployment location is only
highlighted when necessary
• Green non Oracle PIP license restricted locations
• Blue – Oracle License PIP restricted locations

10. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 10)
Phil-at-mp3monster.org
www.mp3monster.org
Diagram Key
• Data Store symbology can mean any form of data store
including flat files for the company & 3rd Party Solutions
• Oracle Symbology is very specific
– OBIEE = BI Platform
– OOTB ETL refers to pre-packaged ETL routines provided
as part of OBIA
– Custom’d (Customised) ETL refers to ETL
extended/customised from prepackaged ETL provided as
part of OBIA
– Any Oracle Data Store relates to data stores in support of
approved Oracle Applications
• End user consuming via dashboards/reports etc
Company
Data Store
3rd Party
Data Store
OBIA
Any Oracle
Data Store
OOTB ETL
Custom’d
ETL
Bespoke
ETL

11. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 11)
Phil-at-mp3monster.org
www.mp3monster.org
Validity Diagram Key & Interpretation
Notes
• Green tick - indicates license compliant utilisation
• Red cross – indicates deployment scenario in conflict with
license constraints
• Orange exclamation – can be done within licensing BUT
brings additional constraints and requires explicit design
justification/documentation with explicit Architectural
Signoff
Notes
• Note in the event of a scenario being deemed in conflict only the conflicting
document references will be provided
• Where okay or requiring explicit governance all significant references will be
identified.

12. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 12)
Phil-at-mp3monster.org
www.mp3monster.org
Example Usage Scenarios

13. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 13)
Phil-at-mp3monster.org
www.mp3monster.org
AIA BASED INTEGRATION
This is specifically for AIA tier of integration – SOA suite tier is addressed
separately

14. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 14)
Phil-at-mp3monster.org
www.mp3monster.org
AIA Licensing Scenarios
Classic AIA Flow
• Connecting Company retained apps and
Oracle solutions with or without an EBF
• Licensing References:
– ALT p6.Application Integration Architecture
(para 3 1) )
– COD p3
Oracle
Product
Custom PIP
Component
Retained
Application
Oracle
Product
Licensed
PIP
3rd Party
Application
Custom
SOA
Composite
Provider ABCS
JMS Adapter
Retained
Application
e.g. MyApp
EBS
EBF
EDW OCH
ConsumerABCS ConsumerABCS
EBS
DB Adapter
3rd party
Application
e.g. AnApp

15. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 15)
Phil-at-mp3monster.org
www.mp3monster.org
AIA Deployment Licensing Scenarios
Oracle App Connection Via PIP using recommended clustering
• Integration to Oracle Applications via a
Licensed PIP, deployed using custom
(company) and Licensed PIP clusters
• Licensing References:
– Alt p6.Application Integration Architecture (para 3 1) )
– OLSA p10.Processor
Oracle
Product
Custom PIP
Retained
Application
Oracle
Product
Licensed
PIP
3rd Party
Application
Custom
SOA
Composite
ProviderABCS
JMS Adapter
Retained
Application
e.g. MyApp
EBS
3rd party
Application
e.g. AnApp
JMS Adapter
Provider ABCS
OCH
EBS
ConsumerABCS
• Integration to Oracle Applications via
a Licensed PIP, deployed using just
Custom PIP cluster
• Incorrect as imposes Licensed PIP
constraints on all capability
• Licensing References:
– OLSA p10.Processor
– Conflict with deployment strategy
ProviderABCS
JMS Adapter
Retained
Application
e.g. MyApp
EBS
3rd party
Application
e.g. AnApp
JMS Adapter
Provider ABCS
OCH
EBS
ConsumerABCS
Oracle App Connection Via PIP using non Licensed PIP Cluster
EBF

16. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 16)
Phil-at-mp3monster.org
www.mp3monster.org
SOA Suite Licensing Scenarios
Indirect with Trigger SOA Suite between
Oracle & Retained / 3rd Party
• Indirect Oracle to 3rd Party and/or Company
application via SOA Suite using file
export/input from a file server to transfer
payload but Web invocation to signal file
readiness
• Licensing References:
– COD p3
Oracle
Product
Custom PIP
Component
Retained
Application
Oracle
Product
Licensed
PIP
3rd Party
Application
Custom
SOA
Composite
OCH
File Adapter
3rd party
Application
e.g. MailShot
File Server
File Server
SOA Composite
File Adapter
File Detection via W/S trigger

17. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 17)
Phil-at-mp3monster.org
www.mp3monster.org
ODI BASED INTEGRATION
Licensing References:
• GTP p10.para 19 & OLSA P11.para 5
• Data Integrator Enterprise Edition, the processor(s) where the data transformation processes are executed must
be counted for the purposes of determining the number of licenses required
• Architectural Governance is required if the target is nor identified by ULA declaration
• Mapping for ODI is done through a Knowledge Module (KM) even if there is no transformation

18. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 18)
Phil-at-mp3monster.org
www.mp3monster.org
ODI Usage Scenarios
ODI Using Oracle Appl Data Store and OBIA
• Between Oracle applications and OBIA
using ODI
• Licensing References:
– COD p3
– GTP p10.para 19 & OLSA P11.para 5
– See section header for Architectural Governance
rule
Company
Data Store
3rd Party
Data Store
OBIA
Any Oracle
Data Store
OOTB
ETL
Custom’d
ETL
Bespoke
ETL
Bespoke
KM
ODI Between the Company & Oracle Application Data Store
• Between the Company & Oracle
using ODI
– At least one of source or target must be
Oracle App
• Licensing References:
– COD p3
– GTP p10.para 19 & OLSA P11.para 5
– See section header for Architectural
Governance rule
Bespoke
KM
Any Oracle
App Data
Store
3rd Party
Data Store
Company
Data Store
File Store
Any Oracle
App Data
Store
OBIA

19. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 19)
Phil-at-mp3monster.org
www.mp3monster.org
ODI Usage Scenarios
Company
Data Store
3rd Party
Data Store
OBIA
Any Oracle
Data Store
OOTB
ETL
Custom’d
ETL
Bespoke
KM
Bespoke
KM
3rd Party
Data Store
Company
Data Store
File Store
3rd Party
Data Store
Company
Data Store
File Store
ODI Between the Company Application Data Sources
• ODI between (to or from) the
Company
– At least one of source or target must be
Oracle App to be compliant
• Licensing References:
– COD p3
– GTP p10.para 19 & OLSA P11.para 5

20. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 20)
Phil-at-mp3monster.org
www.mp3monster.org
INFORMATICA OBIEE SUPPORTING
BASED INTEGRATION
• This covers the Informatica instance licensed to support OBIEE activities – so scenarios
will include (OBIEE) in their name
• Note this could eventually be superseded by an ODI deployment.
• Licensing References:
• GTP p10.para 18 & OLSA P11.para 5
• Informatica PowerCenter and PowerConnect Adapters only the processor(s) on which the target database is
running must be counted for the purpose of determining the number of licenses required.
• Architectural Governance is required if the target is nor identified by ULA declaration

21. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 21)
Phil-at-mp3monster.org
www.mp3monster.org
Informatica OBIEE Supporting Scenarios
Informatica (OBIEE) Using Oracle Data Source
• Transferring content from an Oracle
application data store to OBIA using
prebuilt ETL
• Licensing References:
– OLSA.P14 –Informatica PowerCenter
– GTP p10.para 18 & OLSA P11.para 5
– See section header for Architectural Governance rule
Company
Data Store
3rd Party
Data Store
OBIEE
Any Oracle
Data Store
OOTB
ETL
Custom’d
ETL
Bespoke
ETL
OOTB
ETL
Informatica (OBIEE) Migrates Data from the Company or
Oracle Data Source via Bespoke ETL
• Transferring content from an Oracle
application data store to OBIA
using custom developed ETL
• Licensing References:
– OLSA.P14 –Informatica PowerCenter
– GTP p10.para 18 & OLSA P11.para 5
– See section header for Architectural
Governance rule
Bespoke
ETL
3rd Party
Data Store
Company
Data Store
Any Oracle
Data Store
OBIEE
OBIEE
File Store
Any Oracle
Data Store

22. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 22)
Phil-at-mp3monster.org
www.mp3monster.org
Informatica OBIEE Supporting Scenarios
Informatica (OBIEE) Using Oracle Data Source to the Company Solution with
transform
• Transferring content from an Oracle
application data store to a Company
data store
• Licensing References:
– OLSA.P14 –Informatica PowerCenter
Company
Data Store
3rd Party
Data Store
OBIEE
Any Oracle
Data Store
OOTB
ETL
Custom’d
ETL
Bespoke
ETL
Informatica (OBIEE) Migrates Data from OBIEE to the
Company with transform
• Transferring content from OBIA to
another data store
• Licensing References:
– OLSA.P14 –Informatica PowerCenter
Any Oracle
Data Store
OOTB
ETL
Any Oracle
Data Store 3rd Party
Data Store
Company
Data Store
File Store
OOTB
ETLOBIEE
3rd Party
Data Store
Company
Data Store
File Store

23. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 23)
Phil-at-mp3monster.org
www.mp3monster.org
BI PUBLISHER
• BI Publisher is provided as part of OBIEE1
• Identified as (OBIEE)
• Also available in limited form in support of EBusiness Suite Applications (ALT P13.Oracle E-Business Suite
Applications)
• Identified as (E-Business Suite)
• RDO Provides governance statements
• BI Publisher via OBIEE is limited by named user licensing (named user = app or individual)
1http://docs.oracle.com/cd/E23943_01/doc.1111/e14860/new-bi.htm#BGBJGBDF

24. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 24)
Phil-at-mp3monster.org
www.mp3monster.org
BI Publisher (OBIEE)
• Transferring content to or from a file
store
• Licensing References:
– RDO.Oracle BI publisher
Company
Data Store
3rd Party
Data Store
OBIA
Any Oracle
Data Store
OOTB
ETL
Custom’d
ETL
Bespoke
ETL
BI
PublisherOBIA
3rd Party
Data Store
Company
Data Store
File Store
OBIA Data Output via BI Publisher using OBIEE Instance
BI
Publisher
Company
Data Store
3rd Party
Data Store
Company
Data Store
File Store
Company Data Output via BI Publisher using OBIEE Instance
• Transferring content to or from a
file store
• Licensing References:
– RDO.Oracle BI publisher
3rd Party
Data Store
OBIEESvr
OBIEESvr

25. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 25)
Phil-at-mp3monster.org
www.mp3monster.org
BI Publisher (E-Business Suite)
Company
Data Store
3rd Party
Data Store
OBIA
Any Oracle
Data Store
OOTB
ETL
Custom’d
ETL
Bespoke
ETL
• Reporting using non app data not
allowed due to licensing constraint
– (e.g. staging) not supported
• ALT p13.Oracle Business Intelligence
Publisher.Oracle E-Business Suite Applications
(1) & (2)
• RDO.Oracle BI publisher
BI
Publisher
EBusiness
Schema
3rd Party
Data Store
Company
Data Store
File Store
E-Business Suite Data Output via BI Publisher using Non app
Data
Bespoke
Report
Config
EBusiness
Staging
Schema

26. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 26)
Phil-at-mp3monster.org
www.mp3monster.org
END OF USAGE SCENARIOS

27. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 27)
Phil-at-mp3monster.org
www.mp3monster.org
Questions

28. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 28)
Phil-at-mp3monster.org
www.mp3monster.org
Questions

29. An Approach to making it easer to design in a License constrained
World
19/05/2014 (slide 29)
Phil-at-mp3monster.org
www.mp3monster.org
Thankyou