This article is part of a series. For the previous article, see Moving an App Connect Flow Using MQ onto Containers.
One of the most common integration points is a database, and App Connect is well suited to connecting to a significant variety of datastores. One of the most common protocols used to connect to databases is ODBC, so that is the example that we will work through in this post.
A good application lifecycle management (ALM) package has software that is able to carefully manage and monitor all aspects of software development. ALM applications provide tools for managing and completing the phases of design, development, testing, deployment, and ongoing enhancements. With an ALM solution in place, organizations can significantly improve the way they design, build, test, and adapt their software. Greater customer satisfaction, speed of development, and reduction of cost is the often the result.
VersionOne
Take any integration project and you have multiple applications talking over multiple transports on multiple platforms. As you can imagine, in large enterprises, applications like this can get complex very fast. Much of the complexity stems from two issues:
Making your applications speak transports and APIs is relatively easy on its own. I’m sure everyone knows how to send JMS messages to their broker of choice; though it still requires in-depth knowledge of the JMS specification, which many developers may not have. On top of that, what happens when you want to route that JMS message to another application? You then have to take care of mapping the JMS message to the application plus handle any new concepts related to the application. Add a dozen other applications into the mix and you’ve got quite a headache on your hands.
