Versions Compared

Old Version 57

changes.mady.by.user Mike Terning

Saved on

compared with

New Version Current

changes.mady.by.user Jon Delaney

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Pervasive SQL Database File Format Conversion

...

Upgrading from Previous

...

PSQL Versions

AGRIS 17.2.0 requires you to pre-install Pervasive® PSQL™ to manage dataset operations. Please follow the instructions at  
https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1

...

As a result of many requests for improving the software update process, AGRIS includes a utility for updating AGRIS client computers. This feature, called the AGRIS Auto-Update, assumes the AGRIS users/clients are running AGRIS V9.45.0 or .27 or greater, any updates made to the Component Server are automatically detected by the system.

...

      1. Create a network share (Example: \\servername\apps\AGRISDIST). All users need Read permissions to this share.
      2. The network administrator should copy the entire CD save all the installation files to this share.
      3. If an update is available (update.exe), it should be copied to the same folder that contains the setup.exe, which was created in the previous step.
      4. Install AGRIS Version 17.2.0 or later on all AGRIS servers, for example, component servers, database servers, etc. Also, apply updates, if they exist, for example, update.exe.
      5. Install AGRIS Version 17.2.0 or later on all your AGRIS workstations. The AGRIS clients are now ready to detect updates from your servers. When you receive an update from AGRIS, you only have to update your Component Server(s) and application server(s). If you have not specifically set up a Component Server(s), then we assume the database server is the Component Server.

...

Step #SectionStep

1.

Sec 2.2

Verify your workstations and servers meet or exceed the system requirements and check their compatibility with current hardware requirements.

2.

Sec 2.3

Install any outstanding Windows Service Packs (if necessary).

3.

–

Install a supported version of Pervasive® PSQL™ Server on the database server(s) using the instructions available at https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1

4.

–

Install a supported version of Pervasive® PSQL™ Client on any AGRIS client workstations, including Citrix or Terminal Servers using the instructions available at https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1

5.

Sec 2.5

Set up the Pervasive_Admin group and a padmin user account.

6.

Sec 2.7

Create a COM+ Services user account.

7.

Sec 2.8

Set up network COM+ access on the AGRIS Server.

8.

Sec 2.10

Set up the AGRIS directory structure and permissions.

9.

Sec 2.14

IMPORTANT! Back up your datasets.

10.

–

Stop the Pervasive® PSQL™ services on the AGRIS server.

11.

Sec 3

Manually install AGRIS 17.2.0 Server on the database server.

12.

Sec 4

Manually install AGRIS 17.2.0 Server on any Citrix Servers/Terminal Servers.

13.

Sec 5

Manually install AGRIS 17.2.0 Client on all your workstations.

14.

Sec 2.17

Download and manually install the latest AGRIS Service Pack on the database server and on any Citrix Servers/Terminal Servers.

15.

Sec 1.9

Use the Auto-Update feature to apply the latest service pack to all client workstations.

16.

–

Launch AGRIS from a client workstation to create the datasets folder and first database.

17.

Sec 10

Update the licenses file and the extended options

19.

Sec 7

Install any standalone units that use oneWeigh.

20.

Sec 2.16

If necessary, set up Auto Blender configurations to include AGRIS User information.

...

    1. Click on Start >> Programs >> Administrative Tools >> DNS.
    2. Right-click the server and select Properties.
    3. Click the Forwarders tab.
    4. Click the Enable Forwarders option to enable the field allow the IP addresses to be entered.
    5. Enter the primary DNS server (provided by the internet service provider) and click Add.
    6. Enter the secondary DNS server (provided by the internet service provider) and click Add.
    7. Click Apply >> OK.
    8. Close the DNS window.

Anchor
_Ref88359829
_Ref88359829
Anchor
_Toc158617998
_Toc158617998
Anchor
_Ref190154666
_Ref190154666
Anchor
_Ref190154670
_Ref190154670
Anchor
_Toc190492488
_Toc190492488
Anchor
_Toc190498207
_Toc190498207
Anchor
_Toc478038984
_Toc478038984
Setting up the

...

padmin User

...

Account

You must set up a local user account and group on the Pervasive database server.


