Example scenarios of OpsCenter deployments include configuring for multiple regions or very large clusters.

Configuring named route linking

Enable route URL deep linking within the UI, which allows URL navigating to locations
within the OpsCenter UI web application.

Enable route URL deep linking to allow navigating to locations within the OpsCenter
UI web application and displaying full path URLs in the browser address bar.
Enabling the routes feature allows sending a link to users that directs them to a
particular page or location within a page, with the URL reflecting the current
location within the UI. Routing URLs enhance the user experience with navigating and
sharing links, and facilitate learning the structure of the OpsCenter
application.

When routes are enabled, clicking on certain areas within the OpsCenter application
such as a dashboard preset updates the URL to reflect the current location in the
OpsCenter UI. For example, clicking the Latencies tab displays the URL as
localhost:8888/opscenter/index.html#Test_Cluster/dashboard/presets/latencies.
Alternately, manually entering a known URL also navigates to the UI location.

The slash (root) is the overview route. The route is everything in the URL that comes
after the hash #. The hash allows for linking and navigation. The routes are not
case-sensitive.

If the routes feature is not enabled, the URL does not reflect its current location
within the OpsCenter application. The URL always displays as
localhost:8888/opscenter/index.html regardless of
location.

Note: Live routes is a Labs feature. Not all locations in the OpsCenter and Lifecycle
Manager UIs currently have a URL available for linking.

opscenterd.conf

The location of
the opscenterd.conf file depends on the type of
installation: