TABLE OF CONTENTS (for RJO Hrvyst Hedge, AGRIS Configuration AGS-8899)
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)
Basic Setup / Configuration Overview
A. AGRIS setup/configuration steps
1. Hrvyst Hedge Extended Option
2. Document Tracking
3. System Security/Users
4. CFT Integration Service Setup
5. CFT RJO Integration Configuration
6. Monitor the RJO Hryvst Integration
7. Position Balancing between the two systems
Other setup/configuration steps outside of AGRIS
RJO permissions
Greenstone Datahub Permissions (see “Setup the RJO Hrvyst Hedge Provider“ page)
Datahub connectivity
Hook and test connections
A. AGRIS setup/configuration steps
1. 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”.
2. 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 Hedge Transactions must also be turned on.
3. System Security/Users
Select Customize > System Security > Insert > User Id (consider something obvious like “RJO” or “Hrv”.
Keep password simple but effective (5 digits)
Follow Security Security. Type “M” to skip down to the CFT Pkg section.
AGRIS Web Service Security
For the Administrator of the RJO Configuration, they must have access to the CFT, Communications, AGRIS Web Service menu option.
Import Contracts Security
Type “C” to skip to the GRN Pkg section.
If there are 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. Each user that will be creating transactions in Hrvyst Hedge will need to have the security ability to Import Contracts.
Social Security/Federal Tax ID Security
Type “N” to skip to the NAM Pkg section.
No Social Security numbers or Tax IDs will be sent to RJO in the AGRIS/Hrvyst Hedge integration. However, the CFT Service module within your local network (explained in the next section below) will extract the Name/Address information from the AGRIS database in order to send to the hosted Greenstone Data Hub for further processing. To suppress the Social Security Number/Federal Tax ID within the interim data transformation modules, leave the security option shown below set to “No Access”. The security credentials of the user that starts the CFT service will be used for the data communication process. We suggest there should be a specific User ID set up for the RJO integration. For this User ID, set the Social Security/Federal ID security option to “No Access”. Log into AGRIS with this User ID when the CFT service is initially started (see the section below for “Monitor the RJO Integration”).
4. Commodity setup
Before configuring Hrvyst, it is very important to configure each commodity for every location that you plan to use in Hrvyst.
For each commodity, you plan to work with the Default board, Default month and Near-by month must be configured. This is very important to ensure the hedge position is updated correctly.
Ensure you have set that up in your standard processes to roll the nearby month as nessasary.
5. CFT Integration Service Setup
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 (as discussed in above sections):
AGRIS is installed
AGRIS.ini - Datapath must be set to use UNC paths (drive letters are not supported)
Enable RJO Hrvyst Hedge Extended option (SYS #24)
Review security settings
Turn on Document Tracking for Name ID and Hedge Transactions
Configure the Service
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 gives 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
When working with MSSQL databases and a Trusted Connection data source which is specified in bin\dbconnnections.config, the Account specified under the Log On Tab should have permissions to
create, read, write, update, delete tables within the AGRIS database and the Accelerator database
When working with MSSQL or PSQL the account should have permissions to
create, read, write, update, delete files/folders within the Datasets folder and below
6. CFT RJO Integration Configuration
Create a new Web Service Integration
Launch AGRIS
CFT ->Communications ->AGRIS Web Service->AGRIS Web Service Configuration
Add a new integration (RJO)
The CFT integration MUST be configured in the same dataset as the live commodity system.
You can give any description for the Integration Name (RJO Hrvyst Hedge for example).
The Dataset Number and Data Path MUST be set to be the current dataset (or blank).
You can leave the Dataset Number and Data Path blank as long as the current dataset has a UNC path.
If message below Data Path shows “Blank = (a mapped drive)”, then the Data Path must be filled in with a UNC path.
The Component Server can be left blank, or point to an AGRIS Web Service server.
Output Option 3 with Transaction Integration 05 indicates that it is RJO Hrvyst Hedge.
Select Next to go to the next options on the screen.
Use CFT Service URL must be set to “Y”.
The CFT Service URL and the Transaction URL should automatically default for you once you select OK.
The CFT Service URL should be http://localhost:9090/api/CftRequest (change if needed)
The Transaction URL (NOTE) by default is set to work with PSQL
IF MSSQL please use this URL replacing local host with the correct server name. http://CULGSSQATS02:8080/AgrisSQL/RESTCommandWebService/ExecuteServerCommand/AgentProcessor/AgrisMessage?TransactionType=0
The CFT Service is a new service installed with AGRIS, that will retrieve transactions from the AGRIS database via the AGRIS Web Service and send them to the Transaction URL (SOGE Agent).
The Transaction URL (SOGE Agent) will then send the transactions to the hosted Greenstone Data Hub, which will send them on to RJO Hrvyst Hedge.
Turn On Each Web Service Message
Set up the Extract Filters
Filters can be designated by Commodity, by Name Id Type, and by Location. It is important to set up the Name Id Type filter so that only the Grain Customer information is sent to RJO Hrvyst Hedge.
Select the line for Name Id Types, and then check each Name Id Type that should be able to have contracts created for them in Hrvyst Hedge.
It is important that all growers that use MyGrower should be included in these Name Id Types as well.
Select Continue to save your choices, and then Save/Exit to save the Extract filter.
You can filter the Hedge Transactions that will be sent to Hrvyst Hedge by Location and by Commodity as well. If you don’t set up any filters, then transactions from all locations and all commodities will be sent to RJO Hrvyst Hedge.
Configure each message (Name Id Extract and Hedge Transaction Extract)
Select the Name ID Extract and the following screen for the Name Id Extract Configuration displays
For Name Id Extract:
Set the Last Date/Time (to start sending new changes as of that date/time).
Set the Status to Active (WARNING)
Any names that update since this date will be sent.. It is recommended to wait till you have confirmed integration success before setting the date back significantly.
First test should always be for today’s date and edit a name before sending all names.
Set the Integration Interval (For real-time sending of transactions, set the interval to blank minutes)
The only Name/Address information that will automatically be sent to Hrvyst Hedge will be Name Id, Name, Address Line 1, Address Line 2, City, State, Zip, Country, Phone Number, Active Status.
If you want the customer’s Email address to also be sent to Hrvyst Hedge, set Contact Detail = “Y”.
For all other detail options, leave them set to “N”.
Select OK to save your settings.
For Hedge Transaction Extract:
Set the Last Date/Time (to start sending new changes as of that date/time). Set the starting date/time to be right now. Do not backdate this date!!!!!!!!
Past transactions will fail when sending to Hrvyst
It will tie up processing until complete
It will slow processing for others
You can't stop it sending if you start (it will send them all)
Past transactions don’t add value
You just made the implementation take alot longer if sending past transactions to Hrvyst,
Set the Integration Interval (For real-time sending of transactions, set the interval to blank minutes)
Set the Status to Active
The Hedge Transactions that will be sent to Hrvyst Hedge will be Spot Contract applications, Cancel Contract transactions (under-fills), and over-filled contracts when they become priced.
Select OK to save your settings.
6. Monitor the RJO Hryvst Integration
Start/Stop the Service
Note: if any of the configuration options are changed (in the previous section), the service must be stopped and restarted in order for the configuration changes to take affect.
CFT ->Communications ->AGRIS Web Service->Process/Monitor Web Service Integration
Choose the Integration Number for RJO
The display above will show the status of the CFT Service and the Transaction Service (SOGE Agent).
When you click the start/stop button, it will add the integration to the service and start the integration.
The AGRIS User who clicks the Start button above will be the User ID associated with all transactions extracted from AGRIS and sent to RJO Hrvyst Hedge.
Make sure you have enabled both message types prior to starting the service.
Communication Inquiry
CFT ->Communications ->AGRIS Web Service->Communication Inquiry - > RJO
This inquiry allows you to monitor all transactions that have been received from Hrvyst Hedge and all transactions that have been sent to Hrvyst Hedge. The Status column will show “S”uccessful, “F”ailed, “R”ejected, ”W”aiting, or “U”nsuccessful.
These are the available filter parameters:
You can click on any row above to see the details shown below.
You can also click on the Details button above to see the actual xml messages that have been submitted in and out of the AGRIS Web Service, for complete visibility of all messages that have been logged.
Status: Successful
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=S
Successful transactions RECEIVED from Hrvyst Hedge will include new contracts and changes to contracts. The ID/Description field will indicate GRN Contract Post. The Document field will show the AGRIS Contract Number. The Misc 2 field will show the Hrvyst Hedge Contract Number. The Details button will show the contract information that was supplied from RJO.
Successful transactions SENT to Hrvyst Hedge will include new Name IDs and changes to existing Name/Address information. The ID/Description field will indicate NAM Name ID Extract. The Document field will show the AGRIS Name ID. The Details button will show the Name/Address information that was sent to the local SOGE Agent. Only a small subset of the Name/Address data elements will be sent on to RJO by the hosted Greenstone Data Hub.
Successful transactions SENT to Hrvyst Hedge will also include some hedge transactions that have been entered in AGRIS. These transactions will include Spot Contract applications, Pricing the overfill portion of a contract, or cancelling/under-filling a contract. The ID/Description field will indicate GRN Hedge Transaction Extract. The Document field will show the unique identification of the hedge transaction, including date/timestamp. The Details button will show the information that was sent.
Status: Rejected
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=R
Rejected transactions RECEIVED from Hrvyst Hedge will include contract transactions that have been rejected by the AGRIS web service post/import process. The details of the rejection messages will be available under the Details button. Rejected messages will be sent back to RJO Hrvyst Hedge. There will be no option within the CFT Inquiry to re-post the transaction. It is the responsibility of Hrvyst Hedge or the Greenstone Data Hub to re-post the transaction after the reasons for the rejection(s) have been addressed.
There will be no Rejected transactions logged in the CFT Inquiry for information SENT from AGRIS.
Status: Failed
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=F
Failed transactions RECEIVED from Hrvyst Hedge will include contract transactions that have encountered a system error within the AGRIS web service post/import process. The details of the error message will be available under the Details button. There is not currently any plan to provide an option within the CFT Inquiry to re-post the transaction after an error condition. It is the responsibility of the Greenstone Data Hub to re-post the transaction after the reasons for the error has been addressed.
Failed transactions that are marked as SEND include Name IDs or Hedge Transactions that encountered a system error within the AGRIS web service extract process. The details of the error message will be available under the Details button. When a Failed message occurs in the extracts, the system will automatically retry up to 100 times, based on the integration interval setting in the CFT Configuration. If/when the error condition has been resolved, the Last Date/Time for that message type can be manually set back in time, to tell the system to process/send that transaction again.
Status: Unsuccessful
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=U
Unsuccessful transactions RECEIVED from Hrvyst Hedge are similar to the Failed status. An Unsuccessful contract post would be a transaction that was received from Hrvyst Hedge, and then sent to the AGRIS Web Service post process, but a response was never received. Either a power outage or a termination of the system may result in an Unsuccessful status.
There will be no Unsuccessful transactions logged in the CFT Inquiry for information to be SENT from AGRIS.
Status: Waiting In Queue
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=W
There will be no Waiting transactions logged in the CFT Inquiry for information RECEIVED from RJO. Transactions that are received are posted immediately through the AGRIS Web Service.
Waiting transactions that are marked as SEND include Name IDs or Hedge Transactions that have been made in AGRIS and are in the queue, waiting to be sent to RJO via the local SOGE Agent and the hosted Greenstone Data Hub. In a normal situation, these entries will be in the queue for a very brief amount of time before they are marked as Successful. If the SOGE Agent or Data Hub are not available, then the Waiting transactions will remain in the queue. The Misc 1 field will show the response reason that the transaction was not able to be sent to the SOGE Agent. The AGRIS CFT Service will continue to attempt to send the transaction(s) until the Agent and Data Hub are available.
Communication Report
CFT → Communications → AGRIS Web Service → Communication Report → RJO
A report is also available to show all transactions received or sent, along with the status. These are the available filter parameters:
Here is a example of the Communication Report with all transactions Waiting to be SENT to RJO, The Status shows S for Send, and the Status of Waiting.
For contracts that have been received from Hrvyst Hedge, the AGRIS contract number will be displayed, as well as the Hrvyst Hedge contract number.
7. Position Balancing between the two systems
Hedge Transactions Received In AGRIS From RJO Hrvyst Hedge
GRN → Report Manager → Hedge Audit Reports → Print Standard Reports → Hedge Transactions Detail Report
Press the Sort/Print button. Sort by Commodity Code, Transaction Type. Filter by External System “R” to “R”. Choose “N” for Print Hedge Audit Detail.
You could also print the report to include all detail lines that make up the totals. You might want to also sort/subtotal by location within each commodity. A user-defined report could also be created to print this report daily and add/remove the desired columns on the report.
Hedge Transactions Sent From AGRIS To RJO Hrvyst Hedge
GRN → Report Manager → Hedge Audit Reports → Print Standard Reports → Hedge Transactions Detail Report
Press the Sort/Print button. Sort by Commodity Code, Transaction Type. Filter by External System blank to “A”. Transaction Types To Include: 7BCF. Choose “N” for Print Hedge Audit Detail.
You could also print the report to include all detail lines that make up the totals. You might want to also sort/subtotal by location within each commodity. A user-defined report could also be created to print this report daily and add/remove the desired columns on the report.
Hedge Transactions NOT Sent From AGRIS To RJO Hrvyst Hedge
GRN → Report Manager → Hedge Audit Reports → Print Standard Reports → Hedge Transactions Detail Report
Press the Sort/Print button. Sort by Commodity Code, Transaction Type. Filter External System by blank to “A”. Transaction Types To Include: 1234568ADEGHIJKLMN. Choose “N” for Print Hedge Audit Detail.
You could also print the report to include all detail lines that make up the totals. You might want to also sort/subtotal by location within each commodity. A user-defined report could also be created to print this report daily and add/remove the desired columns on the report.
8. Integrating Other Name and Commodity Contract Information
Because of the flexibility of the AGRIS Name and Commodity Contract module capabilities, you may want or require other AGRIS information to flow through the Hrvyst integration. You may modify Imports for this. Please see the Import Process - Overview, Steps, Layouts, Modifier instructions HERE.
The steps below may help you gain a better understanding of what other information you may wish to integrate.
Name/Address - Code Descriptions
Navigation: Packages > Name/Address System > Setup Information > Code Descriptions
Commodity - Contract Infromation
Navigation: Packages > Commodity Management System > Setup Information > Contract Information
Note that this is “Screen #1 of 6”. You may wish to include information from other screens.
Related Content
