how does the oracle as adapters fit into the service ......how does the oracle as adapters fit into...

How does the Oracle AS Adapters fit into the Service Oriented Architecture (SOA)

Oracle AS Adapters – 10.1.2 – FAQ Author : Meera Srinivasan (Product Manager) Date:03/23/05 1 Introduction

1.1.1 What is the product?1.1.2 What are the list of Adapters available with the Oracle AS 10.1.2 releases?1.1.3 How is the product sold?1.1.4 What are the benefits and how does it differ from the competitive products?1.1.5 How is it integrated to other product components of the integration stack?1.1.6 What are the standards supported in the product?1.1.7 Which editions of Oracle Application Server include the product?1.1.8 Is the Oracle Database required to run the product?1.1.9 Is the Oracle Application Server platform required to run the product?1.1.10 What are the Oracle AS product components that are integrated with this product?1.1.11 What are the interfaces that supported in the various Adapters for release 10.1.2.0.1?1.1.12 What are the hardware and software requirements?

1.2 Availability1.2.1 How can I download the product component?1.2.2 Where can I find documentation on this product?1.2.3 What’s new in the latest release?

1.3 Adapter SDK1.3.1 What is the architecture of Adapter Framework?1.3.2 Is there an Adapter SDK?1.3.3 Is JCA/Adapter SDK the only way to integrate with BPEL PM?1.3.4 What is the nature of the WSDL required by the Adapter SDK?

1.4 Features& Functionality1.4.1 How does the Oracle AS Adapter integrate with the BPEL Process Manager product?1.4.2 How do the Oracle AS Adapters fit into the Service Oriented Architecture (SOA)?1.4.3 Do the Oracle AS Adapters support Unicode?

1.5 Adapter Partners1.5.1 How do we achieve connectivity to over 300+ backend applications?

2 Oracle AS Adapters for Technology2.1 General

2.1.1 What is the list of technology Adapters?2.1.2 Does the technology Adapters support WSDL/SOAP interface?

2.2 Database Adapter2.2.1 What are the salient features of the Database Adapter?

file:///C|/Adapters/fol/product_mgmt/FAQ/Oracle%20AS%20Adapters%20FAQ_OTN.htm (1 of 33)6/17/2005 9:10:39 AM


2.2.2 What are the various databases supported by Oracle AS Adapter for Databases?2.2.3 What are the benefits of using the Oracle AS Adapter for Databases?2.2.4 What are the various strategies available for publication of database events?2.2.5 What are the various Destructive Publish Strategy options?2.2.6 Does the Database Adapter supports join across Views?

2.3 AQ Adapter2.3.1 What are the operations supported by the AQ Adapter?2.3.2 What are the different AQ payloads supported by the Adapter?2.3.3 Does the Adapter support AQ Headers?2.3.4 Does the AQ Adapter support multi-consumer queues?2.3.5 Does the AQ Adapter support native correlation? How can I mimic a request-response scenario using the above?2.3.6 How can I configure the Adapter Consumer component to selectively dequeue messages ?

2.4 JMS Adapter2.4.1 What is the version of the JMS specification supported by the Adapter?2.4.2 What are the list of JMS Providers certified against this adapter?2.4.3 Does the JMS Adapter support Durable Subscriptions?2.4.4 How does the JMS Consumer receive messages from JMS Topics and Queues?2.4.5 Does the Adapter support JMS Transactions?2.4.6 How do I create a JMS Transacted Session ?2.4.7 What are the various JMS acknowledgement modes and how do I set it for the JMS Adapter?2.4.8 What is the value add of the Adapter Translator in the JMS Adapter design-time wizard?2.4.9 What are JMS Headers? Does the Adapter support JMS Headers? How can I manipulate the JMS Headers ?

2.5 Oracle AS Adapter Translator – Native Format Builder & Translator2.5.1 What is the Adapter Translator (nXSD)?2.5.2 Is nXSD applicable to File Adapter only?2.5.3 Please list the native data formats that are currently supported by nXSD?

3 Oracle Adapters for Packaged Application3.1 OracleAS Adapter for J.D. Edwards OneWorld

3.1.1 What are the J.D. Edwards versions supported by the adapter?3.1.2 What are the integration points for the J.D. Edwards adapter?3.1.3 What APIs, library files, and DLLs are required for the adapter (including third party software)?3.1.4 What are the setups and/or configurations required for the adapter?3.1.5 Can you browse and/or generate XML schemas?3.1.6 Does the adapter supports connection pooling?3.1.7 Does the adapter supports load balancing?3.1.8 What are the security features for the adapter?3.1.9 Does the adapter provide delivery confirmations and error messages?3.1.10 What are the advantages of the J.D. Edwards adapter?

3.2 OracleAS Adapter for PeopleSoft



3.2.1 What are the PeopleSoft versions supported by the adapter?3.2.2 What are the integration points for the PeopleSoft adapter?3.2.3 What is Peoplesoft Integration Broker?3.2.4 What APIs, library files, and DLLs are required for the adapter (including third party software)?3.2.5 What are the setups and/or configurations required for the adapter?3.2.6 Can you browse and/or generate XML schemas for component interfaces and messages?3.2.7 Does the adapter supports connection pooling?3.2.8 Does the adapter provide delivery confirmations for the inbound services?3.2.9 Does the adapter supports custom component interfaces?3.2.10 Does the adapter support custom messages (events)?

3.3 OracleAS Adapter for SAP3.3.1 What SAP systems does the adapter support?3.3.2 What external libraries are required in addition to the adapter are required?3.3.3 How does the adapter connect to SAP?3.3.4 How does the adapter manage security?3.3.5 How can I browse the list of objects and create schemas?3.3.6 How can I switch on connection pooling in the adapter?3.3.7 How do I load balance my adapter?3.3.8 How many connections are possible through the adapter?3.3.9 What happens if the SAP server is down?3.3.10 How can I be sure my transactions complete?3.3.11 Can I develop custom objects?

3.4 OracleAS Adapter for Siebel3.4.1 What are the Siebel versions supported by the adapter?3.4.2 What are the integration points for the Siebel adapter?3.4.3 What APIs, library files, and DLLs are required for the adapter (including third party software)?3.4.4 What are the setups and/or configurations required for the adapter?3.4.5 Can you browse and generate XML schemas for all Siebel Business Objects and integration object messages?3.4.6 Does the adapter supports connection pooling?3.4.7 Does the adapter supports custom business services?3.4.8 Does the adapter support custom integration object messages (events)?

4 Oracle AS Adapters for Mainframes & Legacy Applications4.1.1 Describe the architecture of the Oracle AS Adapters for mainframes?4.1.2 What are the different ways to integrate with IMS/DB?4.1.3 How does the Oracle AS Adapter for IMS/DB integrate with the IMS/DB datastore?4.1.4 What are the different ways of integrating with IMS/TM?4.1.5 How does the Oracle AS Adapter for IMS/TM integrate with IMS/TM?4.1.6 How does the CICS Adapter integrate with the CICS application?4.1.7 What are the different APIs available to integrate with CICS?4.1.8 What are the different transports available to integrate with CICS?



