Sunteți pe pagina 1din 29

ELECTRONIC

TRADING 1.0

WHATS NEW
Contents
Chapter 1 Enhancements & Features ........................................................................... 4
1.1 Synchronous Hedging B2B in competition via FXall ...................................................4
1.1.1 Key Features ................................................................................................................................ 4

1.2 Orders Capture from FXall Venues ................................................................................5


1.2.1 Key Features ................................................................................................................................ 5

1.3 Position Totaliser ............................................................................................................5


1.3.1 Key Features ................................................................................................................................ 5

1.4 Multi Spot Rates..............................................................................................................6


1.4.1 Key Features ................................................................................................................................ 6

1.5 RET Reporting Server ....................................................................................................7


1.5.1 Key Features ................................................................................................................................ 7

1.6 Custom Field API ............................................................................................................7


1.6.1 Key Features ................................................................................................................................ 8

1.7 Crossing of Spot and Forward via Different Currencies .................................................8


1.8 Skew Enhancements ......................................................................................................9
1.9 Half Quarter Pip Rounding...........................................................................................9
1.10 Capture Trader................................................................................................................9
1.11 Quick User / Account Search..........................................................................................9
1.12 Automatic Volatility Switching .......................................................................................10
1.13 Split Value Dates (Islamic FX Trading). ........................................................................11
1.14 Support for a Back Office User type .............................................................................11
1.15 Variable decimal configuration per client group ............................................................12
1.16 Deal Modification ..........................................................................................................12
1.17 Phase1/Phase2 Dealer Intervention Routing ...............................................................13
1.18 Linking to External Content ...........................................................................................13
1.19 Money Market Rate Monitor .........................................................................................13
1.20 Good for Amounts on Forwards....................................................................................14
1.21 One Click Autotrader Logic ...........................................................................................14
1.22 TRM Model Ownership .................................................................................................15
1.23 Integration with Reuters Messaging .............................................................................15

Chapter 2 Branding & Usability ...................................................................................16


2.1 Administration Applet Improvements ............................................................................16
2.1.1 Key Features .............................................................................................................................. 17

2.2 Rates Panel ..................................................................................................................17


2.3 Deal Tickets ..................................................................................................................18
2.4 Active Deal Panel..........................................................................................................18
2.5 Deal Log ........................................................................................................................18
Chapter 3 Permissioning ..............................................................................................20
3.1 Parameters ...................................................................................................................20
3.2 Granular Admin Permissioning .....................................................................................20

Chapter 4 LOMS ............................................................................................................21


4.1 Orderwatch Functionality for Trader Applet ..................................................................21
4.2 Orderwatch Functionality for Client Applet ...................................................................21
4.3 Permissions ..................................................................................................................22
4.3.1 Configurable default permissions by user type ........................................................................... 22
4.3.2 Cancellation and Deactivation Filters ......................................................................................... 22

4.4 Routing ..........................................................................................................................22


4.5 Activation and Monitoring Controls ...............................................................................22
4.6 Credit Checking ............................................................................................................23
4.7 Branch Configuration ....................................................................................................23
4.8 Bundling similar orders .................................................................................................23
4.9 Archive search of Limit Orders .....................................................................................23
4.10 Editing active orders .....................................................................................................23
4.11 Reminder for deactivated order ....................................................................................23
4.12 Order Visibility ...............................................................................................................23

Chapter 5 Performance.................................................................................................24
5.1 Database Persister .......................................................................................................24
5.1.1 Key Features .............................................................................................................................. 24

5.2 LOMS Improvement ......................................................................................................24


5.2.1 Key Features .............................................................................................................................. 25

5.3 Filter Optimisation .........................................................................................................25


5.3.1 Key Features .............................................................................................................................. 25

5.4 Message Compression .................................................................................................25


5.4.1 Performance gains ..................................................................................................................... 25

Chapter 6 Supported Environments ............................................................................26


6.1 Software ........................................................................................................................26
6.1.1 Operating System ....................................................................................................................... 26
6.1.2 Oracle ......................................................................................................................................... 26
6.1.3 Windows ..................................................................................................................................... 27
6.1.4 Browsers .................................................................................................................................... 27
6.1.5 Sun Java 1.7 .............................................................................................................................. 27

6.2 Hardware ......................................................................................................................27

