Red Hat JBoss Fuse 6 · Red Hat JBoss Fuse 6.2 Management Console User Guide 4. PART I. INTRODUCTION PART I. INTRODUCTION 5. CHAPTER 1. FUSE MANAGEMENT CONSOLE OVERVIEW ... the Fuse

Red Hat JBoss Fuse 6.2

Management Console User Guide

Managing your environment from the Web

Last Updated: 2017-09-26

Red Hat JBoss Fuse 6.2 Management Console User Guide

Managing your environment from the Web

JBoss A-MQ Docs TeamContent [email protected]

Legal Notice

Copyright © 2015 Red Hat.

The text of and illustrations in this document are licensed by Red Hat under a Creative CommonsAttribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA isavailable athttp://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you mustprovide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinitylogo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and othercountries.

Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.

Java ® is a registered trademark of Oracle and/or its affiliates.

XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the UnitedStates and/or other countries.

MySQL ® is a registered trademark of MySQL AB in the United States, the European Union andother countries.

Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally relatedto or endorsed by the official Joyent Node.js open source or commercial project.

The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marksor trademarks/service marks of the OpenStack Foundation, in the United States and othercountries and are used with the OpenStack Foundation's permission. We are not affiliated with,endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

Abstract

The Fuse Management Console User Guide describes the Fuse Management Console user interfaceand the tasks you can perform to manage containers and fabrics. This guide assumes that you arefamiliar with Red Hat JBoss Fuse components, Apache components, and the processingrequirements for your organization.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

PART I. INTRODUCTION

CHAPTER 1. FUSE MANAGEMENT CONSOLE OVERVIEWOVERVIEWUSER INTERFACE OVERVIEW

CHAPTER 2. ACCESSING THE MANAGEMENT CONSOLEPREREQUISITESACCESSING THE MANAGEMENT CONSOLE

CHAPTER 3. SECURING THE MANAGEMENT CONSOLEOVERVIEWAUTHENTICATIONSSL/TLS SECURITY

PART II. CONTAINER MANAGEMENT

CHAPTER 4. CONTAINER PERSPECTIVEOVERVIEWTOOLBAR

CHAPTER 5. MANAGING CONTAINERSOVERVIEWCREATING A CONTAINEREDITING CONTAINER PROPERTIESDELETING ONE OR MORE CONTAINERS

CHAPTER 6. MANAGING JMS QUEUES AND MESSAGESOVERVIEWCREATING A QUEUEMANAGING QUEUES AND MESSAGES

CHAPTER 7. ACTIVEMQ PAGEOVERVIEW

CHAPTER 8. CAMEL PAGEOVERVIEW

CHAPTER 9. CONNECT PAGEOVERVIEW

CHAPTER 10. JMX PAGEOVERVIEW

CHAPTER 11. LOGS PAGEOVERVIEW

CHAPTER 12. OSGI PAGEOVERVIEW

CHAPTER 13. THREADS PAGEOVERVIEW

PART III. FABRIC MANAGEMENT

CHAPTER 14. FABRIC PERSPECTIVE

5

666

999

11111111

12

131313

1515151516

17171717

1919

2020

2121

2323

2424

2525

2727

28

29

Table of Contents

1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OVERVIEWTOOLBAR

CHAPTER 15. CREATING OR JOINING A FABRICOVERVIEWCREATING OR JOINING A FABRIC

CHAPTER 16. MANAGING PROFILESOVERVIEWCREATING A PROFILEEDITING A PROFILEDELETING ONE OR MORE PROFILES

CHAPTER 17. ASSIGNING PROFILES TO CONTAINERSOVERVIEWCREATING A CONTAINER WITH AN ASSIGNED PROFILEASSIGNING OR REMOVING A PROFILE FROM AN EXISTING CONTAINERASSIGNING MULTIPLE PROFILES TO MULTIPLE CONTAINERS

CHAPTER 18. PROFILES DETAILS PAGEOVERVIEWFUNCTION BUTTONSVIEW ASSOCIATED CONTAINERSABSTRACT TOGGLELOCKED TOGGLEPARENTS LISTDEPLOYMENTS

CHAPTER 19. PATCHING A FABRICOVERVIEWCREATING A VERSIONPATCHING A FABRIC

CHAPTER 20. SERVICES AREA20.1. SERVICES OVERVIEW20.2. CONTAINERS PAGE20.3. PROFILES PAGE20.4. MQ PAGE20.5. APIS PAGE20.6. EIPS PAGE20.7. REGISTRY PAGE20.8. MAP PAGE

CHAPTER 21. WIKI PAGEOVERVIEWACTION BARREPOSITORY EXPLORERDETAILS PANE

CHAPTER 22. DASHBOARD PAGEOVERVIEWNAVIGATION BARACTIVE DASHBOARD PANE

CHAPTER 23. HEALTH PAGEOVERVIEW

2929

303030

3131313131

3333333334

3535353536363636

37373737

393939414345464647

4949505050

51515151

5353


2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PART IV. LOG MANAGEMENT WITH INSIGHT

CHAPTER 24. GETTING STARTEDOVERVIEWPREREQUISITESDATA STORE INSTALLATIONWEB VIEWER INSTALLATIONCONFIGURING LOG COLLECTIONCONFIGURING METRICS COLLECTIONVIEWING AND ANALYZING LOGS AND METRICS

CHAPTER 25. INSIGHT PERSPECTIVEOVERVIEWTOOLBAR

CHAPTER 26. CAMEL PAGEOVERVIEW

CHAPTER 27. LOGS PAGEOVERVIEW

CHAPTER 28. CAMEL EVENTS PAGEOVERVIEW

CHAPTER 29. ELASTICSEARCH PAGEOVERVIEW

PART V. DIAGNOSTIC TOOL PLUG-IN

CHAPTER 30. OPEN A NEW CASEOPENING A NEW CASE

CHAPTER 31. EDIT AN EXISTING CASEEDITING AN EXISTING CASE

CHAPTER 32. USING THE DIAGNOSTIC TOOLUSING THE DIAGNOSTIC TOOL

CHAPTER 33. LIMITATIONS OF THE DIAGNOSTIC TOOL

54

5555555555565656

575757

5858

5959

6161

6363

64

6565

6666

6767

68

Table of Contents

3


4



5

CHAPTER 1. FUSE MANAGEMENT CONSOLE OVERVIEW

OVERVIEW

The Fuse Management Console provides a central interface to manage and configure Fuse entities. Youcan use the Fuse Management Console to configure and deploy containers, Apache ActiveMQ brokers,and fabrics. You also monitor JBoss Fuse and system resources, perform updates, and start or stopservices.

The Fuse Management Console is available by default when you install Red Hat JBoss Fuse, and mustbe accessed using a web browser.

USER INTERFACE OVERVIEW

The Management Console consists of the following areas:

Welcome Page

Introduction to the Management Console and help topics.

Menu Bar

Global and user options. The Menu bar contains the following options:

Option Description

Opens the logging console in a drop-down pane.

Opens the Welcome page and shows the wiki help.

Admin >Preferences

Opens the Preferences page. Use the page to configure global options for the user.

Admin > LogOut

Logs out of the Management Console.

Admin >About

Opens the About page that shows version information.

Container Perspective

Container management options. The actual areas depend on the container features and bundles.The Container perspective can contain the following options:

Option Description

ActiveMQ Tree view and details of running Apache ActiveMQ brokers. This page is available onlywhen you connect to a container with an ActiveMQ profile.


6

Camel Tree view and details of running Apache Camel routes. This page is available only whenyou connect to a container with a Camel profile.

Connect Connection page to a remote server or a local JVM with a running Jolokia agent.

Dashboard Overview of the Management Console status, services status, and systemperformance. You can add views to the dashboard and create additional dashboards. Ifyou create or join a fabric, this toolbar option is not available. Use the Dashboardpage in the Fabric perspective to view information for all containers in the fabric. Formore information, see Dashboard Page.

