About JCA Resource Adapter data instances
Your applications can connect to Java EE Connector Architecture (JCA)-compliant resource adapters that support the Common Client Interface (CCI) of the JCA specification.
The following tabs are available on this form:
JCA implements a mechanism for accessing legacy systems — called back-end enterprise information systems (EIS) — from Java or Java EE applications. A JCA resource adapter plugs into the Java EE application server and connects applications to a specific EIS. A JCA resource adapter data instance defines the properties of a single resource adapter that is deployed in the same application server that hosts Pega Platform.
You can deploy the JCA resource adapter in either a managed environment (deployed in a Java EE application server) or a non-managed environment (deployed in a non-Java EE Web application server).
Before you begin
Before creating a resource adapter data instance, verify that the resource adapter is deployed:
If your system operates in a managed environment, the resource adapter
.rarfile must be deployed in the same Java EE application server.
If your system operates in a non-managed environment, place the resource adapter
.jarfile an appropriate directory and update the compiler class paths. See the Pega Community article About the Process Commander class paths.
A JCA connector rule uses the information in a JCA resource adapter instance when connecting to a resource adapter to send a request to an Enterprise Information System at runtime. See About Connect JCA Rules.
To review or create JCA Resource Adapter data instances, use the Records Explorer.
To start the Connector and Metadata wizard, select Dev Studio > Integration > Connectors > Connector & Metadata wizard.
The Data-Admin-Connect-JCAAdapter class contains JCA resource adapter data instances. This class is part of the Integration-Resources category.