4.1.9 Does the Oracle AS Adapter support CICS transactions?4.1.10 How does the Oracle AS Adapter for CICS publish a CICS event?4.1.11 How does the Oracle AS Adapter for Tuxedo integrate with Tuxedo?

1 Introduction

1.1.1 What is the product?

As more businesses move towards business process optimization, integration with existing Enterprise Information Systems (EIS) efficiently becomes the key to success . These EIS applications are heterogeneous, come from different vendors and are based of different technologies and run on different platforms. These EIS systems can be packaged, legacy and mainframe applications, databases, messaging middleware, web applications, file systems distributed throughout the enterprise and these need to integrated seemlessly to achieve cost savings. The Oracle AS Adapters provide a truly flexible, highly scalable, real-time, bi-directional standards based connectivity platform to over 300+ backend applications.

1.1.2 What are the list of Adapters available with the Oracle AS 10.1.2 releases?

Oracle AS Adapters is a component of the Oracle Application Server Integration Stack.The following list of Adapters are part of the Oracle AS Integration stack.

● Technology ❍ Files/FTP❍ DB ❍ JMS❍ AQ

● Packaged Application❍ Oracle Applications ❍ SAP❍ Siebel❍ Peoplesoft❍ JDE

● Legacy & Mainframes ❍ CICS❍ IMS/TM & IMS/DB❍ Tuxedo❍ VSAM

Oracle provides connectivity to over 300+ backend applications via partnerships with best-of-breed Adapter Vendors.

1.1.3 How is the product sold?



The Oracle AS Adapter for Databases, Files, JMS, AQ and Oracle Applications are bundled as part of the BPEL PM product. The Oracle AS Adapters for Legacy & Packaged Applications are part of the Oracle AS Adapters CD. To purchase Oracle AS Adapters, please contact your Oracle sales representative, Oracle reseller, or access the Oracle Store.

1.1.4 What are the benefits and how does it differ from the competitive products?

The benefits of using Oracle AS Adapters are manifold and listed below: The Oracle AS Adapters support bi-directional and real-time connectivity to over 300+ backends. The Oracle AS Adapters are based on the JCA 1.5, Web Service, WSIF standards and do not have any proprietary interfaces. The Oracle AS Adapters are seemlessly integrated with other Oracle AS product components through the Adapter Framework (AF). Any standard JCA 1.5 Resource Adapter can be seemlessly integrated with the Adapter FW with minimal effort . This reduces the time to comprehend and implement custom Adapters. Customers are not tied to any Adapter Vendor and are free to choose best of breed connectivity solutions that meet their requirements. The Adapters are aligned with the Service Oriented Architecture and are used to create composite services in conjunction with Oracle BPEL Process Manager. The Adapter metadata are exposed as Services and expressed as XSD/WSDL. The Adapter SDK provides tools and documentation to integrate the JCA 1.5 Resource Adapter with the Adapter Framework. The Adapters supports an easy-to-use wizard for dynamically introspecting and generating the metadata. Configuration is metadata driven and no coding is required. The Adapters can be hot deployed at design-time and support non-managed JCA deployment for development purposes. The Adapter wizards are currently available on top of Oracle JDeveloper but will also support Eclipse shortly. The Adapters support other non-Oracle J2EE servers and will be certified with BEA Weblogic, IBM Websphere and JBoss. The Adapters are light-weight and fully utilize the underlying Oracle AS platform system services such as connection management, scalability, thread management, security management and high availability. The Adapters support both BPEL and Oracle AS clusters for scalability. The Adapter Framework provides sophisticated error management and supports a variety of message rejection handlers for error repair in the case of data translation errors The Adapter Framework provides a Stop Watch feature to collect performance statistics across Oracle AS Adapters that can be viewed from the BPEL Console.


http://oraclestore.oracle.com/


The JCA 1.5 Adapters can be deployed on top of a JCA 1.0 Container. The Adapter Framework behaves as a pseudo JCA 1.5 container for overcoming lack of JCA 1.5 support in the underlying J2EE container. Select set of Adapters provide batching capabilities for high performance and throughput. Oracle provides one stop shop for connectivity requirements via partnerships with best-of-breed Adapter Vendors.

1.1.5 How is it integrated to other product components of the integration stack?

The Adapter Framework (AF) is used to integrate the JCA based Adapters to various Oracle AS product components. It exposes the underlying JCA Outbound interactions as Services that can be called from other Oracle AS product components. It also exposes the underlying JCA Inbound Interaction as an “Event” Service for publishing backend events to other Oracle AS product components.

1.1.6 What are the standards supported in the product?

The Oracle AS Adapters support a variety of standards at both design-time and run-time.They are:

(1) XSD, WSDL : for defining Adapter metadata(2) JCA : Adapter run-time is a JCA 1.5 Resource Adapter(3) WSIF : The Adapter Framework is a WSIF JCA Provider that translates Web Service messages to JCA Interactions and back.(4) WSIL: This technology is used at design-time to discover and browse the Adapter WSDLs defined using the Adapter design-time tool.(5) XML : This is the internal data representation of Adapters

1.1.7 Which editions of Oracle Application Server include the product?

The Oracle AS Adapters for packaged, legacy and mainframe applications are bundled on a separate Oracle AS Adapters CD. The Oracle AS Adapters for Technology and Oracle Applications are bundled with the BPEL Process Manager product.

1.1.8 Is the Oracle Database required to run the product?

No. The Oracle Database is not required to run this product.



1.1.9 Is the Oracle Application Server platform required to run the product?

The Oracle AS Adapters are deployed on top of either a stand-alone OC4J or Oracle AS platform (midtier – J2EE and web cache). They will also be supporting BEA Weblogic, JBoss and IBM Websphere deployments shortly.

1.1.10 What are the Oracle AS product components that are integrated with this product?

The Oracle BPEL Process manager, Oracle BAM, Oracle InterConnect, Oracle Portal and J2EE applications have been certified for integration with Oracle AS Adapters. Further, since the Adapter Services are based on JCA/Web Service standards, they are callable from any standard JCA or Web Service client application.

1.1.11 What are the interfaces that supported in the various Adapters for release 10.1.2.0.1?

The Adapter Services can be expressed as either

(1) JCA(2) WSDL/JCA(3) WSDL/SOAP

1.1.12 What are the hardware and software requirements?

The Oracle AS Adapters are deployed on top of standard J2EE application servers. Their hardware and software requirements are dictated by the underlying J2EE Server platform requirements.

1.2 Availability

1.2.1 How can I download the product component?

http://www.oracle.com/technology/software/products/ias/devuse.html

1.2.2 Where can I find documentation on this product?

http://www.oracle.com/technology/products/ias/bpel/htdocs/1012_support.html#docs


http://www.oracle.com/technology/software/products/ias/devuse.html

http://www.oracle.com/technology/products/ias/bpel/htdocs/1012_support.html#docs


1.2.3 What’s new in the latest release?

The Oracle AS Adapters are based of the JCA 1.5 standards in Oracle AS 10.1.2 release unlike the JCA++ proprietary APIs in Oracle AS 9.0.4 release. Other distinguishing features of this release are:

