...

...

Integration Overview

Transactions to be sent from RJO Hrvyst Hedge to AGRIS

1. New contracts (Purchase or Sales)

   1. Basis

   2. Hedge-To-Arrive

   3. Flat Price

   4. AutoHedge Contracts

2. Changes to a contract (or a portion of a contract)

   1. Edit contract details

   2. Price a contract (including ability to price a portion of a delivery/price schedule)

   3. Roll a contract

3. 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

1. 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

1. Name/Address Changes (When changes are made to Name, Address, Phone, Email, Active Status)

2. Hedge Transactions (Spot Contracts, Cancel Contracts, Contract Overfills)

3. 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.

...

• 1. Hrvyst Hedge Extended Option

• 2. Document Tracking

• 3. System Security/Users

• 4. Commodity setup

• 5. CFT Integration Service Setup

• 56. CFT RJO Integration Configuration6. Monitor the RJO Hryvst Integration

• 7. Position Balancing between the two systemsIntegrating Other Name and Commodity Contract Information

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

• Setup Users on Provider Screen

...

A. AGRIS setup/configuration steps

...

5. CFT Integration Service Setup

Explaining the Service

1. 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.

2. Within this Service we can support multiple integrations which can all be configured differently. 

   1. We have the concept of starting an individual integration process (which is a thread/task within the Windows Service)

   2. 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):

...

• The CFT integration MUST be configured in the same dataset as the live commodity system.

• You can give any description for the Integration Name (Use the integration name RJO Hrvyst Hedge for example).The Dataset the description as the Integration Name

• 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

    • http://localhost:8080/AgrisPSQL/RESTCommandWebService/ExecuteServerCommand/AgentProcessor/AgrisMessage?TransactionType=0

    • 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.

...

• 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

...

7. 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.

8. Import modify the configuration.

Set the import modify feature to support unique info from the hrvyst system.

...

*Note all configurations below will drive the same value in AGRIS.. if a specific value is needed for some fields on a contract vs a different value for other contracts when interfacing with RJO hrvyst… contact your RJO representative for additional instruction.

1. Navigate to Maintenance>Import Maintenace>Insert, to add new import

   1. Name the import RJO Hrvyst Hedge (note as discussed in step 6 it must be RJO Hrvyst Hedge)

2. Contract Header details

   1. Contract Signed status - Force to “N”

   2. Transporation mode - Set to “T” if this is the expected contract type for all contracts.

3. Contract Schedule details - custom field configuration.

   1. Determine what transaction code should be used to identify that the contract originated in RJO Hrvyst

   2. Configure any remaining schedule configuration for “ALL” contract schedule required fields that would be the same for all contracts.

4. Contract schedule details - standard field configuration

   1. Board name

   2. Signed

   3. Transport mode

5. Import Maintenance screen Import Path & File Names should be left as defaulted in.

...

9. Import the reports/widgets to manage the Hrvyst Interface

Import and configure the widget to manage the status from AGRIS, GDH and RJO hrvyst system.

1. Download the attached zip

   1. Send the following to the customer

1. Extract to the AGRIS/Support/CFT folder on the AGRIS database server.

2. Import using the Transfer reports and forms

   1. Image Added
   2. Image Added
   3. Image Added

3. Enable the reports for the user who is managing as a Dashboard widget.

   1. Image Added
   2. Image Added

Click https://culturatech.atlassian.net/wiki/x/NwBaY for instructions on

• How to Monitor the Hryvst Integration

• How to Balance the Position between AGRIS and Hrvyst

Related Content

...