System Requirements

System requirements for the Execute Server, Database and Clients

There are four parts to an Execute installation:

  1. An Execute database, deployed on an Oracle or SQL Server database server.
  2. An Execute server component (Windows service), deployed on a PC such as an application server.
  3. The Execute network components, deployed on a network file share.
  4. The web browser (running on desktop and mobile devices) accesses the Execute Service.

Click image to expand or minimize. 

Some, or all, of the infrastructure above may be duplicated for your PRODUCTION and TEST environments.

Workstation Requirements

The majority of the Execute user interface is accessed through the web browser. Execute supports the following common browsers and versions:

  • Internet Explorer 11 and higher
  • Firefox
  • Google Chrome
  • Safari
  • Mobile browsers such as Mobile Safari (iOS), Chrome (Android).

PDF viewing software (such as Acrobat Reader) is required to view “printed” AFE forms.

Microsoft Excel is required to view many data exports from Execute.

For clients upgrading to Execute 2018 from an earlier version, some administrative and reporting activities are accessed using the legacy Desktop UI. To access these components users must be running Windows 7 or later, with .NET 4.6.2, and must use a browser supporting Microsoft’s Click-Once application deployment framework.

Server Requirements

The Execute server component (Windows Service) must be installed on a PC dedicated to Windows services within your organization, such as an application server. This machine must be reliably accessible to all workstations where the Execute client may run.

  • System: 64-bit dual/quad core processor (physical machine or virtual)
  • Memory: 8 GB RAM or more (in addition to base OS requirements). Large environments ((> 50,000 AFEs) will need 16GB of RAM
  • Disk Space: 2GB (application is about 100MB + temporary space)
  • Operating System: Windows Server 2008 (64-bit), Windows Server 2008 R2 (64-bit), Windows Server 2012, Windows Server 2012 R2, Windows Server 2016
  • .NET Framework: 4.6.2
  • Internet: Requires outbound internet access (HTTP and HTTPS)
Execute requires that the Microsoft .NET Framework 4.6.2 be installed on the application server prior to installing the Execute Service. This can be installed using the Windows “Add Feature” wizard.

Network File Share

Execute requires a shared area on your network with file and folder permissions set appropriately (see the Installation and Upgrade Guide for more information) for access to shared files such as desktop program files, shared reports, archived forms, etc.

  • 500 MB (for each environment) + space for attachments
    • By default, this network file share also stores documents attached to AFEs. This can be changed after installation.

Mail Server

In order to user Execute’s email notifications, a mail server that allows the Execute service to send email via SMTP is required. If necessary, Execute can be configured to use authenticated SMTP and SSL (STARTTLS only).

Database

A database server, running Oracle 11g, Oracle 12c, SQL Server 2012 or SQL Server 2016 (or higher), with approximately 50 MB of space per 1000 AFEs.

Execute connects to the database using a single service account and manages user permissions within the Execute service. There are no per-user database accounts required or used by Execute. The service account used by Execute must have the ability to modify the Execute schema (DDL) as this is required in order to add custom fields in Execute.

The Windows and database server versions listed above are those that were tested as part of the release. Newer versions are likely to work but have not been officially tested. For SQL Server users, only “SQL Server Authentication” (with a username and password) is supported. Execute does not support “Windows Authentication” at this time.