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.

Before You Begin With Oracle Analytics Cloud - Classic

Determine your service requirements

Plan your service. Think about what you want before you start.

Before You Create a Service

Create a service

Create a new service with one or more components.

Create a Service

Enable network access

Permit access to network services associated with your Oracle Analytics Cloud - Classic deployments.

Control Access to Service Components

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 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)

    See Before You Begin With Oracle Analytics Cloud - Classic.

  • Which edition do you want to use?

    • Standard 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 Standard, Essbase and Enterprise Editions in Getting Started with Oracle Analytics Cloud.

  • 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 to z or A to Z.

    • 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 Cloud Service to store various Oracle Analytics Cloud - Classic schemas and data. If your Database Cloud Service isn’t set up, you must do that first. See Create a Customized Database Deployment in Administering Oracle Database 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 data sets 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 My Services, 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 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 Enterprise Data 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 Enterprise Data Models

    • Identity management: Oracle Identity Cloud Service

Create a Service

Use My Services to create a service with Oracle Analytics Cloud - Classic.

  1. Sign in to My Services, and click Dashboard.
  2. Go to the Analytics Classic tile, click the Action Menu and select Open Service Console.

    If a Welcome page displays, click Go to Console.

  3. Click Create Instance.
  4. On the Instance page, enter a unique name for the service, and a description.
  5. Enter an email address where you would like a service creation notification and other service-related information to be sent.
  6. Select the region where you want to deploy the service and whether you want to use a custom IP network.
    You must deploy Oracle Analytics Cloud - Classic in the same region and availability domain as the database service that you set up to store Oracle Analytics Cloud - Classic schemas.
    The database service you want to use doesn’t have to be deployed on the same IP network as Oracle Analytics Cloud - Classic. If you decide to deploy Oracle Database Cloud Service and Oracle Analytics Cloud - Classic on different IP networks, you must remember to create an IP network exchange that enables communication between the two IP networks.
    1. Select the same Region and Availability Domain as the database service you set up for Oracle Analytics Cloud - Classic.
    2. (Optional) If the database you set up for Oracle Analytics Cloud - Classic is deployed on an IP network, select the name of that network from the IP Network list.
      If you want to deploy Oracle Analytics Cloud - Classic on a different IP network, ensure that the IP network you select has access to the database through an IP network exchange.
    3. (Optional) Select Assign Public IP if you want any node created for this service to have a public IP address. If you scale out your service in the future, those added nodes are assigned public IP addresses. When you select this option, you see options for reserving IP addresses on the next page.
      If you deselect this option, none of the nodes associated with this service can have public IP addresses.

      This option is available only if you select an IP network.

  7. Click Edit to specify the SSH Public Key to use for authentication when using an SSH client to connect to a compute node that is associated with your service.
    • If you have an existing public key, click Browse to select the file that contains the public key or select Key Value and paste its value, and then click Enter. If you paste in the value, make sure the value doesn’t contain line breaks or end with a line break.

    • To generate a new public and private key pair, click Create a New Key, and then click Enter.

      Click Download to save the public and private key pair locally, and then click Done. You can use the private key to connect to a compute node that is associated with this service.

    You can change the public key value for your service when it’s up and running whenever you want.

  8. For License Type, select whether you want to use your on-premises license with Oracle Analytics Cloud - Classic (and to be charged the Bring Your Own License rate) or subscribe to a new license for Oracle Analytics Cloud - Classic.
  9. Select the edition you want to deploy: Enterprise, Essbase, or Standard.
  10. (Traditional metered subscriptions only). Select a frequency for metered billing.
    • Hourly—Pay only for the number of hours used during your billing period.

    • Monthly—Pay one price for the full month irrespective of the number of hours used.

      For services that start in the middle of a month, the price is prorated. You pay only for the partial month from the start date.

    You can’t switch from hourly to monthly or from monthly to hourly billing after you’ve created the service. If you expect to stop services frequently within a month, for example in development or test environments, you might select hourly billing. If you intend to use services throughout the month, select monthly billing.

  11. Click Next.
  12. In the Identity Management section, specify how user accounts are managed for this service.
    • Select Enable IDCS and Load Balancer to use Oracle Identity Cloud Service.

      Always use this if you subscribe to Oracle Analytics Cloud - Classic through Oracle Universal Credits. Oracle Identity Cloud Service Foundation is automatically provided if you subscribe to Oracle Analytics Cloud - Classic through Oracle Universal Credits.

      If you enable Oracle Identity Cloud Service and chose to deploy Oracle Analytics Cloud - Classicon an IP network (in the previous screen), you must specify whether the load balancer associated with your selected IP network is public or private.

      • Select Public Load Balancer if the load balancer on the IP network is public, that is, accepts traffic from the internet.

      • Deselect Public Load Balancer if the IP network uses a private load balancer. Private load balancers are only visible within your virtual cloud network (VCN).

      If you’re not sure contact your network management team.

    • Deselect Enable IDCS and Load Balancer to use the WebLogic embedded LDAP server.

      Always use this if you subscribe to Oracle Analytics Cloud - Classic through a traditional metered or unmetered subscription.

      In the Service Administrator section, enter a user name and password for the WebLogic embedded LDAP server administrator.

  13. In the Options section, select the type of service you want to create.
    1. Select the features you want to offer.
      • Self-Service Data Visualization, Preparation and Smart Discovery

      • Enterprise Data Models — BI

      • Collaborative Data Collection, Scenarios and What-if Analysis — Essbase

      Select only one type of service. If you select Enterprise Data Models, you automatically get Self-Service Data Visualization, Preparation and Smart Discovery. If you need help to decide, see Features of Oracle Analytics Cloud in Getting Started with Oracle Analytics Cloud.

    2. Select a size and shape for the compute node.
      If you’re not sure about your final requirements, select the minimum OCPUs as you can scale up later if required.
    3. Enter the usable storage or accept the default.
      Total Storage on Disk is the default system and data storage the service uses.
    4. (Optional) Click the Plus icon if you want to allocate specific IP addresses to the nodes created for this service.
      IP addresses are assigned automatically, by default.
  14. In the Cloud Storage Configuration section, specify the container where you want to store any analytics data sets that users upload, and backups for this service.
    1. Enter the REST endpoint URL for the container you want to use.
      • If you specify the name of an existing container, you must ensure the container is empty and used only by this service.

      • If you want to create a container with the name that you specify here, you must select the check box Create Analytics Storage Container.

      Use the format:

      https://domain-storage.oraclecloud.com/v1/Storage-domain/ContainerName

      For example: https://example-storage.oraclecloud.com/v1/Storage-example/myoacstoragecontainer

      To find the REST endpoint URL, go to the Storage Classic tile on your My Services dashboard, click the Action Menu and select View Details. The REST Endpoint value for your storage service is displayed under Additional Information. Copy the REST endpoint and append this value with a forward slash and the name of the container you want to use, for example: <Rest Endpoint value>/<ContainerName>

    2. Enter the user name and password of a user with read and write access to Oracle Cloud Infrastructure Object Storage Classic.
    3. Optional: If the container you specified doesn't exist yet, select Create a Cloud Storage Container.
  15. Optional: Define a public storage container so users can share their data visualizations.

    You don't have to define a public container now. You can set up a public container later when your service is up and running. After you define the container, users will see the menu option that enables them to share their data visualizations.

    Note:

    This step doesn't apply when you select the option Collaborative Data Collection, Scenarios and What-if Analysis — Essbase.
    1. Select Configure storage container for sharing data.
    2. Enter the Shared Storage Container URL.

      Specify the container you want to use to share content. The container must be set up as a public container, that is, a container with global read access. Use the REST endpoint URL format:

      https://domain.storage.oraclecloud.com/v1/Storage-domain/ContainerName

      For example: https://example.storage.oraclecloud.com/v1/Storage-example/mypubliccontainer

      To find the REST endpoint URL for the storage container, go to the Storage Classic tile on your My Services dashboard, click the Action Menu and select View Details. The REST Endpoint value for the service is displayed under Additional Information. Copy the REST endpoint and append this value with a forward slash and the name of the public container you want to use, for example: <Rest Endpoint value>/<PublicContainerName>

    3. Enter the user name and password of a user with read and write access to the public container.
    4. If the container you specified doesn't exist yet, select Create Shared Storage Container.
  16. In the Database section, select the database cloud service where you want Oracle Analytics Cloud - Classic to store its schemas and data.
    1. Select the name of the database you want to use.
    2. For PDB/SID, enter the name of the pluggable database (PDB) or SID associated with the database.
      For Oracle 12c databases, provide the name of the pluggable database. For Oracle 11g databases, provide the SID.

      Note:

      Oracle Analytics Cloud - Classic doesn't support Oracle Database 18c, non-UTF databases, or Real Application Clusters (RAC) databases.
    3. For Database Administrator Username, enter SYS or another user with SYSDBA privileges, and then enter the password for this administrator.
  17. Optional: In the Associations section, select Big Data Cloud Service if you want to integrate Oracle Analytics Cloud - Classic with an existing big data service. Select the name of the service you want to connect to and the administrator password for that big data service.
    This option is available only with Essbase Edition and Enterprise Edition, if you select theOracle Analytics Cloud option Self-Service Data Visualization, Preparation and Smart Discovery or Enterprise Data Models, and enable Oracle Identity Cloud Service (Enable IDCS and Load Balancer).
  18. Optional: In the Service Administrator section, increase the Number of Analytics Servers, if required. The default value is 1.
    You don’t have to scale out now if you’re not sure. You can scale out (and scale in) at any time.
    This option is available only if you select the Oracle Analytics Cloud option Self-Service Data Visualization, Preparation and Smart Discovery or Enterprise Data Models, and if you enable Oracle Identity Cloud Service (Enable IDCS and Load Balancer).
  19. Click Next.
  20. Verify the information you provided, and then click Create.

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 My Services, 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, data sets, 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:

  1. Export a snapshot of your environment:
    1. Sign in to the source service.
    2. Click Console, and then click Service Administration.
    3. Click Manage Snapshots, and then click Create Snapshot.
      Name the snapshot Final snapshot before migration or something similar.
    4. Select the content you want to include, Everything or Custom.
      • Everything - Include everything about your environment in the snapshot.
      • Custom - Select only the content types you want to save in the snapshot. Deselect any items that you don't want.
    5. Download this final snapshot to your local file system. Select the snapshot, click Snapshot Actions menu, and then click Download.
    6. Enter and confirm a password for the snapshot.
      The password must contain at least 8 characters. Don’t forget this password. You’ll be asked for this password when you upload the snapshot on the target service.
    7. Download any other snapshots you want to migrate or keep on your local file system.
  2. Export users and groups. Run the wls_ldap_csv_exporter script:
    $ /bi/app/public/bin/wls_ldap_csv_exporter -u weblogic_admin_user -c oracle_common_folder_path -D output_dir

    Typically, oracle_common_folder_path is the folder /bi/app/fmw/oracle_common

    This script creates two CSV files, one CSV file contains users and the other contains groups. There is also a log file, which describes any invalid or incompatible records that Oracle Identity Cloud Service won’t understand.

    • Everyone has a default password.

    • Oracle Identity Cloud Service doesn't support group memberships, that is, where a group is member of another group. Such records are discarded from the group CSV file and mentioned in the log file.

    • Oracle Identity Cloud Service requires several mandatory parameters for users: User ID,Last Name,First Name,Password,Work Email. Oracle Identity Cloud Service won’t import user records if parameters are missing.

  3. Prepare both CSV files for Oracle Identity Cloud Service. Make sure the CSV files contain all the information Oracle Identity Cloud Service requires.
    1. Review the log file for information about invalid or incomplete records.
    2. Review the users CSV file, and ensure the information is complete.
    3. Repeat for the groups CSV file.
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:

  1. Upload snapshots of the source service:
    1. Sign in to the target service.
    2. Click Console, and then click Service Administration.
    3. Click Manage Snapshots, click the Page menu, and then select Upload Snapshot.
    4. Use Select to navigate to the folder where you downloaded snapshots for migration.
    5. Select the final snapshot that you took before migration.
    6. Enter the snapshot password, and click OK.
      You’ll see a snapshot named Final snapshot before migration or something similar.
    7. Upload any other snapshots that you exported and want to keep on the target service.
  2. Restore the most recent snapshot:
    1. Select the final snapshot, click the Actions menu, and then click Restore.
    2. Select the Restore option you want.

      For example, you may not want to include application roles if you’re restoring a snapshot taken from a pre-production service, to a production service. Pre-production roles often have different members to the production service. If so, select Custom and deselect Application Roles before you restore.

      • Replace Content Snapshot Only - Restore only the content inside the snapshot. Any content types that are missing from the snapshot remain unchanged.
      • Replace Everything - Overwrite all your existing content. Replace your existing content with the content included in this snapshot (listed in the description field). Any content types not included in the snapshot, excluding file-based data sets, plug-ins and extensions, are removed and restored with default values.
      • Custom - Select only the content types you want to restore. You can restore with content saved inside the snapshot or restore your content with default settings. If you don’t want to restore everything, deselect all the items you want to keep.
    3. Click Restore, and then Yes to continue.
      The time it takes to restore your system depends on the size of your snapshot. After the restore completes, you might need to wait a few more minutes for the restored content to refresh through your system.
    4. Sign out.
  3. Import users from the CSV file you exported earlier:
    1. In Oracle Identity Cloud Service console, click Users, then Import.
    2. Click Browse to locate the CSV file that contains user account information.
    3. Click Import.

    See Import User Accounts in Administering Oracle Identity Cloud Service.

  4. Import groups from the CSV file you exported earlier.
    1. In Oracle Identity Cloud Service console, click Groups, then Import.
    2. Click Browse to locate the CSV file that contains group account information.
    3. Click Import.

    See Import Groups in Administering Oracle Identity Cloud Service.

  5. Sign in to the target service.
  6. Activate scheduled deliveries (if any).
    1. Click Console, and then click Service Administration.
    2. Click Monitor Deliveries.
    3. To activate a delivery, click the Actions menu and select Enable Delivery .
  7. Verify everything migrated as you expected.

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.