Adapters:

These are the components which will be interacting with the source system and with
the target systems in the integration process.
Major adapters that we work on

File adapter
FTP adapter
DB adapter
JMS adapter
Oracleapps adapter
Health adapter
HTTP binding adapter
Third party adapter

File adapter:
This will be used in-order to deal with the files with in the local system.
It will reads and writes the files with the local system
Options:
File adapter provides the following options

Read
Write
Synchronous read
List files

Read: This reads the data from a file

There are some options to be prompted while reading a file,
1. Do not read the content of data
2. Delete content once read
3. File streaming
Do not read the content: It will read the entire file and will not bother about the
content in the file
Read File as attachment: it will reads the file as an attachment.
File Streaming: it will helps to fragment the file in to number of parts to read
While reading the file it asks from where the file should be read. We will be
having two options for it
Say,

 Physical path
Logical name
Physical path: we have to give the actual location of the file in our system while
configuring the file adapter.
Logical path: we can give a dummy name while configuring and can give the
actual path at run time.

FTP adapter:
FTP stands for File Transfer Protocol.
The options and the functionality of both FILE and FTP adapters were same.
The major difference between these both adapters is, File adapter supports
only within the local system whereas FTP adapter supports with remote
servers.

DB adapter:
DB stands for Data Base
With this adapter we can interact with the databases of the systems that we
are integrating.
To work with database adapter we need to create JNDI connections at two
levels
JNDI: Java Naming Directory Interface.
1) Data source level
2) Deployment level

The data base adapter will provides the following options.

We have to select what-ever the operation we want to perform with the data
base adapter.
Note: we will be having options like insert or update, insert only, update only,
delete, select etc.., as the quires we write normally in our pl\sql.
There is no need to write any sort of query here; we can give an auto-query
option.
The JNDI connection should be like eis\db\connection name
The JNDI names should be same and with same cases at both the levels.

JMS adapter:
JMS: Java Messaging Service

 This adapter is used in-order to send or receive messages from the source or
target with security.
In-order to work with JMS adapter we need to create JNDI connections at three
levels .

1) Persistent storage level

2) Data source level
3) Deployment level
The options in JMS adapter
Consume message
Produce message
Request\Reply

Consume message: consumes the messages

Produce message: produces messages
Request\Reply: This gives request or reply based on the services.
Types of JMS services:
Queues
Topics
Queue: one-one messaging service
Topic: one-many messaging service
The JNDI connection should be same at the three levels and it should be
eis\jdbc\connection name.

Oracle-apps adapter:
To interact with oracle-apps system directly we can use this adapter.
It can be used only for the Oracle-apps system not to any other systems.

Health-adapter:
This is used to interact with the health care domains

HTTP Binding adapter:

The HTTP binding service enables you to integrate SOA composite applications with
HTTP binding.
There will be two operation types in this

 One-way
Request-response
One-way: A one-way operation that sends or receives messages to or from an HTTP
endpoint
Request-response: A synchronous request-response operation that sends and
receives input and output messages to and from an HTTP endpoint.
For HTTP POST request methods, you can select a payload type of either URLencoded (ampersand-separated name-value pairs) or XML.
For HTTP GET request methods, the payload type is URL-encoded.
For HTTP GET or POST request methods for reference binding components, you
are also prompted to specify the endpoint URL. Support for HTTP authentication and
secure socket layer (SSL) is also provided.

Third-party adapter:
We will be interacting with the third party systems with this adapter .