Integration Overview
Transactions to be sent from RJO Hrvyst Hedge to AGRIS
New contracts (Purchase or Sales)
Basis
Hedge-To-Arrive
Flat Price
AutoHedge Contracts
Changes to a contract (or a portion of a contract)
Edit contract details
Price a contract (including ability to price a portion of a delivery/price schedule)
Roll a contract
Cancel a contract
NOTE: The 4 contract types mentioned above will be a one-to-one relationship between Hrvyst Hedge and AGRIS (Basis, HTA, Flat Price, Hedge). If there are more contract types configured in AGRIS, they will not be communicated from Hrvyst Hedge.
Information requested from AGRIS by RJO Hrvyst Hedge
Customer Storage Balances
These requests will be for specific customers, locations, and commodities, on an on-demand basis.
Transactions to be sent to RJO Hrvyst Hedge from AGRIS
Name/Address Changes (When changes are made to Name, Address, Phone, Email, Active Status)
Hedge Transactions (Spot Contracts, Cancel Contracts, Contract Overfills)
Configurable by multiple Name ID Types, multiple Locations, and multiple Commodities.
NOTE: All Contracts are expected to originate, be updated and priced from Hrvyst Hedge (except for Spot Contracts). As mentioned above, the only transactions that should originate from AGRIS would be Spot Contracts, Cancel Contracts, and Contract Overfills.
The following hedge transactions that might be created by AGRIS users (or other AGRIS imports/integrations) will not be sent to Hrvyst Hedge.
Add Contracts
Edit Contracts
Delete Contracts
Price Contracts
Applications To Contracts (regular applications, direct-haul applications, or cross-location applications)
Stock Transfers
Adjustment Tickets (bin measure-up, position shrink, daily handling loss adjustments)
Customer Vs. Stock Adjustments (adjusting the position for handling loss ticket-by-ticket)
Manual Edit of Inventory Stock On Hand
Sales/Invoicing of commodity items from the product invoicing module (Inventory Management System)
Hrvyst Hedge Extended Option
Help, Update Extended Options
If the Extended option for RJO Hrvyst Hedge has not been installed, that is the first step. Help, Update Extended Options allows the option to become available once the updated license file has been received.
Maintenance, Dataset Maintenance, Select the Dataset, Extended Options, System Support
For this dataset, set the RJO Hrvst Hedge Extended Option (#24) = “Y”.
System Security/Users
For the Administrator of the RJO Configuration, they must have access to the CFT, Communications, AGRIS Web Service menu option.
Each user that will be creating transactions in Hrvyst Hedge will need to have the security ability to Import Contracts. Also, if there are additional users (merchandisers) that will be creating transactions in Hrvyst Hedge, that do not currently have a User ID in AGRIS, they will need to be set up in AGRIS System Security.
Document Tracking
Utilities, Document Tracking, Name/Address Info.
Document Tracking for Name/Address Info must be turned on.
Utilities, Document Tracking, Hedge Transactions
Document Tracking for Name/Address Info must also be turned on.
CFT Web Service Configuration
CFT Integration Service Setup
Server = CUL-GNO-QA02
Client = CUL-GNO-QA01
Explaining the service.
The AGRIS CFT Integration Service is a true Windows Service that is also a Web Server for communicating between AGRIS Clients and the Service via ReST API calls.
Within this Service we can support multiple integrations which can all be configured differently.
We have the concept of starting an individual integration process (which is a thread/task within the Windows Service)
These tasks can run simultaneously and will follow the Interval settings in the CFT Integration Setup for each Extract
Assumptions:
AGRIS is installed
AGRIS.ini - Datapath must be set to use UNC paths (drive letters are not supported)
Enable Extended options
CFT,21
SYS,24 (RJO Integration)
NAM,6
GRN,22
Review security settings
Turn on Document Tracking for Name ID and Hedge Transactions
Configure Server First
Logon to server with Admin rights
Verify AGRIS runs then logout
Open the Services Window
Right click on Cultura AGRIS CFT Integration Service
Change the startup type to Automatic (delayed start). This will allow the service to start automatically after a reboot. It also give other dependent services a chance to start before starting itself.
Click the Log On tab
If this is a standalone installation then Local System Account should work fine
If a client / server installation then choose this account and enter domain\username and password for a Services Type account. The main point here is that when the service starts it will need full access rights to the datasets path where the data is located. This path is specified in the CFT Integration Configuration.
Click the apply button
Click the general tab and click Start
You should see Service Status Running
Launch AGRIS
CFT ->Communications ->AGRIS Web Service->AGRIS Web Service Config
Add a new integration (RJO)
Configure each message (XML Extract)
Here is Name and Address Extract
CFT ->Communications ->AGRIS Web Service->Process/Monitor Web Servcie Integration
Choose the Integration Number for RJO
Notice the status - integration not found - when you click the start/stop it will add the integration and start the integration.
