To install Apache Brooklyn on a production server:
This guide covers the basics. You may also wish to configure:
Check that the server meets the requirements. Then configure the server as follows:
~/.brooklyn directory on the host with $ mkdir ~/.brooklyniptables or other firewall service, making sure that incoming connections on port 8443 is not blockednss for SSL.Download Brooklyn and obtain a binary build as described on the download page.
{% if ‘SNAPSHOT’ in book.brooklyn_version %} Expand the tar.gz archive (note: as this is a -SNAPSHOT version, your filename will be slightly different): {% else %} Expand the tar.gz archive: {% endif %}
{% if ‘SNAPSHOT’ in book.brooklyn_version %}
{% else %}
{% endif %}
This will create a apache-brooklyn-{{ book.brooklyn_version_stable }} folder.
Let's setup some paths for easy commands.
Set up brooklyn.cfg as described here:
Out of the box, Apache Brooklyn includes the default Karaf security configuration. This configuration is used to manage connections to the ssh port of Karaf (which is available to localhost connections only). It is recommended that you update the credentials as detailed in the Karaf Security page.
By default Brooklyn loads the catalog of available application components and services from default.catalog.bom on the classpath. The initial catalog is in etc in the dist or in /etc/brooklyn depending on how you installed Brooklyn. If you have a preferred catalog, simply replace that file.
More information on the catalog is available here.
Launch Brooklyn in a disconnected session so it will remain running after you have logged out:
% nohup bin/brooklyn launch > /dev/null 2&>1 &
Apache Brooklyn should now be running on port 8081 (or other port if so specified).
To install on a different port edit config in etc/org.ops4j.pax.web.cfg.