Managing adapters

Adapters provide the interface between workflow processes and external systems and applications. This section includes the following topics:

workflows use the following categories of adapters to communicate with external applications and systems:

Base adapters interface to systems by using standard protocols, such as JDBC, Telnet, SSH, JMS, and so on.
Application adapters interface to a specific product.

Within the base and application adapter categories:

Actor adapters interact with external systems, sending commands or requests and, in some cases, receiving responses to the requests. For example, an email actor adapter can be used to send an email message.
Monitor adapters listen on external systems and, based on their configuration, generate event messages. An email monitor adapter would monitor an email account on a specified server and generate an event when a specific message is received. This event could be used to trigger a process in a workflow.

Some application adapters require additional Java archive (JAR) files. The required JAR files are identified in the documentation specific to the adapter. If additional or alternate JAR files are required for proper adapter function, copy the files into the AO_HOME/lib/add-ons directory of each configuration distribution peer (CDP) server and any peer where this adapter will be enabled. Then restart the CDP and peer servers that contain the new JAR file.
Recommendation

Put the JAR file in the AO_HOME/lib/add-ons directory of each peer on the grid. If you enable the adapter on additional peers in the grid, the required files are already there.
Use Grid Manager to configure adapters to establish connections and facilitate communications. Adapters are also available in Development Studio so that you can use them when you are creating and testing processes.

Related topics