Session ID:

From OBIEE or OBIA to 10132

Cloud: The Fundamentals
Prepared by:
Mazen Manasseh
Sr. Solutions Architect
How to migrate an on-premises Perficient, Inc.
Oracle BI solution to Oracle
Analytics Cloud (OAC) Apr 22, 2018

Remember to complete your evaluation for this session within the app!
About Perficient

• Founded in 1997
• Public, NASDAQ: PRFT • Oracle Platinum Partner
Cloud Select
• 2016 revenue $487 million
• Major market locations • 3,000+ Oracle Implementations

• Global delivery centers in China and India • Solution Expertise

• 3,000+ colleagues EPM | ERP | BI | CX

• Dedicated solution practices • 15 Oracle Specializations

• ~95% repeat business rate • Oracle Approved Education
Center
• Alliance partnerships with major
technology vendors • Oracle Excellence Award Winner
• Multiple vendor/industry technology and
growth awards
About the Presenter

Mazen Manasseh
Sr. Solutions Architect, Oracle BI

• Joined Perficient in 2009

• 14 Years Experience – BI, Data Warehousing and Oracle Analytics
• Multiple Full Life Cycle Implementations across different industries

• Contact Information
[email protected]
https://www.linkedin.com/in/mazenmanasseh
Agenda

• Introduction to BICS & OAC

• Which Cloud Data Warehouse?
• Data Integration Options
• Architecture Options for Oracle Cloud Analytics
• Migration from OBIEE to OAC
• Oracle BI Apps Deployment on Oracle Cloud
BICS vs OAC
BICS vs OAC

• BICS:
– Oracle Managed
• Test and Prod as part of same subscription
• Backup and Recovery
• Service monitoring and restoration
• Patching and upgrades
• Integrated Oracle Database Schema Service
• Multi-tenant
• User Based Subscription
– User licenses
• OAC
– Customer Managed (Eventually will supersede BICS with an Oracle Managed options)
– OCPU licenses
Cloud Data
Warehouse Options
Oracle Cloud Database:
Data Warehouse Options
Database Cloud Service (DBCS) Oracle Exadata Cloud Service
• DWs are usually Enterprise; or High • Powerful performance, secure, high
Performance editions to support availability
partitioning and analytical functions • Oracle hosted and controlled hardware
• Appropriate for DWs that are ~2.6 TB or • Customer managed database
less. • Larger data warehouses over 2.6TB

Data Warehouse Cloud Service Bare Metal Cloud

• Optimized for DW workloads • DBCS on BMC is best for performance
• Autonomous, Adaptive tuning intensive workloads.
• Based on Exadata technology • Dedicated HW, low latency, high config.
• Self-scaling of compute and storage with • Customer controlled and managed on
no downtime cloud
OAC Data Integration
Options
OAC Data Integration Options

