Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 75 Insurance
- 537.7K On-Premises Infrastructure
- 138.7K Analytics Software
- 38.6K Application Development Software
- 6.1K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.3K Infrastructure Software
- 105.4K Integration
- 41.6K Security Software
Dynamic PartnerLink wsdlLocation
Hello,
I am working on a billing process that needs to be able to determine which partner (i.e. the wsdl location) to connect to at run-time. I've read this can be done via WS-Addressing, but I don't see a way to do this using Oracle's BPEL implementation. I see that the wsdlLocation property is defined in the bpel.xml, but I don't see an api call or other place where I can dynamically set this.
Any help is appreciated.
Thanks,
Chris Natali
I am working on a billing process that needs to be able to determine which partner (i.e. the wsdl location) to connect to at run-time. I've read this can be done via WS-Addressing, but I don't see a way to do this using Oracle's BPEL implementation. I see that the wsdlLocation property is defined in the bpel.xml, but I don't see an api call or other place where I can dynamically set this.
Any help is appreciated.
Thanks,
Chris Natali
Comments
-
Hi Chris,
C:\[orabpel install dir]\samples\references\DynamicPartnerLink shows how you can use an assign activity within a BPEL process to dynamically set the location of partnerLink.
Please note that this information can also be dynamically set by the client/partner as it is initiating the BPEL process ( kind of "please process this request and call me back at this location with this correlation id"). In that use case the client/partner passes in the callback location and the correlation id in a WS-addressing header embedded in the header of the initiating request. Under the hood the BPEL engine, reads the WS-Addressing header and associates the client partnerLink with the provided information. That information is automatically used by the BPEL engine when it runs an invoke activity to call back the client.
I hope this addresses your question.
Edwin
This discussion has been closed.