Tools

 

The ADK provides a robust set of tools to assist you in developing adapters and the design-time GUI.

This section includes information on the following subjects:

• Sample Adapter

• The GenerateAdapterTemplate Utility

• ADK Javadoc

• Ant-Based Build Process

• XML Tools

 

---

Sample Adapter

The ADK contains a sample adapter that provides non-EIS specific code examples to help you start building an adapter. Do not confuse this sample adapter with the e-mail and DBMS adapters also included with WebLogic Integration; these adapters are documented in The DBMS Adapter, and The E-mail Adapter. You can find them in WLI_HOME/adapters/dbms and WLI_HOME/adapters/email.

Why Use the Sample Adapter?

The purpose of the sample adapter is to free you from much of the coding necessary to build an adapter. It provides concrete implementations of key abstract classes that only require customization for your specific EIS. In addition, the ADK provides the GenerateAdapterTemplate utility with which you can quickly clone the sample adapter development tree for use by the adapter you are developing. See The GenerateAdapterTemplate Utility.

What's In the Sample Adapter

Specifically the sample adapter contains:

sample.cci.ConnectionImpl

A concrete implementation of the Connection interface that represents an application-level handle used by a client to access the underlying physical connection.

sample.cci.InteractionImpl

A class that demonstrates how to implement a design pattern using the DesignTimeInteractionSpecImpl class.

sample.cci.InteractionSpecImpl

An interface that provides a base implementation for you to extend by using getter and setter methods for the standard interaction properties

sample.client.ApplicationViewClient

A class that demonstrates how to invoke a service and listen for an event on an application view.

sample.eis.EIS
sample.eis.EISEvent
sample.eis.EISListener

These are classes that represent for demonstration purposes, a simple EIS.

sample.event.EventGenerator

A concrete extension to AbstractPullEventGenerator that shows how to extend the ADK base class to construct an event generator.

sample.event.OfflineEventGeneratorTestCase

A class you can use to test the inner workings of your event generator outside of Weblogic Server.

sample.spi.ManagedConnectionFactoryImpl

A concrete extension to AbstractManagedConnectionFactory that you can customize for a specific EIS.

sample.spi.ManagedConnectionImpl

A concrete extension to AbstractManagedConnection that you can customize this class for a specific EIS.

sample.spi.ConnectionMetaDataImpl

A concrete extension to AbstractConnectionMetaData that you can customize for a specific EIS.

sample.spi.NonManagedScenarioTestCase

A class you can test your SPI and CCI classes in a non-managed scenario.

sample.web.DesignTimeRequestHandler

A concrete extension to AbstractDesignTimeRequestHandler that shows how to add an event or service at design time.

Note: For more details on the classes extended by those in the sample adapter, please refer to the ADK Javadocs.

 

---

The GenerateAdapterTemplate Utility

To facilitate using the sample adapter, the ADK provides GenerateAdapterTemplate, a command-line utility you can use to clone the sample adapter development tree and create a new adapter development tree. See Creating a Custom Development Environment, for complete instructions on using this tool.

 

---

ADK Javadoc

ADK classes, interfaces, methods, and constructors are defined in the development kit's Javadocs. Javadocs are included with the WebLogic Integration installation and are stored in WLI_HOME/adapters/ADAPTER/docs/api, where ADAPTER is the name of the adapter, such as Sample, DBMS, or e-mail; for example, WLI_HOME/adapters/dbms/docs/api.

 

---

Ant-Based Build Process

The ADK employs a build process based upon Ant, a 100% pure Java-based build tool. For the ADK, Ant does the following:

• Creates a Java archive (.jar) file for the adapter.

• Creates a .war file for an adapter's Web application.

• Creates a .rar file for a J2EE-compliant adapter.

• Encapsulate the above listed components into a .ear file for deployment.

Why Use Ant?

Traditionally, build tools are inherently shell-based. They evaluate a set of dependencies and then execute commands, not unlike those you would issue on a shell. While it is simple to extend these tools by using or writing any program for your operating system, you are also limited to that OS, or at least that OS type (for example, Unix).

Ant is preferable to shell-based make tools for the following reasons:

• Instead of a model where it is extended with shell-based commands, it is extended using Java classes.

• Instead of writing shell commands, the configuration files are XML-based, calling out a target tree where various tasks get executed. Each task is run by an object that implements a particular task interface. While this removes some of the expressive power inherent in being able to construct a shell command, it gives your application the ability to be cross-platform.

• If you want to execute a shell command, Ant has an execute rule that allows different commands to be executed based on the OS upon which it executing.

For complete instruction on setting up Ant, see Step 2c: Setting Up the Build Process.

 

---

XML Tools

The ADK ships with two XML development tools, which are considered part of the metadata support layer for the design-time framework. These tools, which comprise the XML Toolkit, are:

• XML Schema API—Characterized by the Schema Object Model (SOM), this API is used to programmatically build XML schemas. The SOM is a set of tools that extracts many of the common details, such as syntactical complexities of XML schema operations so that you can focus on its more fundamental aspects.

• XML Document API— Characterized by IDocument, this API provides the x-path interface to a document object model (DOM) document.

For instructions on using these tools, refer to XML Toolkit.

Also, your installation of WebLogic Integration includes Javadoc on both of these APIs.

• For SOM, go to WLI_HOME/docs/apidocs/com/bea/schema

• For IDocument, go to WLI_HOME/docs/apidocs/com/bea/document