Health List and status of running health mbeans. This page shows any available containerhealth mbeans. If you create or join a fabric, this toolbar option is not available. Formore information, see Health Page.

JMX Tree view of the JMX domains and mbeans. You can view details and executecommands on the mbeans.

Logs List of log entries. Use this page to view activity details and error messages.

Maven Search for Maven repositories using either a simple search or an advanced search withmore parameters. This page is only available if the hawtio-maven-indexerfeature has been installed.

OSGi Detailed view of the JBoss Fuse OSGi environment. Use this page to manage bundles,features and configurations, and view details of Java packages and OSGi services.

Red HatAccess

Gain access to the Red Hat Customer Portal. Sign in to the Red Hat Customer Portal tosearch the Knowledge Base, Open a new support case, or list existing support cases.You can also use this page to use the Log File Viewer.

Terminal Emulator view of the Karaf console. Use this page to run JBoss Fuse commands in thesame way you run commands in the Karaf console.

Threads List of active threads and stack trace details for each thread.

Wiki Explorer view of the fabric configuration repository and wiki content. The repositorycontains files that affect the behavior of the fabric during runtime. This toolbar optionis available only if you create or join a fabric, and opens the Wiki page in the Fabricperspective. For more information, see Wiki Page.

Option Description

Fabric Perspective

Fabric management options. Available only if you create or join a fabric. The Fabric perspectivecontains the following options:

CHAPTER 1. FUSE MANAGEMENT CONSOLE OVERVIEW

7

Option Description

Containers View the containers available on this instance of Fuse. Start/Stop, Delete or Createcontainers. Click the container name to get more information about each container.

Profiles Lists the profiles available to this instance of Fuse. Click Details... to get moredetails of each profile. You can deploy selected profiles to a new container, assignselected profiles to existing container, or add requirements to selected profiles.

Wiki Explorer view of the fabric configuration repository and wiki content. The repositorycontains files that affect the behavior of the fabric during runtime.

Services View the services available on Fuse. Stop or start containers, edit profiles andadminister services.

Scaling Increase or decrease the number of required instances of a profile and review theeffect on the health of the profile. You can also set up SSH or Docker Configurations.

Dashboard Overview of the Management Console status, services status, and systemperformance. You can add views to the dashboard and create additional dashboards.

Health List and status of running fabric and container health mbeans. For more information,see Health Page.


8

CHAPTER 2. ACCESSING THE MANAGEMENT CONSOLE

PREREQUISITES

To access the Management Console, you must start JBoss Fuse and configure user credentials.

NOTE

If you use JBoss Fuse on OpenShift, you can skip this task and access the ManagementConsole directly with the JBoss Fuse application URL after you deploy the JBoss Fusecartridge. For more information about how to get started with JBoss Fuse on OpenShift,see the Cloud Computing with Fabric book for this release of JBoss Fuse.

To configure user credentials and start JBoss Fuse:

1. In the command line, navigate to the directory in which you installed JBoss Fuse and run thefollowing command:

The Karaf console starts and shows version information, the default Management Console URL,and a list of common commands.

2. If no user exists for JBoss Fuse, you can create one by running the

command. You can also define the user name and password directly in the etc/users.properties file. For more information, see the Red Hat JBoss Fuse InstallationGuide.

ACCESSING THE MANAGEMENT CONSOLE

To access the Management Console:

1. In a Web browser, enter the URL to connect to the Management Console in the followingformat:

NOTE

For a list of supported browsers, see access.redhat.com.

For example, use the following default URL to connect to the Management Console locally:

./fuse

esb:create-admin-user

http://<host_name>:<port_number>

http://localhost:8181

CHAPTER 2. ACCESSING THE MANAGEMENT CONSOLE

9

https://access.redhat.com/site/articles/310603

NOTE

You can configure the pax-web property to support HTTPS connections for aspecific container.

See chapter "Securing the Jetty HTTP Server" in "Security Guide" for moredetails.

2. In the login page, enter the user name and password and click Log In.

If you created or joined a fabric, the Management Console opens to the Fabric perspective.Otherwise, only the Container perspective is available. By default, the Management Consoleshows the Welcome page. You can choose to hide the Welcome page at the bottom of thepage.


10

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Security_Guide/WebConsole.html

CHAPTER 3. SECURING THE MANAGEMENT CONSOLE

OVERVIEW

There are two main aspects to securing the Management Console:

Authentication

SSL/TLS security

AUTHENTICATION

Authentication is enabled by default on the Management Console and is required in order for theManagement Console to function correctly. The authentication mechanism consists of the followingkey elements:

HTTP BASIC authentication protocol—the standard HTTP protocol for transferringusername/password credentials is the BASIC authentication protocol. This protocol sendsusername/password credentials in plaintext, so these credentials are vulnerable to snooping,unless you enable SSL/TLS security.

JAAS authentication—the Java Authentication and Authorization Service (JAAS) is a pluggableframework for authenticating credentials on the server side. The Jetty servlet container (whichhosts the Management Console) is configured to use the karaf JAAS realm by default. Thisensures that the Management Console uses the same pool of user credentials as the otherstandard container services (where the user credentials are usually stored in the etc/users.properties file by default, in a standalone container).

SSL/TLS SECURITY

SSL/TLS security is not enabled by default for the Management Console. It is recommended that youenable SSL/TLS security on the Management Console to protect username/password credentials fromsnooping. For detailed instructions on how to enable SSL/TLS security, please see the followingreference:

chapter "Securing the Jetty HTTP Server" in "Security Guide"

CHAPTER 3. SECURING THE MANAGEMENT CONSOLE

11

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Security_Guide/WebConsole.html

PART II. CONTAINER MANAGEMENT

Abstract

You use the Fuse Management Console to deploy containers to a fabric and manage containerproperties. You can manage properties for each container such as the JMX domains, versions, andhosts. You can also review log entries and monitor system status and performance while the containerruns.


12

CHAPTER 4. CONTAINER PERSPECTIVE

OVERVIEW

When you log in to the Management Console, you use the Container perspective to configure andmonitor runtime information about a specific container. By detault, the Container perspective showsinformation about the root container. You can also select and connect to any container from the Fabric perspective.

TOOLBAR

The Container perspective contains a toolbar that you use to manage and monitor containercomponents. The actual areas depend on the container features and bundles and whether thecontainer is deployed to a fabric. The toolbar can contain the following options:

Option Description

ActiveMQ Tree view and details of running Apache ActiveMQ brokers. This page is available onlywhen you connect to a container with an ActiveMQ profile.

Camel Tree view and details of running Apache Camel routes. This page is available only whenyou connect to a container with a Camel profile.

Connect Connection page to a remote server or a local JVM with a running Jolokia agent.

Dashboard Overview of the Management Console status, services status, and system performance.You can add views to the dashboard and create additional dashboards. If you create orjoin a fabric, this toolbar option is not available. Use the Dashboard page in the Fabricperspective to view information for all containers in the fabric. For more information, seeDashboard Page.

Health List and status of running health mbeans. This page shows any available container healthmbeans. If you create or join a fabric, this toolbar option is not available. Use the Healthpage in the Fabric perspective to view fabric and container health mbeans. For moreinformation, see Health Page.

JMX Tree view of the JMX domains and mbeans. You can view details and execute commandson the mbeans.

Logs List of log entries. Use this page to view activity details and error messages.

OSGi Detailed view of the JBoss Fuse OSGi environment. Use this page to manage bundles,features and configurations, and view details of Java packages and OSGi services.

Terminal Emulator view of the Karaf console. Use this page to run JBoss Fuse commands in thesame way you run commands in the Karaf console.

Threads List of active threads and stack trace details for each thread.

CHAPTER 4. CONTAINER PERSPECTIVE

13

Wiki Explorer view of the fabric configuration repository and wiki content. The repositorycontains files that affect the behavior of the fabric during runtime. This toolbar option isavailable only if you create or join a fabric, and opens the Wiki page in the Fabricperspective. For more information, see Wiki Page.

Option Description


