Boston University: Low Code, Cloud-based Solution for Legacy Microservices

What were the underlying reasons or business implications for the need to automate business processes?

Our goal was to have a low code, cloud-based solution for legacy file based application integration Microservices and the ability to implement modern integration patterns.

Describe your automation use case(s) and business process(es).

We have dozens of use cases. Two of our more interesting use cases our admissions synchronization and a use case to gather bio demo data. This use case gathers data for individuals from multiple source systems and provide a common data model that puts all the disparate systems into one common data format. Our admission case is one of our major use cases which we automate synching applicant data from our application processing system on a legacy mainframe platform to our applicant portal which is implemented on a salesforce platform.

Describe how you implemented your automations and processes.

We build our pipelines as a group of reusable components. We then use the pipe execute snap to use them in our larger automation needs. We use many data Snap Packs as well. We have a lot of use of sql server oracle and jdbc for accessing out many different databases. We also call many web services both soap and rest with the soap and rest snap packs. We are also using SNS and SQS snap packs to implement some messaging patterns. For our legacy interactions which are mostly file based we use the binary snap pack and the file snaps in conjunction with the many Transform snap pack snaps quite often to deliver various file formats using different file protocals including ftp s3 and smb.

Who was and how were they involved in building out the solution?

From our initial implementation to now we have grown from 1 FTE to 5 plus contract help from Logan Data in Westford MA when required. I have been involved from the decision process to the current implementation.