none
How to Bind Host instance dynamically for Orchestration RRS feed

  • Question

  • Is there any possibility to specify host instance dynamically for orchestration?, Orchestration logic is same for all the host instances.

    Wednesday, February 18, 2015 9:40 AM

Answers

  • You don’t have a way to have dynamic host instance for Orchestration. Think this in this way, host instance are physical process container, there is nothing called dynamic physical container.

    You want to have dynamic host because some of your configuration data will change and you don’t want to restart your host instance.

    If you expect your configuration data change often and you don’t want to restart the host instance, then don’t cache the data, just get from the data source everything.

    If you still want to keep the data in cache and want to change it, find maintenance windows – a time where you can change the configuration data in backend and restarting the host instance would not affect any business process.


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

    Wednesday, February 18, 2015 4:29 PM

All replies

  • No. An orchestration has to be bound to ONE Host Instance.

    Perhaps if you were to explain what is it that you're planning on doing and how you think dynamic binding for orchestrations would help we might be in a position to better comprehend and respond.

    Regards.

    Wednesday, February 18, 2015 10:55 AM
  • Hi Ramachandraiah,

     “Dynamic” ports are configured/used so that the end point can be resolved dynamically. In case of host instances, why do you want to set the host instances dynamically to Orchestration?

    Host instances are physical containers of BizTalk runtime, there is no need to dynamically configures a host instance to Orchestration.

    May be you want to change the host instances often (again I don’t why) and if you’re looking for automated way to change the host instance configured to Orchestration, then you can consider using WMI or Powershell scripts would unlist the Orchestration and change its host instance configuration and enlist again.


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

    Wednesday, February 18, 2015 10:57 AM
  • Hi,

    No to my knowledge we cant do it. Also I am wondering why is the need for you having HIS picked at run time. We generally define HIS based on parameters like high volume /large msg/send port/rcv port types etc...And before we design the orchestration generally it is decided which HIS it will be using .


    Regards Pushpendra K Singh

    Wednesday, February 18, 2015 3:15 PM
  • Hi Ashwin,

    As you suggested, we can achieve this using WMI, below is my requirement.

    We have many host instances  and related orchestrations,these orchestrations will use configuration information from cache.

    Some time we may require to change configuration data, those data will not update until we restart host instance,that will impact to business if we restart host instance and also those configuration data will be constant up to 70%.

    to avoid those issue, we implemented a orchestration to invalidate specified Appdomain(host instance) cache objects.

    As per this solution orchestration has same logic, but it's require a duplication of orchestration per each host instance.

     

    Wednesday, February 18, 2015 3:43 PM
  • You don’t have a way to have dynamic host instance for Orchestration. Think this in this way, host instance are physical process container, there is nothing called dynamic physical container.

    You want to have dynamic host because some of your configuration data will change and you don’t want to restart your host instance.

    If you expect your configuration data change often and you don’t want to restart the host instance, then don’t cache the data, just get from the data source everything.

    If you still want to keep the data in cache and want to change it, find maintenance windows – a time where you can change the configuration data in backend and restarting the host instance would not affect any business process.


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

    Wednesday, February 18, 2015 4:29 PM