Murex MLC Technicals

Murex MLC Technicals


MLC Murex Limits Controller


1)

Written entirely in Java

2)

Uses Remote Method Invocation (RMI)

3)

Talks to Mx Client (e.g. Currency+) via JNI (Java Native Interface)

4)

Facilitates the real
-
time checking of counterparty credit worthiness and can

stop
deals from being entered into the system.


Murex use clearcase software versioning tool. All software is on the host alfred, under
/vobs/java/murex/limits/

To go into clearcase use the syntax “ct setview <yourViewName>”
–

ct is an Murex
system alias
for cleartool


Parts of the MLC that I worked on during Feb to June 2000
-
05
-
30


Program/Class/Package

Description

MxMain.java

Called by Murex application via JNI, client code for
MLC, contains methods such as addDeal(), addDeals()
–

景f 湫n搠摥a汳Ⱐle浯
癥䑥a氨lⰠ牥浯癥mea汳l⤮

䵸䵡楮⁷i猠浯s楦楥搠瑯⁡cc潭o潤o瑥tca汬楮i⁴ e
䑂piC ⡄eve汯灭e湴⁂a湫⁓楮ia灯牥 i業楴猠s潮瑲潬oe爩



周q⁦潬汯睩湧⁩猠灡牴r⁴桥⁍iC⁈潭e扡獥Ⱐ瑨攠浡楮⁣潮晩ou牡瑩潮⁡湤⁶楥i楮i
c潭灯湥湴o⁴桥⁍iC



ui牢⹪r癡

C潮瑲潬o楮i⁧u
i component called “Limits Request
Browser”, part of MLC Homebase. Allows the viewing of
楮景i浡瑩潮⁳整⁵瀠m渠瑨攠niCⰠ,Kg⸠c潵湴敲灡牴楥sK

䅬汯睳⁴桥⁥x瑲tc瑩潮o⁴桡琠楮景 浡瑩潮⁴漠塍iⰠa湤n
o䑂䵓⁦潲浡琮

塃u瀮橡癡

Ca汬e搠dy⁘ir戮橡癡Ⱐ摩,灬py猠s c潵o
瑥tpa牴y⁶楥眠灡湥⁩渠
瑨攠t楮摯眠潦⁘i牢⹪a癡

塕瑩氮la癡

Ca汬e搠dy⁘ir戮橡癡Ⱐ摩,灬py猠癩e睳渠i業楴猠楮⁴桥
ui牢⁶楥眠灡neK

塒u獵汴⹪慶K

Ca汬e搠dy⁘䍴瀮橡癡Ⱐa湤⁘ 瑩氮la癡Ⱐ,a汬猠塍it物瑥爠瑯r
獥湤⁡汬⁴桥⁩湦漠楮⁴桥⁣u牲e湴⁶ne眠wa湥⁩湴漠o⁘Mi⁦楬 K


塍it物瑥爮橡va

Ca汬e搠dy⁘牥獵汴⹪慶KⰠ瑡步猠癩e眠楮w潲浡瑩潮⁡湤⁣牥ate猠
塍i 晩汥⁦ 潭⁩琮
t楬e⹸浬⁡湤⁦楬攮摴搩

塍iC潮瑡楮o爮橡癡

周楮歳q
–

ca汬e搠dy⁘ 䱗物瑥爬⁰潰猠異⁇sf⁤楡 潧⁢潸
瑯⁧e琠塍i 晩汥 浥⁴漠睲楴e⁴漮

塍ioec潲搮橡va

Ca汬e搠dy⁘ iCo
湴慩湥爬⁣a汬猠塍icie汤⁴漠潵瑰畴⁦楥汤l
摥瑡楬猠t漠塍ic楬e

塍ic楬e⹪慶K

t物瑥猠楮摩癩摵慬⁲ec潲摳⁴漠塍i⁦楬



mac歡ge畲ex⹬K浩瑳⹢t潷獥

mac歡ge⁴漠慬汯眠 a瑡⁩渠瑨攠tiC⁴漠扥⁶楥we搠dn搠
analysed. Didn’t do muck work on this but did copy
塍it物瑥爠an
搠塍iCo湴慩湥爠r牯洠瑨r猠灡ckage⁴漠
create XML file creator in package
murex.limits.lrb.upload
–

something like that anyway.



Package murex.limits.dbslc

The DBSLC system, see below.


MLC Components


MLC Homebase
–

main user interface to control and set
up Murex MLC

MLC Properties editor
–

GUI app to allow the modification of properties in
mlc.props, the main mlc configuration file

MLC Server
–

Server to handle all client requests




DBSLC
–

written by City Practitioners, bridge to transfer Murex mlc req
uests to
DBSLC and TRCS. (See below)


DBSLC murex.limits.dbslc


Development Bank Singapore (DBS) wanted to use their credit checking system
TRCS (?TRansaction Checking System?) DBS Wanted TRCS to check deals entered
into Murex and to use MLC as a fallback
checking system if the trade type was not
handled by TRCS. The architecture is as follows.

DBS has a modified version of MxMain that calls DBSLC before calling MLC. The
original version of MxMain has no knowledge of DBSLC. DBSLC will send the trade
to TRC
S if it is a handled trade type, if not a message is returned to MxMain and the
deal is passed to MLC for checking.

Deal data is sent to TRCS from DBSLC via IBM MQSeries. The format of the data
sent is determined on vector stored in the program that is bui
lt on startup by reading a
configuration file. There are two configuration files, the first determines the format of
the structure that is sent. The second determines the structure of the message that is
received.

The return message is determined by the co
rrelation id and message id. DBSLC will
wait until the correct message is on the Q before retrieving the data.

While the people from Singapore were at Murex, the DBSLC was extended so that
TRCS could send a status back to Mx via DBSLC to tell it that autho
risation was
required for a particular deal.




DBSLC also acts as a client for MLC for the following reason. In a non DBSLC
setup, MLC tells Murex which fields need exporting, i.e. which fields it needs. This
subset of the Murex field database that is ex
ported which each confirmation of a deal
is known as a tick. In the case of the DBSLC, the DBSLC has to connect and query
MLC to get the list of fields, and then add its own needed fields to the list before
returning that list to the Mx Client app.

Skill
Set for someone going to work on Murex MLC


Unix, Unix shell (Bash), Vi/Vim or Emacs, ‘find’ and ‘grep’ commands

NT4

Basic TCP/IP understanding, IP Addresses

Reflection X Server or equivalent, e.g. exceed

Clearcase versioning tool
–

ideal, but not needed

J
ava


Understanding of the use of packages and import statements


Understanding the use of the classpath argument to javac


Reasonable knowledge of the Java API, especially java.util.* and java.lang.*


Reasonable understanding of RMI (client, interface, ser
ver implementation,

server)

Knowledge of JNI (good to know but not needed)

Understanding of Java Swing, or good knowledge of Java AWT

IBM MQ Series
–

maybe needed if the person if supporting DBSLC

RDBMS
–

fundamental und
erstanding of Sybase, esp. login, s
elect and sp_help.

Basic understanding of Mark
-
up Languages especially XML

Knowledge of SAX and DOM (didn’t have time to do this myself so they still have a
requirement)