2 Set Up Services
You must be an administrator to create and set up services with Oracle Analytics Cloud - Classic. If you have existing applications and data that you want to analyze with Oracle Analytics Cloud - Classic, you might want to migrate that content before everyone gets started.
Topics:
Typical Workflow to Set Up a Service
If you’re creating a service with Oracle Analytics Cloud - Classic for the first time, follow these tasks as a guide.
Task | Description | More Information |
---|---|---|
Sign up for a free credit promotion or purchase a subscription. |
Provide your information, and sign up for a free trial or purchase a subscription to Oracle Analytics Cloud - Classic and several other required services. |
|
Determine your service requirements |
Plan your service. Think about what you want before you start. |
|
Create a service |
Create a new service with one or more components. |
|
Enable network access |
Permit access to network services associated with your Oracle Analytics Cloud - Classic deployments. |
|
Migrate content |
Leverage your existing content in Oracle Analytics Cloud - Classic. |
Migrate to Oracle Analytics Cloud - Classic from Other Environments |
Before You Create a Service
Take some time to plan your Oracle Analytics Cloud - Classic service before you create it. Think about the questions outlined here and decide what you want to do, before you start.
-
Check you're subscribed or have access to all the required services
-
Oracle Cloud Infrastructure Compute Classic
-
Oracle Database Classic Cloud Service
-
Oracle Cloud Infrastructure Object Storage Classic
-
Oracle Identity Cloud Service (Oracle Universal Credits required)
-
Oracle Cloud Infrastructure Load Balancing Classic
-
Additional services:
-
Oracle Big Data Cloud (required for Essbase Edition)
-
-
Which edition do you want to use?
-
Professional Edition
-
Essbase Edition *
-
Enterprise Edition
You need the Enterprise Edition if you want to offer enterprise modeling and reporting features available in Oracle Analytics Cloud - Classic. See Professional and Enterprise Editions in Getting Started with Oracle Analytics Cloud.Note:
* Oracle Analytics Cloud – Essbase Edition isn't available in Oracle Cloud accounts created after 12th December 2019. Instead, Oracle Essbase is available on Oracle Cloud Marketplace. See: https://docs.oracle.com/en/database/other-databases/essbase/index.html
-
-
How do you want metered usage to be billed?
-
Hourly
-
Monthly
Oracle recommends hourly billing, if you expect to stop services frequently within a month, for example in development or test environments. If you intend to use services throughout the month, monthly billing is more suitable.
You won’t be asked about hourly or monthly billing if you have a nonmetered subscription or subscribe to Oracle’s Universal Credits program.
-
-
Which compute shape do you think you’ll need?
Oracle Analytics Cloud - Classic offers a set of compute shapes that are optimized for different scenarios. Choose from a set of all-purpose and memory-intensive shapes. The larger the compute shape, the greater the processing power. For more information about the compute shapes and considerations for selecting the shape that is right for your environment, see About Shapes in Using Oracle Cloud Infrastructure Compute Classic.
All-purpose compute shapes include:
-
OC4: 2 OCPUs and 15 GB memory
-
OC5: 4 OCPUs and 30 GB memory
-
OC6: 8 OCPUs and 60 GB memory
-
OC7: 16 OCPUs and 120 GB memory
-
OC8: 24 OCPUs and 180 GB memory
-
OC9: 32 OCPUs and 240 GB memory
Memory-intensive compute shapes include:
-
OC1M: 1 OCPUs and 15 GB memory
-
OC2M: 2 OCPU and 30 GB memory
-
OC3M: 4 OCPUs and 60 GB memory
-
OC4M: 8 OCPUs and 120 GB memory
-
OC5M: 16 OCPUs and 240 GB memory
You can change the compute shape after creating the service, if the needs of your business change.
-
- Which identity management system can I use?
-
Oracle Identity Cloud Service
Use Oracle Identity Cloud Service if you subscribe to Oracle Analytics Cloud - Classic through Oracle Universal Credits. Oracle Identity Cloud Service Foundation is automatically provided with your subscription.
If you want to use single sign-on with Oracle Identity Cloud Service, you need Oracle Cloud Infrastructure Load Balancing Classic.
-
WebLogic Embedded LDAP Server
Use WebLogic Embedded LDAP Server if you have a traditional metered or nonmetered subscription to Oracle Analytics Cloud - Classic. When you create your service, you must provide credentials for the Oracle Analytics Cloud administrator:-
User name must start with a letter and can contain up to 25 characters.
-
Passwords must be at least 8 characters and contain at least one non-alphabetic character. Only these special characters are allowed: underscore _, hyphen -, pound sign #, open bracket (, close bracket )
Note:
If you use the embedded LDAP server:-
You can’t scale out your service.
-
You can’t associate your service with Oracle Big Data Cloud.
-
-
-
What name do you want to for this service?
-
Must contain between 1 and 50 characters.
-
Must start with an ASCII letter:
a
toz
orA
toZ
. -
Must contain only ASCII letters or numbers.
-
Must not contain any other special characters.
-
Must be unique within the identity domain.
-
-
Which Database Cloud Service do you want the service to use?
Oracle Analytics Cloud - Classic uses a Database Classic Cloud Service to store various Oracle Analytics Cloud - Classic schemas and data. If your Database Classic Cloud Service isn’t set up, you must do that first. See Create a Customized Database Deployment in Administering Oracle Database Classic Cloud Service.
Oracle Analytics Cloud - Classic doesn't support Oracle Database 18c, non-UTF databases, or Real Application Clusters (RAC) databases.
When you create services with Oracle Analytics Cloud - Classic, you must specify the cloud database you want to use and other information about the database.-
Database Administrator User Name must be SYS or another user with
SYSDBA
privileges. -
Database Administrator Password must not start with a number or a special character, or contain the @ character. Only these special characters are allowed: $ # _
-
PDB or SID associated with the database. For Oracle 12c databases, the name of the pluggable database (PDB). For Oracle 11g databases, the SID associated with the database.
-
Region and Availability Domain on Oracle Cloud Infrastructure Compute Classic in which the database is deployed.
-
IP Network in which the database is deployed, if specified.
-
Is the load balancer associated with the IP network public or private?
-
-
-
Do you want to create your own public/private key pair for SSH access?
You can ask the Create Service wizard to create a public/private key pair for you, or you can create one beforehand, using a standard SSH key generation tool such as OpenSSH, and upload or paste its public key value.
-
Which storage container do you want to use for analytics datasets and backups?
You can create the container beforehand or ask the Create Service wizard to create a container for you. Either way, you need to provide some information.
-
Name and URL of the container.
Container names support UTF-8 characters. Some special characters aren’t allowed: /, ', ", `, <, and >.
-
User name and password of a user, defined in Oracle Cloud Infrastructure Console, with storage administration permissions and read/write access to the container.
Oracle Cloud Infrastructure Object Storage Classic user names must be between 2 to 50 characters and only contain letters and numbers.
If you want to create the container yourself, ensure that the container is empty and dedicated to a singleOracle Analytics Cloud - Classic service. See Create Containers in Using Oracle Cloud Infrastructure Object Storage Classic.
If you haven’t done so already, you must set an appropriate replication policy for your storage service. You must do this before you set up Oracle Database Classic Cloud Service or Oracle Analytics Cloud - Classic.
-
-
Do you want to integrate Oracle Analytics Cloud - Classic with Oracle Big Data Cloud?
Subscribers to Oracle Big Data Cloud can analyze their big data in Oracle Analytics Cloud - Classic. Enter connection details as you create your service, if you want to enable Single-Sign On (SSO) between Oracle Analytics Cloud - Classic and your Oracle Big Data Cloud service. You need to know:
-
Name of your Oracle Big Data Cloud.
-
Administrator password for Oracle Big Data Cloud.
To use this feature:
-
Billing: Oracle Universal Credits
-
Edition: Essbase Edition or Enterprise Edition
-
Service: Self-Service Data Visualization, Preparation and Smart Discovery or Semantic Models
-
Identity management: Oracle Identity Cloud Service
-
Oracle Big Data Cloud: Version 2.1 or later
-
-
Do you want to scale out you service from the start?
By default, services are deployed with a single analytics server (or compute node). You can increase the number of analytics servers available to your service, up to a maximum of 10, to meet your specific performance requirements. If you’re not sure, you don’t have to decide now. You can always scale out your service later on if your service requires additional resources.
If you want to scale out, you need Oracle Cloud Infrastructure Load Balancing Classic.
To use this feature:
-
Billing: Oracle Universal Credits
-
Service: Self-Service Data Visualization, Preparation and Smart Discovery or Semantic Models
-
Identity management: Oracle Identity Cloud Service
-
Create a Service
Use Oracle Cloud Infrastructure Console to create a service with Oracle Analytics Cloud - Classic.
It takes 45–60 minutes to create the service. When the service is ready, a notification email is sent to the email address that you nominated earlier. To check the current status, go to the Oracle Analytics Cloud - Classic dashboard and check for status messages under Create and Delete History.
Oracle
Analytics Cloud - Classic makes two attempts to create the service. If service creation
fails after the second attempt, log files are copied to the storage
container that you nominated for the service. To find out what went
wrong, go to the Storage Classic page in
Oracle Cloud Infrastructure Console, locate the container, and open
the service_provisioning
folder. Expand the ZIP
file and look for any issues recorded in the logs.
-
For BI and Data Visualization services, look at
setupBICS.log
. -
For Essbase services, look at
continue-service-start-essbase.log
.
Migrate to Oracle Analytics Cloud - Classic from Other Environments
You can migrate content from other cloud and on-premises environments to Oracle Analytics Cloud - Classic.
Migrate From... | More Information |
---|---|
Oracle Analytics Cloud - Classic deployed on Oracle Cloud Infrastructure Classic |
|
Oracle Analytics Cloud deployed on Oracle Cloud Infrastructure |
|
Oracle BI Enterprise Edition 12c |
|
Oracle BI Enterprise Edition 11g |
|
Oracle Essbase |
|
Migrate LDAP-Based Services to Oracle Identity Cloud Service
You can use Oracle Identity Cloud Service if you subscribe to Oracle Analytics Cloud - Classic using Oracle Universal Credits. If you have an existing service that uses WebLogic embedded LDAP server for identity management, you can use various export and import utilities to migrate your artifacts to another Oracle Analytics Cloud - Classic environment that uses Oracle Identity Cloud Service.
Topics:
Migrate BI Content and Users
If you have Oracle Analytics Cloud - Classic services that use the WebLogic embedded LDAP server, you can export everything (including data visualizations, reports, dashboards, user information, and so on) and import them to a new environment enabled with Oracle Identity Cloud Service (IDCS).
Create a New Service with Oracle Identity Cloud Service Enabled
Oracle Identity Cloud Service Foundation is automatically provided when you subscribe to Oracle Analytics Cloud - Classic through Oracle Universal Credits. Creating a service that integrates with Oracle Identity Cloud Service is easy. When you create the service, you select the option Enable IDCS and Load Balancer.
Oracle Identity Cloud Service is only available through Oracle Universal Credits.
Export Content (BI Services)
Start your migration to Oracle Identity Cloud Service by exporting everything from the source service to your local file system. First you upload the migration scripts, and then you export snapshots, datasets, users, and groups. The source service must use an embedded WebLogic LDAP server.
-
Export snapshots of your environment.
-
Export users and groups.
To export content from the source service:
Import Content (BI Services)
After exporting all your content from a service that uses the embedded LDAP, you use migration scripts to import the content on the target service. The target service must be set up to use Oracle Identity Cloud Service.
-
Import snapshots of the source service
-
Import users and groups
To import your content:
Migrate Essbase Applications and Users
You can migrate applications, users, and groups from Oracle Analytics Cloud – Essbase services v17.3.3 (or earlier) to the latest version, using export and import scripts.
Prerequisites
-
Oracle Identity Cloud Service (IDCS) requires that user fields aren’t empty. If you’re enabling IDCS, then in your existing Essbase services and prior to migrating your data, open the Security tab and ensure that all user data fields (including ID, name. email, and role) contain values and aren’t empty.
-
When you export applications, the target file is overwritten. If you want to save the previous version of an exported application, rename it or run the export script with another file name.
-
Before you migrate applications and users, copy the following scripts from the older Essbase service version to the latest version, at the same file location. You can check first whether they already exist on the new service.
-
/u01/app/oracle/tools/acss/BI/esscs_tools/lcm/esscs_lcm.py
-
/u01/app/oracle/tools/acss/BI /esscs_tools/lcm/idcs_users.py
-
/u01/app/oracle/tools/acss/BI /esscs_tools/lcm/ldap_users.py
-
/u01/app/oracle/tools/acss/BI /esscs_tools/lcm/user_group.py
-
/u01/app/oracle/tools/acss/BI /esscs_tools/public/essbase_export.sh
-
/u01/app/oracle/tools/acss/BI /esscs_tools/public/essbase_import.sh
-
Export Script Location
/bi/app/public/bin
Export Syntax
essbase_export.sh filename
Where:
filename
Full path to the tar
archive file that stores all Essbase applications, CSV files of users and groups, and files of settings.
Import Script Location
/bi/app/public/bin
Import Syntax
essbase_import.sh filename
Where:
filename
Name of the tar
created by the export script.