3|P a g e
Chapter 1 Enhancements & Features
1.1 Synchronous Hedging B2B in competition via FXall
Currently The ET system currently allows a bank to outsource liquidity to another, single bank, via an
adaptor connection. Banks are then able to outsource selected currency pairs to other banks, apply
their own margins and hence show a price to their own internal and external clients.
In this workflow a bank providing liquidity is the liquidity provider (LP) and the bank receiving the price
and trading off it is the relationship provider (RP).
The new Synchronous Hedging adaptor extends this outsourcing capability by allowing an ET bank to
back to back (B2B) RFQ trades with multiple LP banks via FXall using just one connection. This
permits a B2B in competition capability ensuring a best price is found from a series of LPs.
The initial phase implements the Synchronous Hedging for RFQ trade flow only via the FXall portal.

Deal types in scope for this feature are:

Spot
Outrights
Swaps (even and uneven)
NDFs

This enhancement will be available from ET 1.0 onwards and is a specific workflow solution that
allows synchronous hedging into FXall only.

1.1.1 Key Features

Permits liquidity sourcing for a desired currency or one underlying pair in a cross
RFQ tickets captured by ET can be back to backed into FXall
FXall Entities configuration provides the LP routing logic for your RFQ requests
Currency to account mappings are made in ET admin, permitting full control of your currency
quote destinations
Quotes can be either one-way or two-way
Best BID/ASK price is determined by ET from LP quotes
Indicative Fixing Date for NDF is supported
Tenor Mismatch handling is supported
Deal Reconciliation handling is supported
Event Logging is supported
Failover is supported*
Note:
We do not support dual outsourcing to both META v2 and Synchronous Hedging (one leg to
META v2 and the other to Synchronous Hedging).
We do not support META v2 and Synchronous hedging adapter running in the same RP
system.
In this release, it is required to disable/untick "Can Accept Client Prices" permission for
manual traders who will be doing outsourced trade with FXall.

4|P a g e
1.2 Orders Capture from FXall Venues
In ET 1.0 we have created an adaptor that allows limit order capture from FXall into ET. Orders
received by ET are then under the management of LOMSServer and are monitored and managed as
per existing ET Order Management workflows.
This change simply connects FXall to ET to receive inbound limit orders. Outbound messages are
then state changes, etc.

Order types supported in this first iteration are:

Take Profit (TP)


Stop Loss (SL)
Benchmark Fixing

1.2.1 Key Features


Limit orders can be created via FXall and ET Order Management will be able to receive and
monitor.
Orders received from FXall can be filled or partially filled as required.
Order modifications of FXall captured orders are supported by ET.
Order cancellation by the FXall client or ET trader is supported.
Order status queries from FXall are supported, for example for order status.
Order recovery.

1.3 Position Totaliser


The RET Trader applet has been enhanced to provide earlier visibility of new positions and not
intended to replace a risk management system. Connectivity issues to downstream systems can result
in a loss of position information or delays that can be costly to traders. RET has been enhanced to
support a position totaliser for completed deals in both the Active Deals Panel and Blotter panels.

1.3.1 Key Features


Positions will be calculated based on completed deals that are displayed in a deal blotter. For
example, if filters are applied then the position totals will be based only on the remaining deals
displayed in the blotter.
The position window will be available when a user toggles the F8 hot key.

5|P a g e
Position windows will be available for Active Deals and Deal Blotters, including floating
windows. In the case of the Active Deals panel, the data will be session based; disconnections
could result in the totals being cleared if deals are removed from the blotter.
Positions will be shown by currency pair for up to 10 currency pairs.
A trader can right click on the position window to setup the currency pairs to be displayed in
each blotter.
A trader can use control and click on selected deals to remove these from the Active Deals
Panel, the position total will be recalculated for remaining deals in display.
Position Totaliser is supported for all usertypes that have access to the Active Deals panel
and / or Deal Blotters e.g. Capture Traders, Traders, Proxy Client and Client usertypes.
Position Totaliser is supported for all FX deal types except Swap, Auxiliary and B2B deal
types.

1.4 Multi Spot Rates


The TRM rate monitor panel has been enhanced to support an additional multi spot view. The new
panel offers greater visibility of essential data to traders and now supports up to 20 currency pairs.
Panel loading times have also been improved as part of applet performance improvements.

1.4.1 Key Features


