WHAT IS THE BIZROUTE CONCEPT?

BizRoute is a highly configurable file transfer solution, facilitating enterprise data integration between business applications and services. Version 1 of the solution will consist of a standard library to provide file routing functionalities and some simple event activities, a Windows service application to facilitate file transfer execution and a WCF service to inject routing requests into the system.

WHAT SHOULD BIZROUTE DO?

The following user stories outline the desired high level capabilities to meet common business file transfer requirements. The term “user” within this document relates to a person within a data integrations specialist role or similar.
ID Title Description
H1 Input routing slips As a user I want the ability to input xml routing slips into BizRoute using common methods (File System & WCF) to make file transfer requests.
H2 Receive files As a user I want BizRoute to receive files using various network protocols (CIFS, FTP & SFTP) to provide inbound integration with business systems.
H3 Cache files As a user I want BizRoute to cache files (to the file system) so that they can be processed by the system during routing activities.
H4 Send files As a user I want BizRoute to send files using various network protocols (CIFS, FTP & SFTP) to provide outbound integration with other systems.
H5 Delete received files As a user I want BizRoute to delete files for their source location once file transfer routing has completed successfully so that redundant files are not left in source locations.
H6 Destroy cache As a user I want BizRoute to destroy cached files once file transfer routing has completed so that system storage resources are not consumed by redundant files.
H7 Event activities As a user I want BizRoute to provide an transfer level event activity capability (create transfer) so that I can provide advanced integration capabilities.
H8 Handle state As a user I want BizRoute to handle routing states for each transfer so that transfer processing is well managed within the system.
H9 Logs As a user I want BizRoute to log routing information (to the Windows Event Log) so that I can monitor actions completed by the system.
H10 Output routing slips As a user I want BizRoute to output completed and failed routing slips (to file system) so that they can be processed by other business solutions.
H11 Isolated input As a user I want BizRoute to handle inputs from isolated hosts so that routing slips can be injected into the system in memory.
H12 Web service As a user I want BizRoute to provide an easy to configure Web Service to allow simple use of modern communication methods (WCF).
H13 Windows Service As a user I want BizRoute to run within a Windows Service so that it can run in the background on my server and provide efficient start up and shutdown functionalities.

HOW WILL BIZROUTE ACHIEVE THIS?

ROUTING PROCESS

The following diagram outlines the routing process to be used by BizRoute.
Innoapps_BizRoute_HighLevelDiagram.png

SYSTEM STRUCTURE

The below diagram displays the high level system structures to be developed.
Innoapps_BizRoute_HighLevelClasses.png

Last edited May 14, 2015 at 10:28 PM by frase, version 6