14

CHAPTER 5. MANAGING CONTAINERS

OVERVIEW

You can create, edit, and delete a container from the Fabric perspective of the Management Console.The type of container you create depends on the purpose and location of the container.

You can create a child container, a cloud container, or an ssh container. If you create a cloud container,make sure you have the credentials to your cloud account. If you create an ssh container, make sureyou have the remote host properties.

If you do not create or join a fabric, you must use the Karaf console to create the container and use theContainer perspective to view and manage container properties. See Red Hat JBoss Fuse ConsoleReference for Karaf Console commands.

CREATING A CONTAINER

Depending on the location from which you create the container, the Management Console auto-fillsone or more container properties. For example, if you create a container for an existing profile fromthe Wiki page, the profile name appears in the Selected Profiles list.

To create a container:

1. To create a container, navigate to one of the pages from which you can create a container andclick the +Create button to open the Create New Container page. You can createcontainers from the following pages:

The Container page

The Services > Container page

The Services > MQ page

2. Set the container properties, such as the name and user credentials to use when JBoss Fuseruns the container.

3. Click the Create and Start Container button to save the container. The Containerspage opens and shows the container name and status. It may take some time to download andassign all the container features and dependencies.

NOTE

If you create an OpenShift container, the container also appears as anapplication on the OpenShift applications page.

EDITING CONTAINER PROPERTIES

You can access the Container Details page from multiple areas in the Fabric perspective of theManagement Console, amongst which are:

The Container page

The Services > Container page

CHAPTER 5. MANAGING CONTAINERS

15

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Console_Reference/Consolefabric.html

To edit a container, click the container name and edit the container properties in the Container Details page. If you added or removed profiles, bundles, or other components, the ManagementConsole shows the progress of the changes and the state of the container.

DELETING ONE OR MORE CONTAINERS

You can delete containers from the Containers page or the Services > Containers page.

To delete containers, select one or more containers from the list and click the Delete button.


16

CHAPTER 6. MANAGING JMS QUEUES AND MESSAGES

OVERVIEW

You can create, edit, and delete message queues for JMS brokers from the ActiveMQ page of the Container perspective. You can also search for messages, move, and resend messages directly fromthe queue.

CREATING A QUEUE

1. Connect to the container and open the ActiveMQ page.

2. Select the top-level node in the tree and click the Create button in the toolbar. The detailspane shows a text box and a type selector.

3. Enter a name for the queue and make sure to select the Queue radio button. The queueappears in the Queue folder under the top-level node in the tree.

MANAGING QUEUES AND MESSAGES

When you select a queue from the Queue folder, the details pane shows a toolbar with the followingoptions:

Attributes

Detailed information about the queue properties. You can click each property to show additionalinformation about the property, such as description, type, and default value.

Browse

Grid view of all messages in the queue. You can select one or more messages to resend, move, ordelete. You can also filter the message list according to properties such as the message ID, priority,type, custom header attributes, and message body.

Send

Composer window where you can create a message to send to the queue. You can format themessage as JSON, plain text, Properties, or XML. You can also add header properties or choosemessage templates.

Diagram

Visual representation of broker components. You can choose to show or hide component types,such as queues, topics, profiles, or containers.

Delete

Options to purge or delete the queue. You can purge the queue to delete all messages withoutdeleting the queue itself, or delete the queue including all messages and attributes.

CHAPTER 6. MANAGING JMS QUEUES AND MESSAGES

17

WARNING

Deleting and purging the queue cannot be undone.

Operations

List of possible operations that you can perform in the queue. To manually execute an operation,you click an operation and define parameters and conditions if exist for the operation.

Chart

Timeline representation of message processing in the queue. The timeline dynamically shows themessage flow in real-time. You can edit the chart to determine which attributes to show in thechart.


18

CHAPTER 7. ACTIVEMQ PAGE

Abstract

You view and and manage Apache ActiveMQ brokers in the ActiveMQ page. You can view brokerattributes, run commands, add destinations, and monitor broker status.

OVERVIEW

You access the ActiveMQ page from the Container perspective. This page is available only whenyou connect to a container that uses one or more ActiveMQ brokers.

The following image shows an example of the ActiveMQ page:

The ActiveMQ page contains the following sections:

ActiveMQ Tree

Tree view of running ActiveMQ brokers organized in folders. You can click a folder to show thefolder contents, and select a topic, queue, or broker to show the details in the details pane.

Toolbar

Options to view attributes, run commands, and view or create charts for the selected entity. Youcan also add the current view to the dashboard and toggle full screen mode. If you select a topic,you can also manually send the message to an endpoint.

Details Pane

Detailed view of the selected entity. The contents of this pane depend on the toolbar option that youselect. You can filter the details pane to show only values that match the text string that you enter.

CHAPTER 7. ACTIVEMQ PAGE

19

CHAPTER 8. CAMEL PAGE

Abstract

You view and and manage Apache Camel routes and dependencies in the Camel page. You can viewroute attributes and source code, debug and trace the route, and monitor route status.

OVERVIEW

You access the Camel page from the Container perspective. This page is available only when youconnect to a container that uses one or more Camel routes.

The following image shows an example of the Camel page:

The Camel page contains the following sections:

Camel Tree

Tree view of running Camel routes and dependencies organized in folders. You can click a folder toshow the folder contents, and select a route, endpoint, or mbean to show the details in the detailspane.

Toolbar

Options to view attributes, run commands, and view or create charts for the selected entity. Youcan also add the current view to the dashboard and toggle full screen mode. If you select a route,you can also debug or trace messages through the route.

Details Pane

Detailed view of the selected entity. The contents of this pane depend on the toolbar option that youselect. You can filter the details pane to show only values that match the text string that you enter.


20

CHAPTER 9. CONNECT PAGE

Abstract

You view and manage local and remote connections in the Connect page. You can connect to aremote server with a running jolokia agent, or connect to a local server if you have a local JVM with ajolokia agent.

For more information about Jolokia JMX agents, see the Jolokia Web site at the following address:http://www.jolokia.org/

OVERVIEW

You access the Connect page from the Container perspective. By default, this page opens to the Remote tab. If you have a local JVM with a jolokia agent, the Local tab also appears.

The following image shows an example of the Remote tab:

The Connect page contains the following sections:

Navigation Bar

Tabbed view of available connection types. The Remote tab always appears. If you have a local JVMwith a jolokia agent, the Local tab also appears. Click the Discovery tab to automaticallydiscover agents.

Saved Connections List

This is a drop-down list of default and custom connections. Select a connection from the list andperform the following operations by clicking on the buttons:

to connect to the selected connection

CHAPTER 9. CONNECT PAGE

21

http://www.jolokia.org//

to delete the selected connection.

to add a new connection.

Connection Settings

User credentials and connection properties, such as the connection name and host properties.When you save the connection a new browser window opens and connects to the remote server. Ifyou select a saved connection you can edit the connection properties in this section.


22

CHAPTER 10. JMX PAGE

Abstract

You view and manage JMX domains and mbeans in the JMX page. You can view mbean attributes, runcommands, and create charts that show statistics for the mbeans.

OVERVIEW

You access the JMX page from the Container perspective.

The following image shows an example of the JMX page:

The JMX page contains the following sections:

JMX Tree

Tree view of the active JMX domains and mbeans organized in folders. You can click a folder toshow the mbeans, and select an mbean to show the details in the details pane.

Toolbar

Options to view attributes, perform operations, and view or create charts for the selected mbean.You can also add the current view to the dashboard and toggle full screen mode. If you select abroker mbean, you can view additional information about the broker and manage durablesubscribers.

Details Pane

Detailed view of the selected mbean. The contents of this pane depend on the toolbar option thatyou select. You can filter the details pane to show only values that match the text string that youenter.

CHAPTER 10. JMX PAGE

23

CHAPTER 11. LOGS PAGE

Abstract

You view log entries for JBoss Fuse in the Logs page. You can filter the page to show specific logtypes, and drill down to each log entry to view detailed information about the log entry.

