TIBCO ADMIN

Getting Started

Tibco

Administrator
components

TIBCO Administrator includes two main

components, the administration server and TIBCO
Administrator GUI. The administration server
manages resources in an administration domain.
The TIBCO Administration GUI provides a web
browser interface, allowing you to configure users
and applications, deploy applications, and monitor
processes and machines in an administration
domain.

The following modules are provided

in the TIBCO Administrator GUI

User

Management
Resource Management
Application Management

User Management

This

module allows you to create users and

roles and assign them access rights to
resources available in the administration
domain

User Management Cont

Usersyou can create users and assign them into roles,

which allow easier administration. You can also set read,
write or administer permissions so a user can directly
access TIBCO Administrator modules and consoles, and
domain and application repositories.

RolesAccess control is easier when roles are used. You

can assign multiple users into roles and then assign
permissions for the role, rather than each individual
user.

SecurityEach resource in an administration domain

can have users or roles assigned to it. The security level
setting determines who can access the resource and at
what access level.

Resource Management
This

module allows you to create application

domains, get information about installed
TIBCO software on each domain machine,
view the status of each domain machine,
and configure monitoring rules and events
that can trigger other actions such as
sending email or running a command.

Resource Management Cont

Application Domains If your TIBCO application supports

this feature, you can create multiple application domains and
assign applications to use them. An application domain allows
you to specify that application data be written to a repository
that is separate from the repository used by the
administration domain. This is useful, for example, if an
application needs to use a local database rather than that
used by the administration domain.

Installed Software You can view TIBCO applications that

are running on each machine in the domain and enable or
disable applications.

Machines Each administration domain contains one or

more machines. You add a machine to an administration
domain using the TIBCO Domain Utility

Application Management
This

module allows you to upload an

applications Enterprise Archive (EAR) file
and optionally change options and global
variables that were set for the application
when it was configured. You can also define
monitoring rules for each application. You
then deploy the application and start (or
stop) it.

Upgrading an Application

If you have installed a new version of TIBCO software

on a machine that is part of your administration
domain, and the software is used in one or multiple
applications, you can use the Upgrade feature to
enable the applications to use the upgraded software.

The Upgrade feature remaps properties in the service

instances and process engines properties files to use
the new software targets. After you have upgraded,
you must continue to use the upgraded software.
That is, you cannot revert to using the previous
software version. You must redeploy your applications
after upgrading.

To Upgrade an Application

Click Application Management.

Click Application > Configuration, where Application is
the application created when you loaded the archive.
In the Configuration panel, click Upgrade.
Select Deploy after upgrade to redeploy your
application as part of the upgrade. You can redeploy
later.
Select Start successfully deployed services to deploy,
stop and restart your service instances and process
engines. If Deploy after upgrade is not selected, this
option is not available.
Select the software to upgrade.
Review the upgrade summary.
Click OK.

Changing Global Variables at

Deployment
An

applications EAR file can contain

global variables with values set at
design-time. The global variables can
be changed at deployment at the
application level, service level, or
service instance level.

To Change Global Variables

In

TIBCO Administrator, click Application

Management.
Select an application and expand it.
In the Configuration Builder pane, click a
service or process name. A service is named
with a .arr suffix. A process is named with a .par
suffix.
Click the Advanced tab.
Change global variables as required.
Click Save.

Setting Fault Tolerant Options for a

Process

The FT Group Settings panel displays only if the

TIBCO Business Works process you have selected has
been added to at least two (different) machines. If
your domain includes components that were
deployed as part of a fault-tolerant group, the display
includes the information about the group.

You can start one or more process engines in the

group. If more than one engine has started, only one
is displayed as Running and all other engines are
displayed as Standing By (or, initially, as Starting Up).
Fault tolerance options can be set only for TIBCO
Business Works processes. TIBCO Adapter services
cannot be assigned fault tolerant options.

To Set Fault Tolerant Options

In

TIBCO Administrator, click Application

Management.
Select an application and expand it.
In the Configuration Builder pane, click process
name. A process is named with a .par suffix.
Click the General tab.
Select Run Fault Tolerant. Change other
options as required
Click Save.

Changing the Checkpoint Data

Repository for a Process

To run TIBCO Business Works using multiple engines

in fault tolerant mode, you must specify a
checkpoint data repository.

For true fault tolerance, you must store the data in

a database. You specify a JDBC Connection resource
for the database to be used when you configure
your project in TIBCO Designer. The database is
then one of the available options on the Checkpoint
Data Repository pop-up menu.

To Change Checkpoint Data Repository

Properties

In TIBCO Administrator, click Application

Management.
Select an application and expand it.
In the Configuration Builder pane, click a process
name. A process is named with a .par suffix.
Click the Advanced tab.
Change properties as required.
Click Save.

Database and File-based

Storage

An administration domain stores domain information in a

database repository or file repository, depending on the
transport type. If TIBCO Rendezvous is set as the transport,
you can store domain data in a database repository or file
repository. If TIBCO Enterprise Message Service is set as the
transport, you canonly store domain data in a database
repository. In most cases, it is recommended to use a
database for the domain repository and files for client
application repositories.

In the case of a file-based domain, domain data is stored in

theSYS_domain.datandAUTH_domain.datfiles. Data stored in
theSYS_domain.datfile is referred to as the administration
domain while data stored in theAUTH_domain.datfile is
referred to as the authorization domain.