Note:In previous versions of AGRIS, the  The padmin username and password wereare hard coded in the AGRIS application. As of the release of AGRIS V9.4.1, users can alter the padmin username and password.

...

  1. Click Customize Menu.
  2. Click Database Security Configuration to display the message:New User and Password must exist on database server and the user must be a member of Pervasive_Admin the local Administrators Group.
  3. Contact our Technical Assistance Center (800-366-2474) for an access code to enter in the Database Security Configuration window.
  4. Type the access code in the Access Code field.
  5. Press Enter or Click OK to display the User Name and Password window.
  6. Enter the username and password for the Pervasive Administrator account.
  7. Click Save.
  8. Exit AGRIS.

...

  1. Go to Start >> Settings >> Control Panel.
  2. Open Administrative Tools.
  3. Open Computer Management.
  4. Browse to Local Users and Groups and expand.
  5. Click Users.
  6. Click Action >> New User or right-click Users and select New User.
  7. Type a username (Typically padmin). The Full name and Description are optional.
  8. Type a password.
  9. Check the following options:
    • User cannot change password
    • Password never expires
  10. Click Create, and then Close.
  11. Click Groups.
  12. Click Action >> New Group or right-click Groups and select New Group:
    1. The case-sensitive group name must be Pervasive_Admin.
    2. The Description is optional.
    3. If AGRIS is installed on a Domain Controller, the group must be a Domain Local Security Group.
  13. Click Add.
  14. Add the padmin account.
  15. Click Create.
  16. Click OK >> OK.Right-click the user created in step 7 and click Properties
  17. Click the Member Of Tab and click Add... and type Administrators then click Check Names followed by OK
  18. Click OK again
  19. Close Computer Management, Administrative Tools and Control Panel.

...

If the AGRIS 17.2.0 server is also a Domain Controller, then the padmin user account must be a domain user . In this case, the Pervasive_Admin group needs rights to log on locally.

...

instead of a local user and made a member of the Builtin Administrators group. 

Anchor
_Installing_or_Upgrading
_Installing_or_Upgrading
Anchor
_Ref88359837
_Ref88359837
Anchor
_Toc158617999
_Toc158617999

Anchor
_Toc478038986
_Toc478038986
Creating a COM+ Services User Account

...

AppsThis is a shared folder where user rights are assigned.
AGRISThis is the folder under the Apps folder in which the program is installed and where the dataset files reside.
AgrisdistThis is the distribution folder under the Apps folder used by the AGRIS Auto-Update Feature to automatically roll out updates to client computers that run AGRIS 17V9.25.0.27 or highergreater. This folder must be accessible via a UNC path in order for clients to update correctly. For additional information about the Auto-Update feature, please refer to Section 1.9.

...

Apps Share Permissions:

    • Administrators = Full Control
    • Pervasive_Admin Padmin = Change and Read
    • Services = Change and Read
    • AGRIS Users = Change and Read

Apps Security Permissions:

  • Administrators = Full Control
  • Pervasive_Admin Padmin = Full Control
  • System = Full Control
  • Services = Full Control
  • AGRIS Users = Modify, Read & Execute, List Folder Contents, Read, and Write

...

IMPORTANT
You must back up all standalone workstations (including oneWeigh units) and servers storing AGRIS datasets to prevent loss of data. Back up the entire Apps folder and all subfolders on a daily basis (recommended).

    • The Apps\AGRIS\datasets\ folder contains setup information and data
    • The Apps\AGRIS\userprog\ folder contains user-defined reports and forms.
    • The Apps\AGRIS\support\ folder contains user-defined printer text drivers, custom logos and backgrounds if present.


Backing Up Open Database Files

...

Note:The software installation folder filename name cannot be longer than eight characters.

...

Windows Server 2008 R2 SP1 Terminal Services

Citrix Server

Windows Server 2012 R2 Terminal Services

Service Pack 1

Latest Windows Service Pack

No Service Pack

Install Terminal Services

Install Terminal Services

Install Terminal Services

 

Install MetaFrame XP/Presentation Server or Citrix XenApp 6.5.0

 

Pervasive® PSQL™ 32-bit Client

Pervasive® PSQL™ 32-bit Client

Pervasive® PSQL™ 32-bit Client

AGRIS 17.2.0 Server

AGRIS 17.2.0 ClientServer

