Tib Emsca Concepts

TIBCO Enterprise Message Service™ Central Administration

ConceptsSoftware Release 1.0November 2008

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN TIBCO ENTERPRISE MESSAGE SERVICE CENTRAL ADMINISTRATION INSTALLATION) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIB, TIBCO, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Enterprise Message Service, TIBCO Enterprise Message Service Central Administration, TIBCO Rendezvous, and TIBCO SmartSockets are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 2008 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xTIBCO Enterprise Message Service Central Administration Documentation . . . . . . . . . . . . . . . . . . . . . . . . . xOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xThird-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Chapter 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Structural Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Central Administration Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Access Control and Central Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2 The Central Administration Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Exploring the Central Administration Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Central Administration Client Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Project Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Understanding Rules and Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

TIBCO Central Administration Concepts

iv | Contents

Chapter 3 The Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

The Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

The Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

The Administration Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

How Conflicts are Resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 4 Advanced Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

The Application Programming Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27


Figures | v

Figures

Figure 1 Detailed Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Figure 2 The Central Administration Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8


vi | Figures


Tables | vii

Tables

Table 1 General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Table 2 Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12


viii | Tables


| ix

Preface

TIBCO Enterprise Message Service™ Central Administration provides a way for administrators of a TIBCO Enterprise Message Service™ deployment to make configuration changes to multiple Enterprise Message Service servers and deploy the changes simultaneously, all from a centralized location.

Topics

• Related Documentation, page x

• Typographical Conventions, page xii

• How to Contact TIBCO Support, page xiv


x | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Enterprise Message Service Central Administration DocumentationThe following documents form the TIBCO Enterprise Message Service Central Administration documentation set:

• TIBCO Enterprise Message Service Central Administration Concepts Read this manual to gain an understanding of the product that you can apply to the various tasks you may undertake.

• TIBCO Enterprise Message Service Central Administration Installation Read this manual for instructions on site preparation and installation.

• TIBCO Enterprise Message Service Central Administration Configuration and Deployment Read this manual for detailed instructions on using TIBCO Enterprise Message Service Central Administration.

• TIBCO Enterprise Message Service Central Administration Java API Reference Review the API reference for details about using the API to create rule selections and actions, and to create custom agents. The Java API reference can be accessed only through the HTML documentation interface.

• TIBCO Enterprise Message Service Central Administration Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues and closed issues for this release.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

• TIBCO Enterprise Message Service™

• TIBCO Rendezvous®

• TIBCO SmartSockets®


Preface | xi

Third-Party Documentation• Eclipse STABLE Documentation, available through

http://www.eclipse.org/documentation/

• Java™ Message Service specification, available through http://java.sun.com/products/jms/index.html

• Version Control with Subversion, available through http://svnbook.red-bean.com/

• Apache HTTP Server documentation, available through http://httpd.apache.org/

• Apache Tomcat documentation, available through http://tomcat.apache.org/


http://www.eclipse.org/documentation/

http://java.sun.com/products/jms/index.html

http://tomcat.apache.org/

http://httpd.apache.org/

http://svnbook.red-bean.com/

xii | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

EMSCA_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco .

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. The directory into which such products are installed is referenced in documentation as ENV_HOME. The value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

TIBCO Enterprise Message Service Central Administration installs into a directory within ENV_HOME. This directory is referenced in documentation as EMSCA_HOME. The value of EMSCA_HOME depends on the operating system. For example on Windows systems, the default value is C:\tibco\ems\ca\1.0 .

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin .

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]


Preface | xiii

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


xiv | How to Contact TIBCO Support

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibco.com/services/support

https://support.tibco.com

| 1

Chapter 1 Overview

This chapter contains a general overview of TIBCO Enterprise Message Service Central Administration components and architecture.

Topics

• Benefits, page 2

• Structural Overview, page 3

• Central Administration Projects, page 5

• Access Control and Central Administration, page 6


2 | Chapter 1 Overview

Benefits

CentralizedConfiguration

With TIBCO Enterprise Message Service Central Administration, you can apply configuration changes across multiple TIBCO Enterprise Message Service servers from a single location.

Graphical UserInterface

Central Administration uses the Eclipse framework to provide a graphical user interface (GUI) for configuring TIBCO Enterprise Message Service servers.