● Alignment with Service Oriented Architecture (SOA) through the adoption of open standards.● One set of Adapters for Oracle AS product components. Integration with BPEL PM, InterConnect,

BAM, Portal and J2EE applications● Enhanced, JCA based Technology Adapters – Files, FTP, Database, AQ and JMS● Connectivity to over 300+ backend applications via partnerships with best-of-breed Adapter Vendors.● Adapter Framework based on WSIF standards and light-weight Adapter SDK.● Scalability through BPEL clusters and Oracle AS clusters● Support for Oracle JDeveloper and IBM Eclipse IDE● Support for standard J2EE servers – Oracle Application Server, BEA Weblogic, IBM Websphere and

JBoss

1.3 Adapter SDK

1.3.1 What is the architecture of Adapter Framework?

The Adapter Framework (AF) seamlessly integrates a JCA 1.5 Resource Adapter with BPEL Process Manager, InterConnect and other Oracle Application Server product components. It employs the Web Service Invocation Framework (WSIF) technology for the above purpose. It exposes the underlying JCA Interactions as Web Services. It requires the Adapter run-time metadata to be exposed as a Service and expressed as WSDLs. The AF also acts as a pseudo JCA 1.5 container for deployment on top of JCA 1.0 only J2EE containers.

1.3.2 Is there an Adapter SDK?

Yes. There is a light-weight Adapter SDK to build custom adapters. There are 2 steps to required to integrate any standard JCA 1.5 Adapter with Oracle AS product components. They are (1) Generate WSDL with JCA extension at design-time (2) Implement the Oracle XMLRecordConverter interface to translate from JCA Record implementation of Vendor to Oracle XMLRecord implementation. This is a simple interface with get/set methods for translating between the 2 formats. The Adapter SDK consists of a cookbook, a custom wizard for generating WSDL over JCA extensions at design-time, sample XML Record Converter class and sample File Adapter source code.

1.3.3 Is JCA/Adapter SDK the only way to integrate with BPEL PM?

No. You could also wrap up your custom Adapter as a Service with WSDL over SOAP/JAVA/JMS/HTTP binding as opposed to JCA binding. BPEL Process Manager has a comprehensive WSIF binding framework that supports the above mentioned bindings. The Adapter SDK is not needed in this case. The JCA 1.5 approach supports bi-directional connectivity, is performant and leverages the underlying J2EE container



for system contracts for scalability & HA.

1.3.4 What is the nature of the WSDL required by the Adapter SDK?

The Adapter SDK requires the WSDL to have a set of JCA extension elements and these are clearly described in the Adapter SDK cookbook. These JCA extension elements contain details on InteractionSpec, JNDI name for the JCA Outbound Interaction and the ActivationSpec and Resource Adapter Class Name for the JCA Inbound Interaction.

1.4 Features& Functionality

1.4.1 How does the Oracle AS Adapter integrate with the BPEL Process Manager product?

The Oracle AS Adapters integrate with BPEL PM via the Adapter Framework (AF) component. The Oracle AS Adapters are based on JCA 1.5 standards and are deployed in the J2EE container. The Oracle AS Adapters run-time functions are exposed as Services and expressed as WSDLs. The Adapter FW employs the Web Service Invocation Framework (WSIF) standard to expose the JCA Interactions as Web Service to the BPEL process and has a WSIF JCA Provider for the above purpose. The WSIF Provider element hides the JCA implementation details from the BPEL PM process and the Web Service aspect from the JCA Resource Adapter. The BPEL PM can also receive the backend events from the JCA 1.5 Resource Adapter via the AF. The AF also plays the role of a JCA 1.5 container and implements the JCA 1.5 specific system contracts for J2EE containers that do not support the JCA 1.5 specification.

1.4.2 How do the Oracle AS Adapters fit into the Service Oriented Architecture (SOA)?

Oracle AS Adapters are aligned with the Service Oriented Architecture through the adoption of Open standards – JCA 1.5, WSIF XML and WSDL. The adapter run-time features are exposed as Services and expressed as WSDLs. Each adapter service is a self-contained, self-describing, modular application with well-defined interface.

1.4.3 Do the Oracle AS Adapters support Unicode?

All Oracle AS Adapters are unicode compliant and support a wide variety of encodings at run-time.



1.5 Adapter Partners

1.5.1 How do we achieve connectivity to over 300+ backend applications?

We partnership with proven Adapter Vendors to provide best of breed connectivity to over 300+ backend applications. The Partner certification has become highly simplified and cost-effective as the Oracle Adapter Framework is based on standards. The current Adapter partner list is as follows:

● iWay Software : http://www.iwaysoftware.com/● Attunity Software: ·http://www.attunity.com● Fujitsu : http://www.fujitsu.com/● Neon Systems: http://www.neonsys.com/● Librados : http://www.librados.com/● GT Software : http://www.gtsoftware.com/support/index.php● Pervasive :http://www.pervasive.com/● Aepona:http://www.aepona.com/● ItemField:http://www.itemfield.com/

2 Oracle AS Adapters for Technology

2.1 General

2.1.1 What is the list of technology Adapters?

The following list of technology Adapters are available with this release:-

● Files● FTP● Databases● AQ● JMS

2.1.2 Does the technology Adapters support WSDL/SOAP interface?


http://www.iwaysoftware.com/

�http://www.attunity.com/

http://www.fujitsu.com/

http://www.neonsys.com/

http://www.librados.com/

http://www.gtsoftware.com/support/index.php

http://www.pervasive.com/

http://www.aepona.com/

http://www.itemfield.com/


No. These adapters do not support WSDL/SOAP integration. The technology adapters are based of JCA 1.5 specification. The current version of the Adapter SDK exposes the underlying JCA interactions as Services (WSDL/JCA). The WSDL/SOAP and the JMS Support are expected in a future release.

2.2 Database Adapter

2.2.1 What are the salient features of the Database Adapter?

The Oracle AS Adapter for Database is based on Toplink technology, the proven, powerful “out-of-the-box” solution for Object to Relational mapping. It is the #1 Java object-to-relational persistence framework.

● The Adapter provides the ability to map information from relational database tables to XML. Application developers work with objects, rather than rows and SQL using JDBC calls.

● The Adapter can connect to a variety of databases through JDBC and supports JDBC versions 1.x to 2.0● It is capable of performing a variety of Data Manipulation operations such as INSERT, UPDATE,

DELETE, UPSERT, WRITE and MERGE. ● It has a rich and robust query framework.

❍ It is capable of executing complex queries that can span across multiple tables. ❍ It supports Query operations such as outer joins and sub-selects. ❍ In addition, it supports Query by Example that enables the “Where” clause of a “SELECT”

statement to be generated dynamically at run-time.● The Adapter supports arbitrarily complex object models and can span across tables and automatically

maintains references between objects. In addition, one can add/drop constraints at the object level .● The Adapter has a Jdeveloper based, easy to use design-time. At design-time, the Adapter browses the

underlying database tables and dynamically creates a set of meta-data “descriptors”, or mappings, that defines how objects are to be stored in a particular database schema. It uses these mappings at run-time to dynamically generate the required SQL statements. No SQL programming is required. No changes to the underlying database schema is required. The meta-data descriptors (mappings) are independent of both language and database and are expressed as XSD. Changing the database schema just requires regenerating the mappings using the design-time tool.

