/
AIS - Configuring AGRIS for high transaction volumes

AIS - Configuring AGRIS for high transaction volumes

Owned by Russell Shirley
Last updated: May 08, 2020
4 min read

Do you have high “spikes” of transactions that are sent from AgSync to AGRIS?

Are you seeing that it takes >5-10 minutes for the processing of work orders to occur?

Do you see that AIS goes to a Yellow Traffic light every so often?

These are signs that either

  1. Your AGRIS is not configured to process the higher transaction load levels.

  2. Your timeouts between report processing is > 1M between report processing runs.

  3. The AGRIS Component server (typically the database server) does not have enough hardware (cpu, ram or storage) to handle the requests.

If your hardware resources for the component server are available… follow these steps to double the speed AGRIS can process transactions from AIS.

Instructions to setup multiprocessing for AIS transactions

Our goal is to configure the AGRIS Web Services to look like this

 

  1. Open AGRIS and navigate to CFT>Communications>AGRIS Web Services

  2. Select AGRIS Web Service Config

    1.  

  3. Now select your AgSync CFT to edit the existing configuration for AgSync

    1. Use the General tab to rename the integration to AgSync - Sync data

       

    2. Adjust the existing AgSync CFT to only send data instead of receiving by inactivating - 999 Receive from transaction server to “I” Inactive.

    3.  

    4. Save and exit

  4. Now insert a second integration to AgSync and name this AgSync - Receive from Transaction Server (1)

  5. Adjust to only receive and not sync with AIS by using the select all (mark them “I” for inactive) then mark 999- Receive from Transaction Server as A and change the frequency to “1” Min

    1.  

  6. Now repeat step #5 to create a 3rd integration - naming it AgSync - Receive transactions #2 and repeat configurations for ONLY Receive.

    1.  

  7. Now repeat step #5 again to create a 4th integration - naming it AgSync - Receive transactions #3 and repeat configurations for ONLY Receive.

  8. Write down the integration numbers used for the next step.

    1.  

  9. Navigate to the main menu and stop the AgSync Report stream.

  10. Navigate to Mainenance>Report Stream Maintenance to add a edit the existing report stream

    1.  

    2. Edit the name of the AgSync Report stream to AgSync - Sync data and adjust to only select the correct web service integration number for (sync data)

      1.  

      2. Now Save and exit

  11. Insert a new report stream for each of the Receive from Transaction Server configs created.

    1.  

    2. Configure the stream to include the following.

      1.  

      2. Save and exit.

  12. Create two more report streams and do the same for the remaining “Receive transactions from server configs”

    1. Please note you must create separate report streams that link to separate CFT AGRIS Web Service integrations to enable multiprocessing! This will not work if you use the same User-defined integration for more than one report stream.

  13. Start the Report streams when finished.

  14. Open AIS and monitor.. you should see success if during a high volume time you see the “AGRIS IN PROCESS” >1

    1.  

       

 

Related articles

Related content