Revision Control Central Administration integrates with the Subversion version control system, allowing multiple administrators to collaborate without fear of introducing conflicts. Revision control also permits you to easily roll back to an earlier deployment.

Validation Central Administration validates configuration settings, showing any conflicts or invalid settings in the Problems view.

Queries Central Administration gives you the ability to assign tags to servers, letting you group and query for a specific set of servers to perform an action on. You can save rules and rule sets to run at a later date.


Structural Overview | 3

Structural Overview

TIBCO Enterprise Message Service Central Administration has two main parts, the Central Administration Client and the Central Administration Server. The Client is installed on an administrator’s local system, and provides a GUI for administering TIBCO Enterprise Message Service deployments. A user creates projects in the Client, with each project corresponding to one Enterprise Message Service deployment.

The Central Administration Server is installed in a centralized location, and acts as the hub between the Client and an Enterprise Message Service deployment. The Server hosts a Subversion repository, which provides source control for the Enterprise Message Service deployment’s configuration files.

Two other objects inside the Central Administration Server, the deployment server and the agent, manage the Server’s connections to the Client and the Enterprise Message Service deployment:

• Central Administration deployment servers are the Client’s connection to the Central Administration Server, and through that to the Enterprise Message Server. There is one deployment server for each project (or Enterprise Message Service deployment) administered by the Central Administration Server.

• The Central Administration agent manages the connection between the Central Administration Server and an Enterprise Message Service server. There is one agent for each server in the Enterprise Message Service deployment.

The Client connects to the Central Administration Server through the deployment server and retrieves source-controlled configuration files from the Server. Through the Client, the user makes the desired configuration changes and saves the changes to the Subversion repository. When a user issues a deploy command to the Central Administration Server, the agent then updates the deployed TIBCO Enterprise Message Service server configuration.

Figure 1 shows the connections between the Central Administration components and TIBCO Enterprise Message Service:



Figure 1 Detailed Architecture

Figure 1 shows a Central Administration Server with two deployment servers, DS1 and DS2.

DS1 administers the TIBCO Enterprise Message Service deployment called Deployment 1. It connects to the servers in Deployment 1 through agents, and stores files for those servers in the Subversion repository.

Similarly, DS2 connects to the EMS servers in Deployment 2 using agents. DS2 also stores Deployment 2 files in the repository.

Central Administration Clients connect to DS1 or DS2, depending on which Enterprise Message Service deployment the Client administers. Client A administers both deployments, and so connects to both DS1 and DS2. Client C administers only Deployment 1, and Client B administers only Deployment 2.

Because each deployment server corresponds to a project in the Client, we know that Clients B and C each have one project. Client A has configured two projects.

Central Administration Server

Subversion Repository

DS2

Client BClient A

DS1

Client C

Deployment 1 Deployment 2

Central Administration Agent

EMS Server

Central Administration Client

Central Administration Deployment Servers

Subversion Repository

Legend

DS1DS2


Central Administration Projects | 5

Central Administration Projects

TIBCO Enterprise Message Service Central Administration organizes TIBCO Enterprise Message Service deployments into projects, where each project corresponds to one TIBCO Enterprise Message Service deployment. All the servers in a single deployment are managed from within the same project. For example, you might have one project for your marketing environment, and one for the sales environment. .

A Central Administration project has two parts:

• The deployment server, which runs in the Central Administration Server. The deployment server is the first representation of the project. All configuration agents (and Enterprise Message Service servers) that connect to the deployment server are part of the project.

• The TIBCO EMS Project, which is configured in the Central Administration Client. The Client can create and manage multiple TIBCO EMS Projects. Each project corresponds to one Central Administration deployment server.

TIBCO Enterprise Message Service servers should not be shared across projects; including a server in two projects can cause configuration conflicts

Before you can create a new TIBCO EMS project in the Client, you must have already installed a Central Administration Server and deployed a Central Administration deployment server.



Access Control and Central Administration

TIBCO Enterprise Message Service Central Administration restricts access to configuration files in several different ways. First, it restricts which users can connect to the Central Administration Server and which users can save changes to the Subversion repository. It also restricts a user’s permissions to edit an Enterprise Message Service server configuration.