Shortcut keys are supported for key functions
The new rates panel can be embedded in the trader or floated and resizable
Columns are also user resizable
Up to 20 currency pairs can be supported in the new panel
User defined Skew settings, direct pip editing and tabbing
Expand mode for full view / Shrink View for key features only
Auto OFF / ON my currency pairs / setup only

6|P a g e
Fast keyboard skew control using arrow keys or direct entry for a selected row / currency pair
Performance
Improved panel loading in the trader applet
Subscription message size reduction ~300k
Market update messages reduced upto 92%
Legacy Rates Panel support maintained
Placeholder Help panel
An HTML help page as a placeholder panel when Multi SPOT is floating.
o Download Multi SPOT Help Resources from filebase.
o Create 'help' directory at the same path as your 'admin.html' or 'trader.html'.
o Extract the downloaded 'help.zip' and place all of its content into that 'help'
directory.
o You can use different directory name but you must set 'helpDirectory'
parameter in admin.html or trader.html to matches it.
Customizable by editing the HTML file.

1.5 RET Reporting Server


A new optional server component is now available that supports much improved data mining and
reporting from the RET database compared to the previous RET 3.3 reporting capability. The reporting
server uses Java Database Connectivity (JDBC) and CoreJavaLib (Proprietary Thomson Reuters
Library) as the underlying library. The data exchange between client api and server is via XML.

1.5.1 Key Features


Platform independent runs on Java1.6+
High performance query response compared to gid.logs
Easy to use reporting api, allows a bank to customize and extend reporting via custom SQL
called from a server configuration file.
Data is returned from queries in a number of pages of a predefined size. Cursors are used on
the database to limit the amount of data handled by the server at any one time.
If a connection is closed before a query completes it is abandoned and associated resources
are freed.
Password authentication utilizes 3DES encryption, user account is given low priority read-only
access.
The reporting server guards against SQL injection and unrestricted access to the database.

Note: This requires an additional api licence.

1.6 Custom Field API


RET already supports a limited amount of data in Taker custom fields. Further enhancements have
now been made to extend the flexibility and use of custom fields by providing more deal data pre trade
via the Custom Field API to an external application.
Example: Typical Workflow
Client user opens a deal ticket

7|P a g e
User populates, currency pair, amount, direction, deal type, and account
User could also populate some custom fields
User presses a pre check button in custom field area
The following data will be sent to the custom api and can be used by an external application:
o Username (customer name)
o User Full Name
o User Group Name
o Deal Direction
o Currency Pair
o Indicative Rate
o Deal Type (e.g. HRET, MRET, HREXT, MREXT, FORWARD)
o Instrument (e.g. FX.CROSS, MM.DEPOSIT)
o Execution Style: rfq
o Currency1 Amt
o Currency2 Amt
o Dealt Currency
o Dealt Amt
o Value Date
o Value Date type
o Basis
Custom API receives data from an external application in the bank e.g. fund sources such as
letters of credit available to the user and validates data input in custom fields
Custom API pushes updated data to the custom fields in the deal ticket
Client user can now submit the deal ticket
Trader can see custom field data and adjust it prior to sending a quote back
Client user can negotiate and complete deal.

1.6.1 Key Features


Custom Fields database schema has now been extended from 1,000 chars to 4,000 chars.
Custom Fields API will receive deal attributes above when a user submits them only.
Custom Fields API can only update/access custom fields in the deal ticket not standard fields.
Custom Fields will be supported for FX deal tickets (excluding limit orders) and MM deal
tickets.

1.7 Crossing of Spot and Forward via Different Currencies


Currently RET-AD only allows a bank to cross spot and forwards via the same currency for the same
currency pair. However, certain currency pairs, particularity Scandinavian currencies would benefit
from being able to cross the spot and forward components via different currencies. For example
crossing the spot part of a GBP.SEK forward trade via the EUR would take advantage of greater
liquidity in the EUR for spot.

8|P a g e
For this reason, the price spread in certain currencies quoted against the USD is generally wider than
in the forward market. A truer price is obtained by crossing spot via the EUR and the forwards via the
USD.
Additional columns have been added to the CCY Admin panel in RET-AD 3.5 to allow differing split
currencies for spot and forward:

1.8 Skew Enhancements


The skew factor can be set on a currency pair basis in the CCY Admin panel and is driven by the
currency pairs DPS setting:

Half Quarter Pip Rounding


Half Pip / Quarter Pip rounding can now be configured in CCY Admin of Admin Applet for SPOT

1.10 Capture Trader


