The middleware can't access F&O database, therefore implementation details of F&O database is irrelevant to it. You need to ask good question about what they actually need, otherwise you'll waste time with something that won't solve anything.
First of all, figure out what the middleware will do, e.g. whether it'll be used to export data and populate a data warehouse, it'll transform data to be imported or so.
Then think about how it'll communicate with F&O. For instance, it may read F&O from Azure Data Lake. Or it may use OData to import data. Or data management APIs.
You mention JSON, which might (but doesn't have to mean) that they want to use OData. Then you can get data in JSON format simply by making a GET request to the OData endpiont. You can also use OData metadata to thing like generated classes in the middleware to work with the data in an object-oriented manner, without any need to work with the particular data format (JSON) directly.