AGRIS 17.2.0 Server

Anchor
_Ref88362347
_Ref88362347
Anchor
_Toc158618015
_Toc158618015
Anchor
_Toc478039011
_Toc478039011
Installing AGRIS 17.2.0 Server on Citrix Server/Terminal Server

  1. Log all users out of the Citrix/Terminal Server(s) and prevent additional users from logging on while installing AGRIS 17.2.0.
  2. Close all other applications and restart the server.
  3. Install a supported version of Pervasive® PSQL™ using the instructions available on the AGRIS Customer Portal site:
    https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1
  4. Complete section 3.2 to install AGRIS.
  5. Manually set the AGRIS data path - see Section 13.1  https://culturatech.atlassian.net/wiki/x/KnnGBQ for additional information.
  6. Save the AGRIS data path and restart the server.

...

IMPORTANT:Before installing the AGRIS 17.2.0 Client, install a supported version of Pervasive® PSQL™ on the client workstation using the instructions available on the AGRIS Customer Portal site:at; at  
https://myaccountculturana.agrisforce.com/s/article/KnowledgeBase/Product-Info/Downloads_and_Updateska036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1

  • Installing the .NET Framework:
    • For Windows 8.1 and Windows 10, part of the.NET Framework must be installed through the Programs and Features:
      • Click Start and type "Programs and Features", then click on the Programs and Features.
      • Click on the Turn Windows Features on or off link.
      • Checkmark the .NET Framework 3.5 (includes .NET 2.0 and 3.0) checkbox
      • Click OK to start the installation
      • Once the installation is complete, click Close
      • Close the Programs and Features
      • Proceed with the next step in the AGRIS installation.
    • For all other supported client operating systems, there are no extra steps for the .NET Framework.
  • Anchor
    ClientNextStep
    ClientNextStep
    Open the Agrisdist network share created in section 2.10,
  • Open the Setup.exe:
    • Right-click the Setup.exe and choose Run as Administrator. If there is a User Account Control message, click Allow.

...

Install the Pervasive Client Engine in accordance with the instructions available on the AGRIS Customer Portal site:at 
https://myaccountculturana.agrisforce.com/s/KnowledgeBase/Product-Info/Downloads_and_Updatesarticle/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1 
Install the AGRIS Version 17.2.0 Server in accordance with the instructions contained in section Server Installation.
Install the AGRIS Version 17.2.0 Client in accordance with the instructions contained in section Client Installation.

...

Data Path

This is the path to the location of the agris\datasets folder where all of your data is kept. If running standalone this value does not need to be set since it defaults to the local machine. If running in a client server environment this value needs to point to the database server.
Examples: f:\agris\datasets or Example: \\server\apps\agris\datasets.

Support Path

This is the path to the location of the support folder. By default this is set relative to the path set for the Data path.

Userprog Path

This is the path to the location of the userprog folder. By default this is set relative to the path set for the Data Path.

Work Path

This is the path to the location of where AGRIS creates temporary files. By default this is set to the Data path. (For best performance, set this to a local drive. Example: c:\apps\agris\temp)

Component Server

This is the name of the server that runs the AGRIS COM+ applications. If left blank, this setting is derived from the Data path. Otherwise, this can be set to the name of a separate Component Server on the network.

Locking Server

This is the name of the server that runs the AGRIS COM+ ServerLock application. If left blank, this setting is derived from the Data path. Otherwise, this can be set to the name of a separate Locking Server on the network. When this field is used all clients need to use the same Locking Server or data corruption could occur due to multiple locking servers.

GEOData Path

This parameter provides the ability to reference your Georeference data such as TIGER data from various locations on your network. This path can contain drive letters or UNC but it must be a valid location, otherwise you will get an error. If the GEOData Path is empty then the default is Agrisroot\support\agy. If the GEOData Path is set then this value will override the default.

Notification URL

Using Notification URL01 - 99 you can point to different Web Services that may be needed. They must be sequentially set with no gaps, starting with Notification URL01.

Examples:
Notification URL03 cannot be set unless Notification URL01 and Notification URL02 have been set. If Notification URL02 needs to be removed, then Notification URL03 should be changed to Notification URL02 or Notification URL02 must be set to something like "Available" or "Unused".

...