● The Adapter is capable of capturing database changes or events and offers multiple ways of publishing the event data ranging from simple and intrusive to sophisticated and non-intrusive.

● The Adapter is capable of invoking a Stored Procedure or Function. The current version supports only Oracle Stored Procedures and Functions. The StoredProcedure implementation is not based on the TopLink technology.

● The underlying TopLink project is fully accessible, enabling you to tap into TopLink’s mature feature set. You can use the OracleAS TopLink Mapping Workbench interface for advanced mapping and configuration, sequencing, batch and joined relationship reading, batch writing, parameter binding, statement caching, connection pooling, external transaction control (JTS and JTA), UnitOfWork for minimal updates, caching and optimistic locking,



2.2.2 What are the various databases supported by Oracle AS Adapter for Databases?

The Adapter is capable of integrating with all JDBC Provider supported databases. The underlying Toplink technology can communicate with any relational database that has a JDBC-compliant driver available such as Oracle, IBM Universal Database, IBM Informix, IBM Cloudscape, Microsoft SQL Server, Microsoft Access, and Sybase Adaptive Server. TopLink supports both the JDBC 1.x and 2.0 standards. The Stored Procedure support (not based on TopLink) is available for Oracle databases only in the upcoming BPEL PM 10.1.2.0.0 release.

2.2.3 What are the benefits of using the Oracle AS Adapter for Databases?

The Database Adapter uses the TopLink technology for performing XML objects to relational mapping. The user is shielded from having to write SQL statements and conversion logic between database rows and XML objects. In addition the user is shielded from having to integrate transactions, queries, caching, locking, sequencing and other key database concepts into their applications. Also, the Database Adapter offers multiple ways of publishing the database events in real-time ranging from simple to sophisticated and non-intrusive.

2.2.4 What are the various strategies available for publication of database events?

The Adapter polls a set of database tables to capture and publish the underlying database table changes. This is also referred as JCA Inbound Interaction. The Adapter offers various ways of publishing a database event ranging from simple and intrusive to sophisticated and non-intrusive. The choice of a particular publish strategy depends on the user restrictions. For example, one of the strategy that is offered is “physical deletes” in which the records are deleted once processed. The Adapter must have write privileges for the above publish strategy and will not work if there is a non-intrusive requirement. The following pre-conditions determine the choice of the publish strategy:

● Delete privilege on the source table● Logical delete on the source table. The schema of the source table might have to be altered to add a

“status” column.● Ability to attach triggers to the source table● Presence of a sequencing column in the source table● Non-intrusive requirements where source table rows cannot be altered or deleted● Ability to create a control table for the source table● Concurrent polling on the same table by multiple Adapter threads or instances



The publish strategies can be grouped as follows:-

● Destructive and Intrusive - Destructive strategy can be used only in cases where an event is a one-time occurrence and the data stored in in the database is only required for the event. In this case, after the event is raised, the data is no-longer required in the database and can be removed (either physically or logically).

• Non-destructive and Non-Intrusive – This does not alter the data in the database. Non-destructive reads are required for systems where data may not be altered in the database for some reason.

2.2.5 What are the various Destructive Publish Strategy options?

Strategy Pre-conditions FeaturesPhysical Delete - This strategy polls the database table for records and deletes them after processing.

The user must have delete privileges on the parent and associated child tables.

This strategy can be used to capture events related to “Insert” operations and cannot capture Database events related to “Delete” and “Update” operations on the Parent table. This strategy cannot be used to poll child table events. This strategy allows multiple Adapter instances to go against the same source table. There is zero data replication and it works out of the box.

Logical Delete - The user must have logical delete privilege or a one-time alter schema (add column) privilege on the source table.

The user must have update privileges on the parent and associated child tables

This strategy can be used to capture events related to “Insert” and “Update” operations but cannot capture events related to “Delete” operation on the Parent table. This strategy can be used to poll child table INSERT and UPDATE events as well. The Update operation requires the creation of trigger. This strategy allows multiple Adapter instances to go against the same source table. There is zero data replication and requires minimal configuration.



Sequence Last Read ID

The Sequence Polling Strategy involves using a helper table to remember a sequence value. A sequence value of 1000 means that every record with a sequence less than that value has been processed already. A File can also be used to store the LastReadID instead of a helper table.

The table must have a sequentially increasing column.

This strategy can be used to capture events related to “Insert” and “Update” operations but cannot capture events related to “Delete” operation on the Parent table. There is zero data replication and requires minimal configuration.

Sequence LastUpdated – In this case, the sequence column contains a time stamp. This strategy involves using a helper table to remember a last_updated value. A last updated value of 2005-01-01 12:45:01 000 means that every record last updated on that time or earlier has been processed already.

The table must have a sequentially increasing timestamp column.

This strategy can be used to capture events related to “Insert” and “Update” operations but cannot capture events related to “Delete” operation on the Parent table. Since many tables have rows with a last_updated or creation_time column maintained by triggers or the application, this strategy can be used often and for non-invasive polling. No fields on the processed row ever need to be modified by the adapter.

Control Table Delete - The Control Table Polling Strategy involves using a control table to store the primary key of every row which has yet to be processed. With a natural join between the control table and the source table (by primary key), polling against the control table is practically the same as polling against the source table directly. However, there is an extra layer of indirection that allows the following:

Destructive polling strategies like the Physical Delete Polling strategy and Logical Delete Polling Strategy can be applied to rows in the control table. alone, while shielding any rows in the source table.

Streams and Materialized View Logs make good control tables.

Only rows which are meant to be processed will have their primary key appear in the control table. The entire row is not being copied to some interface table, and any structure under the source table like detail rows can be raised also without copying.



2.2.6 Does the Database Adapter supports join across Views?

The Database Adapter supports join across Views at run-time but not at design-time. The design-time throws an error when a join is performed against Views. The following workaround is suggested to overcome the above design-time issue. Workaround: Create the equivalent tables in a temporary schema (creating the corresponding constraints in the schema is optional since our design time allows to create relationships that are not present in the underlying database). At design-time, point to this temporary schema and import the tables instead of views. Subsequently, point the run-time connection parameters to the schema containing the desired views. Only “Selects” are recommended with this approach.

2.3 AQ Adapter

2.3.1 What are the operations supported by the AQ Adapter?

The Adapter supports the Enqueue and Dequeue of AQ messages. The Adapter is both a Producer (Enqueue) and Consumer (Dequeue) of AQ messages. The enqueue operation is exposed as JCA Outbound Interaction and the dequeue operation as JCA Inbound Interaction.

2.3.2 What are the different AQ payloads supported by the Adapter?

The Adapter supports both ADT (Oracle Object Type) and RAW queues as payloads. In addition, it also supports extracting Payload from one ADT member column. The Adapter does not support the AQ XML type in this version.

2.3.3 Does the Adapter support AQ Headers?

The Adapter supports Headers for both Enqueue and Dequeue options. Headers are comprised of two elements, namely: standard AQHeader and Payload Header. AQHeader consists of the of standard message properties that are present in every queue. The Adapter supports Payload Header in addition to the standard AQ Headers.