OVERVIEW

You access the Logs page from the Container perspective.

The following image shows an example of the Logs page:

The Logs page contains the following sections:

Action Bar

Options to filter the log entries section according to a text string or the logging level. You can alsoadd the current view to the dashboard.

Log Entries

List view of the log entries. By default, the list shows log entries in descending order. You canchange the default sorting in the User > Preferences > Server Logs page. Click the logentry link to drill down to details about the log entry, such as the bundle name, thread, and the fullmessage text.


24

CHAPTER 12. OSGI PAGE

Abstract

Use the OSGi page to view and manage the JBoss Fuse OSGi environment. You can view and managecontainer bundles, features, and configurations, as well as Java packages and OSGi services.

OVERVIEW

The OSGi page is accessed from the Container perspective. The page contains a toolbar with optionsfor each container component.

The following image shows an example of the Bundles page:

The OSGi page contains the following toolbar options:

Configuration

List of configuration objects. You can view the state of each object and drill down to view or editobject details. You can also create a new configuration object.

Bundles

List of installed bundles. You can install and uninstall bundles, start and stop bundles, and editbundle properties. You can also filter the list and toggle between list and grid view.

Features

List of available features. You can install and uninstall features or feature repositories, and drilldown to view feature details.

Packages

List of installed Java packages. You can view package versions and associated bundles.

Services

CHAPTER 12. OSGI PAGE

25

List of running services. You can view service IDs, associated bundles and object classes.

Declarative Services

List of declarative OSGi services. You can view the service state and drill down to view servicedetails. You can also activate and deactivate services.

Server

Detailed information about the local or remote host in read-only mode.

Framework

Configuration options for the container OSGi framework. You can set the framework start level andthe initial bundle start level.


26

CHAPTER 13. THREADS PAGE

Abstract

You view and monitor the state of threads in the Threads page. You can filter the page to showthreads by status, and drill down to each thread to view stack trace information about the thread.

OVERVIEW

You access the Threads page from the Container perspective.

The following image shows an example of the Threads page:

The Threads page contains the following sections:

Filter

Options to filter the thread list according to the thread state. You can click each state to filter thepage, or click Total to show all threads. Each state shows the number of threads with that state.You can also enter a text string in the Filter box to show only thread names that match the textstring.

Thread List

List view of active threads. By default, the thread list shows all threads in descending ID order. Youcan click each column header to sort the list by that column. You can also click each thread to drilldown to detailed information, such as the lock class name and full stack trace for that thread.

CHAPTER 13. THREADS PAGE

27

PART III. FABRIC MANAGEMENT

Abstract

You use the Fuse Management Console to deploy containers to a fabric and assign containers toprofiles. You can start, stop, and connect to containers. You can also update container versions,manage profiles and dependencies, and monitor the system status and performance.


28


OVERVIEW

When you log in to the Management Console, you use the Fabric perspective to configure andmanage containers, profiles, and general fabric properties.

TOOLBAR

The Fabric perspective contains a toolbar that you use to manage and monitor fabric areas. Thetoolbar contains the following buttons:

Option Description

Fabric The Fabric tab has a drop down menu which enables you to select a Fabric perspective,or a container perspective.

Containers This view shows all the containers available in the Fabric.

Profiles This tab shows the profiles that are available to the Fabric. This page can be used tomanage the profiles.

Wiki Explorer view of the fabric configuration repository and wiki content. The repositorycontains files that affect the behavior of the fabric during runtime.

Services This tab shows the services available to the Fabric. The options on this page include:

Containers - view the containers in this Fabric

Profiles - view the currently active profiles in this Fabric

MQ - view the Fabric-based MQ brokers

APIs - view the APIs in the Fabric

EIPs - view the Camel Enterprise Integration Patterns in the Fabric

Registry - view the contents of the Fabric's runtime registry

Map - view the location of the Fabric on Google Maps

Scaling Increase or decrease the number of instances of a profile and reveiw the effect on thehealth of the profile. You can also set up SSH or Docker Configurations.

Dashboard Overview of the Management Console status, services status, and system performance.You can add views to the dashboard and create additional dashboards.

Health List and status of running health mbeans. This page shows any available container orfabric health mbeans.


29

CHAPTER 15. CREATING OR JOINING A FABRIC

OVERVIEW

To view and manage fabric properties, you must create or join a fabric. You create or join a fabric fromthe Karaf console. Before you create or join a fabric, make sure that JBoss Fuse is running and thatyour system is connected to the network.

CREATING OR JOINING A FABRIC

You create or join a fabric from the Karaf console or from the Terminal page in the Containerperspective of the Management Console. You use the same command syntax in the Karaf console andthe Terminal page.

To create a fabric, run the following command:

The Karaf console shows the default zookeeper password to use when you access the fabric.

To join a fabric, run the following command:

You can set optional arguments, such as the profile or the port range. For more information, seechapter "Creating a New Fabric" in "Fabric Guide" .

fabric:create

fabric:join <zookeeper_URL> <container_name>


30

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Fabric_Guide/ESBRuntimeFabricCreate.html

CHAPTER 16. MANAGING PROFILES

OVERVIEW

A profile is a set of instructions to use when you run containers in a fabric. For example, a profile mightcontain one or more bundles, features, or configuration objects that you want to assign to multiplecontainers.

JBoss Fuse provides a default set of profiles based on the distribution that you install. You must createor join a fabric before you can manage profiles. You can create, edit, and delete profiles. You can alsoadd or remove features, bundles, or feature repositories from an existing profile.

CREATING A PROFILE

1. In the Wiki page, click the +Create icon. Select Fabric8 Profile from the list. Enter aname in the Name: field. The Name: field accepts a combination of letters, numbers, and thecharacters ., - and _.

To create a profile in an existing folder, click on the Wiki tab and drill down to the folder inwhich you want to create the profile. Click the +Create icon.

2. Enter a name for the profile. Use dash characters to create directory levels. Each dashcharacter adds a level to the directory hierarchy. For example, if you enter MyProfile-Profile1, the Management Console creates the directory MyProfile under the mainprofiles directory and creates the Profile1 in that directory.

If you create a profile from an existing folder, you do not need to use the dash character tocreate a directory. The profile appears in the directory from which you create the profile.

3. If you want the profile to inherit features, bundles, or other configuration properties from oneor more existing profiles, you have to change the parents of the profile. Click the edit iconunderneath the parents section and select new parents from the list. Click the Change Parents button to apply your changes.

EDITING A PROFILE

1. In the Profiles tab or the Wiki page, click a profile name. A page will open showing profiledetails.

2. Edit the profile properties and save the changes. The Management Console updates the profileproperties and deploys the changes to any container to which you assigned the profile.

DELETING ONE OR MORE PROFILES

1. Click on the Wiki tab. A list of profiles will be shown.

2. Select one or more profiles, then click on the Actions label. Select Delete to delete all theselected profiles.

CHAPTER 16. MANAGING PROFILES

31

WARNING

Deleting a profile that is in use can have severe consequences for yoursystem. Exercise extreme caution when deleting profiles.


32

CHAPTER 17. ASSIGNING PROFILES TO CONTAINERS

OVERVIEW

You can assign one or more profiles to a container in a fabric. Each profile contains configurationinformation, such as features, bundles, or system properties. You must create or join a fabric beforeyou can assign profiles to containers.

CREATING A CONTAINER WITH AN ASSIGNED PROFILE

1. To create a new container, go to the Containers tab and click the + Create button.Alternatively, you can create a new container from the Services page by selecting + Create.

2. In the Profiles section of the Create New Container page, click a folder to show theavailable profiles for that category or enter a filter string to search the profile list for a specificprofile.

3. Select one or more profiles and enter the container properties in the same way that you enterthe container properties for a standalone container.

ASSIGNING OR REMOVING A PROFILE FROM AN EXISTINGCONTAINER

1. Open the Containers tab or go to Services > Containers and select the container thatyou want to edit. The Container page shows a list of the assigned profiles.

