Take your firm's FIX testing to the next level with Visual FIX®, the next-generation integrated development environment for FIX testing, verification, and validation. The innovative capabilities of the Visual FIX system can help you reduce time to market, lower costs, and significantly improve your efficiency in the development, testing, and support of FIX protocol applications.
| Extensible Visual Environment. | Intuitive WYSIWYG Editors. | Analysis and Validation. | Scenarios/Simulations. |
Designed from the ground up as an intuitive and highly-extensible system, Visual FIX delivers flexibility you won't find in legacy FIX testing solutions. The patent-pending visual workflow construction environment allows you to construct complex FIX testing scenarios with ease, while dynamic code import facilities allow you to seamlessly integrate your proprietary .NET code directly into the system.
It all comes together in Visual FIX - the system's visual workflow editing environment allows you to mix and match components to easily address difficult message processing scenarios. Equally suited to programmers and non-programmers alike, the Visual FIX system allows QA, development, and connectivity personnel to collaborate more effectively by sharing a common visual environment for developing, testing, integrating and troubleshooting FIX applications.
| Visual Workflow | Foundation Components | |
| The Visual FIX system's visual workflow editor provides an intuitive environment for constructing complex FIX testing workflows. Deceptively simple, the system's interface allows you to create complex FIX testing scenarios and simulations by visually combining and configuring our easy-to-use testing components. | The Visual FIX system ships with our Foundation Components package, a suite of easy to use components that address specific FIX testing challenges. These components simplify scenario development, log-based regression testing, and message validation. |
|
The Visual FIX system's service creation and configuration wizards simplify the process of creating and configuring
FIX services and sessions. The system also supports multiple open-source FIX engines, allowing you to select between
the QuickFIX or VersaFIX engines, depending on your needs. Visual FIX projects are multi-service capable, allowing you
to create multiple services and sessions, each with its own service-specific workflow, within a single project.
The Visual FIX system's service wizards allow you to quickly create services for simulating the client or server sides
of a FIX conversation, as well as proxy and loopback configurations for analyzing traffic between systems or for testing
your proprietary code and components in a sandbox environment before deploying it.
|
|
The Visual FIX system includes built-in dictionary editors that allow you to create your own custom FIX dictionaries
or modify the standard dictionaries that are provided with the system. You can create custom messages, fields, repeating
blocks or groups, and export your customized dictionaries as XML files which are compatible with popular open-source FIX
engines, like VersaFix or QuickFIX. Export formats are non-proprietary and allow you to easily convert to and from other
FIX engines or systems using nothing more than an XSLT transform.
|
|
The Visual FIX system's template editor allows you to define custom templates that can be used throughout the system for
generating FIX messages at runtime. Any FIX message that is defined in one of the system's FIX data dictionaries can be
used as the basis for a template, allowing you complete control over how each field in a message is generated. Automatic
generation of fields can be handled by the system, or for advanced applications you can even assign a custom script to any
field in a message.
Once a template has been defined, it is added to your template library where it can be used in any of your future projects.
The template system is integrated with all of the standard Visual FIX components, allowing you to use your own custom templates
anywhere in the system where FIX messages are generated. Templates can also be exported to XML files which can then be shared with
other users of the Visual FIX system.
|
|
The Visual FIX scenario processor allows you to quickly create custom messaging scenarios, without requiring any programming
or scripting experience. The scenario editor's logic components simplify the process of sending and receiving messages, analyzing
message content, evaluating conditional rules, and configuring variables. The scenario editor component allows you to save and
load scenarios from XML files, allowing you to build a library of common scenarios and use them over again in new projects.
The scenario processor component is provided as part of the Visual FIX Foundation Components, included free with the standard
distribution of the Visual FIX system, and is fully integrated with other aspects of the Visual FIX system so that you can use
rules, FUIL tickets, and FIX message templates all from within any instance of the scenario processor. Once configured, you can
save any scenario processor instance as a template for use in projects or workflows you create later on.
|
|
The Visual FIX scripting components allow you to create complex message processing scripts which can be added to your workflow
to provide custom logic. The Visual FIX scripting components use the LUA script language, which is easy to use and supports the
import of any Visual FIX or .NET assembly into your script. Perfect for situations where you want to extend Visual FIX but don't
have time to write a new plug-in component, the scripting component allows you to import and access all of the features in the
Visual FIX extensibility SDK, allowing you to quickly develop scripts to handle even the most complex scenarios.
As with every component in the Visual FIX system, you can save configured scripting components as templates for use in future
projects, allowing you to build a robust library of scripted components to accomodate any FIX message processing challenge. Since
LUA is a popular language, used in everything from video games to industrial control systems, it's easy to get up to speed on it
as well.
|
|
Visual FIX's extensible workflow environment allows you to develop your own .NET components for processing messages or
other events within the Visual FIX system. Dynamic code import facilities allow for seamless integration of your own .NET
code directly into a Visual FIX workflow, allowing you to extend the Visual FIX platform to meet any challenge. If you have
existing code or components that are written in a .NET language, they can be imported into your Visual FIX environment with
a minimal amount of integration overhead.
There's no limit on how you can extend the Visual FIX system, so you're not locked into a single vendor's interpretation of
how you should conduct your FIX development or testing. Best of all, the extensibility APIs are the same APIs that we use
internally to develop the standard Visual FIX components, so you can be confident that your components will always remain
compatible with the components that are distributed with each Visual FIX release.
|
|
The Fix User Interface Layout system (FUIL) included in Visual FIX provides WYSIWYG visual editors for creating your own custom
tickets and order-entry screens. Simply open the FUIL designer, select a FIX message to use as the basis for your ticket, and then
add FIX-enabled user input controls to the screen to create a custom user interface for message generation. Once created, FUIL tickets
can be used throughout the system, with any Visual FIX component that is FUIL-enabled. Build your own library of custom screens and use
those screens over and over again in different projects.
The FUIL system uses Visual FIX templates as the basis for generating FIX messages, so any custom template you have developed using the
Visual FIX template editor can be used as the source construct for a FUIL ticket. The FUIL system can also import and export FIXatdl
compatible screen definition files, which simplifies the process of developing and deploying interfaces to algorithmic trading systems.
|
|
Now you can encapsulate entire workflows within a single, reusable, workflow container. New in version 1.5 of Visual FIX, the
workflow container component allows you to construct complex message and event processing workflows within it in order to simplify
the management and reuse of your custom logic. Simply add an instance of a workflow container to your project's workflow, and
construct a workflow within it. The workflow container component allows you to use entire workflows as reusable building blocks,
and there is no limit to the number of nested workflows that can be contained within a container.
Once you've constructed a new workflow within an instance of a container, you can save that container as a template component for
use in future projects. The workflow container is 100% compatible with all Visual FIX components and, just like a regular workflow,
supports seamless import of your own proprietary .NET components through the Visual FIX dynamic code import system.
|
|
Now you can deploy your FIX messaging workflows to the server side directly from within Visual FIX. The new Visual FIX Server
system provides a fully-integrated server side platform for the deployment and execution of your message processing workflows.
Integration with the Subversion version control system ensures your desktop and server side environments stay synchronized, and
makes deployments and rollbacks easier than ever. Full integration with Visual FIX also means you can manage and monitor your server
environment without ever having to leave your desktop.
Click here for more information about Visual FIX Server.
|
At Assimilate Technology, we understand your focus on the bottom line and your need for serious ROI when it comes to FIX productivity. The Visual FIX system is not only the most technologically advanced FIX productivity system on the market, it's also the most affordable. Please visit our sales page by clicking here for complete details.