Uninstalling Petals ESB Registry

According to Debian policies, Petals ESB Registry packages can be uninstalled with or without purging configuration files, with your favorite Debian tools (synaptic, apt-get, dpkg).

In addition to the runtime files, the purge will remove following directories containing some configuration or working files:

• /etc/petals-registry/member-enable
• /var/lib/petals-registry
• /var/log/petals-registry
• /var/run/petals-registry

The dedicated Petals system user and group are also removed when purging packages. The Petals ESB Registry node configurations (/etc/petals-registry/member-available) are never removed except the sample one, to be reused eventually.

All Petals ESB Registry nodes declared into /etc/petals-registry/member-enable will be automatically stopped during the uninstallation process. If you have started manually other Petals ESB Registry nodes, you must stop them before to launch the uninstallation process.

Upgrading Petals ESB Registry

To update the installed version of Petals ESB Registry:

• just uninstalled Petals ESB Registry packages without purging it:

  > sudo dpkg -r petals-registry ...

• and installed new Petals ESB Registry packages.

All Petals ESB Registry nodes declared into /etc/petals-registry/member-enable will be automatically stopped during the uninstallation process and restarted during the installation process. If you have started manually other Petals ESB Registry nodes, you must stop them before to launch the uninstallation process, and restart them after the installation process.

Content of the packages

Content of the package "petals-registry"

This package arrives with following directories and files:

• /usr/bin/petals-registry: The script used to start a Petals ESB Registry node,
• /usr/bin/petals-registry.sh: A link to /usr/bin/petals-registry,
• /usr/share/petals-registry: Directory containing all Java libraries required by Petals ESB Registry,
• /etc/init.d/petals-registry: Automatic startup/stop script
• /etc/petals-registry/member-available/<member-id>: A directory containing the configuration of a Petals ESB Registry node:
  • member.properties: the base configuration of the Petals ESB Registry node,
  • usually, the following configuration files are placed in the same directory than the file member.properties:
    • cluster.xml: the Petals ESB Registry cluster of which the container is a member,
    • logging.properties: configuration file of the logging system based on JDK Logging
• /etc/petals-registry/member-enable: A directory containing links to sub-directoryies of /etc/petals-registry/member-available. If a Petals ESB Registry node is linked into this directory, it will be automatically started on machine startup,
• /var/log/petals-registry/<member-id>: Default location in which logging files of the Petals ESB Registry node will be written,
• /usr/share/petals-registry/licenses: Directory containing license files.