TIBCO Administrator

TIBCO Administrator provides user, resource, and application management modules for adapters.

User Management This module allows you to set permissions for adapter users. You can define authentication, users, and groups, and assign access control lists to users. This includes security for server-based projects at design-time and for deployed applications at runtime.

Resource Management This module allows you to monitor machines and running applications in a TIBCO administration domain. Alerts can be created, for example, to notify an administrator if the number of processes or disk usage exceed a certain level.

Application Management This module allows you to upload Enterprise Archive (EAR) files, and create, configure, and deploy adapters. This module is also used to start and stop adapters.

Load balancing An adapter can be served by a primary and secondary TIBCO Administration Server. The primary server allows read and write operations, while the secondary server supports read operations. Load balancing is implemented through the use of the TIBCO Rendezvous distributed queue protocol (RVDQ) and therefore is not available for HTTP.

To get the load balancing benefit with HTTP, you must either use an IP redirector or explicitly point to a backup server. Refer to the IP Redirector or HTTP Server documentation for instructions on how to do this.

Failure recovery You can use a load-balanced TIBCO Administration Server for failure recovery. In a completely trusted environment, you can also use a database back-end for your server and use checkpoints in the database for failure recovery.

TIBCO Administration Domain

A TIBCO administration domain is installed only if you have installed the User Management module.

A TIBCO administration domain is a collection of users, machines, and components that an administration server manages. There is only one Administration Server for each administration domain. Components within an administration domain can communicate with systems outside of the domain, but the domain is the administrative boundary of your enterprise integration project.

Each TIBCO administration domain contains one or more machines. Each machine can belong to only one TIBCO administration domain.

By default, all machines within an administration domain are expected to be in the same subnet. You can set up your system to use TIBCO Rendezvous rvrd and then use the components across subnets. See the TIBCO Administrator Server Configuration Guide for details.

TIBCO Administration Server

The TIBCO Administration Server provides a central storage and distribution point for configuration data and schema data needed by an adapter. The server is included in both Administrator editions.

Each administration domain has one and only one TIBCO Administration Server. The TIBCO Administration Server is the machine process that handles the stored projects and requests to manage the TIBCO administration domain.

The TIBCO Administrator Server contains its own web server (Apache Tomcat) that can be accessed through the TIBCO Administrator GUI for configuration and monitoring information.

The TIBCO Administration Server supports centralized authentication and authorization. Using the TIBCO Administrator GUI, users with full administrative privileges can define who has access to projects that are managed by the repository server.

TIBCO Administrator GUI

You can access the TIBCO Administration Server using the web-based TIBCO Administrator GUI. The GUI allows you to create user profiles and assign access to projects managed by the Administration Server. You can invoke the GUI from any machine in a TIBCO administration domain.

Figure 9 TIBCO Administrator GUI