Applications Integration Approaches

It has become common to have applications integration. The increasing availability of the standards, as well as tools alongside with the Service-Oriented Architecture (SOA), shows many signs of much simpler database and system integration than before. Presently, there are two approaches that are used for this, which have become very popular and they are the following:   Point-to-Point integration   In this type of applications integration, there is a direct link created between the applications, with the help of a direct application program interface link, batch interface or simply file transfer protocol. The translation or the transformation of the information may happen due to the data getting transferred via the link. This kind of interface is normally implemented without taking any help from an integration product, with translation of the information occurring with the help of code at the point of integration at just one or both the ends of the interface.   Service Bus Integration   This form of applications integration will use the technological solution that a bus can provide. When this is done, the applications would be able to place the required messages between the bus and the applications. The bus would be able manage the translation of the message formats from in between the applications.   Many organizations have worked towards creating a wide range of services that will be available online. That creates the goal of putting the product lines together in a group as well as look towards streamlining all the call center experiences. It will yield the need of an increase in the back end systems. It is considered normal for call...

The Contractor Silo Problem

Let’s suppose that you have a large system you’d like to redo for the web. You could get it translated, but you don’t want the likely performance and maintainability problems associated with wholesale line-by-line translation. In fact, you don’t even want the new system to look like the old one: you want slick graphics, customized and stylish menus, drop downs, radio buttons… the works. In other words, you want to rewrite it. If the system is big, you might at first consider giving it to a big integrator to redo. The first problem with that approach is that nobody has 80 highly productive developers just sitting there waiting to start your legacy modernization project. Firms may have a few, but not enough good ones. Another approach is to divide the work and give it to 3 or 4 or 5 firms. Not a bad idea, because they will compete, and you won’t have the “entrenched contractor” problem that we hear so much about. There’s only one difficulty: how do you get them to write the code in a consistent style, so that it all fits together and looks like one team wrote it? Because if not, you will get 3 or 4 or 5 “silo” implementations, with the interoperability and maintenance problems that go along with it. You can’t solve this problem with a paper architecture, but you can solve it by implementing an architecture for the entire system and directing the contractors to use common code and put their unique business logic on one place. That’s what ResQSoft(r) Engineer gives you — you can have all the routine...

Micro Focus Cobol — New Options for Modernization of Mainframes

Micro Focus has recently come up with many new options meant to cut expenses and also to cut time, when it comes to building or just maintaining applications used by organizations; some of these options are Micro Focus Cobol, Micro Focus Server Express, Micro Focus DevPartner Studio, Micro Focus Silk4J and Micro Focus for Visual Studio. These options generally enable Java and other devs to modernize their mainframes, by offering a reliable support in the entire cycle that involves editing, compilation and debugging. Micro Focus Cobol– Server Express (RDO) The Micro Focus Server Express will permit client to maintain their programs in Cobol and make the code sourcing on the server that represents the target, preventing them from transferring code between a development environment and the Linux/Unix server, where applications run and are being tested. It also allows the usage of local services and databases. How does it help organizations The RDO along with the Micro Focus Cobol and all the other options is the answer to the needs of any organization in point of debugging and testing application, as close to their production as they can be. This actually translates into a substantial time reduction, because if until now it was a matter of days until a development project could be completed, this can now be done in a few hours, which means more productivity and thus more satisfied customers. Advantages of Micro Focus Cobol and other Micro Focus tools There are many advantages that this option has for its users and these are only a few of them: –          Increase of productivity due to time reduction of...