| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Configuring: System Requirements for the Oracle OCI driver |
|
Configuring Java CAPS for SSL Support
Configuring Java CAPS Business Processes
Business Process and Element Properties Overview
Configuring Business Properties
Configuring General Properties
Configuring Business Process Attributes
Configuring Modeling Element Properties
Adding Logging and Alerts to an Element
Configuring Business Processes for XA Transactions
Persisting Reporting Data for Business Processes
Configuring a Business Process for Reporting Persistence
Configuring Database Connection Information
Creating a Business Process Database Table
Dropping a Business Process Database Table
Configuring BPM for the OCI Driver
Implementing Transparent Application Failover
Configuring Environment Components for the Sun Business Process Manager
Configuring Sun Master Indexes (Repository)
Configuring Java CAPS Project Components for Application Adapters
Configuring Java CAPS Project Components for Communication Adapters
Configuring Java CAPS Project Components for Database Adapters
Configuring Java CAPS Project Components for Web Server Adapters
Configuring Java CAPS Environment Components for Application Adapters
Configuring Java CAPS Environment Components for Communications Adapters
Configuring Java CAPS Environment Components for Database Adapters
Configuring Java CAPS Environment Components for Web Server Adapters
Configuring SAP R/3 for the SAP BAPI Adapter
Configuring Secure Network Communications for SAP
Configuring Siebel EAI Workflows
Importing an SNA Custom Handshake Class
Configuring WebLogic for Asynchronous Communication
Configuring Master Index (Repository) Connectivity and Environments
Related Topics for Sun Adapter for Batch/FTP
The Oracle OCI driver is also called the thick driver because of the extensive native code it uses to communicate with the database. OCI is written in C; all of its Java calls use JNI to direct the calls to the C layer. The C layer communicates with the database and returns the results to the Java layer.
The library to map the Java calls to C calls is installed with the Oracle client’s installation. To enable monitoring and recovery persistence with OCI, you must install the Oracle client software.