|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (3)
View Page HistoryA development installation is an installation that is not suitable for production use.
By default, Petals ESB is configured to work as a single node, on localhost, using an embedded database system.
We recommend to use the ZIP archive to install Petals ESB in a development mode because the user should be able to do following actions to be more productive:
* to (un)install/(un)deploy artefacts through the directories of the auto-loader,
* to patch a JBI component directly in the internal repository of Petals ESB without requiring an (un)installation (just a restart of the Petals container that is faster),
* to update service unit directly in the internal repository of Petals ESB without requiring an (un)deployment (just a restart of the Petals container that is faster).
* to (un)install/(un)deploy artefacts through the directories of the auto-loader,
* to patch a JBI component directly in the internal repository of Petals ESB without requiring an (un)installation (just a restart of the Petals container that is faster),
* to update service unit directly in the internal repository of Petals ESB without requiring an (un)deployment (just a restart of the Petals container that is faster).
By default, Petals ESB is configured to work as a single node, on localhost (it can't be managed from a remote machine through JMX).
h1. Installation