• Access to the Central Administration Server Permissions to connect to the Central Administration Server and any deployment server are controlled through your external LDAP server. Any user with a valid LDAP username and password can connect to the Central Administration Server. You can also control access to the Central Administration Server by restricting non-administrative access to the host, using standard UNIX permissions.

See TIBCO Enterprise Message Service Central Administration Installation for more information about configuring the Central Administration Server to connect to your LDAP directory.

• Access to the Subversion Repository Permissions save configuration changes to the Subversion repository are stored in the Subversion access control list (ACL). The Subversion ACL is initially configured during installation of the Central Administration Server. This controls who can modify and add files to the repository, but does not control view access.

• Access to the Configuration Files Permissions to edit the TIBCO Enterprise Message Service configuration files are determined by the user permissions configured for each Enterprise Message Service server in its acl.conf file. Subversion validates the user's permissions before permitting a save to the repository.

Users can view configurations without receiving edit permissions. When that is the case, the user is not permitted to save configuration changes to the Subversion repository.

Following installation of the Central Administration Server, the system administrator can change the Subversion ACL by editing the pre-commit.perms permissions file located here:

svn-install-dir/repos/conf/pre-commit.perms

See TIBCO Enterprise Message Service Central Administration Installation for more information about the Subversion access control list.


| 7

Chapter 2 The Central Administration Client

This chapter provides a detailed explanation of the Central Administration Client and the tools the Client provides for administering an Enterprise Message Service server.

Topics

• Exploring the Central Administration Client, page 8

• Understanding Rules and Rule Sets, page 12


8 | Chapter 2 The Central Administration Client

Exploring the Central Administration Client

The Central Administration Client is a graphical interface that runs in the Eclipse environment. Multiple instances of the Client can be installed on different computers, allowing administrators to manage an Enterprise Message Service deployment from different locations.

Figure 2 shows the Central Administration Client.

Figure 2 The Central Administration Client

Editor tabs

Identifies the perspective

Server Editor

Project Navigator

TIBCO EMS menu

Problems View tab

EMS Status View


Exploring the Central Administration Client | 9

Central Administration Client LayoutBecause it is part of the Eclipse environment, your Client layout may be different from the layout in Figure 2. The exact location of the screens depends on your personal configuration of the Eclipse display. You should be able to identify the following screens:

• Project Navigator The project navigator shows a list of all projects the Client administers, and all the servers, templates, and rule sets associated with each project.

• Editors and Editor Tabs Editors are the interface to the Enterprise Message Service server configuration files. Each editor corresponds to a .conf configuration file. You can switch between editors by clicking the editor tabs.

• Views Views display status information about the selected TIBCO Enterprise Message Service server or project. TIBCO Enterprise Message Service Central Administration has two custom views: the EMS Status View, and the Problems view.

Project NavigatorThe project navigator lists all the projects configured for the Client, and all TIBCO Enterprise Message Service servers, EMS RuleSets, and EMS Server Templates created for each project.



File Types The file names and types in the project navigator identify the item’s configuration file in the Subversion repository. You can identify an item in a project list as a server, template, or rule set according to its file type.

• .emsserver — identifies an Enterprise Message Service server.

• .emsservertemplate — identifies an EMS Server Template.

• .emsrules — identifies an EMS RuleSet.

The editors use the file type when determining how to display the item. If a file type is incorrect or missing, it does not display correctly in the editor.

EditorsThe editor tabs available in the main panel of the Client provide a visual interface into the configuration of a TIBCO Enterprise Message Service server. There is an editor for each server configuration file, and editor fields correspond to the parameters that can be set in each file.

You modify most parameter settings that are configurable during runtime using the TIBCO Enterprise Message Service Administration Tool. Other parameters can only be set when modifying a new server using the EMS Server Template. When viewing deployed EMS server configurations, these parameter values are displayed for informational purposes only. The parameter names are greyed out, and their settings cannot be modified through the Central Administration interface.

The Central Administration Client includes these editors:

• Server — Controls the characteristics of the TIBCO Enterprise Message Service server. This editor modifies the tibemsd.conf file.

• Topics — Defines TIBCO Enterprise Message Service topics. This editor modifies the topics.conf file.

• Queues — Defines TIBCO Enterprise Message Service queues. This editor modifies the queues.conf file.

