Orc technical training

Orc Technical Training

March 2008

Agenda – Day 1

9 - 9.15 Start @ Orc, introductions 13.00 – 14.00 Market’s in detail (Components connect and configure)
LIFFE (Lina)
9.15 – 10.30 Orc Overview Presentation CME/CBOT (Tom)
Orc System architecture overview EUREX (Howard)
Orc System server side processes
14.00 – 14.30 Preparation for Practical & Questions
10.30 – 10.45 Break for Coffee
14.30 – 18.00 Practical
10.45 – 12.00 Orc Overview Presentation Create a new environment
Location of different components on server file systems Create a market Link
Orc System management LIFFE to test market
CME market process
12.00 – 12.30 Break for Lunch EUREX registered from remote server
Add users for each market
Set-up Orc client’s
Logon to clients and markets

©2007 Orc Software AB. All Rights Reserved. Proprietary and Confidential.

Agenda – Day 2

9 - 9.15 – Day 1 Recap

9.15 – 9.45 – Orc Front End (David)
Still to be decided (common issues)

9.45 – 10.30 – Basic trouble shooting Client/Server

10.30 – 10.45 Break for Coffee

10.45 – 13.00 Practical
Upgrading ORC
Debug, Logs and OS

13.30 Wrap-up and Questions


Objectives

Gain high level overview of the complete system


Part 1 – START

Orc System architecture overview

Orc System Arch - High Level Orc Components

Clients Servers Core Applications
IBM - IDS
MS Windows SUN Microsystems Informix Dynamic Server
SPARC Version 9
Apple MAC Solaris 8,9,10 Version 10

Linux
Disk Management
Intel/AMD X86
Veritas Volume Manager
RedHat


Orc System Arch - System Design Concepts

This will be dependant upon the requirements of the business and will
typically include some of the following :

•How many and which markets are required to be traded on.
How many products.
Fault tolerance
Security
Cost of initial outlay
Client/Server support

* Should always try and seek the fastest system for processing small
amounts of data – high throughput transactional system.


Orc System Arch - Server System Considerations

•Memory
•How many server processes will be running on the server ?
e.g 32 bit CME can consume 4Gb at max so four of these processes is 16Gb

•Storage - Disks
•Fast and mirrored. Database must be placed on rawdevice.
•Preferable on many striped and mirrored disks.
•Recommended software for striping and mirroring is Veritas Volume Manager.
•Hardware arrays can be nowadays provide very fast and scalable solutions for
datamanagement.
•RAID 5 is not a good solution!

•CPU
•The more the better .
•Informix needs to be configured for multiple CPU’s to maximise performance.


Orc System Arch – Linux Server example

•Model: HP ProLiant DL385 SAS Server
•CPU: 2 x AMD Opteron Model 275 2.2GHz/1MB dual-core (or faster)
•RAM: 4Gb PC3200 RAM (2x2GB)
•HD: 8 x 72Gb 10,000 RPM 2.5" SAS disks (Hardware RAID, 2 x boot RAID 1, 4 x
RAID 0+1 for db, 2 hot spares)
•Hot Plug Redundant Power Supply Module (IEC)
•HP Redundant Fan Option Kit (3 fans)
•Slimline DVD-ROM
•Network: Embedded dual-port gigabit
•Integrated Lights-Out Advanced Pack for remote control
•Operating System: RHEL 4 ES Standard edition 3 yr RHN subscription 9x5 support
(ES cannot be purchased in the Premium edition 24x7 support)
•HP Hardware support: 24-Hour x 7-Day, 4-Hour Response On-Site Coverage - 3 yr


Orc System Arch - Client System Considerations

•OS MS Windows or MAC
•Initial cost,
•MAC slightly higher but you get a marginally better performance.
•On-going support costs
•Depends on current staff and market trends. MAC’s generally tend to be
slightly higher in cost because there is less knowledge in market.

•Hardware considerations
•Lots of memory
•Many CPU’s
•Fast graphics card with multiple outputs for screens
•High resolution large monitors


Orc System Arch - Client Example
• Orc Client: entry-level configuration
Model: Any high-level workstation class PC featuring one (1) dual-core x86 CPU
CPU: 1 x 2.6 (or faster) GHz Dual-Core AMD Opteron or Intel Xeon
RAM: 2 GB (or more) DDR2 400 MHz or faster
Hard Disk: 1 x 120 GB (or bigger) – note that disk capacity is not fundamental
Graphics: single or multi-headed graphics card interface with 256 MB RAM, 400 MHz RAMDAC or better specs.
Other: CD/DVD drive, 100 Mbit Ethernet network interface, keyboard, mouse etc.
Operating System: Windows XP Professional SP2 or higher (recommended) or Windows 2000 Professional SP4 or higher.

•Orc Client: high-end configuration
Model: Any high-level workstation class PC featuring two (2) dual-core x86 CPUs
CPU: 2 x 2.8 (or faster) GHz Dual-Core AMD Opteron or Intel Xeon
RAM: 4 GB (or more) DDR2 400 MHz or faster
Hard Disk: 1 x 120 GB (or bigger) – note that disk capacity is not fundamental
Graphics: single or multi-headed graphics card interface with 256 MB RAM, 400 MHz RAMDAC or better specs.
Other: CD/DVD drive, 100 Mbit Ethernet network interface, keyboard, mouse etc.
Windows XP Professional SP2 or higher (recommended) or Windows 2000 Professional SP4 or higher.


