To deploy a Petals ESB composed of several nodes, we should be able to deploy components and SAs on each node concurrently.
As Petals CLI is able to work with only one container at a time, we should be able to launch several Petals CLI in the same time on the same machine.
In script mode, as the connexion establishment must be done in the script file, we can imagine to execute several scripts concurrently with the same Petals CLI instance. But if we can launch several Petals CLI instances in the same time, the script files can be executed concurrently launching a Petals CLI instance by script file, delegating the concurrency to the execution shell.
To deploy a Petals ESB composed of several nodes, we should be able to deploy components and SAs on each node concurrently.
As Petals CLI is able to work with only one container at a time, we should be able to launch several Petals CLI in the same time on the same machine.
In script mode, as the connexion establishment must be done in the script file, we can imagine to execute several scripts concurrently with the same Petals CLI instance. But if we can launch several Petals CLI instances in the same time, the script files can be executed concurrently launching a Petals CLI instance by script file, delegating the concurrency to the execution shell.
Environment:
-
Issue Links
Depends
This issue depends on:
PETALSESBCLI-117
The default value of the HTTP port should be one of the available free ports
Christophe DENEUX added a comment - Thu, 4 Jun 2015 - 15:24:33 +0200 A workaround is to set the parameter embedded.http.port to 0 in Petals CLI preferences.
A workaround is to set the parameter embedded.http.port to 0 in Petals CLI preferences.