• Bridges — Defines bridges between destinations. This editor modifies the bridges.conf file.

• Stores — Defines the locations, either store files or a database, where the server stores messages. This editor modifies the stores.conf file.

The project navigator is also the access point for Subclipse commands. Subclipse is an Eclipse plug-in that provides advanced tools for managing the Subversion repository. Subclipse includes many useful commands. You can access Subclipse commands by right-clicking an item in the project navigator.


Exploring the Central Administration Client | 11

• Routes — Defines routes between this and other TIBCO Enterprise Message Service servers. This editor modifies the routes.conf file.

• Channels — Defines the multicast channels over which multicast messages are broadcast. This editor modifies the channels.conf file.

• Transports — Defines transports used by TIBCO Enterprise Message Service to import messages from or export messages to an external message service, such as TIBCO Rendezvous or TIBCO SmartSockets. This editor modifies the transports.conf file.

• Users — Defines TIBCO Enterprise Message Service users. This editor modifies the users.conf file.

• Groups — Defines TIBCO Enterprise Message Service groups. This editor modifies the groups.conf file.

• ACL — Defines TIBCO Enterprise Message Service access control lists. This editor modifies the acl.conf file.

• Factories — Defines the connection factories stored as JNDI names on the TIBCO Enterprise Message Service server. This editor modifies the factories.conf file.

• Durables — Defines static durable subscribers. This editor modifies the durables.conf file.

• RVCM — Defines the TIBCO Rendezvous certified messaging (RVCM) listeners for use by topics that export messages to an RVCM transport. This editor modifies the tibrvcm.conf file.

ViewsThe Central Administration Client includes two views that provide helpful status information:

• EMS Status View Displays the status of the selected project and its deployment server. You can also view details about the Central Administration agents that are connected to the deployment server.

• Problems Displays any configuration errors in the TIBCO Enterprise Message Service server. The Client reviews the configuration files for errors each time the file is opened or saved.



Understanding Rules and Rule Sets

You can use Central Administration to modify individual Enterprise Messages Service servers, or you can make changes to groups of servers. Servers are grouped together through the use of tags. Once tags are assigned, you can write a rule that selects servers according to their groups, and then performs an action on the entire group. You can gather rules and actions together as part of a rule set, and save the rule set to be used again.

Both tags and rules are features of TIBCO Enterprise Message Service Central Administration, and are created and configured in the Central Administration Client.

TagsTags are customized Name-Value pairs that you can assign to a server. All servers that share the same tag Name-Value combination are part of the same group. Because you can assign multiple tags to a server, it can be part of multiple groups.

Table 2 shows an example of set of tags assigned to eight servers:

Tags are case sensitive and matches are made on whole words, not partial matches. That is, USA and usa are not matching values, and nor are USA and US .

Table 2 Tags

Server Name Tag Names

country city department product

PALO_ALTO_1

Tag

Val

ues

USA Palo Alto engineering widgets

PALO_ALTO_2 USA Palo Alto sales widgets

NEW_YORK_1 USA New York engineering gadgets

NEW_YORK_2 USA New York sales gadgets

PARIS_1 France Paris engineering widgets

PARIS_2 France Paris sales widgets

NICE_1 France Nice engineering gadgets

NICE_2 France Nice sales gadgets


Understanding Rules and Rule Sets | 13

In this example, each server has four tags. Four servers are located in the United States, and four in France. Four servers belong to the Product group gadgets, and four to widgets. Four are in the engineering Department, and four in the sales Department.

AliasesAliases identify the different listen ports configured for a TIBCO Enterprise Message Service server, and are used by rules to create routes between server pairs. You assign an alias to each listen and fault tolerant listen address:port assigned to a server in the Central Administration Client.

When creating routes between servers with multiple listen ports, you must specify an alias to identify the ports on either end of the route. The given alias name must be defined for both servers. That is, the alias name must be the same, but the alias definition can vary. For example, consider two servers with these settings:

• Server1 has listen port tcp://jms01:7222 with alias PRIMARY_LISTEN

• Server2 has listen port tcp://jms05:7224 also with alias PRIMARY_LISTEN

Because both servers have defined listen ports using the alias PRIMARY_LISTEN , you can use a rule to create a route between the servers.

