|
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.
|
|
Programming the J2EE Connector Architecture
BEA WebLogic Server continues to build upon the implementation of the Sun Microsystems J2EE Platform Specification, Version 1.3. The J2EE Connector Architecture adds simplified Enterprise Information System (EIS) integration to the J2EE platform. The goal is to leverage the strengths of the J2EE platform—including component models, transaction and security infrastructures—to address the challenges of EIS integration.
|
|
Overview of the WebLogic J2EE Connector Architecture
This document illustrates functionality defined in a non-final specification, J2EE 1.3. It requires you to run WebLogic Server with J2EE 1.3 features enabled. If you attempt to deploy the WebLogic Server Connector Architecture with the WebLogic Server 6.1 distribution that has J2EE 1.2 features only, the deployment will fail.
|
|
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).
|
|
Connect the enterprise with the JCA, Part 2
In this second article of two in his series on the JCA (J2EE Connector Architecture) -- a standard that allows J2EE (Java 2 Platform, Enterprise Edition) application servers to reach enterprise information systems (EIS) -- Dirk Reinshagen demonstrates a simple JCA adapter implementation. After you read this article, you'll possess a good understanding of how to build your own JCA adapter.
|