Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter 12.2.7 Predefined Transaction Services Documentation | Overview | Overview
 
Overview
 
Predefined Transaction Service Packages
Service Types
Packaging Structure
Document and Service Locations
Transaction Definitions
Updating Transaction Definitions
Database Scripts
Before Installing Components for Predefined Transaction Services on the Oracle Applications Database
Installing Components for Predefined Transaction Services on the Oracle Applications Database
Removing Components for Predefined Transaction Services from the Oracle Applications Database
Business Documents
Predefined transaction services are complete, ready-to-use flow services that you can use with the Oracle Apps Adapter to simplify the process of integrating with Oracle Applications systems. You can use the services after installing the services and defining your Oracle Applications system connection information.
There are three types of predefined transaction services used to communicate between Integration Server and Oracle Applications: Receive services, Query services, and Send services.
The Receive predefined transaction services enable Oracle Applications to receive data from Integration Server. These services provide the following:
*Required inputs and outputs for the services.
*Mapping and transformation between business documents and Oracle Applications.
*Supporting services that perform the data insertion, import (concurrent) process execution, and error handling.
The Query and Send predefined transaction services enable you to query or send data from Oracle Applications to the Integration Server. These services provide the following:
*Required inputs and outputs for the services.
*Combination of database triggers and polling services that provide notification capabilities from Oracle Applications to Integration Server.
*Supporting services to lock and unlock the webMethods process table, and to perform data selection from Oracle Applications to Integration Server and the processing acknowledgment from Integration Server back to Oracle Applications.
The following diagram shows in more detail how the Oracle Apps Adapter works with predefined transaction services.
*Oracle Apps Adapter. The adapter is delivered in a package named WmOAAdapter. The WmOAAdapter package includes:
*Administrative user interfaces to configure and manage different adapter connections. Using these interfaces you can:
*Configure the login parameters that Oracle Apps Adapter uses to establish a client connection with one or more Oracle Applications.
*Schedule a notification.
*Use built-in services to interact with Oracle Applications. The built-in services perform activities such as inserting and updating data, and managing database connections. The predefined transaction services wrap the built-in functions and make them accessible to Integration Server.
*Predefined Transaction Service Packages. The predefined transaction services are delivered in separate packages. Each package contains a set of services for a particular Oracle Applications module and version of Oracle Applications. These packages contain the following types of predefined transaction services:
*Receive services, which deliver data to the Oracle Applications open interface tables for insertion into the production tables.
*Query services, which query the Oracle Applications production tables and return business documents that match the query criteria.
*Send services, which return business documents to Integration Server according to polling intervals. Send services rely on custom webMethods components such as triggers and custom tables to capture business events on the Oracle Applications production tables, and then send the business documents to Integration Server.
*Open Interface Tables and Production Tables. The predefined transaction services interact with the Oracle Applications open interface tables and production tables to send or receive business documents. Receive, send, and query services interact with these tables differently.
*webMethods Custom Components. The predefined transaction services use a combination of triggers, stored procedures, custom tables, views, and sequences (depending on the type of service) to interact with the Oracle Applications open interface tables and production tables.
This chapter describes the predefined transaction services, including how they are packaged, and how you use them to receive data into, or send data from, Oracle Applications systems.
The information in this chapter is intended to help you understand the basic design and functionality of any of the predefined transaction services. After you read this chapter, you can use the information provided in the other chapters of this guide to implement any of the predefined transaction services.