Aliases are only used by rules to create or delete routes. If you do not have multiple listen ports or if you do not use rules to manage routes, then you do not need to define aliases.

The servers and tags shown in this table are used in examples in the following sections.

Aliases are used only by Central Administration, and have no application outside of the Central Administration project.

If you are using rules to manage routes, then keep these important points in mind:

• If you have multiple listens, you must define aliases.

• If an alias is defined, it must be entered in the Create Route rule action panel.

• The same alias name must be defined for all servers selected by the rule.



RulesA rule is a selection of servers and an action. The selection of servers is determined by the application of tags, and the action is applied to all servers in the selection. You can use multiple tags to create the server selection, but the rule is limited to one action.

There are two ways to select servers using tags. The first method selects all individual servers that match the specified tags. The second method uses tags to select pairs of servers. Both methods allow you to enter multiple selectors (or tags) to narrow the list of matching servers. When multiple selectors are entered, a server or pair of servers must match all entered selectors. That is, the selectors are applied using an AND operator.

Select by Server Tags

The Select by Server Tags method of defining a group of servers allows you to enter multiple tag Name-Value pairs in order to narrow down a list of servers. A server must match all listed tags to be a member of the final selection.

For example, consider the servers in Table 2. You could select a group of servers with the tag Name-Value pairs:

• country is USA

• department is sales

The resulting selection would include two servers: PALO_ALTO_2 and NEW_YORK_2 .

Select Two Servers by Tags

The Select Two Servers by Tags method of choosing a selection defines pairs of servers, and is primarily useful for creating routes between servers. This method selects the first server in the pair, then selects the second server in the pair.

There are three ways to select server pairs:

• Add Server One selects the first server in the pair using tag Name-Value pairs. This is the same method used to select a server using the Select by Server Tags rule type. However, this selection applies only to the first server in the pair. The second server in the pair is unaffected.

• Add Server Two selects the second server in the pair using tag Name-Value pairs. This selection applies only to the second server, and does not affect the selection of the first server.

Wildcard values are not supported in rules or rule sets. You must enter tag names and values in their entirety, as they are configured in the Server editor.


Understanding Rules and Rule Sets | 15

• Add Match selects both servers by requiring matching tag values. This selection method requires that you enter tag names but not values. The rule then compares the value set for the tag in Server One, and the value set for the tag in Server Two. If the values match, the servers are a match. The tag names that you specify can be different. Only the tag values are compared.

You can use any combination of these methods to create a list of server pairs. For example, consider the selections show in this screenshot (based on the configuration shown above in Table 2):

Example 1 Select Two Servers by Tags

In this example, the Select Server One and Select Server Two methods are each used twice, and the Add Match method is used once:

• Server One must have the tag country with the value USA, and the tag department with the value sales.

• Server Two must have the tag country with the value France, and the tag department with the value sales.



• Server One and Server Two must both have the same value for the product tag.

These selections result in two server pairs: PALO_ALTO_2 and PARIS_2, which are both sales servers managing widgets, and NEW_YORK_2 and NICE_2, which are also both sales servers, but which manage gadgets.

Rule SetsA rule set is a list of one or more rules that are executed together. All rules are created within a rule set, and you can use a rule set to apply multiple actions to the same selection of servers.

Selection Rule sets also offer the Selection tab, which you can use to narrow down the pool of servers that rules in the rule set can operate on. The selection criteria entered in the Selection tab is applied first, before individual rules in the rule set. Only servers that are included in the pre-selected group of servers are available to the rules in the rule set. A rule cannot modify a server that is not in this group.

Pre-selecting servers with the Selection tab is optional. If you do not enter any selectors, the rule set considers all servers in the project.


| 17

Chapter 3 The Central Administration Server

This chapter describes the Central Administration Server and its components.

Topics

• The Central Administration Server, page 18

• The Deployment Server, page 20

• The Administration Agent, page 21


18 | Chapter 3 The Central Administration Server

The Central Administration Server

The Central Administration Server is at the center of TIBCO Enterprise Message Service Central Administration—it is the link between Central Administration Clients and the Enterprise Message Service deployment. These processes are part of the Central Administration Server:

• Central Administration Deployment Server provides the connection between the Central Administration Client and the Central Administration Server, as well as managing the project in the Central Administration Server.

