Hi Marco, Thanks for the fast answer and your suggestion, but the 2 links you gave me are not suitable for this problem. I read all the user manual of apache ode on the website before but didn't find any solution. The first link describes HOW endpoints can be represented, and the second one, as far as I understand describe is a way to manipulate endpoints on a process-wide level, and there is also a second problem with this solution (copied from http://ode.apache.org/endpoint-configuration.html):
" Dynamic refresh Properties are dynamically loaded and refreshed at run time. The timing is the following: On every request, if the file has not been polled during the last 30 seconds then check the file for updates. If any, reload it. Consequently, if you have updated properties, you have to wait ~30 seconds and then trigger a request." so you have to wait up to 30s to see the changes taking effect. That's "ages" considering you are stopping a running instance to replace an endpoint and continue. Looks like the 3rd suggestion is the only way to go. I'll let you know if I find an applicable concrete solution. Is there someone else with another solution for me? :) Regards, Thuy -----Ursprüngliche Nachricht----- Von: Marco Indaco [mailto:[email protected]] Gesendet: Dienstag, 15. Dezember 2009 14:52 An: [email protected] Betreff: Re: Changing Endpoints of a Process Instance at RUNTIME Hi song, i'am working on your own objective, in my research project. There are many solution that you can investigate. 1) http://ode.apache.org/endpoint-references.html see that link 2)Create, if monitor observes, for example, that a service is down, a file .endpoint located in conf directory in Apache Ode. see that link http://ode.apache.org/endpoint-configuration.html 3) A more intrusive operation for modify source code to added these functionalites If you are any idea please contact me...working together is powerful. Hi, for any question ask me!!! 2009/12/15 Song Thuy Nguyen <[email protected]>: > Hi everyone, > > > > I'm quite new to Apache ODE and mailing lists, hoping for your help. > > As the title says I'm looking for a way to change service endpoints for BPEL > process instances at runtime. That means that only one instance should be > affected by these changes, not the entire process and the deployment > descriptor. By convention of the project I'm working on, it is not allowed > to write a BPEL-process that looks up service endpoints at a registry > service, put it in an variable and use it as the dynamic endpoint. The > reason is we want to provide a fault resistant BPEL process execution by > replacing failing or unavailabe service endpoints by working ones with > transparency to the process. So there should be no sign of the "fault > handling" in the BPEL file. Failing services will be detected by a monitor > component, but this is not my part. > > I have tried to look into the Management API for processes and instances to > find a method that can provide a solution, but I had no luck. There are only > methods to get and set endpoints on a process-wide level, on a instance > level however, those methods are not available. > > It seems to me that the only way to get such a functionality is to extend > the Instance Management API and write those methods myself, If this is > right, can someone please tell me where to start? Any help would be > appreciated. > > > > Thank you in advance > > > > Thuy > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4689 (20091215) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4634 (20091124) __________ E-Mail wurde geprüft mit ESET NOD32 Antivirus. http://www.eset.com __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4634 (20091124) __________ E-Mail wurde geprüft mit ESET NOD32 Antivirus. http://www.eset.com __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4634 (20091124) __________ E-Mail wurde geprüft mit ESET NOD32 Antivirus. http://www.eset.com