Autotrader now has the permission to price a deal submitted by a capture trader
On submission of a deal by the Capture Trader that does not require adjustment a configured
Autotrader will pickup and complete the deal.
On submission of a deal by the Capture Trader that does require adjustment existing Capture
Trader workflow is seen and the deal is booked by the Capture Trader.

1.11 Quick User / Account Search


Quick user and account search has been enabled for Proxy Client.

9|P a g e
1.12 Automatic Volatility Switching
TRM can now be configured on a currency pair basis to automatically change the currency pair
Volatility setting by analyzing the incoming rate spread.
For example, GBP.USD has the following Spread Limits per Volatility range:

Spread: 4 pips
The spread is under 5 pips so the
Volatility rating for GBP.USD is
Normal.

Spread: 6 pips
The spread is over 5 pips so the
Volatility rating for GBP.USD is
automatically changed to Volatile.

Spread: 14 pips
The spread is over 10 pips so the
Volatility rating for GBP.USD is
automatically changed to Highly
Volatile.

If the incoming spread in this example changed to be over 15 pips, the rate would then staled.

10 | P a g e
1.13 Split Value Dates (Islamic FX Trading).
Up to and including RET 3.5 a single FX deal contains a single value date for settlement of the entire
deal, it is assumed that the base and terms currencies are settled upon the same date.
Islamic currencies such as the Saudi Riyal (SAR) follow the Islamic business calendar where the
weekend falls on Thursday and Friday. When trading against an Islamic Currency the system now
allows settlement on each currency in the pair according to the currencies specific holiday/weekend
rules. Thus a deal ticket will show a separate value date field for each currency.
The use of split value dates is supported for the following order types:
SPOT
TODAY
TOMORROW
FX Outright forward deals
Swap deals

1.14 Support for a Back Office User type


It is envisaged that a back office user would log into the Trader applet and would typically have full
access to the deal log / search functions and would be granted limited access to CCY admin or the
Autotrader panel. This user type would not have access to the active deal panel or any dealer
intervention functions but is able to view and print recreated deal tickets and use export functions from
the blotter:

11 | P a g e
1.15 Variable decimal configuration per client group
Currency pair decimal configuration in RET has been extended to allow spot and forward decimal
places to be set on a client group basis.
A new type of currency pair set contains DPS, Fwd Disp DPS and Fwd Scale DPS settings that can be
applied to any system currency pair and its inverse. This set is then applied to a client group and
overrides the CCY Admin panel settings for the pairs included in the set.
This functionality uses Decimal user currency sets, applied to a user group for configuration:

1.16 Deal Modification


A modified deal is essentially the cancellation of an existing deal and replacement with a new deal.
RET-AD already supports back-valued deal capture of FX & MM deals. The existing implementation
involves cancelling the initial deal then creating a new deal with the modified deal data. This can
introduce errors as the trader must carefully check and re-enter 90% of the data from the original deal
ticket on the new back-valued ticket.
Traders often need to make post-deal changes for genuine reasons. For example, the settlement
information may have changed or could be incorrect. In other cases, amounts or other details on the
trade could have been incorrectly entered by the client or proxy user e.g. rate, currency pair, account,
client name, value dates etc.
In order to change these details quickly and easily without further error the system has been enhanced
to support deal modifications.
Deal modifications in RET 3.5 are permission able by a Capture Trader.
Some banks will not allow a deal to be cancelled or modified after part of it has matured.
Some examples:
Near leg of a swap (today-fwd)
Early Take-up
Extensions
The existing permission control Allow Cancel Matured Trades should prevent deal modification of
invalid deals.
The system will also now support cancel or modification reasons, and additionally the view history will
record the action type by user, date and time.
Client and Proxy clients will have the ability to change certain information post deal but prior to
maturity.

12 | P a g e
1.17 Phase1/Phase2 Dealer Intervention Routing
In RET 3.5 it is now possible to define a secondary trader / group of traders to whom a deal can be
routed when the primary trader / group of traders have not picked up an initial deal request. After a
configurable amount of time (defined per transaction type); the deal will automatically be routed to the
secondary trader / group of traders. If after a configurable amount of time, the secondary trader has
not responded to the deal request, the end client user will be notified that there is no trader currently
available to respond to their request.
Changes to the system are:
New Secondary Pickup Filters button in the User groups panel of the admin applet. This
enables the bank to define the trader / group of traders to whom an RFQ should be routed
when a primary trader has not responded to an RFQ after x amount of time (where x is
configurable per transaction type).
Configurable timeout values for primary and secondary pick-up per transaction type.

