Adapters enable to integrate the BPEL process service component with access to file systems, FTP servers, database tables, database queues, sockets, Java Message Services (JMS), MQ, and Oracle E-Business Suite. This wizard enables to configure the types of adapters shown in below figure for use with the BPEL process service component −
The following image shows the different adapter types −
For interaction with a queue. AQ provides a flexible mechanism for bidirectional, asynchronous communication between participating applications.
For publishing data to data objects in an Oracle BAM Server.
For interaction with Oracle and non-Oracle databases through JDBC and Oracle Business Intelligence (which is a special data source type).
For file exchange (read and write) on local file systems and remote file systems (through use of the file transfer protocol (FTP)).
For interaction with JMS. The JMS architecture uses a one client interface to many messaging servers architecture.
For message exchange with WebSphere MQ queuing systems.
For interaction with Oracle Application's set of integrated business applications.
For browsing B2B metadata in the metadata service (MDS) repository and selecting document definitions.
For modeling standard or nonstandard protocols for communication over TCP/IP sockets.
The Service Name window prompts to enter a name, when the adapter type is selected from the pallet. For this example, File Adapter was selected. When the wizard completes, a WSDL file by this service name appears in the Application Navigator for the BPEL process service component (for this example, named ReadFile.wsdl). The service name must be unique within the project. This configuration file includes the adapter configuration settings specified with this wizard. Other configuration files (such as header files and files specific to the adapter) are also created. These files are displayed in the Application Navigator.