Setup - AIS pre-requisites and installation

x This is a high-level overview for the steps to configure a customer to use AIS..  

Network and Server Configuration

1. Installing IIS

Before installing AIS please have your I.T. person review and update your server / network configuration based on the documentation found in the AGRIS IIS attachment. 

Please note - follow the Install steps that start on page 4 that references Microsoft IIS ….  

The steps listed to configure for Microsoft IIS can be downloaded from this document. 

AGRIS Configuration

1. AGRIS Unit of Measure
   1. Ensure that the AGRIS inventory UOM setup includes a UOM called ac and common uom as each
   2. Verify this ac business uom is cross referenced to the "ac" acre in the Agroguid UOM cross reference.
      
2. Apply the updated AGRIS license provided from the Greenstone Support team.   
   1. This license will enable the extended option for the AGRIS web services CFT option.
   2. Once the license is updated individual users responsible for AIS will need AGRIS security enabled for this feature. 
      
      
3. Document Tracking 
   1. From the Utilities Menu, enable Document tracking for each of the documents listed below. Each of these are required for propper operation of the AIS integration
   2. When using AGRIS 10.3.2 and higher crop zone will also need to be enabled. 
   3. 

4. AgroGuide Blend Group normalization

   1. Review your operations types in AgSync.  

   2. These operations types should be compared to the Blend Groups in AgroGuide.

   3. A key component in configuring the AIS interface to AgSync will be to map each operation type to the supporting blend group type in AgroGuide.   (Dry or Liquid) If your company's locations use inconsistent blend group ID's please work with your Greenstone Implementation specialist to discuss next steps.    

AIS web site configuration

1. https://ais.greenstonesystems.com/Login/Login
   1. User Name = (provided by Greenstone)
   2. Once you have entered AIS.. there are many things to do. Some of which are listed below.  
      
      
2. Contact AgSync to get the GUID references for the organization. 
   This list should identify the Organization GUID and each retail site's GUID.  This information is very important as it will cross reference to the AGRIS location codes and dataset used. 
   
   
3. Next locate and document the following: 
   1. Dataset GUID's and name descriptions for the Live dataset and practice dataset. 
   2. License GUID for AGRIS from the customer
   3. Location GUID's for each site that will use AgSync.
      This can be found in a couple different places. 
      1. Help About. 
         1. 
      2. Dataset maintenance
         1. 
      3. Location Codes and Descriptions
      4. You should also ensure the customer has configured the AGRIS WebServices CFT for AgSync. 
         1. 
         2. 
         • • • The URL should be https://aisgreenstonesystems.com/
         1. Now ensure the following web service messages have been turned on .
            1. 
               
               
4. This information can be sent to Greenstone for next steps and configuration of the website initial integration. 
   
5. Configuring new locations for use in AIS  -  Once you have spoken with Greenstone and the organization is configured within AIS there are a few this to do. 
   1. Process the AGRIS WebServices CFT 
      1. Access AGRIS and run the Web Service CFT to send relevant details to AIS for cross-reference
      2. Please review and ensure no errors occurred.  - If errors are encountered... stop and resolve before moving to the next step.
         
         
   2. Location Cross reference
      1. Select the pull-down menu for AgSync Config
   1. 1. 1. 
            
            
      2. Add the location code remembering that the key data... AGSYNC Retailer GUID = AGRIS location code all other data can be copied using Cntrl C (copy) and Cntrl P (Paste)
      3. Today update formula number will be checked and update product amounts would be checked if they plan to deliver / update the product amounts from AgSync.  This may be a problem if using an automated blender
         
   
   
   

Related articles