Scenarios for Oracle BI and Analytics in the Cloud E-BOOK

Transcription

1 5 Scenarios for Oracle BI and Analytics in the Cloud E-BOOK

2 TABLE OF CONTENTS INTRODUCTION SCENARIO 2a APPLICATIONS ON-PREMISES ORACLE APPLICATIONS, DATA AND BUSINESS INTELLIGENCE IN THE CLOUD SCENARIO 3 DATA AND APPLICATIONS ON-PREMISES - BI IN THE CLOUD SCENARIO 5 ORACLE BI APPS RUNNING ON ORACLE PAAS SCENARIO 1 APPLICATIONS ON-PREMISES - DATA AND BUSINESS INTELLIGENCE IN THE CLOUD SCENARIO 2b APPLICATIONS ON-PREMISES - NON-ORACLE APPLICATIONS, DATA AND BI IN THE CLOUD SCENARIO 4 DATA AND APPLICATIONS BOTH ON-PREMISES AND IN THE CLOUD WITH BI IN THE CLOUD

3 INTRODUCTION The benefits of the cloud are no longer a mystery - cost savings, scalability, and agility. Users who need business intelligence and analytics can use cloud based software as a service to access data themselves and apply advanced analytics to quickly make fact-based business decisions. Time to value is faster because you don t need to set up infrastructure or data centers or worry about installing and managing software. What is not so well known is that there are many paths to the cloud. Organizations rarely adopt cloud the same way and cloud adoption is often an evolutionary process. The journey to the cloud usually starts with a specific application, but over time more and more workloads are moved to the cloud. This e-book will explain 5 scenarios for the use of Oracle Business Intelligence and Analytics in the Cloud. 01 Each of these five scenarios answers three important questions that are vital for cloud migration: 1. Where is the application? 2. Where is the data at reporting time? 3. Is that data in a transaction system or a data warehouse? This table provides a quick overview.

4 SCENARIO 1 APPLICATIONS ON-PREMISES - DATA AND BUSINESS INTELLIGENCE IN THE CLOUD This first scenario is relatively straightforward and many choose this path to migrate to the cloud. The source application, such as 02 Oracle E-Business Suite, is running on-premises, the data is in the cloud at the time of reporting and it is stored in a data warehouse.

5 SCENARIO 1 APPLICATIONS ON-PREMISES - DATA AND BUSINESS INTELLIGENCE IN THE CLOUD This is the simplest scenario and could be a good first step on your burden on IT. Apps Associates has developed the following tools cloud implementation perhaps starting with your top 20 reports. It s to the cloud. These include: cloud journey. It s suitable for organizations that need a quick also a very good way to move away from out of date, older on-premises applications like Discoverer. This scenario takes the BI and reporting load off your transactional systems and the self-service aspect of cloud analytics reduces the 03 and processes for modernizing old BI systems and migrating them BICS application accelerators IR/Brio to BICS utility and methodology FSG to BICS utility and methodology Discoverer to BICS utility and methodology

6 SCENARIO 2a APPLICATIONS ON-PREMISES ORACLE APPLICATIONS, DATA AND BUSINESS INTELLIGENCE IN THE CLOUD Scenarios 2a and 2b are similar to scenario 1, but just a little more complex. As indicated in the diagrams, there are some on-premises applications and some cloud based applications in these scenarios. These scenarios describe a company that has started to deploy certain applications in the cloud. Their data is going to be in the Cloud at the time of reporting, whether it s from an on-prem- 04 ises system or a cloud-based application, and it s either going to be in a data warehouse or in a cloud-based transaction system. The difference between Scenarios 2a and 2b is that in Scenario 2a the cloud based systems are only Oracle whereas in Scenario 2b the cloud-based systems are both Oracle and non-oracle (e.g. Workday).

7 SCENARIO 2b APPLICATIONS ON-PREMISES - NON-ORACLE APPLICATIONS, DATA AND BI IN THE CLOUD In Scenario 2b we introduce some non-oracle cloud based transaction systems. Both scenarios 2a and 2b suit a company that has already started to implement a cloud strategy. An organization that needs to run analytics across cloud and on-premises systems and wants to avoid point solutions that can lead to multiple versions of the truth. In both these scenarios, real-time reporting against the Oracle cloud based systems is supported. There are many tools and processes that have been developed to accelerate and simplify this scenario, including: 05 Pre-built Workday to BICS Integration Pre-built Taleo to BICS Integration Pre-built Salesforce.com to BICS Integration Pre-built Financials Cloud to BICS Integration Apps Associates Application Accelerators FSG to BICS Methodology and Utility IR/BRIO to BICS Methodology and Utility Discoverer to BICS Methodology and Utility

8 SCENARIO 3 DATA AND APPLICATIONS ON-PREMISES - BI IN THE CLOUD This scenario shows how to obtain the benefits of Cloud BI (flexi- organizations can use Oracle Remote Data Connector. The systems without moving your data to the cloud. To accomplish this, on-premises network. In this solution the reporting metadata layer bility, agility, lower cost structure) with your existing on-premises 06 remote data connector service runs within WebLogic in your