1.18 Linking to External Content


The RET 3.5 client applet allows the hyper linking to external web content, for example Currency
News and Charts. This feature is enabled per client in the admin applet.

1.19 Money Market Rate Monitor


Currently Money Market rates are fed directly to the Echo MM price engine based on direct
subscriptions to an external feed. RET does not allow traders to adjust market rates for MM. Prices
are published to the client and trader applets as supplied by the source feed with no additional
bank/trader spreads applied.

13 | P a g e
This enhancement allows traders to quote prices independent of the predetermined source feed; this
will allow more accurate pricing and greater trader control in times of market volatility.
Enhancements to the improved Rate Monitor page include:
The ability to select and overwrite the value of an individual rate
A skew value box which displays a list of incremental values by which the rates can be
skewed
A new button to nullify the rates which when pressed, removes all displayed rates from the
trader and client applets and replaces them with N/A

1.20 Good for Amounts on Forwards


In RET 3.5, the good for amount which clients see on their Rates panel is to be applicable to the
following deal types: Spot, Forward, even and uneven swaps.
The client applet will be modified so that the user can always see the good for amount, whether
viewing rates from the Spot view or from the Tenors view.
The Global Panel will include the enhanced global permission:

1.21 One Click Autotrader Logic


The One-click logic has been enhanced with a new parameter enableTTLChecking controlling
whether TTL is checked when the Autotrader is deciding to accept the client rate.

14 | P a g e
1.22 TRM Model Ownership
Currently the system assumes that if traders have the relevant view / edit admin permissions, they are
able to act on all models.
In reality, traders typically own specific currency pairs, and at specific times of day only. At the end of
the day in one time zone, a trader will pass the book to another trader in another time zone. So for
example, during London hours, Trader 1 might own the GBP.USD model, and during NY hours,
Trader 2 then becomes the owner of that currency pair. By assigning an owner to each model, this
ensures tighter security in the system, so that only those traders, who are permission to use specific
models, can override rates etc.
In 3.5 a new setting is being introduced in the Global Panel called All models for all traders, the
default value for which will be checked. When checked, the system will carry on operating as at
present, i.e., it will presume that all traders are able to act on all models (providing they have the
relevant admin permissions assigned). When set to 0 (zero), the system will assume that no trader is
allowed to act on any model unless they are specifically permission to do so.

1.23 Integration with Reuters Messaging


In release 3.5 Reuters Messaging is being integrated into the Connections panel, to allow the
broadcast of messages to Messenger users.
In the Connections panel, when the administrator selects a user, it will be possible to either send a
message direct to the users applet or via Messenger. When clicking on the Messenger button, an
Messenger window will open and the administrator will be able to send an instant message to this user.

15 | P a g e
Chapter 2 Branding & Usability
The branding configuration in ET has been overhauled and simplified allowing much more control and
customization of the look & feel for the applet.
Default naming for all colours.txt and applet embedded images (images contained within the applet
resource zip file) have also been simplified and changed.

2.1 Administration Applet Improvements


The Administration applet has undergone a partial redesign in ET 1.0 to enable the option to reduce
panel and functionality access to non-System Administrators.
In ET 1.0, the existing left hand pane that contains the links to all the panels will be replaced with a
new horizontal toolbar at the top of the applet with a reduced set of panel links, some of which have
had other panels merged into them.
The following table details those changes:

New Admin Panel Link Previous Admin Panel Link (or Links if merged)
User Groups User Groups

Modifiers Modifiers

Filters Filters and Archive Filters

Accounts & Credit Limits Accounts and Credit Limits

CCY Admin Instruments, Prices, CCY Admin, Feed Sources and Feeds

Rate Monitor Rate Monitor

Sets User Sets, Group Sets, Currency Sets and User CCY Sets

Orders Order Routing, Slippage, Fixing and Deferred RFQ and Locations

Advanced Global, Timeouts, ACLs, Holidays

Autotrader Autotrader

System Usage Connections

Access to panels will be driven by an enhanced set of specific admin permissioned (located in the
User Groups Panel -> Admin Tab). The Settings and About links will be located to the right hand side
of this bar.

