Copyright © Cloud Software Group, Inc. All Rights Reserved

Introduction

After the integration development team has configured and deployed the integration project, you can use the TIBCO Administrator GUI for monitoring and management.

This chapter gives an overview of the architecture and of the user management, administration domain monitoring and management, and deployment management options. For more detailed information, see the TIBCO Administrator User’s Guide.

Architecture

TIBCO Administrator consists of the TIBCO Administration Server and the TIBCO Administrator GUI. The Administration Server includes an application server component for HTTP communications and a repository server component for data store management. All three server components run as a single process.

The Administration Server interacts with each machine in the administration domain by way of the TIBCO Runtime Agent (TRA) running on that machine.

•	The Administration Server receives information about CPU and memory usage, alerts, and the process instances and components running on each machine and makes them available via the TIBCO Administrator GUI.

•	The TIBCO Administrator GUI allows users to start and shut down components. Start and shutdown commands are sent from the Administration Server to the appropriate TRA, which in turn starts or stops the process.

The illustration below shows an administration domain with 3 machines in the domain.

•	The first machine runs the Administration Server, which contains an embedded Repository Server for managing data stores. Machines outside the administration domain can view the TIBCO Administrator GUI using a web browser. Each user sees only the components for which s/he is authorized.

•

The second machine runs two adapters. The adapters are started via the TIBCO Administrator GUI. The information entered in the GUI is sent by the Administration Server to the TRA on the machine running the adapter. The TRA starts and stops the adapter and also sends information about component and machine status to the Administration Server for access via the GUI.

•	The third machine runs a process engine. Just like the adapters, the process engine is managed by the Administration Server via the TRA.

Figure 24 Communication inside a TIBCO administration domain

Monitoring and Management Options

At runtime, TIBCO Administrator allows you to remotely access all deployments in your administration domain. Depending on your security privileges, you may be able to perform one or more of the following tasks.

•	User Management—Add users and passwords to the administration domain for authentication, then give each user view or execute privileges for TIBCO Administrator GUI elements or project repositories (data stores).

•	Domain Monitoring and Management—View the status of machines and components running on machines in the domain. Start and stop components as needed.

•	Deployment monitoring—Monitor the status of each deployment component (process engine and adapter) and process instance and the status of the machines executing them. View trace files and throughput.

•	Deployment management—View all running components and stop and restart them as needed.

These aspects of monitoring and management are supported by TIBCO Administrator, which includes the TIBCO Administration Server and the TIBCO Administrator GUI.

Copyright © Cloud Software Group, Inc. All Rights Reserved