Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

JCA Resource Adapter form - Completing the ConnectionSpec tab

Updated on April 6, 2022

Note: Beginning in Pega Platform 8.6, EAR deployments of Pega Platform are deprecated. In the upcoming 8.7 release, EAR deployments will not be supported. As a result, in Pega Platform 8.7, JCA Resource Adapter data instances will also no longer be supported. For more information on the alternatives for EAR-related rules, see Deprecation of EAR deployments in Pega Platform 8.6.

If the JCA resource adapter implements the ConnectionSpec interface of the CCI section of the JCA specification, use this tab to identify the name of the Java class that implements the ConnectionSpec interface and the property/value pairs it requires.

FieldDescription
Connection Spec Implementation ClassEnter the name of the Java class that implements the ConnectionSpec interface.
Connection Spec Standard Properties
User NameEnter the name of a user that establishes the connection with the enterprise information system (EIS) that this JCA resource adapter connects to.
PasswordEnter a password for the EIS user specified in the User Name field.
Connection Custom PropertiesIf the ConnectionSpec Java class requires client-specific property values, CCI, use this section to specify the required property/value pairs.
none Click the none button. Enter the name of the custom property in the pop-up window and click Save. Then enter a value for the property.
  • Previous topic JCA Resource Adapter form - Completing the Connection tab
  • Next topic JCA Resource Adapter form - Completing the MetaData tab

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us