Orc System Arch – Why IDS

Has for a long time been one of the fastest database engines on the market.

Is still a fast solution.

Easy and relatively little maintenance.

Informix works best with rawdevices, for both performance and security
reasons.

With Solaris 8 Orc supports IDS 9.3 and above .


Part 1 - END

Orc System architecture overview

Part 2 - START

Orc System Server Processes

Orc System Server Procs – PM
Orc Core Server Processes Other Server Processes Core Business Logic

PM FP STANDINGD

MARKETS
TRADINGD
STORAGE
DATAD
OP MARKETD
CDS

EM PLAYBACKD THEOD


Orc System Server Procs – Core Processes
Port Mapper Environment Storage Manager Client Data Server
Runs as PMD The Manager Runs as STORAGED daemon. Runs as CDSD Client
port-mapper daemon. Runs as EMD The data server daemon.
manager daemon. Storage daemon. Maintains a
Stores information database “storage” containing Holds all company critical
about the port usage user and environment settings. data, such as contracts,
of other processes. First level security for user/client parameters, portfolios
Keeps track of other
Only one pmd runs on connections and transactions.
server processes on
a server. local host and other Audit logging
Other processes remote hosts. Audit - this table contains ** DO NOT LOSE
maintain Users/clients connect to information on inserted, updated
communication with the EM to start the login and deleted data and information
this daemon by re- process. on the user that has performed
registering every 30 Dynamic/Static the changes.
seconds. registration for other Orc Clients - this table contains
Processes information on logins, logouts.


Orc System Server Procs – Other Processes
Markets FP OP Others

There are over 60 Runs as FPD Runs as OPD daemon. See server admin guide
markets available for Seperates market data Orc Protocol server, used for
connection to Orc. from quotes and orders inserting/extracting data to/from
Each process will being communicaed the Orc Software server system,
have a local database with the exchanges. and for entering orders.
that will store the
market configuration
and market data
downloaded from the
exchange.


Orc System Server Procs – CBL
tradingd marketdataD standingdataD theoreticalD

Handles orders, Handles market data, Handles automation of standing Handles theoretical
trades, and quotes for depth, and other data. That is, automatic calculations and
connected Orc messages (such as download, deletion/creation of theoretical price feeds for
Protocol servers. news) for connected dynamic combinations, and so connected Orc Protocol
Orc Protocol servers. on. Beneficial for both regular servers.
connected Orc clients as well as
connected Orc Protocol servers.


Orc System Server Designs – Single Server

pm

em

storage

cds
api

saxess


Orc System Server Designs – Multiple Env’s

pm pm
pm
em em
eurexv
storage storage

cds cds

op saxess

om


Orc System Server Designs – Starting Up
Client starts and sends broadcast to
local LAN.

Clients Searches for a PM process listening
on a specified port
Portmapper picks up requests and
advises client of the EM’s local
MS Windows Clients connect to an EM which
then validates user and keycode in
pmd the storage DB.
Apple MAC
emd Market access and limits checked
Client now logged on and the
storage directories are checked for
storage templates
EM logs user into CDS

cds Client markets links become
available and client can connect

mc


Part 2 - END

Orc System Server Processes

Break for coffee

Part 3 - START

Orc System Server File Locations

Orc Server File Systems

Configuration
/etc/orc
information, unique
for each
installation. Stop
and startscripts.
Should be backed
Path of choice up. releasetree,
Orc
includes server &
client software.
Only volatile data
are the server
logfiles
/usr/informix Main release
directory for
©2007 Orc Software AB. All Rights Reserved. Proprietary and Confidential. informix

Orc Server File Systems - /etc/orc

• boot_system - Starts all processes specified in orc.conf if all assumptions are fulfilled
• Orc.conf - Configuration file for the serverprocesses on the local host.
• Orcadmin - Orcserver administration script
• shutdown_system - Stops all serverprocesses specified in orc.conf
• start_process - Takes a serverid ( processname) as parameter and starts the
process.
• stop_process - Takes a serverid ( processname) as parameter and stops the process.
• Storage – Directory structure where storage deamon saves the users desks, templates,
columns etc.


Orc Server File Systems – orc.conf
orc.conf includes one line for each serverprocess to be started and environment varibles.
The variable RELEASE points to the actual releasepath.
The ”processlines” must start with PROC:
All fields are separated by a colon. The entries are:
Serverid: Must be unique, this is the processname
Starttime: Time for automaticstartup
Stoptime: Time for automatic shutdown
Days: Days of week when the process should run
Servertype: The type of orcserver deamon f.ex. cds, om
Release: Version of the Orc system
Executable: The executable in /usr/rat/bin/ that shoud be run
Dbname: The name of the database.
Fancyname: Name to display in Sauron if not serverid
Logname: Name of logfile if not default (/usr/rat/log/binary.log)
Extraswitches: Parameters that you can start the serverdeamon with.
Metadata:


