Internet Development and Systems Integration
No matter what industry you're in, the Internet and technology will play a critical role in your organization's future. Whether it's a corporate website, custom database, or specialized software application, GPL Integrated IT, LLC can help you achieve your businesses goals. Since October 24, 1995 when the Federal Networking Council, unanimously passed a resolution defining the term "Internet" the members of GPL Integrated IT, LLC have been working with Internet technologies to win national awards and industry recognition for select clients across the northeastern United States.
The Internet and the businesses using it have changed much in the two decades since it came into existence. It was conceived in the era of time-sharing, but has survived into the era of personal computers, client-server and peer-to-peer computing, and the network computer. It was designed before LANs existed, but has accommodated that new network technology, as well as the more recent ATM and frame switched services. It was envisioned as supporting a range of functions from file sharing and remote login to resource sharing and collaboration, and has spawned electronic mail and more recently the World Wide Web. But most important, it started a new type of business environment that allows companies to work together and grow to become commercial successes with billions of dollars of annual revenue.
The most pressing question for the future of the Internet enabled businesses is not how the technology will change, but how the changing technology can best be incorporated.
Your organization probably uses many applications and services that were built over many months or years, as new business needs were identified. As a result, these applications are of different ages, were written by different people using different technologies, different hardware platforms, different operating systems, and provide very different functionality. In fact, many of your applications often have very little in common at all, resulting in isolated functionality and multiple instances of the same data. This results in redundant activities, higher costs, and an inefficient customer response.
Effective Internet enabled application development can provide your organization with many important business benefits, such as:
- Allowing applications to be introduced into the organization with a common user interface, more efficiently and at a lower cost
- Allowing you to quickly modify business processes as required by the organization
- Providing more delivery channels for your organization
- Allowing you to add automated steps into business processes that previously required manual intervention
- Improve operations by cutting costs, boosting revenue and stremline business processes both internally and with your business partners
Making Application Integration Scalable
An important part of Internet enabled application development is to make applications scalable. Many organizations will invest in application development and neglect to incorporate the ability to increase the number of automated steps and reduce the number of human steps. This generally involves creating interfaces between applications along with predefined logic that replaces human involvement.
Increasing the level of automation generally increases the amount of information traveling between applications without increasing the number of employees required to support the environment. The scalability issues, however, do not stop at simple automation. You should also consider the number of applications themselves and how integration occurs between them.
For automated application integration,
you have two choices:
- Point-to-point model
The point-to-point model describes a decentralized structure in which each application
communicates directly with the other applications. This type of integration is
most appropriate for organizations that need to integrate a few applications with a
small number of services.
As the number of applications and services increases, the number of interfaces and
connections that need to be maintained in a point-to-point environment rapidly
increases.
- Integration hub model
The integration hub model provides a more centralized structure, in which an
integration hub is placed between the applications, and each application communicates
with the hub rather than communicating directly with other applications.
Each application needs only an interface and a connection to the integration hub. To
simplify matters, the integration hub can rely heavily on existing standards, which
means that either the interfaces already exist or the methodologies for writing them
are well-defined.
The main advantage of an integration hub environment is scalability. The integration hub model is significantly more scalable for integration environments
with many applications. A typical large-scale organization has thousands
of islands of information, involving thousands of applications. You simply cannot
create individual interfaces for every point of interaction. Instead, the solution is to create an application integration environment that allows all of your applications to
communicate in a logical, predefined way. This hub infrastructure enables you to
modify or update elements much more easily, and to do so when the business
requires, rather than when the preexisting technology dictates. It should also allow
the organization to more easily change direction and to use the products and services
it has to match evolving requirements.
If you have read this far, your organization has probably identified a business
requirement for applications to work together. Just as employees have to work together to meet business goals, your applications need to do the same. Application integration isn’t easy. Typically, an
environment that supports application integration meets at least the following
requirements:
- Connectivity between different platforms
- Processing of complex business rules, including complex data transformation logic
- Support for business processes, from the very short to the very long, including processes that last weeks or months as data is passed and processed through different parts of the organization
- The ability to modify existing business processes or create new ones as business goals change
- The ability to adapt to changes in hardware, software, and business goals
To help meet these requirements, your application environment should:
- Expose a common interface through which applications can communicate, by using business semantics to request Web services.
- Allow service requests at the functional or data level for applications that do not support using business semantics.
- Use a common set of process and service rules to ensure consistency and reuse of integration services.
- Be capable of reusing the existing transport protocols that already exist in the enterprise.
- Insulate itself from existing technologies by using interfaces.
An application integration environment should not depend on the implementation
of any particular technology. You don’t know what applications and hardware your
organization will be using in five years, but whatever they are, your organization
will need to support them.
Web Services
A Web service is an application component that:
- Exposes useful functionality to other Web services and applications through standard Web service protocols.
- Provides a way to describe its interfaces in detail, allowing developers to build
client applications that talk to it. The description is provided in an XML
document called a Web Services Description Language (WSDL) document.
- Describes its messages by using an XML schema.
Many vendors have endorsed and have started to provide Web service capabilities
in their platforms. Using Web services for integration ensures that your integration
is based on open standards that are language neutral and platform independent, and
helps to ensure that the technology remains relevant over time.
Web services rely on defined specifications to allow systems from various vendors to
interoperate. Web services specifications, commonly referred to as WS-* specs, are in
various states of acceptance. The Web Services Interoperability Organization (http://www.ws-i.org) was formed to provide a framework and a set of tools to ensure that
different vendors’ implementations of a particular WS-* spec are compatible.
|