• Central Administration Agent provides the connection between the Central Administration Server and an Enterprise Message Service server.

• Subversion repository stores configuration files for Enterprise Message Service servers administered through Central Administration.

• Apache HTTPD Server manages communications between the Central Administration server, the Subversion repository, and the Central Administration Client.

• Apache Tomcat services the Central Administration deployment server and agents.

The SubversionRepository

The Administration Server holds copies of the current configuration of all synchronized TIBCO Enterprise Message Service servers in a Subversion repository. When a new project is created, the Administration Server also creates directory in the Subversion repository to hold configuration files for the servers in the project.

Central Administration Clients can make configuration changes to the files in the repository without immediately deploying these changes. When a Client does send a Deploy command, the Central Administration Server updates the deployed Enterprise Message Service server with configuration settings from the repository.

Additionally, the Central Administration Server is responsible for enforcing access control restrictions to the server configuration files stored in Subversion. For more information about how access to the TIBCO Enterprise Message Service server configuration files is controlled, see Access Control and Central Administration on page 6.


The Central Administration Server | 19

Apache HTTPDand Tomcat

The Apache HTTPD Server and Tomcat server are generally transparent components of the Central Administration Server. However, certain tasks require you to edit a process configuration file. For example, configuring the Central Administration Server to connect to an LDAP server after installation requires a change to the Apache HTTPD Server configuration files. See TIBCO Enterprise Message Service Central Administration Installation for more information about these tasks.



The Deployment Server

The Central Administration deployment server is the connection between the Central Administration Server and the Central Administration Client. The deployment server:\

1. Keeps track of the Enterprise Message Service servers that are part of its project.

2. Creates a Subversion repository for each project file, and manage the connection between the repository and the Client.

3. Sends deploy and synchronize commands from the client to the agent.

4. Provides the Client with updated configuration files from agents.

5. Validates Client requests, including requests to view configuration files and to save changes to configuration files.

In other words, the deployment server validates Central Administration Client requests and conveys commands between the Client, Subversion repository, and Central Administration agent.


The Administration Agent | 21

The Administration Agent

The Central Administration agent is the connection between the Central Administration deployment server and an Enterprise Message Service server. The agent has two tasks:\

1. During a synchronization, it retrieves the Enterprise Message Service server’s current configuration. This includes both the initial synchronization with the server and the retrieval of any configuration changes that have been made directly to the Enterprise Message Service server.

2. During a deployment, it updates the Enterprise Message Service server with configuration changes made in the Client.

In other words, the agent updates an EMS server with configurations from the Client, and updates the deployment server with any changes from the EMS server.

The agent establishes a connection to the Enterprise Message Service server when it receives either a synchronize or a deploy command from the Central Administration Client.

Deployment Upon a deploy command, the agent retrieves the specified configuration files from the Subversion repository and deploys the changes to the running Enterprise Message Service server. It updates the configuration using a merge action, which compares the configuration files from the repository to the deployed server files and updates the deployed server files.

During the first deployment, the agent compares the tibemsd server’s configuration with the Central Administration configuration that is being deployed. The agent uses the Java Admin API to change the tibemsd server to match the new Central Administration configuration.

On subsequent deployments, the agent compares the new configuration with the last Central Administration deployment (stored in the Subversion repository), and again updates the tibemsd server using the Java Admin API. Note that the agent does not review the deployed tibemsd server configuration. It looks only at the latest Central Administration deployment.

Because Central Administration does not prevent you from saving or deploying configuration changes containing errors, it is possible to issue a deploy command using files that contain errors, such as illegal parameter values or mutually exclusive parameter settings. If the agent encounters an error during deployment, its default behavior is to quit the deployment and shut down the TIBCO Enterprise Message Service server. You can alter this behavior by setting options in the agent. For more information, see Administration Agent Options in TIBCO Enterprise Message Service Central Administration Configuration and Deployment.



Synchronization A synchronize command directs the agent to retrieve the currently deployed server files and deliver them to the Client, overwriting the current configuration in the Client. Note that a synchronize command does not save any changes to the Subversion repository. It only affects the local Client configuration files.


How Conflicts are Resolved | 23

How Conflicts are Resolved

