Creating an Adapter Not Specific to WebLogic Integration

 

The procedures for developing J2EE-compliant adapters outlined in Developing a Service Adapter, and Developing an Event Adapter, primarily pertain to adapters developed for use with WebLogic Integration. By making modifications to the steps described in that chapter, you can build an adapter compliant with the J2EE Connector Architecture specification but not WebLogic Integration-specific. This section describes those modifications.

This section contains information on the following subjects:

• Using this Section

• Building the Adapter

• Updating the Build Process

 

---

Using this Section

This section shows you how to modify the steps for developing a J2EE-compliant adapter in order to build one that is not specifically designed to run with WebLogic Integration. Each of the steps in this section will refer back to one of the steps described in Developing a Service Adapter, and describe how to modify that step. You should understand each of these steps thoroughly before proceeding with the modifications described below.

 

---

Building the Adapter

This procedure assumes that you have installed WebLogic Integration as described in Installing BEA WebLogic Integration.

1. Determine the development considerations as described in Step 1: Development Considerations in Developing a Service Adapter. Ignore the final bullet point that refers to transaction support. This is because WebLogic Server does not support local or XA transactions.

2. Run GenerateAdapterTemplate, as described in Creating a Custom Development Environment.

3. Assign the adapter logical name, as described in Step 2b: Assign the Adapter Logical Name.

4. Implement the SPI, as described in Basic SPI Implementation You must extend the following classes:

   • AbstractManagedConnectionFactory (see ManagedConnectionFactory).

   • AbstractManagedConnection (see ManagedConnection).

   • AbstractConnectionMetaData (see ManagedConnectionMetaData).

   As you implement these classes, note the following:

   • WebLogic Server does not support adapters that use transactional semantics.

   • Do not implement the ConnectionManager interface, as the adapters you are developing here are managed adapters; that is, they are designed to plug into WebLogic Server.

5. Extend AbstractConnectionFactory.

 

---

Updating the Build Process

In addition to the steps described in Building the Adapter you need to modify the build.xml file to create an adapter not specific to WebLogic Integration. To update the build process, do the following:

1. In your code editor, open the ADK's build.xml file.

2. Refer to Step 2c: Setting Up the Build Process. This step includes the section build.xml Components that breaks down the build.xml file into separate code listings.

3. Locate Listing 6-11 and Listing 6-12.

4. Remove everything in those listings from build.xml.