System Requirements for Policy Manager 8.x

The following table lists the minimum system requirements for running Policy Manager 8.x on Windows and UNIX platforms.

Updated: December 9, 2016

Supported Platforms: 8.1

Component Name Requirement
Akana Platform Version 8.1
Akana Platform Host


  • Single CPU, 2Ghz, 2GB RAM

Operating System:

  • Windows - Windows Server 2008, Windows 7, Windows 8, Windows Server 2012, Windows 10
  • Linux - Red Hat Enterprise Linux 5.8, 6.2, 7
  • Solaris - Solaris 10, 11
  • IBM AIX - AIX 7.1
Client Browser for accessing UI of Akana Platform Features
  • IE 8.0 and above
  • Mozilla Firefox 10+ and above
  • Google Chrome v17 and above
Database Management Systems
  • Oracle 11g (SID, Service Name) - Requires database driver ojdbc5.jar.
  • Oracle 12c - Requires database driver ojdbc7.jar.
  • Microsoft SQL Server 2008, 2012, 2014- Database driver included with Akana Platform.

    Note: The quartz trigger property must be set to True. Select the Configuration tab in the Akana Administration Console, select the com.soa.scheduler.quartz Configuration Category and change the org.quartz.jobStore.acquireTriggersWithinLock property to True.

  • IBM DB2 Universal Database V9.7, 10.5 - V9.7 requires DB2 Universal JDBC Driver (e.g., db2jcc.jar) for your specific DB2 installation.
  • MySQL 5.6 - Requires database driver mysql-connector-java-5.1.28 jar.

    If you are using MySQL 5.6 with Policy Manager 8.0 and/or Policy Manager 8.0 and Community Manager 8.0 a series of MySQL property settings must be configured. See MySQL Database Property Settings.

Note: After installing the Akana Platform and running the "Configure Container Instance Wizard," the database driver .jar file must be dropped into the "/deploy" directory of the container instance that requires the driver (e.g., {platform directory}/instances/{instance name}/deploy) prior to running the database configuration task via the "Akana Administration Console."'The database will usually not reside on the computer that is hosting the Akana Platform.

Database Sizing Guidelines

The base install, with configuration data, consumes an initial 10MB of space.

  • Each detailed transaction log consumes approximately 500 bytes of database storage space. Typically, however, only 5% of transactions are logged in this manner. This means that 25KB of database storage space will be consumed for every 1000 transactions. At the transaction rate used in the test – 1250TPS – the database storage space was consumed at the rate of 112MB per hour.
  • Assume an average recorded message size of 10KB. Typically, however, only 1% of transactions are logged in this manner.
  • Alerts, performance data and SLA Rollup data add up to approximately 1KB per 100 transactions.
Memory Configuration

The default maximum heap size for all Akana Containers (i.e., Java processes) is 2048 MB.


A subset of the Akana Platform product documentation is published in Portable Document Format (PDF) and requires Acrobat Reader 9.0 or above.

Back to top