This section describes how to set up the Ed-Fi ODS / API v7.0 using the release binaries listed in Binary Releases. This is a recommend approach for implementations that have no requirement to extend or customize the source code of the Ed-Fi ODS / API.

Before binary installation, install the prerequisites listed in the following steps:

Table of Contents

maxLevel	1
exclude	Contents

Detail on each step follows.

Step 1. Install and Configure Windows Components

Database Server

Ensure that the following components are installed:

PowerShell 5.0-7.2. PowerShell is used by the database deployment scripts.
PowerShell 7.3 has a known problem, please be sure to use 7.2 or lower. See
Jira Legacy
server Ed-Fi Issue Tracker
serverId e04b01cb-fd08-30cd-a7d6-c8f664ef7691
key ODS-5656

.NET 6.0 SDK. Required by the Database Deploy Tool used in the database deployment scripts.

Expand

title	View detail...

PowerShell 5.0

Verify that PowerShell 5.0 or above is installed:

Press the Windows key on your keyboard, type PowerShell, select Windows PowerShell, and press Enter.
Type $PSVersionTable.PSVersion, and press Enter.
If the required version is not installed, download Windows Management Framework 5.0, which includes PowerShell 5.0.

.NET 6.0 SDK

Download and install the latest release of the .NET 6.0 SDK

Web Server

Ensure that the following components are installed:

Internet Information Services. IIS is the web server that will run the ODS / API.

.NET 6.0 Hosting Bundle. The .NET 6.0 Hosting Bundle is required for running the API on IIS. Must be installed after IIS.

Expand

title	View detail...

Internet Information Services

Press the Windows key on your keyboard, type "features", select Turn Windows features on or off, press Enter.
Check the box next to Internet Information Services. The default selections will be good for most cases.
Click OK.

.NET 6.0 Hosting Bundle

Download and install .NET Hosting Bundle 6.0.

Step 2. Install and Configure Required Software

Ensure that the following software is installed and configured on the database server:

Microsoft SQL Server 2019. Microsoft SQL Server is used to store the data for the Ed-Fi ODS / API. Standard, Developer, or Enterprise Editions are supported.
Alternative PostgreSQL datastore: PostgreSQL 13.x. can be used as the datastore for Ed-Fi ODS / API instance instead of Microsoft SQL Server.
- Microsoft Visual C++ 2015 Redistributable. Required by some of the PostgreSQL Binary tools.

Expand

title	View detail...

PostgreSQL Installation (Optional)

Install PostgreSQL 13.x on port 5432 if you intend to use PostgreSQL as a backing datastore for the ODS / API.

PostgreSQL Visualization Tool

Unlike SQL Server, PostgreSQL does not include a GUI to visualize the database (commands are executed via the command line using psql). Below is a list of various tools that work:

Install PostgreSQL

Installation of PostgreSQL can be done either using the binaries or using Docker. The recommended solution is to use the docker install using Linux containers.

Option 1. Installation using PostgreSQL Installer

Expand

title	Installation using PostgreSQL Installer

Install using the PostgreSQL installer. Version 13.x is compatible with the ODS / API.
- Note the installer includes pgAdmin as an option.
- The PostgreSQL installation guide has details.

Download the version 13.x installer.

Click Next.

If you want to install only the tools uncheck PostgreSQL Server, pgAdmin 4 and Stack Builder.

Click Next.

Enter a password for the Postgres superuser.

Click Next.

Enter port 5432 (default).

Click Next.

Click Next to finish the installation.

Option 2. PostgreSQL Installation with Docker

Expand

title	Installation with Docker

Initial setup with Docker:

Install Docker using this guide.
Create a Docker Compose file.

Run PostgreSQL with Docker in Linux Containers

Create a Docker Compose file (name: docker-compose.yml) to bootstrap PostgreSQL using Linux containers. More information on the Docker Compose file can be found on the Docker documentation site.

Code Block

version: '3.7'
services:
    pg13:
        image: postgres:13-alpine
        container_name: pg13
        volumes:
            - pg13-database:/var/lib/postgresql/data
        ports:
            - 5432:5432
        environment:
            - POSTGRES_PASSWORD=${PG_PASSWORD}
        restart: on-failure
volumes:
    pg13-database:
        driver: local
        name: pg13-database

Create an environment file (name: .env) to be consumed by Docker Compose. By default the environment file needs to be in the same folder as the Docker Compose file.

Code Block
PG_PASSWORD=P@ssw0rd

Sample files for these can be downloaded from the download panel on the right.

Data Retention and Docker Compose

Once you have set up your docker-compose.yml and .env files and placed them in a folder (e.g., C:\PGDockerSetup), navigate to that folder in PowerShell and run docker-compose. This utility reads the docker-compose.yml configuration file and runs all of the containers described in that file.

To bring up the environment:

Code Block

language	powershell

C:\PGDockerSetup>docker-compose up -d

To stop the volumes and containers:

Code Block

language	powershell

C:\PGDockerSetup>docker-compose down

To stop the services and remove them, but retain the data in separate volumes:

Code Block

language	powershell

C:\PGDockerSetup>docker-compose down -v

Configure pgpass.conf

A pgpass.conf file must be set up to store passwords in a location accessible by IIS. It is required by database deployment scripts for the ODS / API. Additionally, a PGPASSFILE environment variable should be setup to specify the location of pgpass.conf file.

Create a pgpass.conf file. Note that the password should be your Postgres superuser password and if you are deploying Postgres via Docker, it should match the password in your environment file.

Code Block
localhost:5432:*:postgres:P@ssw0rd

Set the environment variable PGPASSFILE to the location of the pgpass file that was created, which is the recommended approach. Optionally, the file can be saved in %APPDATA%/postgresql/pgpass.conf.

You can test the environment variable setup using:

Code Block
C:\> get-item env:pgpassfile Name Value ---- ----- PGPASSFILE C:\PGDockerSetup\pgpass.conf

Step 3. Install and Configure ODS / API

PowerShell installers released with the ODS / API provide varied configuration options. The primary ODS / API install use cases are provided as examples below. Choose the option that suits your need and customize parameters as needed.

Include Page

	_Sidebar - Getting Started
	_Sidebar - Getting Started

Panel

borderColor	#fec43d
bgColor	#ffedc4
titleColor	#000
borderWidth	1
titleBGColor	#fec43d
borderStyle	solid
title	Downloads

The following link contains sample docker setup files for PostgreSQL

PGDockerSetup.zip

Versions Compared

Old Version 4

New Version Current

Key

Step 1. Install and Configure Windows Components

Database Server

Web Server

Step 2. Install and Configure Required Software

PostgreSQL Installation (Optional)

PostgreSQL Visualization Tool

Install PostgreSQL

Option 1. Installation using PostgreSQL Installer

Option 2. PostgreSQL Installation with Docker

Configure pgpass.conf

Step 3. Install and Configure ODS / API

Page Comparison

Versions Compared

Old Version 4

New Version Current

Key

Step 1. Install and Configure Windows Components

Database Server

Web Server

Step 2. Install and Configure Required Software

PostgreSQL Installation (Optional)

PostgreSQL Visualization Tool

Install PostgreSQL

Option 1. Installation using PostgreSQL Installer

Option 2. PostgreSQL Installation with Docker

Configure pgpass.conf

Step 3. Install and Configure ODS / API