16 | P a g e
2.1.1 Key Features
2.1.1.1 New User Searching
The User Groups user searching functionality has been updated and given more prominence. Using
the available search field, an administrator enters the first few characters of a user or group (a
minimum of three though a * wildcard option is available (as shown below)) and the results are
automatically displayed below. Both users and group results are displayed.
The Ctrlkey switches the search from Fullnameto Usernameand vice versa.

2.2 Rates Panel


The following new features are available in ET:
Updated user interface with more configurable color options.
The Rates panel is to be enhanced to support a composite view which can include a
combination of up to ten MM and FX instruments, provided they are supported in the system.
The introduction of a charting display mode.
Configurable mini-tenor views.

A new toggle button will enable users to cycle between the All-In, Fwd Points, Mini-Tenors
and Graph view.

17 | P a g e
2.3 Deal Tickets
The client deal tickets have been redesigned in terms of look & feel. All areas of the deal ticket are
now configurable using parameters and colours.txt values

2.4 Active Deal Panel


The primary purposes of the Active Deal panel are as an alert to dealers on incoming quote requests
and to monitor deal status. The use of these deal panels has been fixed up to now, with limited column
settings and filtering restricted to a few pre-defined fields.
Users in the enhanced RET 3.5 system will be able to create up to five deal panels which can be
named and saved. Greater customization for filtering will be allowed if users wish to create separate
panels to view particular deals by currency pair or by client for example. Columns can be set for each
active deal panel and the sorting of these will remain active between logins.

2.5 Deal Log


Up to and including RET 3.4, there has been a single Deal Log which consisted of a session mode
displaying all deals since the user last connected; and an archive mode where a user can search for
deals via a range of search criteria.
In RET 3.5 the distinction between session and archive has been removed so there is just one blotter
type. The Auto Update functionality in the blotter can be activated to show trading during the session

18 | P a g e
19 | P a g e
Chapter 3 Permissioning
3.1 Parameters
Previous versions of RET many Client / Trader permissions were controlled by html parameters,
making it more of a global permission rather than per user based.
In RET 3.5 many html parameters have been moved to Admin Applet and some have been hardcoded
directly into the applet making Client & Trader permissions per user based and easily configurable.

3.2 Granular Admin Permissioning


RET-AD 3.5 will now allow the bank to
Define and control admin permissions easily for trader and administrator user types in the
RET system. The existing long list of options on the Admin tab will be replaced by a more
granular user-friendly mechanism.

Manage admin functions which are grouped and permissionable at a parent panel level. e.g.
allow full access to the modifiers panel but view- only access to all functions within the user
groups panel.
Control parent functions and Child functions which are each permissionable at the following
levels:
No access - Do not display the function
View only - Display the function / setting
Edit - Full access to the function / setting

20 | P a g e
Chapter 4 LOMS
4.1 Orderwatch Functionality for Trader Applet
OW functionality is now available from RET Trader Applet for a suitably permissioned trader user
(Capture Trader). Capture Trader can now do normal FX deals as well as place orders, monitor orders
and fill orders.

4.2 Orderwatch Functionality for Client Applet


OW functionality is now available from RET Client Applet:
Access to configurable filters
Access to strategy builder
Ability to enter order via quick ticket
Access to Quick filters
Access to New order ticket

21 | P a g e
4.3 Permissions
4.3.1 Configurable default permissions by user type
The implementation of granular administration permissions will allow maker banks to define Internal
Sales and View Only users in addition to Orderwatch Traders. The introduction of user types with
configurable default permissions gives control to the maker bank to build roles that suit their workflow
with minimal configuration when creating new users.

4.3.2 Cancellation and Deactivation Filters


The existing RET filter functionality has been extended to control the cancellation and deactivation of
orders. The following user types can be permissioned via Cancellation and Deactivation filter sets
applied at group level in the Administrator applet, User groups panel.
Client
Proxy Client (includes Taker APIs)
Internal Sales User

4.4 Routing
Five new routing criteria have been added to the Order Routing panel. All of these criteria can be used
to route to an auto accept user
Routing by Risk Amount
Routing by Time
Routing by User Set
Routing by Execution Style
Routing by Direction

4.5 Activation and Monitoring Controls


The activation and monitoring of orders can now be administrated via a new section of the LOMS tab
in the Administrator applet Global panel. Day and time constraints can be setup for the automatic
activation and monitoring of orders. The time zone of the specified daily control times can also be set.