2.3.4 Does the AQ Adapter support multi-consumer queues?



The Adapter supports dequeue/enqueue of AQ messages to/from multi-consumer queues. At design-time, the Adapter wizard supports the specification of a message recipient list for the Producer component and the consumer name to be specified for the Consumer component. In addition, the Adapter allows overriding the message recipient list specified at design-time for the Producer component.

2.3.5 Does the AQ Adapter support native correlation? How can I mimic a request-response scenario using the above?

Yes. The AQ Adapter supports native correlation. At design-time, the BPEL “invoke” and “receive” activities have to point to the same AQ Partner Link activity. The Adapter Framework can perform one of the following correlations: MessageID of request to MessageID of response, MessageID of request to Correlation ID of response and Correlation ID of request to Correlation ID of response.

2.3.6 How can I configure the Adapter Consumer component to selectively dequeue messages ?

You can filter messages using the following options:

(1) Dequeue based on Correlation ID : Only those messages that match a specified Correlation ID are dequeued.(2) Rule-based Subscription : AQ also offers unique content-based filtering of AQ messages in addition to subject based filtering. A rule is used to define one or more Consumers interest in subscribing to messages that conform to that rule. The messages that meet this criterion are then delivered to the interested subscribers. The AQ Adapter allows specifying a rule to filter messages in a queue to select only those on a specific subject. The rule is specified as a boolean expression (one that evaluates to true or false) using syntax similar to the WHERE clause of a SQL query. This boolean expression can include conditions on message properties (currently priority and correlation id), user data properties (object payloads only), and functions (as specified in the where clause of a SQL query).

2.4 JMS Adapter

2.4.1 What is the version of the JMS specification supported by the Adapter?

The JMS Adapter currently supports JMS version 1.02b and will support JMS specification version 1.1 in the future.



2.4.2 What are the list of JMS Providers certified against this adapter?

OC4J JMS – 10.1.2OJMS - AQ Based JMS TIBCO Enterprise Message Service version 4Websphere MQSeries 5.3

2.4.3 Does the JMS Adapter support Durable Subscriptions?

Yes. The JMS Adapter supports creation of durable JMS Topic Subscribers. Durable subscribers registers a durable subscription with a unique ID that is used to retrieve messages for redelivery for guaranteed message delivery By default subscribers are non-durable and the non-durable subscriptions last for only the life-time of the subscriber object. If there is no active Subscriber for a durable subscription, JMS stores the message to a persistent Store until the subscriber becomes active or until the message expires. If subscriber is active messages are delivered normally. The JMS Topic Publisher must of Persistent type. The Adapter design-time provides a way to set Durable subscriber ID when configuring a JMS Topic Subscriber (Consumer).

2.4.4 How does the JMS Consumer receive messages from JMS Topics and Queues?

The JMS API supports both synchronous or asynchronous communication for message consumption. In the synchronous case, the consumer explicitly calls the receive() method on the topic or queue. In the asynchronous case, the JMS client registers a MessageListener for the topic or queue and the message is delivered by calling the listener’s onMessage() method. By default, the consumer uses a polling method. The Adapter design-time is used for overriding the default behavior and can be used to configure a message listener for receiving JMS messages in an asynchronous fashion.

2.4.5 Does the Adapter support JMS Transactions?

The Adapter currently supports JMS Transactions only. The JMS transacted session supports transactions that are contained within a JMS session and does not have any effects outside of the session. The JMS Transaction is used to coordinate a group of messages for production and consumption and the set of messages within the transaction boundary are treated as an atomic unit. When the application rolls back the transaction, the messages it received within the transaction are returned to the messaging system and messages it sent are discarded.

2.4.6 How do I create a JMS Transacted Session ?

Set the “isTransacted” property in the <connector-factory> element of the oc4j-ra.xml to true.



<connector-factory location="eis/aqjms/Topic" connector-name="Jms Adapter">

<config-property name="connectionFactoryLocation" value=""/> <config-property name="factoryProperties" value=""/> <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/> <config-property name="isTopic" value="true"/> <config-property name="isTransacted" value="true"/> <config-property name="username" value="jmsuser"/> <config-property name="password" value="jmsuser"/></connector-factory>

The acknowledgeMode attribute is ignored for transacted sessions. In this case, messages are acknowledged when the transaction is committed using the commit() method.

2.4.7 What are the various JMS acknowledgement modes and how do I set it for the JMS Adapter?

You can set the JMS acknowledgement modes in the OC4j-ra.xml file of the JMS Adapter. <connector-factory location="eis/aqjms/Topic" connector-name="Jms Adapter">

<config-property name="connectionFactoryLocation" value=""/> <config-property name="factoryProperties" value=""/> <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/> <config-property name="isTopic" value="true"/> <config-property name="isTransacted" value="true"/> <config-property name="username" value="jmsuser"/> <config-property name="password" value="jmsuser"/></connector-factory> Acknowledge Mode Description

AUTO_ACKNOWLEDGE The JMS Session object acknowledges receipt of a message after consumption by the receiving application.

CLIENT_ACKNOWLEDGE The application calls the acknowledge method on the received message. Once the method is called, the session acknowledges all the messages received since the last acknowledgement.

DUPS_OK_ACKNOWLEDGE Similar to auto acknowlege but duplicate acknowledgements are permitted. NO_ACKNOWLEDGE No acknowledge is required. In this case, the JMS Messages are immediately

deleted from the server.

2.4.8 What is the value add of the Adapter Translator in the JMS Adapter design-time



wizard?

The payload of the JMS adapter can be explicitly defined using the Native Format Builder at design-time. This allows users to browse and manipulate the payload schema of a JMS message while modeling a business process. The inbound/outbound payload of a JMS server may not be XML. The payload can eventually be translated into an XML document as specified in the nXSD.

2.4.9 What are JMS Headers? Does the Adapter support JMS Headers? How can I manipulate the JMS Headers ?

A JMS message has 3 sections, regardless of whether it is addressed to atopic or a queue. • Header (certain header fields are mandatory)• Properties (optional)• Payload (optional) JMS Headers are JMS specific properties that are set by the underlying JMS Provider and JMS Producer. JMS Properties is used for specifying additional properties by applications, vendors, and administrators on JMS systems. The Adapter supports the specification of both JMS Headers and Properties. The attributes of the JMS Header and property element can be manipulated and set to BPEL variables at design-time. The following property type are supported in the Adapter 1. String2. Integer3. Boolean4. Double5. Float6. Byte7. Long8. Short Inbound JMS Header <complexType name="JMSInboundHeaderType"> <all>

<element name="JMSCorrelationID" type="string" minOccurs="0" maxOccurs="1"/> <element name="JMSDeliveryMode" type="integer" minOccurs="0" maxOccurs="1"/> <element name="JMSExpiration" type="long" minOccurs="0" maxOccurs="1"/> <element name="JMSMessageID" type="string" minOccurs="0" maxOccurs="1"/> <element name="JMSPriority" type="integer" minOccurs="0" maxOccurs="1"/> <element name="JMSRedelivered" type="boolean" minOccurs="0" maxOccurs="1"/> <element name="JMSType" type="string" minOccurs="0"maxOccurs="1"/> <element name="JMSTimestamp" type="long" minOccurs="0" maxOccurs="1"/>