2. Choose whether to add or remove profiles from the container.

To add profiles to the container, click the Add button and select one or more profiles from

CHAPTER 17. ASSIGNING PROFILES TO CONTAINERS

33

the list. You can add profiles based on the profiles that you already assigned to thecontainer. For example, you cannot add a JON profile to a container that runs with a SOAPprofile.

To remove profiles from the container, select one or more profiles and click the Removebutton. If you remove all profiles from a container, JBoss Fuse assigns the default profileto the container.

ASSIGNING MULTIPLE PROFILES TO MULTIPLE CONTAINERS

1. In the Profiles page, select one or more profiles by clicking on the name. A green tick willappear beside the name indicating that the profile has been selected.

2. Click the Assign button. A list of available containers will be shown.

3. Select one or more containers from the list. To select more than one container, hold down ctrl key when selecting the container.

4. Click the Assign button to apply the selected profiles to the selected containers.


34

CHAPTER 18. PROFILES DETAILS PAGE

OVERVIEW

You can edit profile details on the Wiki profile page. Use this page to add and remove artifacts,features and feature repositories. Other functions are provided via buttons and editable lists.

FUNCTION BUTTONS

Some functions are available using the following buttons:

Button Function

Configuration View a list of the bundles and features that make up this profile.

Refresh Deploy the latest version of this profile on all associated containers.

Copy Create a new profile by copying this one.

Assign Assign this profile to a container that already exists in the system.

New Create a new container and assign this profile to it.

VIEW ASSOCIATED CONTAINERS

To view the containers that this profile is assigned to, click the sentence Assigned to X Containers, where X is a number indicating how many containers have this profile assigned. You willbe taken to a list of the containers where you can click on individual containers to see any details yourequire.

CHAPTER 18. PROFILES DETAILS PAGE

35

ABSTRACT TOGGLE

Use the Abstract toggle to mark this profile as abstract. This means that the profile must be inheritedby other profiles, and cannot be instantiated in its own right.

LOCKED TOGGLE

Use the Locked toggle ensure that no changes can be made to the profile unless it is deliberatelyunlocked.

PARENTS LIST

This list shows all the parent profiles from which this profile inherits features. You can remove a parentprofile by clicking the red X next to it. Confirm the removal in the pop-up window.

You can add to the parent profiles list by clicking the green edit icon at the bottom of the list. To addthe features of a profile, select from the presented list in the pop-up window. Click Change Parentsto confirm. The list of parent profiles will be updated with the new information.

DEPLOYMENTS

The Deployments section shows lists of artifacts, features and feature repositories deployed to theprofile.

To add to the Artifacts list, either drag an artifact or enter the address of an artifact into the Addbox. Click the green + to add the artifact.

To remove an entry from any of the Deployments lists, click the red X next to the entry. Confirm thedelete in the pop-up box by clicking Delete.

To edit an entry in any of the Deployments lists, click the pencil icon at the end of each entry. Edit thedetails required, then confirm the change by clicking the green tick, or cancel by clicking the red X inthe pop-up box.

To edit the Features list, click the green edit icon at the bottom of the list. On the Edit Profilename Features page, you can perform the following:

Filter the list of available features.

Select additional features from the list. Click + Add to add the name to the features list, orclick + Add With Version to add the name and version number to the features list.

Delete entries from the Features list. Click the red X next to the feature name in the Profile Features list.

See which features are inherited, by referring to the Inherited Features list.

Confirm the changes by clicking the Save Changes button. Click Done when you have finished, or ifno changes have been made.

To add a feature repository, enter a repository name in the specified format into the Add box. Click thegreen + to add the repository.


36

CHAPTER 19. PATCHING A FABRIC

OVERVIEW

This section explains how to apply patches to a fabric. In a fabric, patches are applied to individualcontainers, so you can choose whether you want to apply a given patch to just some or all containers ina fabric.

CREATING A VERSION

You may want to create a new version before patching a fabric. This will enable you to have multipleversions of a fabric container available, and make them easier to manage. To create a new version:

1. Go to the Wiki tab. Click the version number on the action bar. Select Create Version fromthe drop-down menu.

2. On the Create new Version pop-up window, enter a version name and a description. Click Create to complete the version creation process. The version name must be composed oflowercase letters, numbers, and any of the following symbols: -_.

PATCHING A FABRIC

To patch a fabric container (or containers) from the Management Console, perform the following steps:

1. Go to the Wiki tab. Click the version number on the action bar. Select Patch Version fromthe drop-down menu.

2. Select the version that you want to apply the patch to. Click Continue.

3. Fill in the fields on the Applying Patch to Version .... page as follows:

CHAPTER 19. PATCHING A FABRIC

37

1. Use the Add button to add one or more patch files.

2. (Optional) Enter a name for the new version (to which the patch will be applied).

3. Enter the administrator credentials, User Name and Password.

4. Click Apply.

4. Apply the patched version to one or more containers from the Containers page.

Perform the following steps:

1. Select one or more containers to migrate, by selecting the line in the list. Hold down ctrland select the line to select more than one container.

2. Click the Migrate X Containers to: label to show a dropdown list of availableversions. Select the patched version that you wish to migrate to.

3. A log message will appear to show that action is being taken, and that it might take a while.

If the migration is successful, you will see the changed version of the container on the Containers page.


38

CHAPTER 20. SERVICES AREA

Abstract

You use the Services area to view and manage containers, profiles, ActiveMQ brokers, and APIs. Youcan perform rolling updates to entities, monitor registered services, and view the location of yourcontainers on a map.

20.1. SERVICES OVERVIEW

Overview

Toolbar

The Services tab contains a toolbar that you can use to access management pages for fabric entities.The Services toolbar contains links to the following pages:

Containers

List of available containers. Use this page to view container status, drill down to container details,and create containers in the fabric.

Profiles

List of assigned profiles. Use this page to view profile and container details and define minimum andmaximum container requirements for each profile.

MQ

Graphical view of ActiveMQ brokers in a broker topology. Use this page to move, group, andconnect containers.

APIs

List of installed Apache CXF Web Services APIs. Use this page to view and manage API properties,such as parameter values and exceptions.

EIPs

Dynamic diagram of installed Apache Camel containers. Use this page to view the details of theCamel route endpoints and dependencies.

Registry

List of registered services. Use this page to drill down to services and view service details andstatus.

Map

Locations of deployed containers according to the fabric geoIP data.

20.2. CONTAINERS PAGE


39

Abstract

You can view and manage containers in a fabric in the Containers page. You can view the list ofcontainers, drill down to container details, and create containers.

Overview

The following image shows an example of the Containers page:

The Containers page contains the following sections:

Action Bar

Options to filter the container list, add the view to the dashboard, create a new entity, delete acontainer, or stop a container. The whole bar is shown when one or more containers is selected.

Container List

This is a list of the deployed containers. Click the name of the container to drill down to thecontainer details page.

Action Bar

The Action Bar contains the following options:

Select All / Select None

Selects all containers in the list or clears all selections. Use the clear circle to clear all selections,and the solid circle to select all.

Filter

Filters the container list to show only containers that match a string that you enter in the text box.The container list refreshes as you type. To clear the filter, click the X in the filter box.

Set Location

Use this option to set the location of one or more containers. Select Set Location and eitherselect No Location or select New... and add a location in the pop-up box.

Add to Dashboard

Adds the current view to the dashboard. The view appears in the fabric dashboard.

+Create


40

Opens the Create New Container page. The new container appears as a child of the rootcontainer in the container list.

Start/Stop

Starts or stops the selected containers. This icon toggles between start and stop, depending on thestate of the selected container.

Delete

Deletes the selected containers.

Container List

The container list contains the following elements:

Status

Icon that shows the status of the container.

Version

Version number of the associated profile.

Container Name

Name of the container. You click the container name to drill down to the container details page.

Open a New Window and Connect to this Container

Use the icon next to the container name to open the container in the container perspective in a newwindow.

