|
Java Connector Architecture: The Future of EAI?
Enterprise Application Integration (EAI) is difficult partly because there's no standard infrastructure for communicating with heterogeneous systems.If you're developing a customer support system that needs to integrate Siebel, SAP, and a host-based order processing system, you'll need a separate connector to communicate with each of these platforms. There's no widely accepted Java standard for connectors (like JDBC for database connectivity), so EAI developers working in Java have to write custom code for each connector.
|
|
Integrating EJB and COM Using the J2EE Connector Architecture
Enterprise JavaBeans (EJB) and Microsoft's Component Object Model (COM) are the two main competing standards for building distributed systems. Many enterprises, however, have both EJB- and COM-based applications. The task that developers in these organizations now face is getting these applications to communicate with one another, despite the competing standards.
|
|
Why You Need to Look at the J2EE Connector Architecture in 2001
Sun Microsystems' new Connector Architecture specification for the Java 2 platform, Enterprise Edition (J2EE) is important for everyone building Web applications using a J2EE application server.
|
|
J2EE Connector Architecture Promises to Simplify Connection to Back-End Systems
Sun recently released the proposed final draft of the J2EE Connector Architecture (JCA) 1.0, aimed at providing a standard way for back-end applications — e.g., enterprise resource planning (ERP), customer relationship management (CRM) and legacy systems — to plug into the J2EE platform. JCA, which was developed under the Java Community Process (JCP), will be part of the next version of J2EE, version 1.3, slated for early 2001. Although JCA 1.0 is missing some key functionality required in more complex integration situations, it marks an important step toward reducing the costs and burden of building high-value, Web-based applications.
|
|
Enterprise application integration with J2EE connectors
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. However, our experience shows that these claims are only partially realized. They overlook the needs of a complete and complex e-business solution, which requires integration with legacy data and enterprise information systems (EISs). Integration is a huge challenge, particularly because most e-commerce packages rely on third-party proprietary tools.
|
|
Making EAI Scale
We are running into a scalability roadblock in implementing enterprise application integration (EAI) solutions within many enterprises. EAI projects around the world are stalling, as EAI architects hit the upward limits of existing technology and architectures. This scalability problem has been the dominant theme of the application integration conferences I've been
|
|
NEON Announces Native Integration Capabilities for J2EE Java Developers
New Era of Networks, Inc. (Nasdaq: NEON ) a leading e-Business infrastructure provider, today announced the first in a set of new product offerings and a development vision for integrating J2EE application servers with a total e-Business environment.
|
|
J2EETM Connector Architecture
As more businesses move towards an e-business strategy, integration with existing Enterprise Information Systems (EIS) becomes the key to success. Enterprises with successful e-businesses need to integrate their existing EISs with new web-based applications. They need to extend the reach of their EISs to support business-to-business (B2B) transactions.
|
|
J2EETM CONNECTOR ARCHITECTURE BRINGS BUSINESS SYSTEMS TO THE WEB
August 2, 2000 -- The list is long: PeopleSoft. SAP R/3. IBM's CICS. Bull's GCOS. Legacy COBOL, RPG, and 4GL applications. IMS, VSAM, FOCUS, Pick, and other non-relational database systems. In a nutshell: enterprise information systems (EIS). The popularity of distributed Web and component-based JavaTM technology architectures notwithstanding, EIS such as these will remain strategic and entrenched in most global IT organizations for many years to come.
|
|
Differences Between JDBCTM Drivers and the J2EETM Connector Architecture Common Client Interface (CCI)
JDBCTM technology defines a standard client API for accessing relational databases. The J2EETM Connector Architecture CCI defines an EIS independent client API for EIS applications that are not relational databases. If access to an EIS is through a relational database, JDBC should be used. The J2EE Connector Architecture CCI comes into play for all other types of EIS integration.
|
|
ENTERPRISE COMPUTING ENTERS A NEW ERA
With the September 27th Beta release of the JavaTM 2 Platform, Enterprise Edition (J2EE), developers now have access to a complete development platform specifically architected to meet the needs of enterprise application development. J2EE makes all Java enterprise APIs and functionality available and accessible in a well integrated fashion, simplifying complex problems in the development, deployment, and management of multi-tier server-centric enterprise solutions. The J2EE platform exemplifies two familiar Java technology findings: (1) Open standards are better than closed, and (2) "Write Once, Run AnywhereTM" beats proprietary vendor-lock every time.
|