The Gartner AADI Summit in London is only a month away which means it’s time to start talking architecture, development, and integration of applications. This Summit is beneficial in that informative analysts and industry leaders will provide applications professionals with deep insight into the best practices of cloud, SOA, and key trends in applications today. At the event, we will be explaining how Thru’s SOA architecture enables customization and integration of Managed File Transfer features to fit a wide range of business processes and deployment options. This blog should serve as an introduction to Thru’s architecture and a primer for AADI.
SaaS Applications and End Points
Thru is a global network with a multi-tier and multi-component service-oriented architecture. Each component of the structure communicates in a loosely-coupled manner; deployment consists of cloud, on-premise, and hybrid models. The top layer of the structure is made up of the SaaS Applications which connect to Thru that include:
- Web application
- Connectors to integrate with enterprise applications such as Outlook, IBM Notes, Salesforce.com, and SharePoint
- Mobile applications for iPhones and iPads as well as Android phones and tablets
Connectors access the Thru core server via endpoints such as SOAP and REST web services, SFTP, FTP; users of FTP and SFTP gain additional business logic not available using most FTP and SFTP servers. The middle layer is composed of this business logic available to all Connectors from the Thru core server.
Applications such as CRMs, ECMs, bespoke software, and any other application that speaks Web services can be connected with Thru to provide managed file transfer capabilities. Integrating Thru with enterprise applications adds compliance and security controls to organizations and provides the ability to manage and send files or folders of any size with no limitations.
All user connectors communicate with the Thru core server made up of a relational database and a virtual file system. The relational database contains all metadata of files and users and recordings of every file transaction. The core of the Thru design is the audit. Everything that happens inside Thru is recorded and made available for analysis with data mining tools. These tools are available to administrators from the web application to extract recordings from the database such as:
- IP address
- User email and name
- Uploads and downloads
- Successful or unsuccessful transaction
- Timestamp for every transaction
Part of the core server is Thru File Exchange which utilizes Thru’s Content Delivery Network to transfer data globally. With deployments in America, Europe, Asia and Australia, users can rapidly transfer files over high latency, wide area networks.
Thru Service Processes
Below the Core Server is a layer of Thru Service Processes including:
- Workflow and notifications
- Expiration of files
- Retention rules
- Custom extension services
For example, retention actions are managed by administrators that can tell Thru to delete certain files or folders based on multiple levels of rules including time in the system and file type. These retention and purge services make Thru compliant with government rules where files must be deleted after a certain period of time.
A process to guard against security threats is Thru’s antivirus integration service which performs real time and ongoing scanning of incoming and stored files. When Thru is deployed on-premise, those customers can use their organization’s standard antivirus protection with Thru’s integration capabilities.
Thru’s service-oriented architecture and integration has made Thru not just a point solution for secure file transfer, but rather it is built to be an flexible and scalable comprehensive solution to cover a multitude of file transfer needs for the enterprise. Watch the 9-minute video, linked above, to learn more about the Thru architecture, or come visit us at AADI next month!