Components of TIBCO Enterprise Administrator

The TIBCO Enterprise Administrator comprises a server, an agent corresponding to a product, a server UI, a shell interface, and python scripts.

The TIBCO Enterprise Administrator has the following components:
The Server
The server is the equivalent of a web server. The server is hosted within a web server and caters to the HTTP requests coming from the browser. The server manages the communication between the browser and agents. The server interacts with the agent to get data about the products registered on the TIBCO Enterprise Administrator. The server is responsible for:
  • Collecting data on all the products registered with it
  • Maintaining a cache of the data; thereby promoting faster searches
  • Hosting all the TIBCO Enterprise Administrator server views
  • Responding to auto-registration requests from agents
  • Providing details about the machines on which the products are running
  • Providing user management features such as granting and revoking a user's permissions
The Agent
An agent is a bridge between the TIBCO Enterprise Administrator server and a product. When an agent is registered with the TIBCO Enterprise Administrator, it discovers the product that must be exposed to the administrator. The agent creates a graph of objects specific to the product that needs to be rendered on the TIBCO Enterprise Administrator server UI. The agent interacts with the server using the REST API. TIBCO Enterprise Administrator agents can run in any of the following ways: standalone, embedded, or hosted. TIBCO Enterprise Administrator comes with an extensible API that helps you develop your own agents for your products. An agent provides the following basic concepts:
  • Group: is a container of artifacts. For example, a cluster, domain, and ActiveMatrix environment.
  • Process: is any operating system process. For example, a BusinessWorks engine, and ActiveMatrix node.
  • Resource: is a shareable configuration or artifact. For example, a JMS connection, or a port number.
  • Application: is any deployable archive. For example, a WAR and DAA.
  • Access_Point: is a means of interacting with an application. For example, an ActiveMatrix service endpoint, or an EMS queue.
  • Top_level: A special type that represents the root-level object in the tree. There can be only one such instance of the object per agent. This is the only object that cannot have a configuration or state. Note that methods that access objects of this type do not have the key argument that is otherwise required by other concepts.
Web UI
TIBCO Enterprise Administrator provides a default UI to manage and monitor products. You can customize labels and icons on the UI to match the object types of your product. You can add more views to suit your product requirements.
Shell
TIBCO Enterprise Administrator provides a command-line utility called the TIBCO Enterprise Administrator shell. It is a remote shell based on the SSH protocol. The Shell is accessible using any terminal program such as Putty. The scripting language is similar to bash from UNIX, but has important differences. You can use the Shell to perform almost all the tasks offered by the server UI.
Python Scripting
You can use Python scripting to perform any activity you performed using the Web UI. Python scripting is especially useful when you have to repeat a task for multiple users or use control structures to work through some conditions in your environment. Although you can use the Shell utility to use the command-line UI, the Shell UI does not support conditional statements and control structures. Python scripting proves to be useful in such cases.
Related concepts