LogoLogo
3.6.9
3.6.9
  • Introduction
  • Getting started
    • Installation
      • Prerequisites
        • Server requirements
      • On-premises
        • Single-node
          • Directory structure
        • Multi-node
      • Azure Market Place
      • AWS Market Place
    • Tutorials
      • Amazon AWS CUR
      • Amazon AWS CUR (Athena)
      • Azure Stack
      • Azure EA
      • Azure CSP
      • Google Cloud
      • VMware vCloud
      • VMware vCenter
    • How-to guides
      • How to configure receiving a monthly billing report
      • How to automatically trigger a monthly billing report
      • How to update your license
      • How to store contract information with an Account in a report
      • How to automatically send workflow errors as webhooks to a monitoring system
    • Concepts
      • User interface
      • Services
    • Releases
      • Upgrading to version 3
      • Known issues
      • Announcements
      • Archive
  • Reports
    • Accounts
    • Services
    • Instances
    • Summary
    • Budget
  • Services
    • Manage
    • Rates
      • Tiered Services
        • Aggregation Levels and the Account Hierarchy
    • Adjustments
    • Subscriptions
  • ACCOUNTS
    • Budget management
  • Data pipelines
    • Extract
      • Configuration
      • Extractor templates
      • Script basics
      • Parslets
      • Subroutines
        • check_dateformat
        • check_dateargument
        • format_date
        • validate_response
      • Language
        • aws_sign_string
        • basename
        • buffer
        • csv
        • clear
        • decimal_to_ipv4
        • discard
        • encode
        • encrypt
        • environment
        • escape
        • exit_loop
        • foreach
        • generate_jwt
        • get_last_day_of
        • gosub
        • gunzip
        • hash
        • http
        • if
        • ipv4_to_decimal
        • json
        • loglevel
        • loop
        • lowercase
        • match
        • pause
        • print
        • return
        • save
        • set
        • subroutine
        • terminate
        • unzip
        • uppercase
        • uri
        • var
    • Transform
      • Configuration
      • Transformer templates
      • Transform Preview
      • Language
        • aggregate
        • append
        • calculate
        • capitalise
        • convert
        • copy
        • correlate
        • create
        • default
        • delete
        • dequote
        • environment
        • event_to_usage
        • export
        • finish
        • Functions
        • if
        • import
        • include
        • lowercase
        • normalise
        • option
        • rename
        • replace
        • round
        • services
        • set
        • sort
        • split
        • terminate
        • timecolumns
        • timerender
        • timestamp
        • update_service
        • uppercase
        • var
        • where
    • Datasets
    • Lookups
    • Metadata
    • Reports
    • Workflows
  • Administration
    • User management
      • Users
      • Groups
    • Notifications
      • Budget Notifications
      • Report notifications
      • Workflow notifications
    • Settings
      • Global Variables
      • White Labeling
  • Advanced
    • Integrate
      • GUI automation
        • Examples
      • API docs
      • Single sign-on
        • Claims-based identity provisioning: users, Account access and user groups
        • Azure-AD
        • Auth0
        • OKTA
        • OneLogin
        • ADFS
        • LDAP
    • Digging deeper
      • Authentication flows
      • Transformer datadate
      • Dataset lifecycle
      • Config.json
      • Databases
  • Security
    • Security
    • Authentication
      • Token
      • LDAP
      • SAML2
    • Password reset
    • Password policy
    • Announcements
  • Troubleshooting
    • Logs
  • Terms & Conditions
  • Privacy Policy
Powered by GitBook
On this page
  • Server
  • Client

Was this helpful?

Export as PDF
  1. Getting started
  2. Installation
  3. Prerequisites

Server requirements

Learn about the server requirements and browser support

Server

Exivity can be installed on any Microsoft Windows 2016 or higher server in your on-premises data center or in the cloud. Depending on the amount of data, Exivity recommends the following system configuration:

Size

CUPR

Web & Backend

RabbitMQ

PSQL

CPU

RAM

Storage

Small

< 5000

1 – 2 node(s)

0 – 1 node

0 – 1 node

4 cores

12 GB

200 GB

Medium

< 10000

1 – 2 node(s)

0 – 1 node

0 – 1 node

6 cores

16 GB

400 GB

Large

< 15000

2 – 4 nodes

1 instance*

1 instance*

8 cores

24 GB

600 GB

X-Large

> 15000

4 or more nodes**

1 instance*

1 instance*

8 cores

32 GB

TBD**

* a managed high available and high-performance cluster would be recommended ** consult with Exivity for advisory on appropriate sizing of extra-large environments

Each node can be either a physical or virtual machine. The CPU and RAM requirements provided in the table above are defined per node whereas the Storage requirements are to be considered for the complete UMB deployment as a whole and should be hosted on shared storage (i.e. SMB/NFS). An operating system will need to be pre-installed on every node. Web and Backend nodes require a version of Windows 2016 Standard or higher to be installed. In scenarios where the RabbitMQ and/or PostgreSQL nodes are deployed on dedicated or clustered environments, the operating system guidelines specific to those applications are to be considered.

Client

The Exivity front-end supports the following desktop browsers:

  • Google Chrome v59+

  • Microsoft Edge v41+ (EdgeHTML 16+ / Blink 80+)

  • Opera v46+

  • Mozilla Firefox v65+ (support added in Exivity v2.10.0)

  • Apple Safari v10.1+ (support added in Exivity v3.2.7)

We aim to provide the fastest metering and billing solution available today, and this means we have to rely on modern (web) technologies. Part of our speed comes from pre-processing the raw data, and part comes from having almost all processed data available right in the browser, and streaming the missing pieces on request.

To efficiently and reliably achieve this we use some very specific technologies not yet available in all browsers. When they do catch up, we'll fully support those browsers.

PreviousPrerequisitesNextOn-premises

Last updated 3 years ago

Was this helpful?