Studio system requirements

Studio's system requirements are listed below.

Hardware requirements

In addition to these, you must also have a running Oracle Endeca Server 7.7.x to point Studio to.

Minimum hardware requirements:
  • x64 2.0 GHz processor
  • 4 GB RAM
  • 4 GB disk space
Recommended hardware requirements:
  • x64 3.0 GHz dual-core processor
  • 8 GB RAM

Supported operating systems

Platform Description
OEL Oracle Enterprise Linux 6 (version 6 for x64) running on x64 processors. Only the Red Hat Compatible Kernel is supported.
RHEL

  • Red Hat Enterprise Linux Server (version 6 for x64) running on x64 processors.

  • Red Hat Enterprise Linux Advanced Platform (version 6 for x64) running on x64 processors.

For best performance on Red Hat Linux version 6 (Server and Advanced), we recommend the latest version.

Windows Windows Server 2012 R2 Enterprise running on x64 processors.

Software requirements

Studio is a Web-based application that runs in an application server. It supports the following software:
Software Supported Versions
Application server Oracle WebLogic Server 12cR1 (12.1.3)
Java
  • Java SE JDK 7u67+
  • Java SE JDK 8_66+

If you're installing Studio on WebLogic Server, you must manually install the JDK beforehand. You can download it from the Oracle Technology Network. When installing it, be sure to change the install location to one that doesn't contain spaces; for example, C:\Java\jdk1.8.0_66\.

Database system
  • MySQL 5.5.3+
  • Oracle 11g
  • Oracle 12c (12.1.0.1.0 or higher)
Note: Hypersonic (HSQL) is also supported, but not for production environments.
Browser
  • Firefox ESR on Windows. This is the recommended browser for Studio.
  • Internet Explorer 11.
  • Safari on the iPad. iPad can only be used to log in to Studio and view applications. Users cannot create or configure Studio applications from an iPad.

Alternative database support

The Studio server uses a relational database to store configuration and state. Studio has been tested on the databases listed above. However, many other databases are expected to work.

Customers should feel free to use any database, including shared systems they may already have in place. As with application servers, customers who choose to deploy on un-tested databases will always be supported on any issue that can be traced back to core Studio code and can be reproduced on a supported database.

If you're installing in a production environment, you must change the database afterward. For instructions on doing this, see Changing the Database Used to Store Studio Application Data.