AGRIS Customer Documentation

MSSQL - Configuring your Terminal or Citrix Server to access the database

Owned by Russell Shirley
Last updated: Mar 22, 2017
2 min read


When configuring one or many client servers the following question was posted that will provide a working example.

 - I have about 60 Agris users and 100 Users total that connect to (3) Citrix servers (about to be replaced with 4 new Citrix servers)


My questions are as follows:

1) Is it correct that the Agris client would be installed on the Citrix Farm?  

(Yes this is correct on each user server)

2) Is there an element of Agris that needs to be installed on the server? 

(No on the database server, Yes each Citrix server will need AGRIS loaded, If you are looking to load extra performance load balancing a separate type of server can be used "Component" server.) 

3) Iif so does it require a separate server for that? 

(AGRIS should be loaded on each client server in the citrix server)

(AGRIS should be loaded on any component server used)

4) If so, what kind of specs does it need?

(Specs for Terminal / Citrix servers are adequate) 


Step-by-step guide for configuring Component servers

For each component server piece

  1. The agris.ini on each (TS) Terminal Server or Citrix Server can have component server=TSbox name
  2. The data path= line should be the same for all ini's
  3. The dbconnections.config should be the same for all TS boxes
  4. The only diff is the agris.ini component server=TS box name should be the same id or blank as it should be filled in as the default for the data path. (all termininal servers should be directed at the same component server location)
  5.  If the data-path points to a share on one of the TS boxes then you can leave the component server= line as blank because it will default to the server of the data path

 



✦✦✦

3820 Mansell Road, Suite 350 ✦ Alpharetta, GA 30022 ✦ www.GreenstoneSystems.com
© 2011 - 2024 Cultura Technologies LLC. All Rights Reserved Worldwide.  Products and company names mentioned herein may be trademarks or registered trademarks of their respective owners.