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 MetaData tab

Updated on November 23, 2022

Use the MetaData tab to provide information about the capabilities of the resource adapter.

Before completing this tab, complete the Connection and ConnectionSpec tabs. Then, use the Import Metadata button to retrieve from the resource adapter values for the fields on this tab.

FieldDescription
Adapter Properties
Vendor NameEnter the name of the vendor that created the resource adapter.
Adapter TypeEnter the type of the adapter.
Adapter VersionEnter the version of the adapter.
Supported Execute Methods Specify in this section which Execute() methods the resource adapter supports.
With Input Record Only When selected, signifies the resource adapter supports an Execute() method that takes the input record and the name of the InteractionSpec implementation Java class to use.
With Input and Output Record When selected, signifies the resource adapter supports an Execute() method that also takes a reference to an instantiated output record in addition to the input record and the name of the InteractionSpec implementation Java class to use.
Supported Interaction Specs This section lists the Java classes from the resource adapter that implement the InteractionSpec interface.
row # The name of a Java class that implements the InteractionSpec interface.
Import MetadataClick to import the resource adapter metadata.

A resource adapter can support both CCI Execute() methods. However, if both methods are supported, the Execute method that does not require the connector rule is used to instantiate the output record.

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