OnixS Java CME iLink 2 Audit Trail Generator — Programmer's Guide

Version 3.3.0

Introduction

Onix Solutions Java CME iLink 2 Audit Trail Generator is a Java library that provides a functionality to generate a complete and accurate record of all activity through the connection, and account for every electronic communication by the order routing or front-end system from the time such order routing or front-end system receives or generates an electronic communication until it is communicated to CME Globex.

Below are the key features of the OnixS CME iLink 2 Audit Trail Generator:

High-level and easy-to-use API that enables quick integration of the OnixS CME iLink 2 Audit Trail Generator without deep involvement in the specific requirements.
Getting Started sample designed to get up and running rapidly.
Light hardware and deployment requirements.
Complies with CME Globex Front-End Audit Trail Requirements.

Note: It's highly recommended to read the "Minimum Acceptable Audit Trail Elements - Data Definitions and Validation Rules" before reading this Guide to get familiar with core aspects of CME Globex Front-End Audit Trail Requirements. It's also highly recommended to review the source code of the sample project which comes as part of library's distributive package alongside reading this Guide.

System Requirements

JDK 1.7 (or higher).

Getting Started

This section guides through the most significant parts of the Audit Trail Generator architecture.

Prerequisites

The OnixS CME iLink 2 Audit Trail Generator library depends on the OnixS Java FIX Engine library.

All classes of the OnixS CME iLink 2 Audit Trail Generator belongs to the biz.onixs.cme.audit.trail.spreadsheet.generator packet.

How to use generator?

The typical way of using the OnixS CME iLink 2 Audit Trail Generator is:

Create an instance of the biz.onixs.fix.engine.EngineSettings class to adjust FIX Engine settings.
Set a path to a FIX Dictionary file using biz.onixs.fix.engine.EngineSettings.setDialects method. Our standard name for CME Trading dictionary file is CmeTradingFixDialect.xml.
Initialize FIX Engine using biz.onixs.fix.engine.Engine.init method.
Create an instance of the biz.onixs.cme.audit.trail.spreadsheet.generator.SpreadsheetGenerator class.
Call biz.onixs.cme.audit.trail.spreadsheet.generator.SpreadsheetGenerator.generate method to generate a report.

Example

The following Java code snippet illustrates basic usage of the OnixS CME iLink 2 Audit Trail Generator.

EngineSettings settings = new EngineSettings(); settings.setDialects("config/CmeTradingFixDialect.xml"); Engine.init(settings); final SpreadsheetGenerator generator = new SpreadsheetGenerator("Sender-CME-FIX_4_2_2016111808291264111111.summary", ';'); generator.generate();

Frequently Asked Questions

Do you have a specification for the .summary file?

The format of the FIX Engine .summary file is very simple: <IN|OUT> <timestamp> <raw FIX message>.

Support

OnixS provides online support resources to the customers and development partners.

Requesting Support Using JIRA

OnixS Support for the product is based on facilities of JIRA issue logging and tracking system. Registered customers may directly push support requests and get timely status updates and replies on the posted issues. By using issue tracking system requests are delivered to development Q/A teams without any delays caused by dispatching support mail, therefore OnixS Support Team highly recommends to use JIRA instead of mail.

Support Requests via E-Mail

For those who can't take advantage of using the OnixS issue tracking system, support requests can be sent via email at support@onixs.biz.