Use Transformer’s comprehensive kit of ready-built components to model the mappings and validations you need.
Transformer eliminates the ‘spec handover’ from analyst to developer. In fact, there’s no coding stage at all.
Instead, you quickly build up a clear and easily understood model of the required behaviour – and then create the deployables directly from it.
This revolutionary approach dramatically speeds up the creation of even the most complex validation, enrichment, mapping and data transformations.
Going forward, the models created in Transformer are a crystal-clear and up-to-date record of the deployables they embody. They are also far easier to maintain over time than traditional spreadsheet-based specs and opaque code.
You specify mappings in Transformer quickly and easily, in most cases simply dragging a field from the source message onto the target.
You can do this because Transformer understands exactly how dates, amounts and other basic data types are represented in any given standard. So it automatically takes care of any reformatting that may be needed between the source and target syntax.
To create more complex transformations, you simply select from a huge range of ready-built mapping actions and combine them as required. Conditional statements are also provided, so it is easy to create complex logic that remains easy to read.
Trace Financial has also created sets of complete, ready-built mappings to deal with publicly defined mapping requirements (e.g. SWIFT MT<>MX for CBPR+). Your project task is then simply to review and adjust these pre-built mappings to suit your local business practices and needs. More details here.
Transformer’s standards libraries are truly comprehensive, because they describe every aspect of message standards – including cross-field validations, which simple schemas cannot represent – giving you the best possible start.
They are also easy to understand, as they include business-friendly versions of field names and fully described ranges of valid values. You can focus on the actual meaning of fields, and their relationships – spending less time on the technical syntax. Transformer libraries cover all of the following standards and formats:
Trace Financial updates these libraries as the standards change, helping to remove the need for standards handbooks entirely. Find out more about standards here.
All message definitions are displayed in an uncluttered, non-technical way to provide a clear, intuitive view of even the most complex structures:
Users can also quickly define non-standard formats, such as in-house and proprietary standards. Let us show you how easy it is to create these formats here
Transformer moves the testing process as far upstream as possible. With a single keystroke you can Test-As-You-Build each new element of a mapping or validation, as soon as it is added.
The results are displayed instantly within the screen used to create that mapping line.
Building and testing thus become interwoven aspects of a single ongoing process, to ensure that the model performs exactly as intended. This, in turn, reduces the time taken to perform system-level tests using the deployables created from the models.
Maintenance can be the most time-consuming aspect of working with messages.
As public standards are updated, in-house formats evolve and business needs change, many validations and mappings will need to be adjusted. For many firms, this is a really difficult and time-consuming task.
Transformer’s model-based approach changes everything. Because you have created clear and easily understood models of the behaviour of every process in the messaging project, it is much easier to maintain later.
Features such as “Where-used?” – which highlights every location in validations and mappings in which a given field is used – make it easy to analyse the impact of standards changes.
After a mapping has been built, Transformer saves both the input test data and the resulting output, along with the mapping itself. The test can thus be repeated later in regression mode, to highlight any differences.
This greatly speeds up the task of checking the continued correctness of a large number of message mappings following minor updates to just one or two elements.
Transformer’s simple API and its range of specialised service builders allow solutions to be deployed rapidly into any integration architecture, including OSGi, development frameworks such as Java or .NET, RESTful service containers and traditional Enterprise Service Bus (ESB)/Enterprise Application Integration (EAI) architectures. Each deployment is independent and thread-safe, allowing for complete scalability within the overall architecture.
Transformer has been qualified on platforms ranging from Windows servers to Linux and Unix, and is available from both Java and .NET runtimes.
Transformer also includes a range of functions to facilitate the product’s use with Apache Camel, the open-source integration framework. For example, special-purpose mapping actions simplify interactions with Camel message Headers and Exchanges, while a Camel/OSGi specific service builder simplifies deployment to a few clicks.
Transformer has also been deployed successfully within Websphere, Tibco BusinessWorks, Sonic ESB and similar infrastructures.
More information about how Transformer can deployed into any environment can be found here
Transformer is simply the faster, better way to build complex message transformations. For a demonstration, either online or in your office, please contact us.
If you are about to start a messaging project, send us the specifications and we will amaze you with what Transformer can do in a day.