– Direct Query:
• DV direct connections
• RPD direct connections (RDC or VPN)
– Direct import (upload data into an OAC data set (50MB max per data set)
– Batch import such as with DataSync or ODI
OAC Connection to On Prem Data Sources

Two options are available:

1. Remote Data Connector (RDC)

• Requires an on-prem WebLogic or Apache Server to host RDC component

• Heavier processing on OAC and therefore may require additional OAC OCPUs

2. VPN: A more robust and reliable solution compared to RDC.

a. Corente VPN Gateway is free software that can be hosted on Oracle Cloud Compute in same
Identity Domain as OAC
• Hosted on a separate OCPU on Oracle Compute Instance
• Create an IPSecure Tunnel between OPC and on-prem.
• Create a GRE Tunnel between Corente Gateway on Cloud Compute and OAC Instances.
b. Or Oracle VPNaaS (New Cloud Service)
• VPNaaS is an easier to manage solution compared to Corente.
Architecture Options
Current State Architecture Cloud On Prem

Source Systems Data Transformation Data Warehouse Analytics Platform

Other Cloud
Connector OBIEE 11g / 12c
SaaS
APIs
Enterprise Model
Oracle BI Cloud
Fusion Connector BI
Cloud OTBI ETL Apps
(ODI)
Data
Warehouse
3rd Party Catalog
Source BI
BI Apps BI
EBS, Apps Apps
PeopleSoft,
Fusion,
Siebel
Cloud Architecture Options

1. BI Apps & OBIEE on IaaS

2. BI Apps on-premises with OAC front end
3. BI Apps on PaaS
1. Cloud Sources
2. On Premises Sources
Architecture Options:
Data Warehouse on Premises with OAC Front End
Cloud On Prem

Source Systems Data Transformation Data Warehouse Analytics Platform

Other Cloud
SaaS Connector OAC
APIs
Enterprise Model
Oracle BI Cloud
Fusion Connector BI
Cloud OTBI ETL Apps
(ODI)
Data
Warehouse
3rd Party Catalog
Source BI
BI Apps BI
EBS, Apps Apps
PeopleSoft,
Fusion,
Siebel
Architecture Options:
BI Apps on PaaS (On-Prem Sources) Cloud On Prem

Source Systems Data Transformation Data Warehouse Analytics Platform

DB Cloud Service OAC

Enterprise Model
Storage
BI
Cloud
Apps
Service
Data
Warehouse
Catalog
BI
Apps BI
3rd Party Apps
Source ETL
(ODI)
EBS,
BI
PeopleSoft,
Apps
Fusion,
Siebel
Architecture Options:
BI Apps on PaaS (Cloud Sources)
Source Systems Data Transformation Data Warehouse Analytics Platform

Compute Service DB Cloud Service OAC

Cloud Enterprise Model
Other ODI
SaaS Connector
APIs BI
Config Mgr Apps
Oracle BI Cloud Data
Fusion Connector FSM Warehouse
Cloud OTBI Catalog
OBIEE BI
Apps BI
BI Apps
Apps
Architecture Options: BI Apps on IaaS
Cloud On Prem

Source Systems Data Transformation Data Warehouse Analytics Platform

Other Cloud
Connector OBIEE 11g / 12c
SaaS
APIs
Enterprise Model
Oracle BI Cloud
Fusion Connector BI
Cloud OTBI ETL Apps
(ODI) Data
Warehouse
3rd Party Catalog
Source BI
BI Apps BI
EBS, Apps Apps
PeopleSoft,
Fusion,
Siebel

Compute Cloud Service

OBIEE to OAC
Migration Steps
Migration Process

Migrate
Subscribe to Create OAC OBIEE
OAC Service Content to
OAC
Subscribe to OAC

1. Subscribe to OAC

2. and Other Oracle Cloud Services:

a) Oracle Cloud Compute (uses block storage to store binaries)
b) Oracle Database Cloud Service
c) Oracle Storage Cloud Service (for backup storage)
Create OAC Service
1. Create an SSH key pair: Either use your already existing public key to enter it in or generate a new one and
download its private key locally to connect from Putty or WinSCP for example.
2. Choose Billing: Metered (Monthly or Hourly) or non-metered: Need to decide on metered vs non-metered for
billing upfront.
3. Authentication for OAC users: Chose between: OAC Weblogic embedded LDAP or IDCS
4. Type of OAC service to enable:
a) Data Visualization
b) Enterprise Data Models (this includes Data Visualization)
c) Essbase Cloud (Scenarios and what-if analysis)
5. Chose Compute Shape: Combination of OCPU and RAM for example: 2OCPUs and 16GB. Compute shape can be
scaled up or down after creating service instance.
6. Specify the DB Cloud Service to use for OAC schemas PDB (pluggable DB). This needs to be ready before creating
OAC service. Provide a unique prefix for the OAC schemas. Different schema prefixes allow hosting multiple OAC
service (dev, test, prod) on the same cloud database.
7. Specify a Storage Container location (Oracle Cloud Object Storage): Requires the URL and Login and is used for
analytics data sets, logs and backups.
Migrate from OBIEE to OAC

Based on the on-prem OBIEE version:

A. From OBIEE 11g 11.1.1.6 or later

1. Download migration-tool.jar from OAC Snapshot Console to local OBIEE 11g instance
(Windows or Linux).
2. Use this tool to create import bundle (.jar file) for all 11g metadata.
3. Copy generated JAR file over to OAC instance and run: migration_import_bundle
command.
4. Restart OAC services.

B. From OBIEE 12c

Just create a snapshot (.bar file) and export/import/restore to OAC service. This includes
data model, dashboards, analyses and application roles.
Additional Considerations
• Update connection pools of on-prem RPD as necessary to point to the correct databases.

• Make sure on prem RPDs are valid through the consistency checker.