</all>



</complexType> Outbound JMS Header <complexType name="JMSOutboundHeaderType"> <all>

<element name="JMSCorrelationID" type="string" minOccurs="0" maxOccurs="1"/> <element name="JMSType" type="string" minOccurs="0" maxOccurs="1"/>

</all> </complexType> JMS Destination TheDestination to which message is sent and is

set by the JMS Producer. This attribute is mandatory and must be set by the JMSProducer.

JMSDeliveryMode Set to persistent or non-persistent mode by the JMS Producer. The JMS Provider sets it to non-persistent by default.

JMSExpiration Duration of the message beforeExpiration set by the JMS Producer. –1 indicates no expiration.

JMSPriority Number between 0 and 9 set by the JMS Producer. Larger numbers represent higher priority. The JMS Provider automatically sets it to the default priority of the JMS Queue or Topic if not set by the JMS Producer.

JMSMessageID Unique message identifier set by the JMS Producer. The JMS Provider automatically generates this if not set by the JMS Producer.

JMSTimestamp Timestamp when message was sent to the JMS provider for forwarding. This is automatically set by the JMSProvider.

JMSCorrelationId Set by both Producers and Consumers for linking the response message with the request message. This is an optional attribute

JMSReplyTo Optional attribute indicating the destination to which a message reply should be sent. Can be set by the Producer and Consumer.

JMSType JMS Message Type set by both the JMS Prodiucer and Consumer.



JMSRedelivered Set by the JMS Provider to indicate that the Provider has tried to send this message once before to the consumer and has failed.

The Adapter design-time allows you to manipulate the JMS Headers.

2.5 Oracle AS Adapter Translator – Native Format Builder & Translator

2.5.1 What is the Adapter Translator (nXSD)?

The Adapter Translator or nXSD is a Native Format Builder (at design-time) and Translator (at run-time). It is used for handling non-XML (non-XSD) data formats to XSD. The conversion logic is captured as an XSD. It uses the extraneous non-schema namespace attributes (XSD annotations) for specifying native data specific formats and transformation logic. It replaces Data Definition Description Language (D3L) language that was used in the previous versions of the product, by supporting all the D3L constructs and extensible to support more constructs if required in the future.

2.5.2 Is nXSD applicable to File Adapter only?

The nXSD is used across Technology Adapters. In future, it might be available as a stand-alone activity in the BPEL Process Manager product. The Database and hence the Oracle Applications Adapter do not currently support nXSD.

2.5.3 Please list the native data formats that are currently supported by nXSD?

Delimited, Positional, COBOL copybooks, binary data are examples of native data formats. In addition, the nXSD component also supports DTD based XML.

3 Oracle Adapters for Packaged Application

This section provides answers to frequently asked questions about the following adapters: • Oracle Application Server Adapter for J.D. Edwards OneWorld (OracleAS Adapter for J.D. Edwards OneWorld) • Oracle Application Server Adapter for PeopleSoft (OracleAS Adapter for PeopleSoft)



• Oracle Application Server Adapter for SAP (OracleAS Adapter for SAP) • Oracle Application Server Adapter for Siebel (OracleAS Adapter for Siebel)

3.1 OracleAS Adapter for J.D. Edwards OneWorld

3.1.1 What are the J.D. Edwards versions supported by the adapter?

• Enterprise One • Enterprise One 8.9 • Enterprise One 8.10 • Enterprise One 8.11

3.1.2 What are the integration points for the J.D. Edwards adapter?

The adapter uses OneWorld APIs to interact with OneWorld. These APIs are functions provided to manipulate OneWorld data types, provide common functionality, and provide database access. Several categories of APIs exist, including the Common Library APIs and J.D. Edwards Database (JDEBASE) APIs. The adapter establishes a connection to OneWorld and make direct calls to OneWorld APIs or business functions. The OneWorld object does its work while your calling program waits. Results are available immediately upon completion of the call.

3.1.3 What APIs, library files, and DLLs are required for the adapter (including third party software)?

The following are available in \\system\Classes either on the Enterprise server or client machine to connect to the system:

• log4j.jar • jdeutil.jar • Connector.jar • Kernel.jar

iwoevent.dll is required for notification for outbound events.

3.1.4 What are the setups and/or configurations required for the adapter?

No setup or configuration is required for inbound. For out bound, you must subscribe to outbound transactions.



For more information, see the Interoperability Guide.

3.1.5 Can you browse and/or generate XML schemas?

Yes. Using the OracleAS Adapter for J.D. Edwards, you must: • Define a target to J.D. Edwards. • Place the GenJava files in the repository. • Connect to the system every time when you start Application Explorer. GenJava files can be generated by GenJava tool. For more information, see the Interoperability Guide.

3.1.6 Does the adapter supports connection pooling?

Yes. Connection pool is establishing a session by setting the session attribute of the standard jdeRequest element. When the session attribute is an empty string, a new session is started. On the server, the SessionManager singleton class creates a new instance of a session object when given the user name, password, and environment name. The session can be reused before it expires to avoid the overhead of session initialization. You can specify the session ID in the session attribute for an already established session in an earlier request. Session expiration is addressed by the sessionidle attribute of the standard jdeRequest element. This attribute, when given on a session creation request, specifies the amount of time in seconds that this session is allowed to be idle. If the SessionManager determines that a session has not had any requests processed in this amount of time, it terminates the session and frees all associated resources. For more information, see the Interoperability Guide.

3.1.7 Does the adapter supports load balancing?

Yes. Load balancing configuration is controlled by various interrelated run-time settings in the jde.ini file on the server. These settings are in the JDENET and applicable JDENET_KERNEL_DEFx sections. All relevant settings are listed and described in the preceding section. You can control two types of processes: • Network jobs (JDENET_n) • Dedicated kernel process jobs (JDENET_k). For more information, see the System Administration Guide.

3.1.8 What are the security features for the adapter?

The adapter supports standard JDE security. Security is managed by user profiles defined in the system. For more information, see the Server and Workstation Administration Guide.

3.1.9 Does the adapter provide delivery confirmations and error messages?



Each transaction is assigned session ID by J.D. Edwards. See the application P92002 for server side error messages. If the target is down or queues are full, you will not be able to connect to the system. A Jdenet time out exception error message appears for Inbound. See the System Administration Guide to increase queues and recycle server.

3.1.10 What are the advantages of the J.D. Edwards adapter?

• No code modifications are required to upgrade. • When a J.D. Edwards data structure changes, source modifications are minimal to non-existent. • Common functionality provided through the APIs is less prone to error. When the code in an API changes, typically, you simply recompile and relink business functions and regenerate GenJava files.

3.2 OracleAS Adapter for PeopleSoft

3.2.1 What are the PeopleSoft versions supported by the adapter?

The adapter goes by the PeopleTools version, not by the application version. The adapter supports all People Tools versions 8 and above.

3.2.2 What are the integration points for the PeopleSoft adapter?

The inbound messages (services) use the component interfaces. The outbound messages (events) use the PeopleSoft messages in Integration Broker.