The Central Administration Server can receive configuration changes from multiple Clients. How does Central Administration resolve any conflicting configurations it receives from different Clients?

Conflicts During an Update Command

When a Client updates configurations from the Subversion repository, the Central Administration Server retrieves the latest configuration files from the repository and attempts to update the Client’s local configuration files with any new settings. The update behavior depends on whether:

1. The Client has the latest head revision from Subversion.

When the updating Client local files match the most current revision number in Subversion, the update command has no effect. The Client does not revert or lose any changes made since the last save to the repository. (You can revert to a previously saved revision using the Subclipse Revert command.)

2. Another Client has submitted a newer revision to Subversion.

When the Client’s local files do not match the latest revision number in Subversion, the Central Administration Server attempts to merge configuration settings from the latest revision with settings in the Client’s local files. When a client is working with a revision older than the latest revision saved in the repository, and when the Client has modified the same settings that the latest revision modified, a conflict can occur. In other words, a conflict occurs when the Client has changed a setting that is also changed in the latest revision in Subversion.

A conflict prevents the update from completing and generates an error. You must resolve the conflict by manually editing the XML configuration file in the Client. The Subclipse command Edit conflics, available through the Team menu, facilitates this resolution. Alternatively, you can discard your changes and synchronize with the Central Administration Server, then make the necessary changes to the latest revision.

Conflicts During a Save Command

When a Client saves its configurations to the repository, the Central Administration Server can encounter a conflict only when the Client does not have the latest revision from the Subversion repository. As it does with an update command, the Central Administration Server attempts to merge the Client’s configuration with the saved configurations. If it cannot complete the merge because of a conflict, the save fails and generates an error.



Conflicts During a Deploy Command

Because the Central Administration Server deploys configuration files from the Subversion repository, conflicts in this command are not between the Client’s configuration files and the Subversion repository. Conflicts during a deployment occur between the repository files and the deployed TIBCO Enterprise Message Service server files.

Most of the time conflicts during a deployment do not generate errors. However, there are two important things to consider:

1. Changes that are made directly to the deployed Enterprise Message Service server are not automatically saved to the Subversion repository. Therefore, they are not included in the merge action during a save to the repository.

2. The configuration files stored in Subversion take precedence over the deployed server files. During a deployment, the Central Configuration agent overwrites a deployed configuration file with the modified file from Subversion. Any .conf file that has been modified is included in the deployment. This means that any changes manually made to the deployed file are overwritten.

Deploying Configuration Files with Conflicting Settings

The Central Administration does not require that all settings be complete or consistent when a configuration file is saved to Subversion. This allows you to save without resolving any problems, but also means that you could potentially deploy a configuration that contains internal errors.

For example, creating an RVCM listener without assigning a name and saving the file prints an error in the Problems view. However, the error does not prevent you from completing the save, and the Central Administration Server does not then prevent you from deploying the illegal configuration.

If the Central Administration agent encounters illegal or invalid parameter values or combination, it exits the deployment and shuts down the TIBCO Enterprise Message Service server.

To save changes from the deployed server in the Subversion repository, you must first synchronize a client with the Enterprise Message Service server and then save the configuration to the repository.


| 25

Chapter 4 Advanced Features

This chapter describes advanced TIBCO Enterprise Message Service Central Administration features.

Topics

• The Application Programming Interface, page 26


26 | Chapter 4 Advanced Features

The Application Programming Interface

TIBCO Enterprise Message Service Central Administration offers a Java application programming interface that allows you to write custom rule sets that can run in the Central Administration rules engine:

• Create an action plug-in that performs a custom action on a selection of TIBCO Enterprise Message Service servers.

The Java API can be accessed through the HTML documentation set.


| 27

Index

A

access control 6administration agent 21aliases 13API 26, 26architecture 3

B

benefits 2

C

central administration server 18conflicts

resolving synchronization 23customer support xiv

E

eclipseeditors 10views 11

editors 10EMS status view 11EMSCA_HOME xiiENV_HOME xii

J

JavaDoc 26

P

permissions 6problems

view 11projects

project navigator 9

R

rules 16

S

security 6Subversion

security 6support, contacting xiv

T

tags 12technical support xivTIBCO_HOME xii


28 | Index

V

views 11EMS status view 11problems 11


Documents

Tib Emsca Concepts