![]() |
Copyright © Cloud Software Group, Inc. All Rights Reserved |
The following sections provide an overview of TIBCO ActiveMatrix Administrator. To get a quick introduction on the use of the administration tools, see TIBCO ActiveMatrix Service Grid Getting Started. For detailed information about the administration tools, see TIBCO Hawk Administrator’s Guide.Figure 10 shows ActiveMatrix Administrator components, and the relationship between ActiveMatrix Administrator, other servers, and ActiveMatrix machines and nodes.
• TIBCO ActiveMatrix Administrator Server Gathers management data from nodes, responds to requests from the ActiveMatrix Administrator graphical and command-line UIs, interacts with the authentication realm server to authenticate users, and interacts with TIBCO Management Daemon to manage nodes.
• TIBCO ActiveMatrix Administrator Cluster Groups one or more ActiveMatrix Administrator servers together. ActiveMatrix Administrator servers within a cluster share a database and authentication realm and are kept synchronized.
• ActiveMatrix Database Stores ActiveMatrix administration data.
• Authentication Realm Manages user authentication data. The authentication realm can be provided either by TIBCO Administrator or by another server or a file.
• ActiveMatrix Administrator Graphical UI Displays the ActiveMatrix Administrator user interface. Figure 11 shows the ActiveMatrix Administrator graphical UI welcome page. In ActiveMatrix Administrator, functionality is divided into perspectives. A perspective is a set of controls used to carry out a category of administration tasks.
• ActiveMatrix Administrator Command-Line Interface Provides a script-based interface for ActiveMatrix Administrator functions.
• Management Daemon Gathers installation information and displays ActiveMatrix node life cycle operations.Figure 11 TIBCO ActiveMatrix AdministratorServices deployed on multiple containers are highly available; if one container fails, service requests will be handled by one of the remaining containers. No configuration is required to make services highly available. Messaging Bus automatically routes to any available service instance identified in the message exchange.Requests to services deployed on multiple containers are load balanced between the available providers. No configuration is required to load balance between services. Messaging Bus uses a round robin algorithm for routing requests to service instances.
![]() |
Copyright © Cloud Software Group, Inc. All Rights Reserved |