Orchestration being able to call another orchestration Hot

by Roberto Fedele on August 04, 2015

Currently orchestrations don’t allow to be reused in a different orchestration. It would be very useful if an orchestration would be able to be called from within another orchestration as this would remove the duplication that sometimes is required in some orchestration. Example: - Orchestration A: calculations of some kind + send to integration A - Orchestration B: same calculations as in orchestration A + send to integration B It would be easier and more scalable if it would have the following behavior: - Orchestartion A: calculations of some kind - Orchestartion B: Orchestartion A + send to integration B - Orchestartion C: Orchestartion A + send to integration C By having this enhancement it would limit my changes to only Orchestration A instead of having to change it multiple times in all orchestration it has been copied (as it needs to happen now).

  • Ideas

    Status
    Target Release
    2HCY'16
  • Please login to view any attachments.

  • After further review, we believe this is a duplicate of http://www.serenacentral.com/community/ideas/sbm/methods-or-functions-as-reusable-orchestration-snippets.
    David J. Easter Commented by David J. Easter May 02, 2016
    #1 Reviewer  -  

    After further review, we believe this is a duplicate of http://www.serenacentral.com/community/ideas/sbm/methods-or-functions-as-reusable-orchestration-snippets.

    We will put this under consideration for the 2HCY'16 release.
    David J. Easter Commented by David J. Easter February 21, 2016
    #1 Reviewer  -  

    We will put this under consideration for the 2HCY'16 release.

    You can indeed do what Vitaliy describes, we did run into one issue when we created a custom event in composer, exported the wsdl, and imported into composer so we could call it. If the custom event is in the same msd file as the one that you imported into the wsdl you will encounter issues when deploying and you will need to revert the changes (we had to go back to a previous version before the wsdl was imported). If it is in an independent msd, this will work fine. We've seen the issue with 10.1.3.x and 10.1.4.x, but possibly goes forward to the current versions.
    David Matsumoto Commented by David Matsumoto December 01, 2015
    Top 50 Reviewer  -  

    You can indeed do what Vitaliy describes, we did run into one issue when we created a custom event in composer, exported the wsdl, and imported into composer so we could call it. If the custom event is in the same msd file as the one that you imported into the wsdl you will encounter issues when deploying and you will need to revert the changes (we had to go back to a previous version before the wsdl was imported). If it is in an independent msd, this will work fine. We've seen the issue with 10.1.3.x and 10.1.4.x, but possibly goes forward to the current versions.

    ... of course that solution doesn't give us the ability to get some response since asynchronous orchestrations doesn't return anything but it still can be used for some approaches.
    Another solution that can be implemented fully in Composer - possibility to create callable orchestration parts letting user call them within the orchestrations of the same application. Such parts can be given to the BPEL encoder as single orchestration and be transparent to it. So this question can be addressed to Tom.
    Vitaliy Olexandrovych Tkachenko Commented by Vitaliy Olexandrovych Tkachenko September 21, 2015
    Top 50 Reviewer  -  

    ... of course that solution doesn't give us the ability to get some response since asynchronous orchestrations doesn't return anything but it still can be used for some approaches.
    Another solution that can be implemented fully in Composer - possibility to create callable orchestration parts letting user call them within the orchestrations of the same application. Such parts can be given to the BPEL encoder as single orchestration and be transparent to it. So this question can be addressed to Tom.

    You can easily do this calling asynchronous orchestration from any orchestration. Just export the WSDL for the asynchonous orchestration you'd like to call and import this WSDL in any orchestration you'd like to call from. Then call it as any other SOAP service!
    Vitaliy Olexandrovych Tkachenko Commented by Vitaliy Olexandrovych Tkachenko September 21, 2015
    Top 50 Reviewer  -  

    You can easily do this calling asynchronous orchestration from any orchestration. Just export the WSDL for the asynchonous orchestration you'd like to call and import this WSDL in any orchestration you'd like to call from. Then call it as any other SOAP service!

     

PrintEmail

Recent Tweets