Version: 17.07

Supported Since: 17.01

IPS has the capability to deploy UltraESB instances on different zones. The idea of zone is established as users may want to deploy their mission critical processes on a high performance and less fault prone datacenter while they keep a backup data center to continue the operations only if the primary data center goes down. This is a very common requirement in a high available enterprise deployment. A fully fledged production ready IPS cluster may contain more than on physical nodes users are free to add machines from both primary data centers and secondary data centers to IPS network. Then using the IPS console you can tag those machine with respect to the zone they belong in. IPS defines two zone.

  • PDC (Primary Data Center) - All the UltraESB instances will be given the priority to be scheduled on this zone if there are enough resources in the machines of this zone

  • SDC (Secondary Data Center) - UltraESB instances will be spawned in this zone if and only if there is no running machine in PDC or there is no enough resources in PDC to start instances

Adding machines (nodes) in IPS to a specific Zone

  • Go to Infrastructure tab and select Zones tab

S2I workflow
Figure 1. Go to Zones tab
  • Select the Zone that should be configured

S2I workflow
Figure 2. Click to add Nodes to Zone - PDC
  • Select the nodes that should be included in to the zone

S2I workflow
Figure 3. Add Nodes to Zone - PDC
If any UltraESB instance is scheduled on SDC due to the lack of resources, will not come back to PDC zone automatically. You may have to refresh the cluster that particular instance belongs or you have to manually kill the instance deployed on SDC. Then framework will spawn an identical instance on PDC zone
Zones differ from node groups in the aspect that they are not a strict enforcement of the running node for an UltraESB instance, rather a priority-based preference.
In this topic
In this topic
Contact Us