rss
SOATUBE
Oracle
Custom Search SOABYTE here

Monday, November 8, 2010

Deploy/run an AQ adapter process using a schema different from what is used

AQ Adapter design time wizard generates some artifacts associated with the schema name.  Before 10.1.3.3 release it was required that both design time and runtime schema name should be same for the process to function correctly. But with 10.1.3.3 this limitation has been removed.
  • For pre-existing processes         
 Make sure to remove 'DatabaseSchema' attribute, if it exists, from the PartnerLink wsdl before deploying the process.
Incorrect Correct
<jca:operation 
     ActivationSpec="oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec" 
     DatabaseSchema="<DESIGN-SCHEMA-NAME>" 
     QueueName="<QUEUE-NAME>" 
     OpaqueSchema="false" > 
 </jca:operation>
<jca:operation 
      ActivationSpec="oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec" 
      QueueName="<QUEUE-NAME>" 
      OpaqueSchema="false" > 
</jca:operation>
  • New processes can be generated by selecting 'DEFAULT SCHEMA' option instead of a particular schema name during design time.

0 comments:

Post a Comment

 
Blogger Profile