Skip to Main Content
Forums

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

SOA / SOAP - Direct Binding

PuneetRekhadeSep 6 2013 — edited Sep 9 2013

Hello,

I have already searched and googled for plenty for online resources about the question, although they haven't really made my concepts clear.

I am following this document - Using the Direct Binding Invocation API

Section : 36.1 Introduction to Direct Binding

for clarifications about Direct-Binding.

Objective : Interaction between OSB and SOA Suite Components(BPEL, Mediator).

Question 1: Why would I use a "direct-binding", instead of a "web/soap binding" ? What are the (dis)advantages ?

I am quoting snippets from the aforementioned document, around which I have some doubts.

[Document] A common way to invoke a composite is to use SOAP over HTTP.

[Question.1]  What are other ways of invoking a composite ? I am aware of SOAP over JMS, however, never used it.


[Document]  This is enabled by creating a SOAP service for your composite using web service binding. Direct binding enables Java clients to directly invoke composite services, bypassing the intermediate conversion to XML required with web service binding.

[Question.2]  What I interpret this is : Composite + WebService Binding = SOAP Service of my Composite. I added a "Direct Binding" to the composite and deployed the service. The deployed concrete "directWsdl"  contained 2 auto-generated bindings for SOAP1.1 and SOAP1.2. The Endpoint URL contained "t3" URL. Now the question is, if the aim of direct binding was to avoid to conversion into XML, as with WebService binding, then, why is the deployed directWsdl contains SOAP 1.1 and SOAP1.2 bindings ?


Any pointers to some theoretical books / resources will help !

Thanks !

Comments

Karthick2003
945400 wrote:
create index ts_portfolio_dm.instrument_ref_dim_indx1 on ts_portfolio_dm.instrument_reference_dim(instrument_type_dvd, revenue_source_dvd, pricing_dt, instrument_dim_key);

when I execute this command the process is taking too long to create an index .is there any additional coding that can help create index fast.
The time taken to create an index depends largely on the the volume of data in the table and number of columns being indexed.
fjfranken
Hi

You could add the "NOLOGGING" option.
This might speed it up a bit, because no redo logging is written for the index-creation. But it is only a small improvement

Your statement would then look like: 
CREATE INDEX ts_portfolio_dm.instrument_ref_dim_indx1
   ON ts_portfolio_dm.instrument_reference_dim (instrument_type_dvd
,                                               revenue_source_dvd
,                                               pricing_dt
,                                               instrument_dim_key) nologging ;
Maybe also add the PARALLEL clause to force parallel execution. But for the remainder I agree with the other reply. It is simply the amount of data that makes the time here
948403
Hi ,

thanks for the reply .

could you please give me the statement that contains both

1.parllel creation 2.no logging.

Is there any further improvements that can be done on this .
The table is very huge and lot of procedures use this .Hence the reson we are not able to allow the statement to execute for more time .
cheers,
P
1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 7 2013
Added on Sep 6 2013
#soa, #soa-process-management, #soa-suite-discusssions, #soap
1 comment
264 views