| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: Inbound JCA Resource Adapter Client Code |
|
Creating a Runtime Environment
Designing Business Processes in the Sun Business Process Manager
Working with TCP/IP HL7 Collaborations
Developing Sun Master Indexes (Repository)
Developing Sun Master Patient Indexes
Developing OTDs for Application Adapters
Developing OTDs for Communication Adapters
Developing OTDs for Database Adapters
Developing OTDs for Web Server Adapters
Designing with Application Adapters
Designing with Communication Adapters
Designing with Web Server Adapters
Designing with Sun JCA Adapters
Technical Overview for Sun JCA Adapters
Outbound JCA Resource Adapter Client Code
Object Type Definition Wizards
Installation of Netbeans Modules
Installation of Base Components for Sun JCA Adapters
Configuring Runtime Components in an EJB/JCA Application
Configuring Connector Pools for File Adapter
Configuring Connector Pools for Oracle Adapter
Deployment of Sun JCA Adapters
To Deploy JCA Adapters via Command Line
To Deploy JCA Adapters via the Admin Console
Using the Oracle Wizard and JCA Adapter Tooling with an EJB Project
To implement the Oracle JCA Adapter with an EJB Project
Using the Oracle Applications Wizard and JCA Adapter Tooling with an EJB Project
To implement the Oracle Applications JCA Adapter with an EJB Project
Using the Oracle Applications Object Type Definition
JCA Resource Adapters that support inbound communication depend on deployment of a Message-Driven Bean (MDB). To develop an application utilizing a JCA Adapter for inbound communication, the JCA Message-Drive Bean wizard must be used. When the wizard is finished, the message driven bean code skeleton is generated. For example, for the File JCA Adapter, the following MDB code skeleton is created:
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package test;
import javax.ejb.MessageDriven;
import com.stc.connector.fileadapter.eway.FileListener;
import com.stc.connector.framework.eway.FaultException;
import com.stc.connector.framework.eway.InboundException;
/**
*
* @author SUN
*/
@MessageDriven(name="test.FileJCAMessageBean")
public class FileJCAMessageBean implements FileListener {
public FileJCAMessageBean() {
}
public void onContents(byte[] data, String encoding) throws FaultException,
InboundException {
// implement listener interface here
}
}
Note - The MDB generated implements the associated Listener interface for the JCA Adapter specified in the JCA Message-Driven Bean wizard. In the case of File JCA Adapter, the FileListener interface is implemented.