Installing Internet Information Server (IIS) for AGRIS™ Mobile Applications

Owned by
Mike Terning
Last updated: Feb 27, 2019
10 min read



Table of Contents
Chapter 1: Introduction
1.1: Purpose
1.2: Tips for Minimizing Downtime During the Installation
1.3: Technical Requirements
Chapter 2: Installing AGRIS™ Web Service
2.1: Installing Internet Information Server (IIS)
2.2: Testing the IIS installation
2.3: Configure the AGRIS Virtual Directory and AGRIS.Env.MessageRouter Application
2.4: Preparing AGRIS for access via Web Service
2.5: User/Dataset Security


Chapter 1: Introduction


1.1: Purpose


This document explains how to install and use the Internet Information Services (IIS). IIS must be installed and configured in order to post and/or retrieve information to/from AGRIS via Web Services and ancillary products including:

  • Agronomy Integration Service (AIS)
  • Insight


IIS is NOT required for the AGRIS Sales mobile application, the AGRIS Warehouse mobile application or the MyGrower customer engagement platform.

1.2: Tips for Minimizing Downtime During the Installation


The AGRIS Agribusiness Management System (AGRIS) 19.1.0 or greater with the latest Software Update must be installed on the component server(s) that you wish to expose for web service integration. If you do not have this version installed or need assistance, contact AGRIS customer support at 800-366-2474. Within AGRIS, from the main menu, select Help > About AGRIS to display the version information. If planning the installation outside of normal support hours, please call AGRIS Technical Assistance Center (800-366-2474) to make special arrangements for generating access codes.


1.3: Technical Requirements


  • The AGRIS Agribusiness Management System (AGRIS) 19.1.0 or greater with the latest Software Update must be installed on the server(s) that you wish to expose for web service or AGRIS mobile applications integration.
  • Supported Operating Systems: To ensure that you are using a supported operating system for the version of AGRIS that you are using, refer to the general AGRIS System Requirements for that version of AGRIS.
    • Important: The AGRIS Web Service and mobile applications are only supported on server-class operating systems. See the AGRIS 19.1.0 System Requirements for details on those operating systems supported for the AGRIS Web Service and mobile applications.


Chapter 2: Installing AGRIS™ Web Service


Note:Please perform these tasks prior to using the AGRIS Web Service and mobile applications. IIS must be installed on each server that you wish to expose for web service integration.


2.1: Installing Internet Information Server (IIS)


This section provides instructions on how to install Microsoft's IIS. The service provides an internal web service interface to AGRIS.
This section is divided into three subsections:


  • Windows Server 2008 R2 SP1
  • Windows Server 2012 R2
  • Windows Server 2016



Windows Server 2008 R2 SP1


  1. If you are not already logged on to the AGRIS server, you need to log on as a user with administrative rights on the system.
  2. Click on Start > Programs > Administrative Tools > Server Manager
  3. Click on Roles, and then Add Roles. The Add Roles Wizard will open.
  4. On the Before You Begin step, click Next
  5. On the Server Roles step, click on the checkbox next to Web Server (IIS), then click Next


  • If a prompt appears asking to Add features required for Web Server (IIS), click the Add Required Features button


  1. Click Next, click Next
  2. Check the checkbox for: ASP.NET


  • If a prompt appears asking to Add role services and features required for ASP.NET, click the Add Required Role Services button


  1. Click Next, click Install


  • The install will start. This can take several minutes to complete.


  1. When the installation is complete, click the Close button.
  2. Close the Server Manager window.
  3. Register ASP.NET 4.0 with IIS by going to Start > All Programs > Accessories > Right-click on Command Prompt and select Run As Administrator. At the command prompt, type:


C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
Press Enter. When the process indicates "Finished installing ASP.NET", close the command prompt screen.
Enable 32-bit Applications:


  • Click on Start > Programs > Administrative Tools > Internet Information Services (IIS) Manager
  • In the Connections, click on the Plus sign next to your server
  • Click on Application Pools
  • Right-click on the DefaultAppPool and select Advanced Settings…
  • On the Advanced Settings window, change the Enabled 32-Bit Applications setting to True
  • Click OK to save changes
  • Close the Internet Information Services (IIS) Manager window