Icon list

Next at the end of each container row is a list of icons representing the services available in thecontainer. Hover the mouse over each icon to identify it.

20.3. PROFILES PAGE

Abstract

You can view and manage assigned profiles in a fabric in the Services > Profiles page. You candrill down to profile and container details and create containers for the profiles. You can also defineprofile requirements for the fabric.

Overview

You access the Profiles page from the Fabric perspective. If the Fabric perspective is notavailable, make sure that your fabric is available or create a new fabric.

The following image shows an example of the Profiles page:


41

The Profiles page contains the following sections:

Action Bar

Options to filter the container list, add the view to the dashboard, or define profile usage targets.

Container List

List of assigned profiles. You can click the name of the profile to drill down to the profile detailspage where you can manage profile settings.

Action Bar


Filter

Filters the profile list to show only profiles that match a string that you enter in the text box. Theprofile list refreshes as you type. To clear the filter, click the X in the filter box.

Add to Dashboard

Adds the current view to the dashboard. The view appears in the fabric dashboard.

Target

Configure the mininum number of required instances for each profile. Click Target to open a pop-up window in which you can configure the maximum and mininum number of instances for eachprofile. You can also add or remove dependent profiles for each profile.

Count

Shows the number of running containers for each profile. Click on the number to add morecontainers.

Profile List

The profile list contains the following elements:

Show / Hide

Arrow icon to show or hide containers for each profile. Each container shows the same information


42

as the container list on the Containers page.

Profile

Name and version of the profile. Click on the profile name to drill down to the profile details page.

Instances

Icon that shows the number of profile instances. You can click the icon to create additionalcontainers for the profile.

20.4. MQ PAGE

Abstract

You view and manage Apache ActiveMQ brokers in the Services > MQ page. You can create andorganize ActiveMQ brokers in topologies, and monitor broker status during runtime.

Overview

The following image shows an example of the MQ Configuration Topology page:

The MQ page contains the following sections:

Action Bar

Options to filter the topology viewer, add brokers and containers.

Topology Viewer

Graphical overview of Apache ActiveMQ brokers, profiles, and topologies.

Action Bar


Filter


43

Filters the topology viewer to show only brokers that match a string that you enter in the text box.The topology viewer refreshes as you type. To clear the filter, you click the X icon.

+Broker

Opens the Master Slave Broker page. In this page, you create a broker configuration that actsas a fabric profile. If you create a broker from the Action Bar, you must manually specify in whichgroup to create the broker.

+Container

Opens the Create New Container page. The new container appears in the container list.

Diagram

Toggles between the Configuration view, as shown above, and the Diagram view.

Configuration Topology Viewer

The Configuration topology viewer contains the following elements:

Group

Broker group with one or more profiles. Each group appears as a box that shows the name of thegroup. You can click the + to create a broker in the group. When you create a broker in the group,you can choose to assign the broker to an existing profile in the group or choose a different profile.

Profile

Profile with one or more brokers. Each profile appears as a box that shows the name of the profileand one or more nested boxes that represent brokers. You can click the profile name to drill downto the profile details. You can also click the + icon to create a broker in the group. The broker isassigned to the existing profile.

Broker

Apache ActiveMQ broker with one or more containers. Each broker appears as a box that showsthe name of the broker and icons that represent the containers of the broker. You can click thebroker name to view the configuration properties of the broker.

Container

One or more active containers that run with the parent profile and broker. Each container appearsas a box that shows the container icon. You can hover over the container icon to view the containername, and click the icon to drill down to container details.

Diagram Viewer

The Diagram topology viewer shows a diagrammatic representation of the AMQ topology. It showslinks between components. The Diagram page contains the following elements:

Filter

The Filter field allows you to focus your diagram on specific parts or specific versions of thesystem.

View


44

The View drop-down menu allows you to select the components you want to see in your diagram.You can include or exclude a number of components, and configure how the diagram is presented.

The following image shows an example of the MQ Diagram page:

20.5. APIS PAGE

Abstract

You view and manage Apache CXF Web Services APIs in the Services > APIs page.

Overview

The following image shows an example of the APIs page:

The APIs page contains the following sections:

Filter

Filters the API list to show only APIs that match a string that you enter in the text box. The API listrefreshes as you type. To clear the filter, you click the X icon.


45

API List

List of active Web Services APIs. Each API shows the service name, a link to the availableoperations, the container that uses the API, and the location of the Web Service.

20.6. EIPS PAGE

Abstract

You view Apache Camel routes and dependencies in the Enterprise Integration Pattern (EIPs) page.

Overview

The EIPs page contains the following sections:

Action Bar

Options to filter and show or hide entities from the route viewer.

Route Viewer

Graphical overview of Apache Camel routes and dependencies. You can click each entity to displaythe properties in the right pane.

Action Bar


Filter

Filters the route viewer to show only entities that match a string that you enter in the text box. Theroute viewer refreshes as you type. To clear the filter, you click the X icon.

View

Drop-down list of entity types. You select or clear the check box next to each entity type that youwant to show or hide.

Route Viewer

The route viewer shows active Camel routes and dependency clusters. You can use the mouse scrollbutton to zoom in and out. You can also use the mouse to drag the clusters in the pane. When you clickeach entity, you can view details and properties in the right pane.

20.7. REGISTRY PAGE

Abstract

You view the status and manage registered services in the Registry page. You can view the detailsand monitor the status for entities such as clusters, servlets, webapps, and repositories.


46

Overview

The following image shows an example of the Registry page:

The Registry page contains the following sections:

Navigation Bar

Breadcrumb view of the location in the service list.

Service List

List view of the registered services.

Navigation Bar

The Navigation Bar shows a breadcrumb view of the location in the service list. Each node in thehierarchy appears as a link. You can click each link to drill up in the hierarchy. By default, the Registry page shows the clusters node.

Service List

The service list shows registered services in folders. Click the folder to drill down to the service details.

When you drill down to service details, you can view the following general properties:

ID

Identifier of the service.

Container

Name of the container that uses the service.

Services

URL of the service.

Each service can show additional properties based on the type of service and the profile that runs thecontainer.

20.8. MAP PAGE


47

Abstract

You view the location of deployed containers in the Map page.

Overview

The Map page contains the following sections:

Container Tree

Tree view of the deployed containers. You can click a container in the tree to center the map to thelocation of the container.

Map

Google Map control that shows the location of the container. You can switch between the map viewand the satellite view. You can also zoom in and out of the map.


48

CHAPTER 21. WIKI PAGE

Abstract

You view and manage the fabric configuration repository and integrated wiki content in the Wiki page.You can view the list of configuration objects, drill down to object details, and manage wiki documents.

OVERVIEW

You access the Wiki page from the Fabric perspective. If the Fabric perspective is not available,make sure that your fabric is available or create a new fabric.

The following image shows an example of the Wiki page:

The Wiki page contains the following sections:

Action Bar

Breadcrumb view of the location in the configuration repository and document managementoptions.

Repository Explorer

Tree view of the fabric configuration repository and wiki documents.

Details Pane

Detailed view of the configuration object or wiki content.

CHAPTER 21. WIKI PAGE

49

ACTION BAR


Version

Version of the repository branch to view. You can open the drop-down list to switch versions.

Navigation Bar

Breadcrumb view of the location in the repository. Each hierarchical level appears as a link. You canclick each link to drill up to the parent directory. By default, the Wiki page opens to the mainprofiles directory.

Create

Opens the Create Document dialog box. You can use this dialog box to create configuration objectssuch as profiles, property files, Camel routes, or wiki pages. You cannot use this dialog box to createprofiles or containers.

Edit

Switches the details pane to a wiki markdown view. You can edit the wiki markdown contentdirectly in the page and save the updated wiki document.

Actions Menu

Object management options based on the contents of the details pane. For example, when you edita profile you can use the Actions menu to change the profile parent, assign the profile to a newcontainer, or edit the profile features. Use the mouse to hover over the menu options and view thedescription.

