.Create a file in etc/featuresBoot.d/flows.boot
[source, console]
----
sudo vi etc/featuresBoot.d/flows.boot
----

.Add the following features to Sentinel on startup
[source, flows.boot]
----
sentinel-jsonstore-postgres
sentinel-blobstore-noop
sentinel-jms
sentinel-flows
----

.Connect to the Karaf shell via SSH
[source, console]
----
ssh -p 8301 admin@localhost
----

.Configure Sentinel tracing, REST and ActiveMQ endpoints
[source, karaf]
----
config:edit org.opennms.sentinel.controller
config:property-set location SENTINEL<1>
config:property-set id 00000000-0000-0000-0000-000000ddba11<2>
config:property-set broker-url failover:tcp://my-activemq-ip:61616<3>
config:update
----
<1> A location string is used to assign the Sentinel to a monitoring location.
This can be an existing location or a new location and does not impact the messages that this Sentinel will process.
<2> Unique identifier you define to use as a node label for monitoring the Sentinel instance within {page-component-title}.
This can be a GUID or a hostname.
<3> URL that points to ActiveMQ broker.

.Configure the credentials and exit Karaf shell
[source, karaf]
----
opennms:scv-set opennms.broker my-sentinel-user my-sentinel-password<1>
----
<1> Set the credentials for the ActiveMQ message broker

NOTE: The credentials are encrypted on disk in `$\{SENTINEL_HOME}/etc/scv.jce`.

Exit the Karaf Shell with kbd:[Ctrl+d]

.Restart the Sentinel to apply the configuration
[source, console]
----
sudo systemctl restart sentinel
----

.Run health-check to verify configuration
[source, karaf]
----
opennms:health-check
----

.Ensure features are installed and work properly
[source, output]
----
Verifying the health of the container

Verifying installed bundles                    [ Success  ]
Retrieving NodeDao                             [ Success  ]
Connecting to JMS Broker                       [ Success  ]
Connecting to ElasticSearch ReST API (Flows)   [ Success  ]

=> Everything is awesome
----
