AGRIS Customer Documentation

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »

If your team currently has access issues opening AGRIS please continue to read below for more details on how to configure this feature.

Benefits

  • Simplifies steps to identify who is currently using AGRIS.

  • Improves license “lock” logic when multiple servers communicate with the AGRIS System.

AGRIS has added the ability to monitor and identify users of the AGRIS system from the utility menu under the Login Inquiry option.

This feature provides quick and easy access to assess which users who are actively using the AGRIS System and related log in history to simplify events where multiple users need to take an action.

Purpose

The license service will allow users access to licensed features within AGRIS. It will track licenses consumed along with identity information to help identify users or processes that are using AGRIS licenses.

  • The service should be configured to run on one dedicated machine only.

  • If you are using PSQL/ZEN as your database we recommend this DB server is also where you want to configure the license service assuming AGRIS is also installed on the DB Server.

  • If you are using MSSQL, we recommend the license service is configured to run on a separate dedicated machine where AGRIS is also installed. This is likely the same machine where other AGRIS services are running. “Typically identified as the AGRIS application server”.

Configuration

Client/Server configurations: Standalone Installation Type

Permissions

  • If AGRIS is installed following the Standalone Installation Type and the agris.ini/datapath is a local drive then the default permissions of the system account should be sufficient. See details below.

  • If the AGRIS.ini/datapath points a folder on a different machine/server, then you should follow the Client/Server Network Installation Type below. This installation type should use a domain\username and password. These credentials should have full permissions to the AGRIS.ini/datapath.

Client/Server Network Installation Type

*** Note: only 1 instance of the License Service should be configured and running

*** Note: Datapath settings should be UNC Paths for machines in a Client/Server configuration

Client Settings (AGRIS.ini)

The default URL for the license service is http://servernamehere:9092/api/SysLicenseRequest

When should the License Service URL be set in AGRIS.ini?

  • In most cases, it is not necessary to set the License Service URL. AGRIS can automatically determine the location of the license service as long as the service is installed on the same machine that the AGRIS.ini/DataPath is pointing.

  • Exceptions:

    • If the license service is configured to run on a different machine than the AGRIS.ini/DataPath is pointing, then you will need to set the License Service URL to point to a specific machine/server.

    • If it is necessary to configure the License Service to run on a different port than the default port 9092, then you will need to set the License Service URL and port accordingly.

    • Configuring the License Service URL in AGRIS.ini

      • Add “License Service URL=license_service_url_goes_here” to AGRIS.ini

      • Example:

      • Open AGRIS.ini in a text editor

      • Add this line to AGRIS.ini (if it doesn’t already exist)

  • Server Settings

PSQL/ZEN Database: If this installation is a Client/Server install (network environment) where users and the AGRIS applications are running on different machines than the Database Server, then we recommend configuring the License Service to run on the Database server.

MSSQL Database: Usually the AGRIS.ini/DataPath is pointing to a different machine than the MSSQL Database Server. We recommend installing AGRIS on the same machine where the AGRIS.ini/DataPath is pointing. This is usually the same server where other AGRIS services are configured to run. Configure the License Service based on the following steps.

See screenshots below.

Configure the service “Log on as” set to This account.

Be sure that the Log On Account has full permissions to the AGRIS Datapath and all its subfolders. The AGRIS Datapath is expected to be a UNC path.

Set the Startup type.

Set the Recovery options.

Click Apply to apply these settings.

Click Start to start the service.

 

Standalone Installation Type

In most cases, the following steps may not be necessary. When AGRIS is launched and it needs to access the License Service, the user will be prompted to Start the Service. Assuming they answer “Yes” to the question the steps below for configuring the service should not be necessary. If the user is unable to start the service, please modify the AGRIS shortcut/Properties/Advanced, check the Run as administrator box and try again. The AGRIS install will check this box automatically beginning in 22.1, however, if users have custom shortcuts to AGRIS on their desktop, those shortcuts may need to be updated in order for the user to start the service from within AGRIS.

This installation type assumes the agris.ini/datapath will be a local path. It will only access local resources.

There is no need to change the AGRIS.ini since the default License Service URL is pointing to localhost.

Configure the service “Log on as:” set to Local System Account.

Set the Startup type.

Click Apply to apply these settings.

Click Start to start the service.

Client/Server configurations:

Firewall considerations depend on your organization's requirements.

Use the settings below for Inbound and Outbound Rules.

  • No labels