|
Enterprise Integration with IBM Connectors and Adapters
Integration of enterprise applications is a critical part of e-business solutions. Many of today's solutions use simple connectivity to databases and transaction managers, but integration of legacy, ERP, CRM and SCM systems is becoming essential to maintain a competitive advantage. However, the difficulty of exchanging information between systems which have differing APIs, data models, and protocols means that integration is often hand-crafted.
|
|
Java Connectors for CICS: Featuring the J2EE Connector Architecture
What is the best method for connecting a Java application to CICS? There are a wealth of options that are available, ranging from using the Java class libraries that are shipped with the CICS Transaction Gateway (CTG), to using the Common Client Interface (CCI) component of the Java 2 Enterprise Edition (J2EE) Connector Architecture. There are also important application development choices to make, such as whether to code to an API directly, or to use a tool such as VisualAge for Java's Enterprise Access Builder.
|
|
Business-to-Business Integration Using MQSeries and MQSI, Patterns for e-business Series
Patterns for e-business are a group of proven, reusable assets that can help speed the process of developing applications. The patterns discussed in this book, Business-to-Business Integration patterns two and three, form the basis for many of the more complex and functional B2B patterns. It is relevant to all enterprises dealing with partner integration issues over the Internet.
|
|
Web services and J2EE connectors for B2B integration
Web services and J2EE connectors promise to simplify the integration of heterogeneous enterprise information systems and provide a way for business partners to share their respective applications' functionality over the Internet. This article uses an insurance broker scenario, in which the programmatic functions from legacy transactions are incorporated into a Web application, to illustrate these capabilities. Share your thoughts on this article with the authors and other readers in the discussion forum by clicking Discuss at the top or bottom of the article.
|
|
Java Junction
E-business applications, especially business-to-consumer applications, have grown haphazardly. Early Web technologies provided quick ways to establish a Web presence, but they didn't scale well. Now the market offers a myriad of proprietary packaged solutions. These packaged solutions promise out-of-the-box commerce functionality and a shorter time to market
|
|
IBM J2EE™ Connectors for the WebSphere e-business platform
Two technologies dominate today's integration server market - message oriented middleware and web application servers. IBM is the market leader in the Application Integration Broker market1 with its MQSeries™ Integrator and MQSeries Workflow products. IBM's MQSeries is the market leader in message oriented middleware with 75% market share2.
WebSphere is growing faster than BEA's WebLogic, and today have approximately equal market shares3.
|
|
Managing the WebLogic J2EE Connector Architecture
Based on the Sun Microsystems J2EE Connector Specification, Version 1.0, Proposed Final Draft 2, the WebLogic J2EE Connector Architecture integrates the J2EE Platform with one or more heterogeneous Enterprise Information Systems (EIS).
|
|
Connectors in J2EE
Connector architecture became part of the Java™ 2 Platform, Enterprise Edition (J2EE) specification in 2000. The J2EE Connector architecture has effectively standardized the Java classes needed by an application to access resources through connectors. It has also standardized the behavior of connectors. At the time of this publication, the J2EE Connector architecture was in the final stage of approval for inclusion in the language. You should see it in Java in the near future. In this article, we will explain what connectors are and how they benefit data-intensive applications. We will provide an overview of the J2EE Connector architecture and show how it is suited to applications using the Web as the means to access resources. The overview will include an explanation of a key concept: managed and non-managed connections.
|
|
Application and Data Access with
J2EE Connector Architecture
In the 2-Tier usage scenario, a fat client works against an application adapter directly (the 1
st
tier). The
application adapter works against the EIS (the 2
nd
tier). Here the client uses the CCI and SPI interfaces
and has complete control over the entire operation of the application adapter.
|
|
Using the J2EETM Connector Architecture Common Client Interface
This article describes the J2EETM Connector architecture Common Client Interface (CCI) API. The CCI provides the access from J2EE clients, such as enterprise beans, JavaServer PagesTM (JSPTM) technology, and servlets, to an underlying enterprise information system (EIS). The J2EE Connector architecture, and the CCI API, are currently available as a beta release.
|
|
UML for EAI
UML Profile for Event-based Architectures in
Enterprise Application Integration (EAI)
As the pressure mounts for companies to reap immediate gains from mergers and acquisitions, expand the electronic exchange of information with trading partners, and deploy best-in-class business applications, enterprise application integration tools from vendors such as New Era of Networks, Software Technologies Corp., and Tibco have become hot commodities. They've also become a hot target, as the major enterprise resource planning software vendors make a play for the EAI market.
|
|
Using J2EE Connectors : Simplifying the connections between application servers and enterprise information systems
Connectors make it easier for you to integrate your Enterprise Information Systems (EIS) with your Application Servers and client applications. At the recent Solutions conference, IBM's Eric Herness presented material prepared by his colleague Kevin Sutter. The session presented material on the soon-to-be-finalized J2EE Connector Architecture and how you will be able to use it to integrate the WebSphere Application Server with your EIS. He showed how the Connector Architecture is based on IBM's Common Connector Framework and explained how this would speed IBM's support for the new technology.
|
|
A component approach to EAI for a heterogeneous world
In the new globalized Internet economy, IT managers are challenged as never before. They are frequently tasked to find ways of integrating existing enterprise assets with Enterprise Resource Planning (ERP) and Supply Chain Management (SCM) systems. Upper management is adding additional pressure to get their e-business infrastructure operational and reduce costs. These combined forces are the main drivers behind Enterprise Application Integration (EAI) projects today. However, with the core business logic embedded in host applications, organizations cannot afford reengineering efforts that could critically affect time-to-market.
|
|
Portals: An Architectural Approach
RFG believes IT executives who are contemplating extending their enterprise out into the Web need to
integrate planning and implementation of online portals tightly with other key elements of their IT
infrastructures. In some environments, this may be best accomplished with portal offerings from currently
established vendors of other key enterprise IT infrastructure components, instead of or in addition to
offerings from vendors focused solely on portals.
|
|
Introduction to BEA WebLogic Application Integration
BEA WebLogic Application Integration provides a WebLogic-based integration solution that supports existing and forthcoming standards for connecting applications both within and between enterprises. BEA WebLogic Application Integration provides a means to define communication endpoints, which may be included in a process flow using BEA WebLogic Process Integrator or using custom Java code to form a complete integration solution.
|
|
Understanding the Integration Framework
BEA WebLogic Application Integration provides a WebLogic-based integration solution that supports existing and forthcoming standards for connecting applications both within and between enterprises. BEA WebLogic Application Integration provides a means to define communication endpoints, which may be included in a process flow using BEA WebLogic Process Integrator or using custom Java code to form a complete integration solution.
|
|
Managing the WebLogic J2EE Connector Architecture
Based on the Sun Microsystems J2EE Connector Specification, Version 1.0, Proposed Final Draft 2, the WebLogic J2EE Connector Architecture integrates the J2EE Platform with one or more heterogeneous Enterprise Information Systems (EIS).
|
|
Plug 'n' Play: Enterprise Apps Enterprise application integration is made easy
with the J2EE Connector Architecture
For companies that operate with multiple enterprise information systems (EISes), integrating these systems is critical to achieve the highest level of operational efficiency. Because J2EE support for enterprise application integration has been minimal (essentially, JMS and XML support it with the JAX APIs), Sun and its Java Community Process partners have proposed the J2EE Connector Architecture (JCA) standard as part of version 1.3 of the J2EE specification. The JCA provides a standard Java solution to the problem of connectivity between the many application servers and EISes already in existence.
|
|
Dietzen Charts Course for BEA Innovation
A lot has happened in the Java world since our last interview with Scott Dietzen, chief technical officer for BEA Systems, a little more than a year ago. XML Web services have moved to center stage while app server competition has intensified and dot-bombs have detonated. To assess the reconfigured landscape, Dan Ruby, Java Pro editorial director, and Jim Fawcette, president of Fawcette Technical Publications, sat down with Dietzen at BEA's San Francisco office shortly before Christmas. His left ankle was wrapped in a seasonal green-and-red cast, the result of a pick-up basketball game injury. But that didn't slow Dietzen's enthusiasm for Java and BEA's technology plans.
|
|
JOnAS and the Connector Architecture
This chapter is dedicated to advanced JOnAS users concerned by EAI (Enterprise Application Integration). The Java Connector Architecture (JCA) defines a way for enterprise applications (based on EJB, servlet, JSP or J2EE clients) to communicate with external existing Enterprise Information Systems (EIS).
|
|
J2EETM CONNECTOR ARCHITECTURE
The J2EETM Connector Architecture, part of JavaTM 2 Platform, Enterprise Edition (J2EETM) 1.3, specifies a standard architecture for accessing resources in diverse Enterprise Information Systems (EIS). These may include ERP systems such as SAP R/3, mainframe transaction processing systems such as IBM CICS, legacy applications and non-relational database systems.
|