9 SCENARIO 3 DATA AND APPLICATIONS ON-PREMISES - BI IN THE CLOUD (ie RPD) of Oracle's on-premises BI platform, OBIEE (Oracle This scenario is suitable for organizations that don t want to, or Cloud BI engine. This allows customers with existing investments will give you real-time access to your on-premises transaction Business Intelligence Enterprise Edition), is used by the Oracle in on-premises OBIEE deployments to continue to leverage that investment with Oracle's Cloud based BI platform. To achieve this, the OBIEE reporting metadata is simply copied to the cloud BI engine using Oracle's Lift and Shift utility. The cloud BI engine then leverages the OBIEE reporting metadata for all reporting.the OBIEE (Oracle Business Intelligence Enterprise Edition) on-premises RPD Client Admin Tool is also required because the repository or RPD is the file for the reporting metadata layer which is the brains behind any BI system. It tells the BI engine how the underly- ing data is interconnected. Then it will be configured to connect to the remote data connector service. Lastly, that on-premises reporting metadata layer will be copied up into the cloud using the Oracle Lift and Shift utility. The Cloud BI is now leveraging the OBIEE metadata layer to access the on-premises systems. 07 cannot move their data to the cloud. It is a very secure solution that data. With this scenario you can continue to leverage your existing investments in on-premises OBIEE and use your on-premises data warehouse as the single source of the truth. There are a couple of challenges with this scenario, when you use Oracle Lift and Shift then you cannot use the Oracle BICS (Business Intelligence Cloud Service) data model and the reporting workload will continue to run on your on-premises transaction system (if an on-premises data warehouse is not being used).

10 SCENARIO 4 DATA AND APPLICATIONS BOTH ON-PREMISES AND IN THE CLOUD WITH BI IN THE CLOUD Scenario four is the most complex scenario of all but it is also one of the most common. Here the source systems are a mix of on-premises and cloud-based applications,and the data at reporting time is also both on-premises and in the cloud. The systems 08 that hold the data are also a mix - some are data warehouses set up for reporting and some are transaction systems for more real-time operational reporting.

11 SCENARIO 4 DATA AND APPLICATIONS BOTH ON-PREMISES AND IN THE CLOUD WITH BI IN THE CLOUD In this scenario, sometimes there are on-premises systems whose data you don t want to move into the cloud, but you don t want to keep two BI platforms running (one on-premises and the other in the cloud). Oracle BI Cloud is fully capable of handling that, so to address this issue, use the Remote Data Connector Service to connect those on-premises systems and use the OBIEE on-premises RPD to connect these on-premises systems to the cloud. The users are shielded from this complexity by virtue of the single reporting metadata layer the Oracle BI Cloud leverages. All they will see is a simple, unified interface that allows them to work with their data whether it s on-premises or in the cloud. This scenario is also suitable for organizations that want to keep their data on-premises and that want to continue to leverage their existing investments in on-premises OBIEE. This solution will also give you real-time access to your on-premises transaction data while allowing you to continue to use your on-premises data ware- 09 house as the single source of the truth. While there are many benefits in this scenario, perhaps the biggest benefit is the ability to shield users from the complexity of your IT systems, giving them a single, simple view of the data and analytics available to them. This scenario provides reporting against both cloud and on-premises systems. There are several tools available to enable this scenario including: Pre-built Oracle Cloud Apps to BICS integration Apps Associates Application Accelerators FSG to BICS utility and methodology IR/BRIO to BICS utility and methodology Discoverer to BICS utility and methodology

12 SCENARIO 5 ORACLE BI APPS RUNNING ON ORACLE PAAS The fifth scenario runs Oracle BI Applications on Oracle PaaS Oracle BI Apps are pre-built analytical applications that use on-premises (E-Business Suite, PeopleSoft or JD Edwards), the extract data into a pre-built data model optimized for reporting. (Platform as a Service). The source system is Oracle ERP data and the data warehouse are in the cloud on Oracle PaaS. 10 Oracle ERP on-premises as the data source with pre-built ETL to Platform as a service combines a compute service, storage and

13 SCENARIO 5 ORACLE BI APPS RUNNING ON ORACLE PAAS database as a service in the cloud. Everything is provided for running your applications and you re running Oracle BI Applications on PaaS, in the Oracle cloud. As you might expect, in this scenario the OBIEE on-premises reporting metadata (i.e. the RPD) continues to be used and the OBIEE RPD Client Admin Tool is used on an ongoing basis to maintain the OBIEE reporting metadata. Oracle's RPD Lift and Shift utility is used to copy the OBIEE reporting metadata to the cloud whenever changes are made. The Oracle BI Cloud Service (BICS) BI engine then uses the OBIEE reporting metadata for all reporting. The pre-built BI Apps reports are copied to the cloud via a one time copy utility provided by Oracle. 11 If you also have Oracle SaaS applications you can use Oracle Cloud Adapters to copy your data into the Source Data Store. This scenario is ideal for organizations that want to migrate Oracle BI Apps from an on-premises data center to the cloud and lever- age existing investments in BI Apps such as customized reports and tailored ETLs. It does however require an extra step to copy the data to the cloud but this scenario does provide all the benefits of the cloud including agility, scalability and potential cost savings. Apps Associates has developed an accelerated deployment approach for BI Apps in the cloud.

14 NEXT STEPS AND HOW TO LEARN MORE Watch this webinar to learn more details about these scenarios. Apps Associates also provides a complementary assessment of your current BI environment and provide recommendations for leveraging the Cloud for BI. Contact myles.gilsenan@appsassociates.com to schedule the assessment of your BI environment. ABOUT APPS ASSOCIATES Apps Associates is a global IT and business services organization that provides solutions for Cloud, Analytics and Integration. Our mission is to partner with customers to enable business improvement by streamlining business processes using advanced technology. We innovate by constantly launching new services and solutions and we differentiate through our relentless attention to delivery excellence and customer care. OUR STRATEGIC PARTNERS North America (HQ) Europe Asia Copyright 2017, V , Apps Associates LLC. All rights reserved.