Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Anchortoptop
Enterprise Information Systems (EIS) transact enterprise level information that can be stored in various formats like ERP systems, databases, and mainframe systems. As more organizations move towards Internet-based businesses, integration between applications and these legacy heterogeneous EIS becomes necessary. But most EIS vendors and application server vendors use non-standard vendor-specific architectures to provide connectivity between application servers and EIS.

...

...

1.1.1 Connector deployment plan descriptor according to JEE connector 1.0

...

...

The DTD is available at http://java.sun.com/dtd/connector_1_0.dtd

1.1.2 Connector deployment plan descriptor according to JEE connector 1.5

...

The DTD is available at http://java.sun.com/xml/ns/j2ee/connector_1_5.xsdImage Removed

2.0 The Resource Adapter Geronimo Deployment Plan

...

A typical resource adapter deployment plan is been structured.

geronimo-ra.xml

...

Following are the main attributes defined in the above given code

xmlns The main namespace for the deployment plan, which should always be http://geronimo.apache.org/xml/ns/j2ee/connector-1.1Image Removed

xmlns:sys A secondary namespace, used to identify the common elements for common libraries and module-scoped services. If there are any of those present in the deployment plan, this attribute should be present, and should be set to http://geronimo.apache.org/xml/ns/deployment-1.1Image Removed

moduleId

Module IDs and dependencies are defined in the <environment> block of an XML file. Any application
or module can declare a module ID for itself using the moduleId element, and can declare dependencies
using the dependency element

...

Assuming the repository has a file repository/org/apache/derby/derby/10.2.2.0/derby-10.2.2.0.jar
, and the server has a JMS broker configuration called MessagingServer. A resource adapter could refer to them as follows

...

...

It's also possible to refer to the dependency using the split-up syntax, but the import cannot use that syntax because the module that's being imported did not use that syntax in its moduleId. That would look like as follows:

...

3.2. Resource Adapter Configuration

The main resource adapter configuration appears in the resourceadapter element. Note that you may deploy the same resource adapter more than once by specifying more than one resourcead-apter block. For example, in the case of the TranQL resource adapter used for JDBC connection pools, you could deploy several connection pools in the same deployment plan, by configuring each in a separate resource adapter section.

...

borderStylesolid

...

...

Different types of connectors use different child elements here. Each of those elements holds a number
of children for further configuration settings.

...

This section will use the http://cwiki.apache.org/GMOxDOC11/jms-and-mdb-sample-application.htmlImage Removed sample for the details of discussing the further in Resource Adapter.

...

...

3.2.1 A Resource Adapter Instance Configuration

...

resourceadapter-instance This element has dose several jobs.It gives the resource adapter a name to identify it,specify a WorkManager implementation for use with inbound resource adapters and provide values for the configuration properties specified in the resourceadapter element in the ra.xml deployment descriptor

...

The outbound resource adapter configuration is a complex topic.There are some important element to be configured in the deployment plan in order to have a external resource adapter in an application.

...

...

connection-definition This element holds all the information for a particular connection style (identified by the connectionfactory-interface). For example, if a certain resource adapter supported outbound connections using JDBC (with an interface of javax.sql.DataSource) and also a proprietary API (with a custom interface), there would be two connection definitions here, one for each interface style.

...

This code has been excerpt from the jms-resource-plan.xml from the http://cwiki.apache.org/GMOxDOC11/jms-and-mdb-sample-application.htmlImage Removed

...

adminobject-interface Matches the adminobject-interface specified for this adminobject type in ra.xml.

...

*Retrieves the content of one of the files.
The second module is a Web application that uses the adapter and provides online access to the files.

J2EE RAR Deployment Plan

...

...

J2EE RAR Geronimo v1.1 deployment plan

...

To deploy the adapter on Geronimo it's necessary to have a deployment plan specific to the geronimo server. Such a plan can be either named geronimo-ra.xml and be placed into the META-INF folder of the corresponding RAR archive, or can have any name and stay outside the archive. In the latter case, the path to the plan should be specified during the deployment of the resource adapter.Considering the above deployment plan let have a look in details.

...

The main resource adapter configuration appears in the resourceadapter element.This sample has only one resource adapter.As previously mentioned one can deploy the same resource adapter more than once by specifying more than one resourcead-apter block.As different connectors use different child elements, this sample has used Outbound Resource Adapters which is basically handled connections to external systems.Resource adapter level configuration properties are also set along the Repository Path.

...

...

This article is written to cover to give an basic knowledge of depcan be stored in various formats like ERP systems, databases, and mainframe systems. As more organizations move towards Internet-based businesses, integration between applications and these legacy heterogeneous EIS becomes necessary. But most EIS vendors and application server vendors use non-standard vendor-specific architectures to provide connectivity between application servers and EIS.