3.2.3 What is Peoplesoft Integration Broker?

PeopleSoft Integration Broker provides a mechanism for communicating with the outside world using XML files. Communication can take place between different PeopleSoft applications or between PeopleSoft and third-party systems. To subscribe to data, third-party applications can accept and process XML messages posted by PeopleSoft using the available PeopleSoft connectors or by adding a custom built connector to the Integration Gateway. Some Integration Broker concepts are as follows:

• Message

A Message is a container for the data that goes into the XML. It contains basic structural information,



such as records and fields. The Message must be in an Active status to send the XML file

• Message Channel

The Message Channel is a mechanism for structuring records into logical groupings. Each Message can belong to only one Message Channel. The Message Channel must be in an Active (Run) status for the Message to be delivered.In release 8.1, the Message Channel also provides preliminary routing instructions; you can specify which Message Nodes handle the message. Each Message Channel can route messages to multiple Message Nodes


psjoa.jar - Provided by PeopleSoft (Available from the PSHOME\web directory). PeopleSoft Java API’s - Generated from PeopleTools. Note: Both psjoa.jar and APIs are specific to PeopleTools release.


• Loading of 2 custom component interfaces. • Security access for component interfaces. • Generation and compilation of Java APIs. • Integration broker configuration for events.

Note: For more information, see the Oracle Application Server Adapter for PeopleSoft User’s Guide.

3.2.6 Can you browse and/or generate XML schemas for component interfaces and messages?

Yes. Using the OracleAS Adapter for PeopleSoft, you can: • Create a target to the PeopleSoft instance. • Connect to the target. After connecting with the target you can see browse the component interfaces and messages. • Expand the component interfaces or messages to display a list of component interfaces and messages. • Click a particular object to display options enabling you create the XML schemas.

Note: For more information, see the Oracle Application Server Adapter for PeopleSoft User’s Guide.




Yes. A connection pool is a set of client connections to a specific destination. The pool may automatically create new connections to the specified remote system or return an already existing connection. It also provides methods to return a connection back to the pool when it is no longer required. A connection pool can check which connections are no longer in use and can be closed to save system resources. The time period after which the pool checks the connections as well as the time after which a connection will time out can be configured by the calling application. A pool is always bound to one user ID and password, meaning that all connections taken from this pool will also use these credentials. A PeopleSoft connection is always bound to a PeopleSoft user ID and a PeopleSoft Client number. If you log on with a pool size that is set to one, no connection pool is created (one user ID and one process thread). If you log on with a pool size that is greater than one, a pool is created with a size of n, which is the number you specified.

3.2.8 Does the adapter provide delivery confirmations for the inbound services?

Yes. The Adapter for Peoplesoft can be configured as either a HTTP Listener or TCP/IP Listener or JMS Listener to receive Integration Broker events. The Adapter can be configured to perform delayed acknowledgement to the Integration Broker post consumption of the event by the Adapter client.

3.2.9 Does the adapter supports custom component interfaces?

Yes. You should generate the Java APIs for the component interfaces from PeopleTools, you should compile them and create a Jar file for them with the other Java APIs for component interfaces, and store them in the adapter lib directory.

3.2.10 Does the adapter support custom messages (events)?

Yes. The Adapter supports custom Peoplesoft Application Messages.

3.3 OracleAS Adapter for SAP

3.3.1 What SAP systems does the adapter support?

The following SAP platforms are supported:: • SAP Basis 4.0B – 4.6D, all versions. • SAP Web Application Server Version 6.2 and higher. • SAP Enterprise R/3 4.7.

All or portions of: MySAP.com technology solutions (SAP BW, SAP APO, SAP CRM, SAP SRM, SAP EBP, SAP SEM, SAP WP, SAP KW). Note: Release versions may vary by product component. In addition, SAP functions may vary by SAP



product version and support package. SAP R/3 Basis Release 3.1 is “off SAP maintenance.” Oracle can support this release under special circumstances, but not all functions can be supported.

3.3.2 What external libraries are required in addition to the adapter are required?

The adapter requires the SAP RFC library, and the SAP Java Connector. Both of these products are download under one package from the SAP Service Marketplace: http://service.sap.com/connectors .

3.3.3 How does the adapter connect to SAP?

The SAP system provides the RFC API (Remote Function Call Application Programming Interface) that you install on non-SAP systems to help you implement RFC partner programs. The RFC API is a set of C-language routines that perform certain communications tasks for you. The SAP Remote Function Call (RFC) protocol allows you to call ABAP function modules from external applications. An external application using the RFC interface can act as both the client and the server to a SAP system.

3.3.4 How does the adapter manage security?

To connect to the server, the adapter supports SAP standard security, and the additional protocol of SNC. Consult the SAP RFC manual for details on RFC SNC . Once connected to the SAP application server, application security is managed by user ID, roles and profiles. See the SAP documentation for information on SAP application security.

3.3.5 How can I browse the list of objects and create schemas?

SAP supports three different types of objects: RFC, BAPI, and IDOC. To browse the available business functions, you must first define a target to SAP. After you define the target, it is automatically saved. You must connect to the SAP system every time you start Application Explorer or after you disconnect. When you click on an object in Application Explorer, your schemas are automatically generated and saved to the default repository.

3.3.6 How can I switch on connection pooling in the adapter?

A connection pool is a set of client connections to a specific destination. The pool may automatically create new connections to the specified remote system or return an already existing connection. It also provides methods to return a connection back to the pool when it is no longer required. A connection pool can check which connections are no longer in use and can be closed to save system resources. The time period after which the pool checks the connections, as well as the time after which a connection will time out, can be configured by the calling application. A pool is always bound to one user ID and password, meaning that all connections taken from this pool will also use these credentials. A SAP



connection is always bound to a SAP user ID and a SAP client number. If you log on with a pool size that is set to 1, no connection pool is created (1 user ID to 1 process thread). If you log on with a pool size that is greater than 1, a pool is created with a size of n, which is the number you specified.

3.3.7 How do I load balance my adapter?

Load balancing in client (outbound from adapter to SAP) situations is handled only by the SAP application design. If your system supports a Message Server, then you can load balance in client situations. If you have only one application server, you cannot load balance except by application server tuning, such as maximum number of connections permitted or time of day limits on connections. Load balancing in server (inbound to adapter from SAP) situations is handled by connecting multiple instances of the adapter to the SAP system. The SAP system will then load balance the connections. You cannot tune this performance.

3.3.8 How many connections are possible through the adapter?

The SAP system default limit is 100 RFC (communication) or adapter users. Each user takes up more than 2 MB of memory on the application server of the SAP system, and more or less on the adapter depending on the workload.

3.3.9 What happens if the SAP server is down?

If you are sending a request to SAP and the system is down, you will not be able to connect and create schemas. If the SAP system is sending data to you and if your request is under TRFC rules, (see SAP documentation) then those rules apply to your request. If you are not under TRFC, you may have to manually verify your entries. Consult the SAP documentation for more information.

3.3.10 How can I be sure my transactions complete?

