...
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 AGRIS 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”).
...
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 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 AGRIS Greenstone Data Hub, which will send them on to RJO Hrvyst Hedge.
...
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 AGRIS 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.
...
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 AGRIS Greenstone Data Hub to re-post the transaction after the reasons for the rejection(s) have been addressed.
...
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 AGRIS Greenstone Data Hub to re-post the transaction after the reasons for the error has been addressed.
...
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 AGRIS 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.
...