REPOSITORY EXPLORER

The repository explorer shows a tree view of all configuration objects and wiki documents organized infolders. You can click a folder in the tree to show the folder contents, or click a profile or a wikidocument to show the details in the details pane.

You can select one or more objects and use the Actions menu to move, delete, or view the versionhistory of the selected objects. You can also hover over each object to view the last modified date andtime and the size of the object.

DETAILS PANE

Detailed view of the configuration object or wiki content. When you edit a profile, this pane shows theprofile details. When you drill down to a directory with a wiki document, this pane shows the contents ofthe wiki document.

If the directory does not contain a wiki document, this pane is empty.


50

CHAPTER 22. DASHBOARD PAGE

Abstract

Monitor system performance and runtime status using the Dashboard page. You can view recent logentries, active profiles, running containers, and system services.

OVERVIEW

The Dashboard page contains the following sections:

Navigation Bar

Tabbed view of available dashboards and management options.

Active Dashboard Pane

Detailed view of the active dashboard.

NAVIGATION BAR

The navigation bar shows a tabbed view of available dashboards. Custom dashboards that you createor import appear in the navigation bar. You can click the dashboard name to switch betweendashboards.

You can click the Manage button to create or import custom dashboards.

ACTIVE DASHBOARD PANE

The active dashboard pane shows a detailed view of the selected dashboard. By default, this paneshows the Welcome dashboard. You can use the Add Current View to Dashboard button invarious areas of the Management Console to customize the default dashboard or create a newdashboard.

You can click and drag each area in the dashboard to arrange the dashboard. You can also click theedit icon next to each area title to edit the area name.

The Welcome dashboard contains the following areas:

Java Heap Memory

Pie chart view of used and free Java heap memory.

Java Non Heap Memory

Pie chart view of used and free Java non-heap memory.

Containers

List of deployed containers and container management options.

Active Profiles

List of active profiles and profile management options. Active profiles are profiles that youassigned to containers.

CHAPTER 22. DASHBOARD PAGE

51

Loaded Classes

Pie chart view of loaded classes and unloaded classes.

Process CPU Load

Graphical view of CPU usage.

Threads

Timeline view of running threads and status information, such as thread count and thread user time.

Logs

List of recent log entries. You can click the log type to view basic information about the log entry, orclick the log entry link to open the full log entry syntax.


52

CHAPTER 23. HEALTH PAGE

Abstract

You view the status of health mbeans for containers and fabrics in the Health page. Health mbeanscontinuously check running Java code and services for syntax errors.

You can view the status for each broker and profile. The actual content of this page depends on theactive brokers and profiles.

OVERVIEW

The following image shows an example of the Health page:

The Health page contains the following sections:

Filter

Filters the brokers and profiles pane to show only brokers or profiles that match a string that youenter in the text box. The pane refreshes as you type. To clear the filter, you click the X icon.

Brokers and Profiles Pane

Graphical view and service names for the active brokers and profiles. Each broker and profile showsthe name and type of the broker or profile. You can click the information icon to expand the detailspane for the seleected broker or profile.

CHAPTER 23. HEALTH PAGE

53

PART IV. LOG MANAGEMENT WITH INSIGHT

Abstract

You use the Insight plugin to centrally manage logs and metrics for multiple containers in a fabric. TheInsight plugin is a set of profiles that uses Elasticsearch and Kibana technology to collect log messagesand events from multiple containers in one or more data stores. You then access and analyze themessages from the Insight perspective of the Fuse Management Console.


54

CHAPTER 24. GETTING STARTED

OVERVIEW

To get started with Insight, you set up the data store, configure the containers to send messages orevents to the data store, and install the embedded Web viewer to show the data in the ManagementConsole. You then configure each container that you want to add to the Insight ensemble to send logsor metrics to the data store.

PREREQUISITES

Before you install and configure Insight, you must create a fabric or join an existing fabric.

DATA STORE INSTALLATION

To ensure optimal system resource usage, it is recommended that you install each data store in aseparate container.

To install the data store, create a container with the following profiles:

insight-elasticsearch.node

Listener process that collects logs and events from the containers and writes the data to the datastore. This profile contains all the configuration for the data store, such as size and location.

To customize the data store configuration, edit the io.fabric8.elasticsearch-insight.properties file. For more information about the Elasticsearch node configurationproperties, see the Elasticsearch configuration documentation .

insight-elasticsearch.datastore

Database instance that uses Elasticsearch to store log messages and events from multiple sources.This profile extends the insight-elasticsearch.node profile and inherits its configuration.

WEB VIEWER INSTALLATION

To install the Web viewer, add the following profiles to the root container:

insight-elasticsearch.node

This profile enables the container to join the Elasticsearch cluster as an Elasticsearch client.

insight-console

Enables the Insight perspective in the Fuse Management Console.

After adding these profiles to the root container, the Web viewer is then available from the Insightperspective.

You can configure a different Web viewer to access logs and metrics. To connect directly to the clusterfrom an external Web viewer, enter the IP address from the Connect box of the Elasticsearchpage as the destination of the data store cluster. You cannot use the command line to query the datastore.

CHAPTER 24. GETTING STARTED

55

https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html

CONFIGURING LOG COLLECTION

By default, containers send log messages to standalone log files that you view in the Logs tab of thecontainer. To instruct a container to send the messages to the Insight data store, add the insight-logs.elasticsearch profile to each container that you want to add to the Insight ensemble.

CONFIGURING METRICS COLLECTION

By default, containers with Camel routes use stack tracing to collect metrics. To instruct a container tosend the messages to the Insight data store, add the insight-metrics.elasticsearch and the insight-camel profiles to each Camel container that you want to add to the Insight ensemble.

VIEWING AND ANALYZING LOGS AND METRICS

You access the logs and metrics for all containers and brokers from the Insight perspective. Formore information, see Chapter 25, Insight Perspective.


56

CHAPTER 25. INSIGHT PERSPECTIVE

OVERVIEW

When you log in to the Management Console, you use the Insight perspective to view and analyzelog messages and events stored in the Insight data store. The Insight perspective shows informationfor all the containers and brokers in the fabric that you add to the Insight ensemble.

TOOLBAR

The Insight perspective contains a toolbar that you use to manage and monitor Insight components.The actual options depend on which Insight profiles you install and the type of containers from whichyou collect log messages and events. The toolbar can contain the following options:

Option Description

Camel Detailed view of a Camel event based on the exchange ID of the event.

Logs Embedded Web viewer that you use to access all logs stored in the Insight data store.

Camel Events Embedeed Web viewer that you use to access all Camel events stored in the Insight datastore.

Elasticsearch Overview of all data stores in the fabric.

CHAPTER 25. INSIGHT PERSPECTIVE

57

CHAPTER 26. CAMEL PAGE

Abstract

You view metrics about a Camel route in the Camel page. You can view route attributes and sourcecode, debug and trace the route, and monitor route status.

OVERVIEW

You access the Camel page from the Insight perspective. This page is available only when youinstall and configure the Insight plugin for one or more containers with a Camel route.

The following image shows an example of the Camel page:

The Camel page contains the following sections:

Exchange ID

Text box where you enter the exchange ID of a Camel route. To locate the exchange ID, select anevent from the Camel Events page of the Insight perspective and copy the value of the exchange.id field.

Details pane

Gantt chart and diagram view of the message processing time in each part of the route. You can usethese diagrams to locate bottlenecks and optimize the route.


58


Abstract

You view and and analyze log messages in the Logs page. The page displays logs of all containers thatuse the insight-logs profile. You can query the Elasticsearch data store, filter the log list, and drill downto message details.

OVERVIEW

You access the Logs page from the Insight perspective. This page is available only when you installand configure the Insight plugin for one or more containers in the fabric.

The following image shows an example of the Logs page:

The Logs page contains the following sections:

Quick-filter

Drop-down list with options to filter the log list and graph according to predefined times, such aslast 15 minutes or last 7 days. The list also includes a Refresh icon that you can use to displaymessages that were generated after you navigated to this page.