Orc Server File Systems – ”release_dir/etc”

• Orc_dbupdate
Takes one parameter, the unique process name for the process you wish to upgrade. This does the
same as the “upgrade” button in Sauron, showing you all the output of the upgrade as it progresses.
• Orc_dbupdate2
Takes two parameters: the name of the Informix database you wish to upgrade and the “type” of the
database. This script can be useful if you want to perform an upgrade for a database which does not
have a process configured in orc.conf. However, it is not recommended to do this, because the
process should always be configured in orc.conf.
• orc_sync_crontab
If you have manually made any changes to the orc.conf file on the server, this file will adjust the
server's crontab entries to match the current contents of the orc.conf file.
• orc_dbcreate
This script requires a server name (i.e. cds, seats etc) as parameter, and creates the database for
the corresponding server process. Optional parameters are: [-l] for buffered logging and [-n
namespace] to specify the database namespace
• orc_dbcreate2
This script requires two parameters: the name of an informix database and the server name (i.e.
cds, liffe etc). This allows you to create databases that are not referenced in /etc/orc/ orc.conf.
Optional parameters are: [-l] for buffered logging and [-n namespace] to specify the database
namespace.]

Orc Server File Systems – ”release_dir/etc”
• ctrl-scripts, omctrl,saxessctrl etc.
Pearlscript for configuring market connection databases. If no parameter is given the default name for
the database is used. If the database is named differently use –d dbname. All ctrlscript will show the
current configuration if you type Info and will give you help when typing a ?.
• pminfo
Shows the different Orc processes running on this machine and their ports.
• cdsutil
This utility allows you to mark some portfolios as restricted for a particular user.
• keycode_interpreter
To be able to verify the correctness of a keycode before taking the Orc application into production
you can apply the keycode interpreter.
• orcadmin
Updates the storage database. (Command line utility corresponding to Environment Manager)
run_as_orc
creates the orc user,changes ownership of orc-directories and databases.
• orcinfo
Gives brief information, regarding Orc version, server hardware and last few lines from informix log


Orc Server File Systems – Daily Checks
• Check status of disks and volumes
vxprint ( or equivalent)
• Check free space in filesystem
df -k
• Check free space for the database
onstat -d
• Check over all memory and CPU usage
top or any other utility that gives an idea of
this
• Check Informix statistics
onstat –p Cached reads should not go below
95%
Cached writes should not go below 90 %
You should have 0 deadlocks
onstat –F You should have 0 foreground
writes.
onstat –g iov io/wup should not be higher than
1,5 for aio class


Orc Server File Systems – Daily Checks, cont.
• Check that all Orcserver processes are up and
running, and check the logs for problems during
startup.
• Check the informix log. Make sure you don’t have
long checkpoint time or errors.
• Check the system log. Make sure there’s no
hardware or software problems
/var/adm/messages
• Check that backup jobs went OK. Both dbbackups,
and filesystem backups.
• Check that there’s no core files. If there are,
what processes and when did it core dumped.


Orc Server File Systems – Basic Troubleshooting.

• Questions to answer:

– Is this critical or not, can the users still use the system and trade ?
– One or all users having a problem?
– Are the Orc server processes up and running ?
– Can the users login to the system ?
– Problems with just one or more market connections?
– If just one, is there some disturbances at the marketplace or with the communication
lines to the market?
– What’s common for all afflicted users if not all users are involved ?
– Any changes in the environment, such as: new release, network reconfiguration, new
serverprocess started, changes on a market ?
- If the problem is located to the server: ( more probable if all users experience problems)
- Have I checked all things included in the recommended daily maintenance ?


Orc Server File Systems – Basic Troubleshooting cont.

Check for errors in the logs in /usr/orcrelease/log/
Check informix log /usr/informix/online.log
Check system resources
Check networks
If a process isn’t up and running as expected, check for core files
If more information is needed, turn on debugging on process that experience problems
May help to stop and start a process or all server processes

If the problem is located at one client:
Check the Orc.log
Check the system resources and logs
Turn on sdebug after contact with OrcSupport team.
Activating crashreport on MacOSX
Reboot clientmachine if the users can’t use it all.


Orc Server File Systems – Upgrade

• An upgrade should be discussed and
agreed on with the users and also
communicated with the local support
office in good time before taking place.
• Prepare yourself and the users by
reading releasenotes and ask for more
information if needed
• Someone with Orc client knowledge
should verify that the upgrade went
well, best person to do this is probably
one of the more experienced users. The
person technically responsible for the
server can verify that all technical
aspects of the upgrade went well, but
a trader will verify functionality.
• Follow the procedure outlined in
chapter 4 in the ServerAdmin Guide
when upgrading.

Orc Server File Systems – Practical

• Create a new environment
• Create a market Link
• LIFFE to test market
• CME market process
• EUREX registered from remote server
• Add users for each market
• Set-up Orc client’s
• Logon to clients and markets

Use both Sauron and
commandline !


Orc technical training

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (19)

Similar a Orc technical training

Similar a Orc technical training (20)

Orc technical training

Notas del editor