22 | P a g e
4.6 Credit Checking
The GID.credit and LOMS servers have been upgraded to include Limit Order credit checking, thus
allowing a single credit check module for RFQ and Orders.
Order credit checking has additional nuances over standard RFQ credit checking, primarily as the
banks acceptance of an order usually indicates a contractual obligation to fill the order and the pre-
determined price.
Non-Utilization CC (GID.CREDIT) at Activation
Partially Filled Orders
Order Strategies
Reconciliation & Expiration/Cancellation

4.7 Branch Configuration


Order management workflow has been enhanced to support monitoring of orders against branches
other than FX.CROSS.

4.8 Bundling similar orders


A new functionality has been introduced that permits the grouping or Bundling of orders of the same
CCY pair within a filter by price. There is a further granular permission where Stop Loss and Take
Profit orders can be put into separate bundles.

4.9 Archive search of Limit Orders


It is now possible to retrieve historical orders via the Order Watch, LBN API. Permission for a user to
see the Archive Order Search function is controlled by the System Administrator via the RET Admin
Applet. A user extended the permission may run a search for previously executed orders that have
been archived by the system based on precise search criteria.

4.10 Editing active orders


This function is now permitted for trader users who have the responsibility of watching the orders in
the market.

4.11 Reminder for deactivated order


The action to reactivate or not reactivate an order is a decision made by the user performing the
activity a reminder to this fact has been added to remind the user when closing the order ticket of a
deactivated order.

4.12 Order Visibility


New system wide settings permit order visibility manipulation and for our existing clients preserve the
current workflow. The main aspect of visibility that can be switched relates specifically the Proxy
Client user type (or sales user).
The user type, on selecting a client they wish to enter orders on behalf of, can now either have a client
style by account listing of orders or a by selected user type of view.

23 | P a g e
Chapter 5 Performance
5.1 Database Persister
The Database Persister improves the speed of transferring captured trades to persistent storage in ET.
This replaces the series of database writes seen at various points in the trading workflow and
detaches the need for this persistence to have completed before the trade is marked as completed
and published by ET as such.
The implementation of the trade persistence layer therefore reduces write times across the system
substantially and removes the wide variability in write times. It:
Addresses delays in the user interface presenting positive trade done confirmations to clients
and traders.
Gives consistent performance during busy/volatile markets where it is common to see higher
system activity.
Allows for quick and accurate trading signals to be reported as we remove latency around
database persistence.
This asynchronous approach to database writing allows us to achieve 100% of database writes in less
than 10ms. The comparison between RET 3.5.2 and ET 1.0 can be shown as follows:

5.1.1 Key Features


Database write times 10 ms or less for all writes.
ET 1.0 with Persister gives faster notification and deal completion rates.

5.2 LOMS Improvement


As part of ongoing investment in ET the Order Management capability was identified as requiring
stability improvements and streamlining. As a path to further enhancements the key aim of this piece
of work was to bring system messaging in line with a new and more efficient model. This has also
enabled our development teams to provide Live-Live redundancy in ET LOMS 1.0.

24 | P a g e
5.2.1 Key Features
Improved, stricter messaging model.
Clearer failure reasons in Order Management progress window when a prohibited action is
made.
Efficient messaging yielding performance gains.
Full Live-Live resiliency implementation.
Improved archiving process.
Note:
This Live-Live resiliency is not for POMS. It only supports 2 LOMSServer instances with the
same resource name.
GID.orders is enhanced to always prevent multiple login for LomsProxy regardless of
PreventMultipleLogins value.

5.3 Filter Optimisation


ET checks each new incoming deal request against pickup filters to determine where the deal needs
to go for pricing, etc.
However, each time this is done the filter XML is parsed. This is a relatively slow operation, especially
where there are a lot of trader users with many a filter conditions.
Therefore this performance improvement accelerates this process and changes the way in which we
evaluate the filter XML.

5.3.1 Key Features


Prevents parsing of filter XML and rules (i.e. logical operations) on each and every evaluation.
Reduces server processing times, improves pricing speed.
44% reduction in deal submit processing time.
55% reduction in first trade update response time when a streaming price is requested.

5.4 Message Compression


This enhancement reduces bandwidth usage and reduces transmission time latency for large
messages. This has been achieved by redesign of message formats between the ET servers and also
between servers and remote APIs/applets.

5.4.1 Performance gains


