Configure Aeries Database Connections

 

On the Aeries Web  Server(s):

 

Open the  AeriesNetConnections.config file with Notepad. Please note that you may need to run Notepad as an administrator to save your changes. The files are most commonly located in the C:\AppSettings directory or could also be in D:\WebConnections.

 

Adjust the  following sections appropriately and add additional sections as necessary:

 

<DatabaseGroup> – this is the name of the group of databases contained inside this node (set of connections or group of connections).  Normally, this can be the name of the district or something like “Summer  School” or “Training”.  Multiple instances of this section of its subsections can be placed inside the  <AeriesNetConnections> node.

 

 

Adding A New Year

 

<Year> – This is the name of the year of the database that the next properties will point to. The year text needs to be formatted “YYYY-YYYY” i.e.“2017-2018”. This section can be repeated as many times as necessary inside the <DatabaseGroup> node for each year you would like available in Aeries Web. Note that the student portal would normally only have access to the current school year, and the teacher portal usually would only have access to an additional 1  or 2 prior years.

 

<Server> - The name or IP Address of your SQL  Server.

 

<Database> - The name of your Aeries database.

 

<UserID> - The SQL Username that Aeries will use to access the SQL database. This account must have full permissions to all tables. (db_datareader, db_datawriter)

 

<Password> - The password  for the SQL Username used for <UserID>.

 

 

Important: When adding a  new year, remove the Default=“True”  from the old <Year> node after adding the New Year to the connections file.


Example:


<?xml version="1.0"  encoding="utf-8"?>

<AeriesNetConnections>

   <DatabaseGroup id="Eagle USD" Default=“True”>

      <Year  id="2017-2018"Default=“True”>

          <Server><![CDATA[EUSDSQLServer]]></Server>

          <Database><![CDATA[DST17000AeriesDemo_ID]]></Database>

          <UserID><![CDATA[AeriesNetUser]]></UserID>

          <Password><![CDATA[myAeriesPassword]]></Password>

     </Year>

 <Year id="2016-2017">

          <Server><![CDATA[EUSDSQLServer]]></Server>

          <Database><![CDATA[DST16000AeriesDemo_ID]]></Database>

          <UserID><![CDATA[test]]></UserID>

          <Password><![CDATA[myAeriesPassword]]></Password>

     </Year>

 <Year id="2015-2016">

          <Server><![CDATA[EUSDSQLServer]]></Server>

          <Database><![CDATA[DST15000AeriesDemo_ID]]></Database>

          <UserID><![CDATA[test]]></UserID>

          <Password><![CDATA[myAeriesPassword]]></Password>

     </Year>

      <Year  id="2014-2015">

          <Server><![CDATA[EUSDSQLServer]]></Server>

          <Database><![CDATA[DST14000AeriesDemo_ID]]></Database>

          <UserID><![CDATA[test]]></UserID>

          <Password><![CDATA[myAeriesPassword]]></Password>

     </Year>

   </DatabaseGroup>

   <DatabaseGroup id="Summer School”>

      <Year  id="2016-2017">                     

          <Server><![CDATA[EUSDSQLServer]]></Server>

          <Database><![CDATA[DST16000AeriesDemo_SS]]></Database>

          <UserID><![CDATA[test]]></UserID>

          <Password><![CDATA[test]]></Password>

     </Year>

   </DatabaseGroup>

</AeriesNetConnections>


For Summer School Programs that need normal permissions even though you already created the coming year's database, consider the following...