TIBCO ADMIN*
*
*
Getting Started…
TIBCO ADMINISTRATOR
Tibco Administrator components
*
The following modules are provided in the TIBCO Administrator GUI
User Management
Resource Management
Application Management
User Management
*
User Management Cont…
Users—you 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.
Roles—Access 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.
*
Resource Management
*
Resource Management Cont…
*
Application Management
*
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.
*
To Upgrade an Application
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.
Changing Global Variables at Deployment
*
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.
Click Save.
Copyright © 2013 Tech Mahindra. All rights reserved.
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).
*
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.
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.
*
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.
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 can only 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.
*
Tibco Administration Products
Tibco RV
RV software supports many hardware and software platforms
Inter-operable across different hardware/software platforms
*
Benefits as Applications Evolve
*
TIB/Rendezvous Daemon
Data transport, Packet ordering, receipt acknowledgment, retransmission requests, and dispatching information to the correct application processes
Invisible to the applications that depend upon it.
*
Interactions Between Applications
*
Subject Names
Each message has a Subject Name.
A subject name is a character string that specifies the destination(s) of a message.
Subject Name can also describe the message content.
Sending and receiving applications must agree upon a subject name
Subject-based addressing technology enables anonymous messaging
have the freedom (and the responsibility) to establish conventions for using subject names
Subject names consist of one or more elements separated by periods.
*
Subject Names (examples)
Subject Names (examples)
Max 500 chars
Each element max chars - 255
*
Some issues with elements
For better performance use
less no of chars in an element (not > 50)
Make them meaningful
Quality of Service(Transport)
Reliable Messaging
No file storage overhead.
Rvd retains outbound messages for 60 seconds.
60 seconds, or Rvd process termination—whichever is first.
*
Certified Messaging
Offers greater certainty of delivery—even in situations where processes and their network connections are unstable.
FEATURES
*
Distributed Queue
Group of cooperating transport objects, each in a separate process
All groups members listen on the same subject
Members share same CMQ name
Senders are not group members
Member Roles—Worker and Scheduler
Inside the group, the member acting as scheduler assigns each task message to exactly one of the other members
Load Balancing
Fault Tolerance
Helps achieve fault tolerance by coordinating a group of redundant processes
*
Fault Tolerance Vs Distributed Queues
Fault tolerance requires that every member of a fault tolerance group receive each message.
*
Transports
Transport Parameters
Service
Communication across networks
As a direct result, services divide the network into logical partitions called service groups.
Each session belongs to a single service group.
A session can communicate only with other sessions in the same service group.
*
Network
You don’t need to worry about this parameter
Otherwise, specify the IP address or host name
*
Daemon
Default 7500
If you want to connect to an rvd on another machine
Use it along with Host name or IP address
Ex:
Tibco HAWK
TIBCO Hawk is a tool for monitoring and managing distributed applications and operating systems.
Unlike other monitoring solutions, TIBCO Hawk software uses TIBCO Messaging software for communication and inherits many of its benefits.
*
Functional Components of HAWK
Tibco Messaging
*
TIBCO Hawk Agents and Microagents
In a TIBCO Hawk environment, agents on each local computer perform the monitoring work.
Agents use objects called microagents to represent and interact with managed objects.
Microagents support methods which are invoked to extract monitoring information and carry out specified tasks.
This allows a total de coupling of the management data from the management rules or policies.
*
Rulebases and Rules
A rulebase is a collection of one or more rules.
A rule is a user defined monitoring policy.
It specifies a data source in the form of a microagent method, one or more tests that check for conditions, and one or actions to perform if a test is true.
*
TIBCO Hawk Display
*
Features
Scalability
Advanced Monitoring Logic
Scalability
A scalable network management tool seeks to minimize network traffic so the least amount of bandwidth is used.
*
Location Transparency and Fault Tolerance
A TIBCO Hawk agent runs on each node, where it collects information, applies monitoring logic, and carries out event notification and corrective actions.
Fault-tolerance is built in because agents perform tasks independently of other agents.
If one or more agents on the network ceases to function, other agents continue to monitor local data and perform tasks.
*
Copyright © 2013 Tech Mahindra. All rights reserved.
System Management Over Networks of Any Size
Using TIBCO Hawk Display, administrators can easily monitor and manage nodes in a large, distributed network using a collective or "follow the sun“ approach.
*
Advanced Monitoring Logic
TIBCO Hawk provides flexibility in performing monitoring tasks.
The rules or policies you create can be very simple or complex.
Using advanced features, you can implement solutions like the following:
Automatically restart a failed process.
Create a series of escalating actions to respond to a continuing or deteriorating problem.
Clear an alert when certain criteria are met.
Selectively ignore an intermittent condition and respond only after it persists.
Take an action when an alert clears, such as sending a stand-down notice to a backup systems administrator who is on call.
Switch rules automatically to support different monitoring setups.
Create thermostat-like controls to respond to fluctuating conditions.
Automatically alter monitoring behavior based on user defined schedules.
*
Flexibility
A distributed network typically must support multiple platforms and enterprise applications.
In such a heterogeneous environment, many different combinations of objects require monitoring and many variations of routine tasks require automation.
*
Tibco EMS
JMS Message Models
Point to Point
Point to Point
Point-to-point messaging has one producer and one consumer per message.
This style of messaging uses a queue to store messages until they are received.
*
Publish & Subscribe
Many publishers can publish to the same topic, and a message from a single publisher can be received by many subscribers.
*
Multicast
*
EMS Destination Features
TIBCO Enterprise Message Service allows you to configure destinations to enhance the functionality of each messaging model.
Set a secure mode for access control at the queue or topic level
Set threshold limits for the amount of memory used by the EMS server to store messages for a topic or a queue and fine-tune the server’s response to when the threshold is exceeded.
Route messages sent to destinations to other servers.
Create bridges between destinations of the same or different types to create a hybrid messaging model for your application.
Control the flow of messages to a destination.
Set queues to be exclusive or non-exclusive.
Trace and log all messages passing through a destination.
*
EMS Destination Features Cont…
Ex: create bridge source=queue:Queue_Test target=topic:Topic_Test
*
Security
For communication security between servers and clients, and between servers and other servers, you must explicitly configure SSL within EMS.
Secure Sockets Layer (SSL) is a protocol for transmitting encrypted data over the Internet or an internal network. SSL works by using public and private keys to encrypt data that is transferred over the SSL connection.
EMS supports SSL between the following components:
between an EMS client and the EMS server
between the administration tool and the EMS server
between the administration APIs and the EMS server
between routed servers
between fault-tolerant servers
Fault Tolerance
You can configure EMS servers as primary and backup servers to provide fault tolerance for your environment.
The primary and backup servers act as a pair, with the primary server accepting client connections and performing the work of handling messages, and the secondary server acting as a backup in case of failure.
*
Routing
EMS provides the ability for servers to route messages between each other.
Topic messages can be routed across multiple hops, provided there are no cycles (that is, the message can not be routed to any server it has already visited).
*
Thank You!