What Does Integration Mean?
At the most basic level, system-to-system integration means that one system can use information from another system, or that they can exchange information. In many older systems, this means that one system creates a file and sends it to the other system, usually by File Transfer Protocol (FTP) or Secure File Transfer Protocol (SFTP).
In more modern systems, integration may not just mean exchanging data. It may also mean that one system can call a function within the other system. Decades ago, we accomplished this with a Remote Procedure Call (RPC) or with some kind of object broker mechanism. More recently, this kind of integration may be implemented using a web service interface, like Simple Object Access Protocol (SOAP) or more modern alternatives built using JavaScript Object Notation (JSON).
Writing Integration Code Automatically
From the above discussion, you can see that there are kinds of integration mechanisms that have a lot in common. Using ResQSoft Engineer, we can automatically write a lot of the source code needed to implement integration using file transfer, and even remote calls. The code is accurate, standardized and secure. What’s not to like?
Integration of the Applications
We’ve talked about integrating two or more independent applications by passing data or making remote calls. But, what if you have to integrate, truly integrate by combining the functionality of multiple applications into one? An example of this would be in a merger and acquisition (M&A) environment: there might be tow personnel systems, two purchasing systems, two accounting systems… so what do you do? Well, you can
- Force all the users onto one system, biting the retraining bullet and migrating the data
- Keep running the competing systems, and forego the benefits of synergy; or
- Rapidly develop a new system that melds the functionality of the two older systems
This Last approach is almost impossible to do by hand, especially if the systems are old, undocumented, and may not even have source code available. But, with ResQSoft Engineer, we simply execute our modernization / re-engineering approach on both systems, reconciling the data base schemas and the functionality. Once both systems are in the same modern platform, it’s much easier to review the UI differences and reconcile the user experience. And, you have the benefit of reduced maintenance effort, greater security, and increased user acceptance.
Not Happy with Your Current COTS Package?
Exhorbitant license fees? Vendor unresponsive? Need to deliver on those promises of synergy after an acquisition or merger? We can integrate the functionality in those existing business systems, leaving you with 100% fresh source code that you own. It’s more affordable than you think!
ResQSoft Succeeds
More than 50% of large software projects based on COTS software fail. With ResQSoft, success is achieved by using an approach that greatly reduces risk. Engineer manages the re-engineering of custom or COTS software – one or many – and easily accommodates changing requirements as the project progresses.