The adapter complies and is certified for the SAP Transactional RFC model. This model processes transactions in the following manner: Each transaction is assigned a transaction identifier by the SAP system, which the adapter stores in a log. When the transaction completes, the transaction identifier is again given along with a status of completed or rolled back. If the server fails, only those transactions not completed will be processed by the server and adapter.

3.3.11 Can I develop custom objects?

As long as any objects deployed on the SAP system comply with the rules of SAP Remote Function Call, then custom objects can be deployed on the SAP system and used through the adapter.



3.4 OracleAS Adapter for Siebel

3.4.1 What are the Siebel versions supported by the adapter?

The adapter supports Siebel versions 6.01 through 7.x.

3.4.2 What are the integration points for the Siebel adapter?

All Siebel business objects are accessible by the adapter. For inbound messages (services) to Siebel, the adapter can access and execute Business Components, Business Services, and Integration Objects. The outbound messages (events) use Siebel integration objects, which support one of four transports (MSMQ, MQSeries, HTTP, and File).


For Siebel 2000 (6.0.1), 6.2 or lower, the Siebel 2000 client must be installed. The adapter uses the underlying ODBC connection configured for the client.

For Siebel 6.3 or higher: • SiebelJI_Common.jar • SiebelJI_enu.jar • SiebelJI.jar

For Siebel 7.7 or higher: • SiebelJI_enu.jar • Siebel.jar


Locating and verifying the applicable Siebel version jar files are accessible and available to the adapter. For more information, see the Oracle Application Server Adapter for Siebel User’s Guide.

3.4.5 Can you browse and generate XML schemas for all Siebel Business Objects and integration object messages?

Yes. Using the OracleAS Adapter for Siebel, you can:



• Create a target to the Siebel instance. • Connect to the target. After connecting to the target you can view and browse the Siebel Business objects and integration objects. • Click a particular object to display options to create XML schemas, after expanding a particular business object or integration object.

For more information, see the Oracle Application Server Adapter for Siebel User’s Guide.


Yes, the adapter, using the Java Data Bean to connect to Siebel versions 6.3 and higher, connects and communicates with a Siebel Application Object Manager. The Siebel Application Object Manager, which could be running on a remote Siebel Server, is a multithreaded, multi-process application server that hosts Siebel objects and supports session-based connections by clients. The Siebel Application Object Manager specified in the connect string must be running on the specified Siebel Server.

3.4.7 Does the adapter supports custom business services?

Yes. All business objects, such as modified business services are accessed by the adapter transparently.

3.4.8 Does the adapter support custom integration object messages (events)?

Yes. The Adapter supports custom Siebel Integration Objects.

4 Oracle AS Adapters for Mainframes & Legacy Applications

4.1.1 Describe the architecture of the Oracle AS Adapters for mainframes?

It consits of a server process called Oracle Connect running on the mainframes. This is the core piece that provides connectivity to mainframe transactionmonitors (TM) and Data stores (Files, databases etc). It has inbuilt native Adapters for facilitating the above. The Oracle Application Server product components are integrated with Oracle Connect through the JCA Legacy Adapter.

4.1.2 What are the different ways to integrate with IMS/DB?

The access to IMS/DB can be provided in a variety of ways:



● directly access IMS/DB● access IMS/DB through IMS/TM● access IMS/DB through CICS

4.1.3 How does the Oracle AS Adapter for IMS/DB integrate with the IMS/DB datastore?

The data access API to IMS/DB is called DL/I, which is a function by which the IMS/DB database can be traversed and operated on. The Oracle Connect runs on the machine where IMS/DB is installed and running. The Oracle Connect captures and maintains a metadata schema for IMS/DB by importing various IMS definition files such as a PSB file, DBD files and COBOL copybooks. These are available as XSD and WSDLs for BPEL PM and other Oracle AS product components to consume.

4.1.4 What are the different ways of integrating with IMS/TM?

The application components in IMS/TM are executable programs called transactions. These programs are typically written in COBOL but may possibly be written in other languages, such as PL/I, C and even Java. There are several types of IMS/TM programs including MPPs (Message Processing Programs) and BMP (Batch Message Processing Programs). IMS/TM transaction can be invoked using the following ways:

• OTMA API (Open Transaction Manager Access)

• 3270 terminals.

• TCP/IP access via IMS/TM transaction gateway

• MQSeries integration (IMS/TM must be WebSphere MQSeries enables).

4.1.5 How does the Oracle AS Adapter for IMS/TM integrate with IMS/TM?

The Adapter for IMS/TM supports only MPPs (Message Processing Programs) and not BMP (Batch Message Processing Programs). This Adapter talks to IMS/TM transactions via OTMA (Open Transaction Manager Access). It can also talk to IMS/TM via the TCP/IP layer and needs an IMS/TM transaction gateway to enable this.

4.1.6 How does the CICS Adapter integrate with the CICS application?

The Adapter uses EXCI (EXternal Call Interface) to invoke CICS transactions and uses COMMAREA



transactions to exchange message buffers. The Adapter creates a metadata schema for CICS by importing COBOL copybooks and transforming them into mapping definitions for Oracle Connect for CICS on the OS/390 machine and by associating the data structures with specific physical files. The Adapter is also capable of receiving events from CICS.

4.1.7 What are the different APIs available to integrate with CICS?

CICS supports the following API to communicate with non-CICS system. ● External Call Interface (ECI) – Used to communicate with CICS programs and transactions in sync/

async fashion.● External Presentation Interface (EPI) – Used to communicate with 3270 terminals.● External Security Interface (ESI) – It enables user applications to verify and change passwords against

the External Security Manager deployed in a CICS systems.● MQSeries integration

4.1.8 What are the different transports available to integrate with CICS?

There are 3 ways to perform data communication. They are System Network Architecture (SNA), TCP/IP, or TCP 62 (SNA over TCP/IP).

● SNA is a proprietary IBM architecture developed for the mainframes. Older mainframes have SNA support only. SNA client installation is required for NT/UNIX to communicate with mainframe over SNA.

● TCP 62 allows NT/UNIX to communicate via TCP/IP with mainframes which understand SNA only. However you need AnyNet to be running on the mainframe system

● The 3rd approach is to communicate with mainframes over regular TCP/IP. This is supported in CICS transaction server 2.3 and above.

For the last 5 years IBM has moved its customers to TCP/IP. TCP/IP has become a standard part of the MVS operating system.

4.1.9 Does the Oracle AS Adapter support CICS transactions?

The Oracle CICS Adapter supports CICS transaction or sync points (rollbacks) and interfaces with IBM's Resource Recovery Manager.

4.1.10 How does the Oracle AS Adapter for CICS publish a CICS event?

The Oracle AS Adapter for CICS includes a set of APIs that enable pushing a CICS native event from a COBOL program, to the Oracle Connect for CICS component using a CICS transaction. The CICS Socket



Interface must be enabled for the above.

4.1.11 How does the Oracle AS Adapter for Tuxedo integrate with Tuxedo?

Oracle AS Adapter for Tuxedo implements the C-ATMI API. It supports the synchronous request-response interaction with Tuxedo. It also supports event integration with Tuxedo. The Tuxedo services have to be modified to write to the Oracle Connect for Tuxedo queues.


how does the oracle as adapters fit into the service ......how does the oracle as adapters fit into...

Documents