Windows Server 2012 R2


  1. If you are not already logged on to the AGRIS server, you need to log on as a user with administrative rights on the system.
  2. Click on Start. Type "Server Manager" and then click on the Server Manager
  3. Click on the Local Server in the selection tree.
  4. Scroll down to the ROLES AND FEATURES section
  5. In the TASKS dropdown, select Add Roles and Features
  6. On the Before you begin step, click Next
  7. On the Select installation type step, select Role-based or feature-based installation and click Next
  8. On the Select destination server step, ensure your server is selected and click Next
  9. On the Server Roles step, expand the Application Server option, checkmark Web Server (IIS) Support, and click Next
  10. On the Add features that are required for Web Server (IIS) Support? prompt, click Add Features, then click Next
  11. On the Features step, click Next
  12. On the Web Server Role (IIS) step, click Next
  13. On the Role Services step, expand Application Development and checkmark ASP.NET 4.5
  14. On the Add features that are required for ASP.NET 4.5? prompt, click Add Features
  15. click Next
  16. On the Confirmation step, click Install
  17. Once the installation is complete, click Close to close the Add Roles and Features Wizard.


Enable 32-bit Applications:


  • Click on Start and type "IIS" then click on the Internet Information Services (IIS) Manager
  • In the Connections, expand your server
  • Click on Application Pools
  • Right-click on the DefaultAppPool and select Advanced Settings…
  • On the Advanced Settings window, change the Enable 32-Bit Applications setting to True
  • Click OK to save changes
  • Close the Internet Information Services (IIS) Manager window



Windows Server 2016


  1. If you are not already logged on to the AGRIS server, you need to log on as a user with administrative rights on the system.
  2. Click on Start. Type "Server Manager" and then click on the Server Manager
  3. Click on the Local Server in the selection tree.
  4. Scroll down to the ROLES AND FEATURES section
  5. In the TASKS dropdown, select Add Roles and Features
  6. On the Before you begin step, click Next
  7. On the Select installation type step, select Role-based or feature-based installation and click Next
  8. On the Select destination server step, ensure your server is selected and click Next
  9. On the Server Roles step, checkmark Web Server (IIS) Support, and click Next
  10. On the Add features that are required for Web Server (IIS) Support? prompt, click Add Features, then click Next
  11. On the Features step, click Next
  12. On the Web Server Role (IIS) step, click Next
  13. On the Role Services step, expand Application Development and checkmark ASP.NET 4.6
  14. On the Add features that are required for ASP.NET 4.6? prompt, click Add Features
  15. click Next
  16. On the Confirmation step, click Install
  17. Once the installation is complete, click Close to close the Add Roles and Features Wizard.


Enable 32-bit Applications:


  • Click on Start and type "IIS" then click on the Internet Information Services (IIS) Manager
  • In the Connections, expand your server
  • Click on Application Pools
  • Right-click on the DefaultAppPool and select Advanced Settings…
  • On the Advanced Settings window, change the Enable 32-Bit Applications setting to True
  • Click OK to save changes
  • Close the Internet Information Services (IIS) Manager window




2.2: Testing the IIS installation


Copy http://localhost/ into the web browser address and press enter or click GO. You should see a page describing Microsoft Internet Information Services. If you do not see this information then IIS is not installed properly. You should make sure this is working correctly before proceeding to the next step.
Windows Server 2008 R2 SP1: the Internet Explorer browser should look like the following screenshot:

Windows Server 2012 R2 or Windows Server 2016: the Internet Explorer browser should look like the following screenshot:


2.3: Configure the AGRIS Virtual Directory and AGRIS.Env.MessageRouter Application


As of AGRIS version 10.1.1 the AGRIS Web Service is no longer a separate installation; it is integrated into the main AGRIS installation. To configure the AGRIS Web Service, follow the instructions below.
In the instructions below, the <AGRIS Directory> is the location of the AGRIS installation on the server. This is typically C:\APPS\AGRIS
There are two sets of steps below: steps for Upgrading and steps for a New Installation. Follow one set of steps or the other. If you are not sure about which set of steps to follow, open Control Panel > Programs and Features. If there is an AGRIS Web Service program listed then follow the steps for Upgrading, otherwise follow the steps for New Installation.
Steps for Upgrading from the previous version of the AGRIS Web Service
The upgrade instructions below assume that your existing AGRIS Web Service is installed under the Default Web Site and is located at AGRIS\AGRIS.Env.MessageRouter. However, as this is customizable, your AGRIS Web Service may be located under a different Site and may have a different name.


  1. Open Control Panel > Administrative Tools > Internet Information Services (IIS) Manager
  2. In the Connections tree, expand your server
  3. Expand the Sites
  4. Expand the Default Web Site
  5. Expand AGRIS
  6. There will be an AGRIS.Env.MessageRouter application under AGRIS
  7. Take note of any customizations that you may have set on the AGRIS.Env.MessageRouter application (such as in Basic Settings…, Advanced Settings…, or in any other settings at the application level). Screenshots may help with this. This is important, as you may have settings for your particular web service environment that you will want to reestablish after the upgrade.
  8. When you have captured your settings, right-click on AGRIS.Env.MessageRouter and select Remove, then click Yes to confirm the removal
  9. Right-click on Default Web Site and select Add Virtual Directory…
  10. For the Alias enter: AGRIS
  11. For the Physical path click the […] button and select the <AGRIS Directory>
  12. Click the Ok button to save and close the Add Virtual Directory window
  13. Right-click the AGRIS folder and select Add Application…
  14. For the Alias enter: AGRIS.Env.MessageRouter
  15. For the Physical path click the […] button and select the <AGRIS Directory>\bin folder
  16. Click the Ok button to save and close the Add Application window
  17. Reestablish the customizations that you captured previously.
  18. Close the IIS Manager window
  19. Open Control Panel > Programs and Features
  20. Right-click on AGRIS Web Service and select Uninstall
  21. If you receive a "Are you sure you want to uninstall AGRIS Web Service?" message, click Yes
  22. The uninstall should complete in a few seconds and AGRIS Web Service should be removed from the list of installed programs
  23. Proceed to the Test the AGRIS Web Service step.



