Fusion FAQ

Technology Stack

Q:  What technology stack is used? 

A:  Fusion is a Java application running on TomCat and MS SQL Server/Oracle. Javelin offer Fusion as hosted on your servers and managed by you, or as a hosted option by us; where it would be (typically) installed on a Windows server.

Cloud

Q:  Do we setup and configure the Fusion technology on our systems or is it only a cloud-based solution? 

A: Fusion consists of a console application – for configuration and monitoring of the host – and a host application that can independently monitor for events and trigger workflows. These two can be in different locations.

Q:  If it’s not cloud-based, how are updates handled to the Fusion technology stack to introduce new functionality or fix existing bugs? 

A:  You make changes in your console and commit these to the version control database. Then publish your changes to the production system.

Extension/Adaptation

Q:  Do we have access to source code to extend/modify/adapt the Fusion solution? 

A:  New functions may be written within the application. Fusion is effectively a Rapid Application Development platform. You create data source objects, actions, rules and functions. These are utilised in workflows. The workflows are then run on a schedule or triggered by events (like a file or e-mail arrival).

DirectoryDirectory1Directory2

 Integration

Q:  Would we connect to our own internal system by developing a plugin to act as an integration endpoint? 

A:  Fusion has ‘Data Sources’ that are utilised within ‘Data Transformation Actions’ and workflows. For instance; you would create a number of JSON data sources to access your internal systems.

PluginPlugin1

Q:  Does the Fusion solution support integrations which can be heavily customised (such as Salesforce) and, if so, how would we work with the customised elements such that it can be programmatically built into an automated data flow? 


A:  For something as complex as custom Salesforce data structures you may need to write a Java scriptlet to interpret customer’s data and put these into a normalised format. Fusion will take care of transport, error handling, notifications and transformation of the normalised data into another normalised format.


Q:  How are new third-party integrations added into the system? Is there a mechanism to describe the capabilities offered by new integrations in a discoverable and automatable fashion? 


A:  New templates for connecting to third parties may be posted on the Fusion web site for download or publishing to your version control database.

Security Database 

Q:  How do we manage data flows and credentials for thousands of users in an automated fashion? Setup, modification, and teardown for both internal and external credentials. 

A:  Fusion has a security database that conforms to the Common Security Framework. You can use this or connect to your own data store. A web interface to manage users and suitable authentication steps within your Fusion workflows would be the typical solution.

Development

Q:  What parts of the Fusion solution are currently manual, or is it 100% scriptable and automatable with zero manual steps including setup of new accounts and removal of closed accounts? 

A:  With corresponding development (within the RAD environment) the solution is 100% scriptable.

Q:  Is there an API? Does it cover 100% of the functionality of the product including areas which are typically done via their graphical designer? Can the output of the graphical designer be programmatically retrieved via the API? 

A:  There is no API for Fusion. Artifacts and workflows may be exported (saved to file as an XML definition) and imported. All artifacts are stored in an ODBC compliant database.