The Tick42 Configuration Manager features a sophisticated centralised management system capable of delivering changes to all applications in real time.
Configuration Manager WebUI. Data values can be changed by editing the value fields. The bottom part of the display summarises the change history.
An example view of a fragment of the Schema. Metadata is used to control how the the elements are named in the data view
View the audit log to see who has made changes
Easy, real-time access to a centralised store of system data, typically comprising application configuration files as well as the large system-wide data sets required to store product reference data. Any changes to the data are broadcast to all applications in real time, avoiding the need to restart systems on data changes.
This tool provides easy, real-time access to a centralised store of system data, typically comprising application configuration files as well as the large system-wide data sets required to store product reference data. Any changes to the data are broadcast to all applications in real time, avoiding the need to restart systems on data changes.
- Easy-to-use interface for Java,.Net and Streambase applications
- Data can be entered via a Web GUI, via CSV import or directly from client applications
- Run on a range of standard transports including Tib/RV, TCP and various MQ providers
- Store product reference data.
- Store application configuration data.
- Permissioned access to data
The Tick42 Configuration Manager provides an easy-to-use interface for Java,.Net and Streambase applications. Data can be entered via a Web GUI, via CSV import or directly from client applications. It can be run on a range of standard transports by leveraging the sophistication of bus technologies such as TIBCO RV and various MQ providers, allowing the use of easily available data cache architectures.
Tick42 also provides its own high-performance transport, allowing simple licence-free deployments.
So why would you want it?
The Tick42 Configuration Manager allows a system to dispense with local xml or csv configuration files, or with Windows registry-based configuration, and store its configuration in a centralised repository. This guaranteed, consistent view of the configuration is particularly useful in distributed systems where multiple components are running on a variety of machines, and orchestrating changes to individual Configuration files can be a time-consuming, error-prone business.
Once the system configuration is sourced from the Configuration Manager, applications can be coded to respond to changes in real time, avoiding the need to restart all the components in a system when changes to the configuration data are made. All changes to the configuration are audited and can easily be rolled back from the audit log entries. Meanwhile a secure permissioning system sees that all access and/or change requests are initiated only by authorised users and applications.
The Tick42 Configuration Manger can also be used to store reference data instead of using a database. There are three major advantages to this:-
Ease of access,
The ability to broadcast changes in real time.
The ability to use a distributed set of Read-Only caches to provide local access to the data.
In a future release these local caches will be able to augment this reference data with local data relevant to a single business area.
Where the Tick42 Configuration Manager can help:
Where all Instruments are held in the Configuration Manager, adding a new instrument to a pricing or trading system is straightforward and can be done without restarting any components.
Storing key parameters for Pricing Systems. Since the Configuration Manager broadcasts data changes to all permissioned applications in real time, storing pricing parameters such as Spread, Skew or Algorithm for each product allows all the applications in a system to use a consistent set of parameters. The use of a bus-based distribution also means that new pricing applications can be dynamically added to the system and have full access to the parameters.
Many systems run multiple copies of a particular service to provide load balancing, with load allocation based on some kind of regular expressions on an Instrument’s name. These regular expressions are held in the Configuration Manager, linked to some instance name. This allows a new server instance to be run up and then load dynamically moved to the new instance by changing the regular expressions associated with each instance. All without restarting anything.
How it works.
A Configuration Manager server stores information in top-level schemas. Each top-level schema defines a Tuple data structure that can hold fields, records and lists of sub Tuples. The Schemas are defined in Configuration files read by the server and can be changed at run time without requiring a restart of the server or its clients.
The Configuration Manager publishes its data over a Tick42 Transport, which can support a variety of existing systems such as TIBCO RV and MQ as well as Tick42's own TCP-based subject-orientated transport.
The server uses the Tick42 User Manager to control access to the data and make sure only approved users have the authority to view or change the relevant data.
All data changes are written to an audit log and contain sufficient information to back out a change.
A web server provides a GUI to see the data structure and to view and edit the data. A CSV import/export facility is also provided to allow the data to be manipulated in Excel. Applications may access the Configuration Manager from Java, .Net and Streambase. Clients may receive Snapshots, updates and also edit and create data via the API. Java and .Net clients may chose between an unstructured Tuple style of API or use a Hibernate-style set of automatically generated classes.
Changes to the data whether via CSV import or from the API are treated as transactional and delivered to client applications as a single event.
The Configuration Manager may also be deployed in high-availability configurations.