If you have an existing Essbase on-premises application and cube to migrate to the cloud service, keep in mind the following design considerations and prerequisites. Lifecycle Management Utility
With the Lifecycle Management (LCM) command-line utility, you can export on- premises applications and cubes, and then import them to the cloud service. First read these prerequisites. When you are ready to migrate, see Migrating Cloud Service Applications.
Use of the LCM utility requires JDK 8 or higher.
To learn about other options for creating applications (besides LCM), see Application Creation Options Other Than LCM.
Unicode Mode
You must convert all applications and associated artifacts to Unicode mode (UTF-8 encoding) before you export and then migrate them to the cloud service.
Substitution Variables
If you have server-level substitution variables, then you must convert them to application-level variables before migrating to the cloud service. Server-level substitution variables are not supported.
Hybrid Aggregation Mode
The default calculation and query processor in the cloud service is hybrid mode. Hybrid mode enables block storage cubes to have dynamic, upper-level sparse
members, and fully dynamic query and calculation. You can query data immediately after updating it, without running batch calculations. In hybrid mode, there is no impact to your cubes if you choose not to apply Dynamic Calc to upper level sparse members. For more information about hybrid mode, see Calculation and Query Processor. Implied Sharing
Implied sharing is not supported in the cloud service. All stored intersections have data, regardless of their child count.
Configuration Settings
Default configuration values are different in the cloud service.
• IGNORECONSTANTS setting is now TRUE by default. Calculations in hybrid mode do not assign constants.
• INDEXCACHESIZE and DATACACHESIZE settings now control cache sizes for all cubes on the cloud service (except aggregate storage cubes). Formerly, these settings only affected newly created or migrated cubes.
You cannot change the cache sizes using MaxL. You can only change the cache sizes using these configuration settings.
• GRIDSUPPRESSINVALID is now TRUE by default. Invalid intersections are not displayed in Smart View grids.
• QRYGOVEXECTIME is now set by default to 300 seconds, meaning that queries time out if not completed in that timeframe.
In addition to the above noted configuration changes, other configuration settings are in place with default, pre-set values, that you can modify (if needed) at the application level. See Setting Application-Level Configuration Properties.
Oracle strongly recommends managing all configuration settings at the application level. Application-level configuration is preserved during the LCM utility export and import processes.
Application Files and Artifacts
You must convert all application-level files and artifacts into database-level files and artifacts before you export them from on-premises Essbase instance, and before you migrate to the cloud service. This includes calculation scripts, rule files, and text files. In the cloud service, artifacts are supported at the database level only.
You can import on-premises rules files to the cloud service and execute them in the cloud service.
If you encounter file upload size restrictions between external clients and the cloud service, then you may need to split large files into smaller files and then concatenate them together after uploading them to the cloud service, using an SSH connection to the server.
Outlines
Outlines are encrypted on the cloud service deployment servers. If you need to export and import outlines between cloud service servers, then the LCM utility and application workbooks are the only supported methods for doing so.
Chapter 13
Unsupported Application and Database Settings
The following application and database level settings are no longer supported: • Enable/disable Commands (enabled by default)
• Enable/disable Connects (enabled by default) • Enable/disable Updates (enabled by default)
• Data and index cache size controls (defaults are fixed, but can be changed per application using INDEXCACHESIZE and DATACACHESIZE configuration settings)
• Minimum permission levels (create security filters prior to LCM export instead) • Set lock timeout
• Currency conversion • Disk volumes Partitions
Only transparent are supported by the LCM utility. Linked and replicated partitions are not supported. When you export the target application using the LCM utility, the partition definition is exported as part of the application.
When you perform the LCM import operation, always import the source applications before the target applications. If the source application has not been imported prior to the target application, then the partition definition will not work, and you will have to use MaxL to re-create the partition definition after importing the source application. Size Requirements
Ensure that pre-existing applications you plan to migrate to the cloud service will fit at the resource level you procure. Estimate sizing requirements, and procure the most relevant combination of CPU, memory, and storage.
Application Creation Options Other Than LCM
In addition to using LCM to migrate exported applications, you can also create applications in the following ways:
• Use Excel application workbooks. See About Application Workbooks.
• In Smart View, use the Cube Designer extension. See About the Cube Designer Ribbon.