ADF bc based SDO works well for data fetch and data transformation , however applications interacting using WS interface and needs Transaction support with SDO need to understand :
Web Services Atomic Transaction &
Web Services Coordination (WS-Coordination)
These specifications define an extensible framework for coordinating distributed activities among a set of participants. As per oracle doc :
Coordinator :
Manages the transactional state (coordination context) and enables Web services and clients to register as participants.
Activation Service :
Enables the application to activate a transaction and create a coordination context for an activity. Once created, the coordination context is passed with the transaction flow.
Registration Service Enables an application to register as a participant.
Application Protocol X, Y : Supported coordination protocols, such as WS-AtomicTransaction.
How to enable these while using SDO :
1. In the ServiceImpl.java class of service interface add following to the class and methods
@Transactional(
version=Transactional.Version.[WSAT10|WSAT11|WSAT12|DEFAULT],
value=Transactional.TransactionFowType.[MANDATORY|SUPPORTS|NEVER]
)
This will enable SDO to participate in JTA transaction
2. For this to support the domain should have been created with WebLogic Advanced Web Services for JAX-WS Extension , Or need to extend the domain for this.
This option will create following resources :
WseeJaxwsJmsModule : JMS Module
WseeJaxwsFileStore_server_designator : File store
WseeJaxwsJmsServer_server_designator : JMS server
WseeJaxwsJmsServeruniqueID : JMS subdeployment
weblogic.wsee.jaxws.mdb.DispatchPolicy : Work Manager
ReliableWseeJaxwsSAFAgent_server_name : SAF service agent
WseeBufferedRequestQueue_server_designator : JMS queue
WseeBufferedRequestErrorQueue_server_designator : JMS queue
WseeBufferedResponseQueue_server_designator : JMS queue
WseeBufferedResponseErrorQueue_server_designator :JMS queue
WseeStore : Logical store
Cheers !!
No comments:
Post a Comment