Steps for a New Installation of the AGRIS Web Service


  1. Open Control Panel > Administrative Tools > Internet Information Services (IIS) Manager
  2. In the Connections tree, expand your server
  3. Expand the Sites
  4. Expand the Default Web Site
  5. Right-click on Default Web Site and select Add Virtual Directory…
  6. For the Alias enter: AGRIS
  7. For the Physical path click the […] button and select the <AGRIS Directory>
  8. Click the Ok button to save and close the Add Virtual Directory window
  9. You should now have an AGRIS folder under the Default Web Site
  10. Right-click the AGRIS folder and select Add Application…
  11. For the Alias enter: AGRIS.Env.MessageRouter
  12. For the Physical path click the […] button and select the <AGRIS Directory>\bin folder (typically C:\APPS\AGRIS\BIN)
  13. Click the Ok button to save and close the Add Application window
  14. If this was an upgrade from a prior version of the AGRIS Web Service, reestablish the customizations that you captured previously.
  15. Proceed to the Test the AGRIS Web Service step.



Test the AGRIS Web Service:


  1. On the server running the web service, open a browser and go to this address: http://localhost/agris/agris.env.messagerouter/agris.env.messagerouter.asmx.
  2. The MessageRouter Web Service screen below will appear if the test was successful.



  1. On the server running the web service, open a browser and go to this address: http://localhost/agris/agris.env.messagerouter/agristest.aspx
  2. Click the Basic Webservice Test (IIS/ASP.NET) button
  3. If the test was successful you will see the text "Basic Test Passed!!" in the Output, as seen in the screenshot below.



2.4: Preparing AGRIS for access via Web Service


AGRIS Web Service provides 3rd party applications the ability to send and retrieve information to and from the system. This integration is provided using Web Service and XML Messaging. IIS Web Services provides the communications. AGRIS XML messaging is the format of the data moving between AGRIS and other 3rd party applications.
If you do not have a need to retrieve documents based on date/time modified, then you can skip the remaining information for this topic.
If you need to retrieve documents based on last modification date/time, you will need to enable the AGRIS Document Tracking modules. These options are available under AGRIS Main Menu > Utilities > Document Tracking. These options can be configured by dataset, by individual document type.
Note: Turning on the Document Tracking process may occupy your machine for a few hours, depending on the size of your dataset. Our recommendation is to start this process at the end of the day after all essential work has been completed. If Document Tracking is already turned on for this dataset, an X appears in the "On" box next to each Document Type. If Document Tracking is not on, perform the following steps.
This is an example of how document tracking can be enabled.
Choose ACR INVCE Invoices.


  • Select Turn Document Tracking On.
  • At the "List of Documents Will Now Be Updated" prompt, select OK.
  • Close the Document Tracking window. Select Back to display the AGRIS main window. Re-open the Document Tracking window when the list of documents has been updated to verify that document tracking is on.
  • You can turn on Document Tracking for multiple document types at the same time.




2.5: User/Dataset Security


Note:If you do not use dataset security, you can disregard this step.
1.If you use dataset security, use Customize > System Security to set up a "web service" User Id within each dataset that you want to extract information, or bring data back in to the system.
2. For data extract abilities, the web service User Id must have at least View ability for each of the security items.
3. For bringing data back in to the system, we suggest to set up the web service User Id to have Delete ability for the security items. Although, you could set up the User Id to have only Add or Edit security access, based on your specific data import needs.
4. This web service User Id and Password would then be supplied with all of your Web Service messages.