Server User Manual
Table Of Contents
- Developing Applications for J2EE™ Servers
- Contents
- Ch 1: Introduction
- Ch 2: Programming for the Java 2 Platform, Enterprise Edition
- Ch 3: Creating applications with J2EE technologies
- Ch 4: Configuring the target server settings
- Ch 5: Using JBuilder with Borland servers
- Configuring Borland servers in JBuilder
- Making the ORB available to JBuilder
- Configurations, partitions, partition services, and J2EE APIs
- Starting the configuration or server
- Remote deploying
- Remote debugging
- Web module workarounds
- Displaying the Borland Management Console in JBuilder
- International issues
- Borland servers and JDataStore 7.0
- Ch 6: Using JBuilder’s CORBA tools
- Ch 7: Using JBuilder with BEA WebLogic servers
- Ch 8: Using JBuilder with IBM WebSphere servers
- Ch 9: Using JBuilder with JBoss servers
- Ch 10: Using JBuilder with Tomcat
- Ch 11: Editing J2EE deployment descriptors
- Ch 12: Integrating with Enterprise Information Systems
- Ch 13: Building J2EE modules
- J2EE modules
- Setting module build properties
- Adding custom file types
- Sample build scenarios
- EJB JAR without any bean classes
- EJB JAR with custom files
- EJB JAR without EJB designer XML descriptors
- WAR with custom descriptor(s) in the WEB-INF directory
- WAR without any classes
- WAR with custom class filters
- WAR with custom file types
- EAR with custom files
- RAR with classes and dependencies
- Application client module with classes and dependencies
- Improving module build performance
- Index
Chapter 12: Integrating with Enterprise Information Systems 105
Chapter
12
Chapter 12Integrating with Enterprise
Information Systems
The J2EE Connector architecture addresses the problem of integrating Java enterprise
applications with existing Enterprise Information Systems (EIS). An EIS can be a
system such as ERP, CRM, and supply chain management applications and database
systems. Previously, if an enterprise application had to access information in an EIS,
some one had to build a custom connection between the application server and the
EIS.
Now the J2EE Connector architecture defines a uniform way to integrate J2EE
application servers with existing information systems. Each EIS vendor creates a
resource adapter using this architecture. A resource adapter is much like a JDBC
driver, as both provide a standard API through which an application can access a
resource that is outside the J2EE server. This resource adapter plugs into a J2EE
compliant application server. As long as the resource adapter follows the Connector
specification, it provides a scalable, secure, and transactional connection to an
application server.
To use a resource adapter for an application server, you can use JBuilder’s Connector
Module wizard, which creates the deployment descriptors for the resource adapter.
Then you use the Connector Module DD Editor to provide the information the resource
adapter needs to make the connection to the EIS.
Creating a connector module node in the project pane
To create a connector module, you use JBuilder’s Connector Module wizard. Besides
creating a new empty connector module, the Connector Module wizard also gives you
the option to copy an existing connector module to your project instead of creating a
new one. You can also use the wizard to create a module node in the project pane that
represents an existing module directory outside your project. Or you can use it to
create a module node that represents an archive (.rar) outside your project; you can
view the archive using the Connector Module DD Editor, but you won’t be able to edit it.