Based on a 32 kbps bandwidth the XML message receive latency is reduced from 160.66 ms
to 95 ms a reduction of 41%.
The total size of all system update messages is reduced from 829 Mb to 526 Mb by, a 37%
reduction.

25 | P a g e
Chapter 6 Supported Environments
6.1 Software
6.1.1 Operating System
The supported Operating System for running the SCS and resource servers for the RET platform is
Solaris 10.
The SCS and SCS Relay are the only software components on the server side for which Microsoft
(MS) Windows may be used as the OS software.
Supported Windows OS: Win XP, Win 2K3 Server, Win 2K8 Server & Win 7

Solaris Version Comments


The following patches must be applied:
119059-14
10 120068-02
118666-16
118667-16

6.1.2 Oracle
Oracle is the database software used on the server side. The database must be an Oracle Server
Enterprise Edition or Standard Edition (64 bit) running on Solaris
RET 3.5.2 is officially qualified with Oracle 11.2.0.3 (Standard & Enterprise edition)
Qualified
(Test cycle executed with
Oracle Version this version) Supported
9.x No No
Yes, only with these patches:
Client 7143299 and 6750296
10.2.0.4 Standard Edition Yes
Server 7452373, 8576156,
7143299 and 6750296
Yes, only with these patches:
Client 7143299 and 6750296
10.2.0.4 Enterprise Edition Yes, including RAC. Server 7452373, 8576156,
7143299 and 6750296

Yes, only with these patches:


Client 7143299 and 6750296
10.2.0.5 Standard Edition Yes
Server 7452373, 8576156,
7143299 and 6750296
Yes, only with these patches:
Client 7143299 and 6750296
10.2.0.5 Enterprise Edition Yes, including RAC.
Server 7452373, 8576156,
7143299 and 6750296

11.2.0.3 Standard Edition Yes Yes

26 | P a g e
11.2.0.3 Enterprise Edition Yes Yes

11.2.0.4 Standard Edition Yes Yes

11.2.0.4 Enterprise Edition Yes Yes

6.1.3 Windows
RET 3.5.2 Applets have been tested on Windows XP SP1+, Windows 7 SP1+ (32bit & 64bit) &
Windows 8 (32bit & 64bit).

6.1.4 Browsers
RET 3.5.2 Applets supports IE 7, IE8, IE9, IE10, IE11 and Google Chrome & Mozilla Firefox.

6.1.5 Sun Java 1.7


RET 3.5.2 Client applets are officially qualified and tested with the latest Java 1.7.x version. In addition,
given multiple clients reporting support challenges due to Java auto updating on the client side
resulting in users being totally unable to trade

6.2 Hardware
RET 3.5 has been qualified and is recommended on the following HP DL 300 series Intel based
servers
CPU Internal disk space for
speed CPU / Memory O.S./System/Application
Purpose Model (GHz) Cores (GB) software (GB) Other
Intel E5-
RET 2690
Application HP DL 2
processes 360p Processors 2x 300GB
& Adaptors Gen8 2.9GHz 8 Core 128GB 2x900GB
Oracle
certified
Intel Xeon 2 x Dual
5600 Port
Series 8Gbps
2 Fibre
HP DL 380 Processors 2x 300GB Channel
Oracle Gen7 2.93GHz 6 Core 96GB 2x900GB HBAs
Intel E5-
2690
HP DL 2
SCS & 360p Processors 2x 300GB
Web server Gen8 2.9GHz 8 Core 128GB 2x900GB

27 | P a g e
Thomson Reuters also supports RET on non HP hardware, please contact your hardware vendor for
details of equivalent specification Intel machines based on our qualified servers listed above.
Thomson Reuters also supports RET on Sun M4000 or M5000 (UltraSPARC IV) series of servers.
Please note, SPARC support is likely to be removed in the future as this is no longer our preferred
platform.

28 | P a g e
2012 Thomson Reuters. All rights reserved. For more information
Republication or redistribution of Thomson Reuters
content, including by framing or similar means, is Send us a sales enquiry at
prohibited without the prior written consent of reuters.com/salesenquiry
Thomson Reuters. 'Thomson Reuters' and the
Read more about our products at
Thomson Reuters logo are registered trademarks
reuters.com/productinfo
and trademarks of Thomson Reuters and its
affiliated companies. Find out how to contact your local office
reuters.com/contacts

Document Version 1.01

S-ar putea să vă placă și