« Deployed BPEL Process do not show up in BPEL Console on startup | Main | Error while invoking bean "finder": Cannot lookup BPEL domain »

Controlling Remote invocations of BPEL or ESB Services through Apache

There could be cases where you would not want clients in other machines to invoke a BPEL process or an ESB Service, but you would still want to view the WSDL of the process/service from the BPEL Console/ESB Control. For instance, you might have a BPEL process on the machine A[host name="exampledel.oracle.com"], and you wish to prevent invocation of the process from all machines other than A.


You can use the <Limit> directive to achieve the desired behaviour.


<Location /orabpel/<domainName>/<processName>/*>
   <Limit POST PUT DELETE>
   Order Deny,Allow
   Deny from all
   Allow from exampldel.oracle.com
   </Limit>
</Location>


This ensures that "GET" requests are allowed from anywhere [for viewing the WSDLs etc], but "POST" which is used for SOAP invocation of the Service is only allowed from the machine exampledel.oracle.com.


 

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on July 30, 2007 6:39 PM.

The previous post in this blog was Deployed BPEL Process do not show up in BPEL Console on startup.

The next post in this blog is Error while invoking bean "finder": Cannot lookup BPEL domain.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type and Oracle