Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 62 Insurance
- 536K On-Premises Infrastructure
- 138.2K Analytics Software
- 38.6K Application Development Software
- 5.7K Cloud Platform
- 109.4K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
Technical differences between JCA properties and binding properties of Adapters

What are the technical differences between JCA properties and binding properties of Adapters.
For example in a JMS adapter, jca.jms.JMSMessageID is a JCA property and adapter.jms.receive.threads, adapter.jms.retry.interval are binding properties.
As I understand, JCA properties are specific to the config required for interacting with the target resources/systems like DB, JMS, File etc.
Binding properties are used to configure a SOA service for how it has to be deployed/executed in the soa infrastructure/engine runtime. Can someone, please confirm if it's correct.
Can someone please, also articles related to the internal design/architecture of the SOA infrastructure implementation used in the Oracle SOA product.
BR,
Naveen.
Answers
-
Hi Naveen,
for any technology adapter, there are primarily 2 parts, interaction spec(outbound) and activation spec( inbound)
those are implemented by internal classes and that require a few properties, that we are providing through JCA file
few properties are used for representation purposes and a few are used for controlling the execution purpose
adapter.JMS.receive.threads, adapter.JMS.retry.interval, binding properties instruct the engine how to execute and with what resources, if a receive .threads =2, then 2 threads would be listing on the queue or subscriber topic, same as retry interval
Suman