Query box

Text box where you enter a query to search for log messages in the data store. By default, the pageshows only events of type log. You can define queries with the lucene query string, regularexpressions, or topN formats. For information and conventions, click the colored circle icon on theleft side of the query box and open the About dialog box.


59

Filtering pane

Filter settings for the logs list. You can use this pane to add, edit or delete filter settings.

Log Events Over Time graph

Visual representation of the messages as they are collected in the data store. You can drag themouse cursor to highlight an area in the graph and show the events that occured during theselected time frame. The log list refreshes as you zoom in or out in the graph.

All Logs list

List of logs messages for all containers and brokers in the Insight ensemble. The events in this listdepend on the query, filter, and graph settings. Use the left and right arrows to navigate the list.

You can click an event to drill down to detailed information, such as log level, full message, bundlename, and so on. You can also perform actions on the event, such as add or remove a filter based onone of the event properties.


60

CHAPTER 28. CAMEL EVENTS PAGE

Abstract

You view and analyze events for all containers with Camel routes in the Camel page. This pageprovides functionality similar to route tracing.

OVERVIEW

You access the Camel Events page from the Insight perspective. This page is available only whenyou install and configure the Insight plugin for one or more containers with a Camel route.

The following image shows an example of the Camel Events page:

The Camel Events page contains the following sections:

Quick-filter

Drop-down list with options to filter the event list and graph according to predefined times, such aslast 15 minutes or last 7 days. The list also includes a Refresh icon that you can use to displaymessages that were generated after you navigated to this page.

Query box

Text box where you enter a query to search for events in the data store. By default, the page showsonly completed and failed events. You can define queries with the lucene query string, regular

CHAPTER 28. CAMEL EVENTS PAGE

61

expressions, or topN formats. For information and conventions, click the colored circle icon on theleft side of the query box and open the About dialog box.

Filtering pane

Filter settings for the event list. You can use this pane to add, edit or delete filter settings.

Camel Events Over Time graph

Visual representation of the events as they are collected in the data store. You can drag the mousecursor to highlight an area in the graph and show the events that occured during the selected timeframe. The event list refreshes as you zoom in or out in the graph.

Statistics pie chart

Visual representation of the percentage of completed events. You can click the completed area inthe pie chart to add a filter that shows only completed events.

Trends overview

Statistical information about the Camel events that occured in the last hour and the last day. Thetrends are displayed based on the query settings. By default, the overview shows information aboutcompleted and failed events.

All Camel Events list

List of events for all Camel containers and brokers in the Insight ensemble. The events in this listdepend on the query, filter, and graph settings. Use the left and right arrows to navigate the list.

You can click an event to drill down to detailed information, such as exchange ID, full message,endpoint, and so on. You can also perform actions on the event, such as add or remove a filter basedon one of the event properties.


62

CHAPTER 29. ELASTICSEARCH PAGE

Abstract

You view and and manage the Elasticsearch data stores in the Elasticsearch page. You can viewdetailed information about all the data stores in the fabric, such as cluster and node state. You can alsorun custom queries on the database.

OVERVIEW

You access the Elasticsearch page from the Insight perspective. This page is available only whenyou install and configure the Insight plugin for one or more containers in the fabric.

The following image shows an example of the Elasticsearch page:

The Elasticsearch page contains the following sections:

Cluster overview and toolbar

General information about the data store cluster, such as the address and the state of the cluster. Ifyou want to connect directly to the cluster from an external Web viewer, you use the IP addressfrom the Connect box to indicate the location of the data store cluster.

Data Store list and details

List of all the data stores in the cluster. Each node represents a data store container. The right paneshows general information about each node, such as storage size according to date, number ofmessages, and so on.

CHAPTER 29. ELASTICSEARCH PAGE

63

PART V. DIAGNOSTIC TOOL PLUG-INThe Diagnostic tool is implement as a Hawtio plug-in integrated in the Fuse Management Console. Theplug-in is deployed either as a feature in a non-fabric environment or as a profile in a Fabricenvironment called support-base.

The plug-in can be accessed on the Fuse Management Console under the Red Hat Access menu in thetop right corner. The plug-in allows you to add artifacts such as LOGS, SUPPORT_ZIP, ETC, HEAPDUMPand THREADDUMP.

The diagnostic tool allows the following attachments:

LOGS: logged information of the root container.

SUPPORT_ZIP: Generates a comprehensive zip of diagnostic information.

ETC : Generates a zip of the configuration folder.

HEAPDUMP: Generates a zipped heap dump.

THREADDUMP : Generates a thread dump.

NOTE

In case of Fabric, the SUPPORT_ZIP artifact would contain extra Fabric-specificconfigurations such as the contents of the ZooKeeper registry (calls zkdump).


64

CHAPTER 30. OPEN A NEW CASEYou can open a new case through the Fuse Management Console.

OPENING A NEW CASE

1. Login to Fuse Management Console.

2. In Fuse Management Console, click on Red Hat Access in the top right corner.

3. Login with your Red Hat Subscription ID and Password.

4. Select Open New Case from the drop-down list.

5. In the Open New Case window, click My Account and the owner field and Product field areupdated automatically, select the product version, enter the Summary and Description andclick Next.

6. On the next page, select the Support Level,Severity and Case Group

7. You can upload local files and server files when you open a new case.

To upload local files, click Attach local file, enter file description and click Add.

8. To attach server files, select the file type from the listed option and click Submit.

CHAPTER 30. OPEN A NEW CASE

65

CHAPTER 31. EDIT AN EXISTING CASEYou can edit an existing case through the Fuse Management Console.

EDITING AN EXISTING CASE



3. Login with your Red Hat Subscription ID and Password.

4. Select List Cases from the drop-down list.

5. The case list can be filtered using the search box, selecting a case group, or as per the status ofthe cases.

Select the case for editing from the search results.

6. On the next page, there are different section such as Details, Attachments and Case Discussion.

To modify the case details, edit the Details section and click Update Details.

7. In the Attachments section you can add new attachments and click Upload Attachments ordelete existing attachments.

8. In the Discussion section you can add comments and choose to make the comment public orprivate.

You can access existing solutions in the Recommendations section. You can also choose to escalatethe case with Red Hat Support manager.


66

CHAPTER 32. USING THE DIAGNOSTIC TOOLTo use the Diagnostic tool, you need to install and create an instance of Red Hat JBoss Fuse 6.2. Youcan access the diagnostic tool through the Hawtio interface.

USING THE DIAGNOSTIC TOOL



3. Select Diagnose Log from the drop-down list.

The Log File Viewer screen opens.

4. In the Log File Viewer, click Please Select the machine and click root, select the logfile and click Select File.

The contents of the log file are displayed in the Log Viewer window

NOTE

The log file used in this step is for example purpose. You can choose any file fordiagnostics.

5. From the list of the log messages, click on the message relevant to your issue and click Red Hat Diagnose.

6. The Recommendations panel opens, click the appropriate Support case in the panel to accessthe information related to the problem.

In case the issue is not listed in the recommendations panel, you can click the Open a New Support Case to file a case with Red Hat Support Team

CHAPTER 32. USING THE DIAGNOSTIC TOOL

67

CHAPTER 33. LIMITATIONS OF THE DIAGNOSTIC TOOLThe diagnostic tool has certain limitations:

The diagnostic tool can only get extra information from root, child, or SSH containers.

Cloud containers are not supported.

The diagnostic tool collects the extra information by a process running on the remotecontainer, in extreme cases (heavily overloaded container), the tool might not be able togather statistics from a badly failing container.

Extra artifacts are delivered straight from container, so container host must have Internetaccess.


68

Documents

Red Hat JBoss Fuse 6 · Red Hat JBoss Fuse 6.2 Management Console User Guide 4. PART I. INTRODUCTION PART I. INTRODUCTION 5. CHAPTER 1. FUSE MANAGEMENT CONSOLE OVERVIEW ... the Fuse