Enterprise Controller Considerations and Requirements

Consider the following factors when selecting a platform for the Enterprise Controller:

  • System: The Enterprise Controller has many parallel executing processes and a multi-core system will significantly improve performance. There are some processes that are by their nature single threaded and benefit from higher clock speed. It is recommended to choose a process that is both multi -core and has a high single thread CPU speed.


    Do not install the Enterprise Controller on a hardened system. The installation will complete successfully, but you will encounter several issues when you use the software.

  • Memory: The core JVM machine consumes memory and its resource utilization will increase with the number of assets being managed. If the Java virtual machine is forced into virtual memory, then Enterprise Manager Ops Center performance will reduce significantly.

  • Database: A database is present in Ops Center and a high performing disk I/O is important in the implementation. Generally, disk striping or the use of a well configured high performing file system with such features built in, such as ZFS, is highly recommended. See Management Repository Considerations for information on database sizing.

  • Operating system: While not a scaling issue, the system must be running on a version of Oracle Solaris 11 if you plan on using Oracle Enterprise Manager Ops Center to manage Oracle Solaris 11 Operating Systems or virtualized environments, or if you plan on discovering and managing Oracle SuperCluster and other Oracle engineered systems. Because Oracle SuperCluster uses Oracle Solaris 11, you must install your Enterprise Controller on Oracle Solaris 11 if you plan to manage Oracle SuperCluster.


    It is recommended that you use Oracle Solaris 11.2 or higher for the Enterprise Controller operating system.

  • Network: Start-up times of the Enterprise Controller can be minimized by ensuring that the network link to the repository is as low latency as possible. The start-up process involves a large number of queries as the state machine is being built. It is recommended that a 10 GigE connection be available between the Enterprise Controller and Management Repository.

    For a remote customer-managed database, set up the network according to the Oracle database networking setup defined in the Oracle Server Installation Guide. See the Related Resources for Scaling section for more information about database requirements. See Management Repository Considerations for more information on database considerations.

An Enterprise Controller can manage up to 3,000 mixed assets including hardware, operating systems, virtualization technologies, and other assets. Deployments above 1,000 assets might require you to tune your Java Virtual Machine (JVM) heap size.

An Enterprise Controller system must meet the following minimum requirements:

  • Oracle SPARC or x86 platform that is running a supported Oracle Solaris or Linux OS, such as Oracle Solaris 11

  • 200 GB of disk space

    Memory Settings

    • 12 GB if the Enterprise Controller uses an embedded database

    • 6 GB if the Enterprise Controller uses a customer-managed database

  • Swap space for embedded database

    • Equal to physical memory if the physical memory is less than 16 GB

    • 16 GB if the physical memory is greater than 16 GB

  • Swap space for remote database

    • 12 GB minus the amount of physical memory (swap is required if this number is <=0)

Changing the Database Fetch Size

In large environments, the default database fetch size can be too small, causing the Enterprise Controller to start slowly. If your Enterprise Controller is slow to start, you can increase the fetch size in the user interface.

  1. Expand the Administration section in the Navigation pane, then click Enterprise Controller.
  2. Click the Configuration tab.
  3. Select EC Manager from the Subsystem menu.
  4. Edit the persistent.cached.manager.ec.connection.prefetch.size variable.
    A value of 10,000 is sufficient for most large environments. Do not increase the variable beyond 30,000.
  5. Restart the Enterprise Controller.