...
An Ultra Pipeline calls a SOAP service and the service can process five API calls at one time => Set the number of instances to 5 for the Snaplex.
Instances per Node
This selection sets the number of pipeline instances per node through pre-defined values on a scale. Use this setting during times when the request volume on the Ultra Task is predictably steady , without and when there are no limits on the number of concurrent requests that the downstream systems can process. The balancing mechanism is designed to distribute them evenly.
For example, setting :
Setting this to 2 runs two pipelines pipeline instances on each JCC node. If the Snaplex has four JCC nodes, then eight pipeline instances start.
This approach doesn’t guarantee two instances per node, but eight nodes in total. The balancing mechanism is designed to distribute them evenly.
In this configuration, you can specify manually how many instances to run per Snaplex node. Setting this to four runs eight instances start.
This setting suits both types of Ultra Pipeline designPipelines, providing redundancy through scaling.For example, if you run two instances in a Snaplex with four JCC nodes, then eight instances of the pipeline are run per node. Likewise, specifying two instances at six JCC nodes in the Snaplex creates twelve instances of the pipeline.
AutoScaling
Scale the number of pipeline instances based on the number of requests being processed. This option can be used when the request rate is expected to be variable, with low and peak volumes being significantly different.
...