• Prior to migration, backup OAC by creating a snapshot. Note that uploading data model
(rpd) to OAC replaces any other models created through the OAC thin UI modeler.

• To maintain the data model after migrating an on-prem RPD to OAC, use the OBI Admin
Tool. The thin data modeler UI in OAC won’t work once an RPD is uploaded.
Post Migration Activities
1. Migrate data and content between OAC services using:

a. Snapshots (.bar file): data models, analyses and projects via web console (rpd and
calalog) (snapshot/export/upload/restore).
b. Data sets: use migrate_datafiles script with export/import options
c. If using internal Weblogic LDAP: Export/Import users and groups using script
wls_ldap_csv_exporter.

2. Monitor service instances

3. Patch a service

4. Backup a service
Oracle BI Applications
Cloud Deployment on PaaS
Deployment of BI Apps on PaaS:
Requirements
1. Create Oracle Storage Containers
2. Create VM public and private keys
3. Create Oracle Compute Cloud Service
4. Create Oracle Cloud DBaaS instance
5. Create Oracle Analytics Cloud (OAC) instance
6. Setup Security Rule on DBaaS Cloud Compute: Setup Public IP Addresses for OAC and
Compute Cloud Service to connect to DBaaS
7. Setup Vnc Desktop against Oracle Cloud Compute (needed for Install Wizard)
8. On Cloud Compute Service download BI Apps Software Latest Release 11.1.1.10.2 for
Linux 64bit – Also supports release: 11.1.1.7.1, 8.2, 9.2
Steps to Deploy BI Apps on PaaS

Install BI Apps on Compute Cloud Service

Configuration
WebLogic
System Setup and Config per BI Apps Install
OBIEE Configure Guide
11.1.1.9.0 DBaaS backup Lift & Shift BI Apps to OAC
ODI 11.1.1.9.0 SDS Mode
Memory Remote Data
BI Apps allocation for Register Source Application Connector
WebLogic Systems Roles &
Config OBIEE Configure RDC
Admin and Connect to Presentation
Config BI Apps Managed Target DW Catalog if needed
servers Data Model
Functional
Configuration
Deployment of BI Apps on PaaS:
Data Integration
BI Apps on PaaS picks up data once its loaded in Source Dependent Store (SDS) Schema.

How can we load BI Apps SDS?

1. Oracle Cloud Applications (Fusion Apps): Data is pulled into SDS Schema directly by BI
Apps using HTTPS. Data is then transformed with BI Apps ODI. With Cloud Sources, BI
Apps takes care of populating SDS.

2. On-prem applications (such as EBS, PeopleSoft, etc..): Data is pulled used one of the
following ways:
i. VPN connection (Corente VPN or Oracle VPNaaS): With this BI Apps sees both on-
prem databases and DBCS on the same network, so no additional config is needed.
ii. Use a data replication tool over SSH to replicate data into SDS schema in the Cloud
DW. For example, DataSync or Golden Gate.
Deployment of BI Apps on PaaS:
Data Integration from on-prem sources 1
Cloud On Prem

Source Systems Data Transformation Data Warehouse Analytics Platform

Storage
Oracle Cloud Cloud
Source Apps HTTPS Service
Compute Service
DB Cloud Service OAC
ODI
Enterprise Model
BI Data
Apps BI
Warehouse
Apps
BI
Corente Apps
VPN or VPNaaS Catalog
VPN Tunnel DWH
VPN BI
Apps
DataSync or SDS
GoldenGate SSH Tunnel
EBS, PeopleSoft,
Siebel, etc..
Deployment of BI Apps on PaaS:
Comparison of on-prem Connection Methods

Comparison Criteria Corente VPN or VPNaaS Replication Tool (RDC, OGG)

SDS is not required SDS is required, more DB space
Easy configuration, register Additional configuration to replicate
the on-prem source as usual tables into SDS and setup schedule
BI Apps Configuration Supports all BI Apps ETL ETL Mappings that depend on source
mappings DB SQL packages are not supported
on SDS. Sourcing from DB views add
complexity to replicate into SDS.
Infrastructure Requires a separate Oracle Replication tool client is hosted on an
Cloud OCPU to host Corente on-prem machine
VPN
 [email protected]

Session ID:
10132

Remember to complete your evaluation for this session within the app!