Access Trading System Manual For Computer Programmer's

• Access Client (ets.exe)
• Terminate
• Back Office Interface Client (bointerface.exe)
• Price Reporting System Interface Client (prsinterface.exe)
• Corporate Explorer
• PRSArchiView
• C21 Emulation
• PRS Emulation(msggen.exe)
• Test Harness
• Library Code
• Deployment

Entry Point: Access Client (ets.exe)

• Extention Modelling
  
• Preferences and Profiles
  
• ets.cpp(CETSApp)
  
• doc.cpp(CPersistDoc)
  
• mainfrm.cpp(CMainFrame)
  
• childfrm.cpp(CChildFrame)
  
• Views

Terminate

This Application Is A Dialog That Displays After The Client Has Been Terminated
This can either be by a forced logoff from the Servers or the fact that a Server crashed

Back Office Interface Client (bointerface.exe)

This application keeps a record log of the SQL it sends in the morning to the database via ODBC
These data feeds from C21 are to ensure that the latest months can be picked up by Corporate Explorer
when it performs the day translation.

The afternoon task is to read trade records from the Access Trading System
When typically, at 05:00 am the C21 reader connects to the BOInterface machine
a log of the socket connectivity is also kept by the application.

Price Reporting System Interface Client (prsinterface.exe)

This Access Application connects to the trading system for the purposes of collecting current market prices
The Price Reporting System accepts a connection from this Interface
Should the connection drop then the Interface attempts to reconnect
If the PRSInterface fails it will attempt to collect the prices for the period it failed
and pass these onto the PRS.

Corporate Explorer

PRSArchiView

This Application is a file reader for the serialised output produced by PRSInterface
It is an internal developers tool

C21 Emulation

The Back Office C21 or Trade Management System receives trades from Nymex Access via socket connections
This internal developers tool fakes up that relationship

PRS Emulation(msggen.exe)

The Price Reporting System collects information from Nymex Access and distributes to the Price Vendors
This internal developers tool fakes up that relationship

Test Harness

This application is for use by developers
Its purpose is to analyse messages between client and server
It can also be used to playback production data
Unlike the main client executables ets.exe bointerface.exe and prsinterface.exe Test Harness does not have the Broker Layer baked into operation, it dynamically interprets messages.
Historically this meant that the data_desc (broker idl file) was noted as available via the Registry
HKEY_CURRENT_USER/SOFTWARE/IPE/TESTHARNESS/1.0
Please ensure that this path actually exists with a valid data_desc file being present


If you are running (local) NT Servers it is quite a performance to ensure that Test Harness runs.

Start up Test Harness with your normal HostName[MONTEGODATA] and PortNumber[5961] Registry Settings in place.

Test Harness Connection Monitor will present the Connect: Host, Port and System Dialog
Edit System to [s] but the Connect Port should be left as [5961]

In the Accept part of the dialog set System to [c] and use the Port [5955] if that is not the default.

Open up Registry HKEY_LOCAL_MACHINE/SOFTWARE/NYMEX/ACCESS/2.0
Change the PortNumber from [5961] to [5955] or rather the Accept Port selected in TestHarness.

It is now possible to set up Clients that are delivered via Test Harness

Library Code

Deployment

It is the general practice that the source code is extracted from Microsoft Visual Source Safe to the directory c:\ets on a build machine.
There are two major working batch files

The batch file shipout.bat is actually parameter driven.

The c means clear and deletes all release and debug objects, libraries, binaries and broker source files
The r means release version
The d means debug version
The f means to remove all the objects for the version being built.
To make this easier, there is a batch file wrapped around shipout.bat called build.bat
Typically the contents of build.bat would be:
call shipout.bat c
call shipout.bat r f
call shipout.bat d
The file made.bat is the core distribution file from the developers point of view.
This has become disjointed since the introduction of Citrix.
The internal clients BOInterface and PRSInterface are installed via the install shield created distribution package
The Access Trading Client is installed by the Citrix Managers and done so via a drag and drop means
The reasoning was the Citrix Managers did not want any risk of unwanted DLL files appearing on the Windows 2000 Servers
Regardless all these files are pulled from the Access Network Drive under "Nymex Inbox" on a version basis.

The detailed how to create servers and clients can be found in the build document.