Adeptia in Chicago offers their B2B integration solution to enables enterprises to accelerate customer data onboarding from months to a matter of minutes. Adeptia Connect provides a simple user interface (a front-end) to manage all external connections and data interfaces for a company. It provides self-service partner on boarding and no-code approach that enables business users from a company and its partners to view, setup and manage data connections with each other.
I recommend the program for an advanced stage, it is not a program for small companies, it is a program for medium or large companies where you know about data and its flow in which you need to make the leap to a 3.0 level of the same.I could immediately recommend it to colleagues for its great storage capacity and agile control.
BizTalk is well suited as middleware. Where you wish to translate an input file into an output file and send it to some endpoint. In our case, we used it to convert and send files to SAP. In many ways, it very flexible, and you can do almost anything you want with it. In many ways, it's a better solution than your SAP XI or PI as middleware, since it's much less expensive, and allows you do interface with non-SAP systems.
It is very user friendly. Users can change rules during run time and change workflow.
Huge capacity for queueing messages. It supports all types of adapters like Oracle, Salesforce, SMTP, FTP, etc. Also users can built custom adaptors.
If users want to dynamically deploy their solution without any downtime, this is a perfect solution. BizTalk will be a good fit, especially for public-facing websites.
Well-proven in the market. I used it when developing a website for Virgin Trains, catering more than 800K user requests per day.
BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.
We mainly choose Adeptia Connect for the friendly UI. From the first minutes, it was really easy to use and understand how it works and then manages complex connections.
BizTalk was selected here mainly because it is easy to integrate to a .NET application (most of them are Web Service, WCF SOAP, WCF REST and Web API) and many backend databases are Microsoft SQL Server. Another benefit is that the monitoring job is easy to set up and centralize with other .NET application monitoring jobs.
The user can set up the whole template and then enter the data or we simply have to connect that data by making use of connections from an account through an API.
We can do reference lookups in the database to further enhance it before sending it to the data link and as part of this process flow
We can attach by taking up a little bit of time or batch and this can be a multi-directional process. So I needed this data transformation
A positive impact has been the quicker turnaround time of a part request and that part showing up in SAP using Biztalk as middleware.
A somewhat negative impact has been the somewhat insufficient error logging/message capture settings that Biztalk provide. This has caused occasional delays when attempted to create parts for the business.
A somewhat negative impact has been the need to have a specialized developer who understands Biztalk to troubleshoot issues with the Biztalk and SAP interaction when creating parts, and when adding new fields to the parts.