TIBCO BusinessEvents Installation

Software Release 5.0 April 2011

The Power to Predict

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 THE LICENSE FILE) 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. TIBCO, The Power of Now, TIBCO ActiveMatrix, TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO ActiveSpaces, TIBCO Designer, TIBCO Enterprise Message Service, TIBCO Hawk, TIBCO Runtime Agent, TIBCO Rendezvous, 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 2004-2011 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Changes from the Previous Release of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii TIBCO BusinessEvents Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x TIBCO BusinessEvents and Add-On Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Accessing TIBCO BusinessEvents Functions Reference Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii xvii xvii xvii

Chapter 1 Installation Requirements and Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Required and Optional Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Required and Optional Third-Party Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Optional TIBCO Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 TIBCO BusinessEvents Components and Add-on Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 TIBCO BusinessEvents Standard Edition Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 TIBCO BusinessEvents Express Edition Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Add-on Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Upgrading TIBCO BusinessEvents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Standard Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Supported Windows Platforms and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Supported Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Windows Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Supported UNIX Platforms and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Supported UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 UNIX Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Installation History Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2 TIBCO BusinessEvents Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 TIBCO Environment and Default Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Limiting Access to TIBCO BusinessEvents Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

TIBCO BusinessEvents Installation

iv

| Contents
Using an Existing Eclipse (or TIBCO Business Studio) Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Installing TIBCO BusinessEvents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 18 20 20

Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Verifying TIBCO BusinessEvents Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Verifying Add-On Product Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Uninstalling TIBCO BusinessEvents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 3 Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Post Installation Tasks for All Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Migrating Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Re-Initialize Studio Plug-ins Registry after Add-on Software Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Check and Update JVM Settings in Properties Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 All UNIX Installations Directory Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Permissions for TIBCO BusinessEvents Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuration for 64-bit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 4 Migrating Projects from Earlier Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Project Migration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 For Berkeley DB Object Management Users Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Migration from 4.x to 5.0 Automatic Migration Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Migrating 4.x Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Importing a TIBCO BusinessEvents 4.x Project at the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Migrating 3.x Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Understanding the CDD File (For 3.x Users) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Most Runtime Properties are Configured in the CDD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Units (Engines) and Agent Classes are Configured in the CDD File . . . . . . . . . . . . . . . . . . . . . Metadata Properties (Extended Properties) are Configured in the CDD File . . . . . . . . . . . . . . . . . . . . . . . . 50 50 51 51

Importing a 3.x TIBCO Designer Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Importing a 3.x Project into TIBCO BusinessEvents Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Importing a TIBCO BusinessEvents 3.x Project at the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Clean and Validate 3.x Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clean and Validate the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fixing Ambiguous Reference Errors (Unqualified References) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fixing XSLT Mapper Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fixing Errors Due to Use of Words in Reserved Word List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 55 55 56 56

Oracle Types to JDBC Backing Store Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

TIBCO BusinessEvents Installation

Contents v

Backing Store Data Migration Property Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 5 Property Migration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Property Migration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Appendix A Deprecated and Unused Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

TIBCO BusinessEvents Installation

vi

| Contents

TIBCO BusinessEvents Installation

| vii

Preface

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. Please see the readme.txt file for the availability of this software version on a specific operating system platform. TIBCO BusinessEvents allows you to abstract and correlate meaningful business information from the events and data flowing through your information systems, and take appropriate actions using business rules. By detecting patterns within the real-time flow of events, TIBCO BusinessEvents can help you to detect and understand unusual activities as well as recognize trends, problems, and opportunities. TIBCO BusinessEvents publishes this business-critical information in real time to your critical enterprise systems or dashboards. With TIBCO BusinessEvents you can predict the needs of your customers, make faster decisions, and take faster action.

TIBCO BusinessEvents The Power to Predict

Topics
Changes from the Previous Release of this Guide, page viii TIBCO BusinessEvents Express, page ix Related Documentation, page x Typographical Conventions, page xiv Connecting with TIBCO Resources, page xvii

TIBCO BusinessEvents Installation

viii

| Changes from the Previous Release of this Guide

Changes from the Previous Release of this Guide
This section itemizes the major changes from the previous release of this guide. Migration Topics The migration topics have been updated. See the following: Chapter 4, Migrating Projects from Earlier Versions, page 33 Chapter 5, Property Migration Reference, page 61

Other Changes The full version of TIBCO Hawk was required for the machine-level monitoring feature available in TIBCO BusinessEvents Monitoring and Management. Now the limited version provided with TIBCO Runtime Agent is sufficient. The documentation has been updated accordingly. In the section Using an Existing Eclipse (or TIBCO Business Studio) Installation on page 16, the requirements have been updated to specify Eclipse Orbit package plug-ins, and not just Apache Xerces. The documentation now addresses the needs of partial installers as well as full installers. The chapter on installation FAQs and troubleshooting section has been removed because the content was no longer relevant for the current release.

TIBCO BusinessEvents Installation

Preface ix

TIBCO BusinessEvents Express

The TIBCO BusinessEvents Express edition provides more limited functionality than the TIBCO BusinessEvents standard edition. Some content in this documentation is not relevant to users of TIBCO BusinessEvents Express. Such content includes but is not limited to any chapters and major sections that contain a note indicating that the content does not apply to TIBCO BusinessEvents Express. Minor references to unsupported features may not be called out in the text. Use the following general guidelines to understand what is and is not supported in these cases: Only In Memory object management (OM) is supported. Therefore all functionality that requires Cache OM, such as use of a backing store, is not available. Berkeley DB OM is also not supported with the TIBCO BusinessEvents Express edition. The Monitoring and Management component and the related Site Topology editor are not supported with the TIBCO BusinessEvents Express edition. Instead you can use TIBCO Administrator and JMX for deployment, monitoring, and management. Only the TIBCO BusinessEvents Decision Manager add-on is supported with the TIBCO BusinessEvents Express edition in this release. Other add-on products are not supported.

TIBCO BusinessEvents Installation

| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.

TIBCO BusinessEvents and Add-On Product Documentation

The following diagram shows the main documents in the TIBCO BusinessEvents documentation set, and the documentation sets for the optional add-on products.
TIBCO BusinessEvents Getting Started

Architects Guide

Administration

Developers Guide Java API Reference Functions Reference

TIBCO BusinessEvents Data Modeling Add-On Documentation

TIBCO BusinessEvents Decision Manager Add-On Documentation

TIBCO BusinessEvents Event Stream Processing Add-On Documentation

TIBCO BusinessEvents Views Add-On Documentation

Legend

PDF

HTML

Eclipse help

Each set also contains an installation guide, release notes, and a readme file. TIBCO BusinessEvents Documentation TIBCO BusinessEvents Studio, the design-time UI, is supported on Windows and Linux. The documentation set for TIBCO BusinessEvents is as follows. TIBCO BusinessEvents Installation: Read this manual for instructions on site preparation, installation, upgrading from an earlier release, and project migration. TIBCO BusinessEvents Getting Started: After the product is installed, use this manual to learn the basics of TIBCO BusinessEvents: project design, cache

TIBCO BusinessEvents Installation

Preface xi

OM, and backing store. This guide explains the main ideas so you gain understanding as well as practical knowledge. TIBCO BusinessEvents Architects Guide: If you are architecting an application using TIBCO BusinessEvents, read this guide for overview and detailed technical information to guide your work. TIBCO BusinessEvents Developers Guide: Use this guide when you implement a project design in TIBCO BusinessEvents Studio. It covers topics such as project-level tasks, resource-level tasks, debugging, and integration with TIBCO ActiveMatrix BusinessWorks. TIBCO BusinessEvents Administration: This book explains how to configure, deploy, monitor, and manage a TIBCO BusinessEvents application and the data it generates. It explains how to configure the CDD file for different object management options, set up a backing store, and how to work with TIBCO BusinessEvents Monitoring and Management component, and with TIBCO Administrator. Online References: TIBCO BusinessEvents Java API Reference: This online reference is available from the HTML documentation interface. It provides the Javadoc-based documentation for the TIBCO BusinessEvents API. TIBCO BusinessEvents Functions Reference: This reference is available from the HTML documentation interface. It provides a listing of all functions provided with TIBCO BusinessEvents, showing the same details as the tooltips available in TIBCO BusinessEvents Studio. TIBCO BusinessEvents 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.

TIBCO BusinessEvents Event Stream Processing This TIBCO BusinessEvents add-on is available separately, and includes the TIBCO BusinessEvents Query Language features and the Pattern Matcher Service. TIBCO BusinessEvents Event Stream Processing Installation: Read this brief manual for installation instructions. A compatible version of TIBCO BusinessEvents must be installed before you install any add-on. TIBCO BusinessEvents Query Developers Guide: This manual explains how to use the object query language to query various aspects of the running system For details on configuring and deploying query agents, see TIBCO BusinessEvents Administration.

TIBCO BusinessEvents Installation

xii

| Related Documentation
TIBCO BusinessEvents Event Stream Processing Pattern Matcher Developers Guide: This manual explains how to use the pattern matcher language and engine to correlate event patterns in a running system. TIBCO BusinessEvents Event Stream Processing 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.

TIBCO BusinessEvents Decision Manager This TIBCO BusinessEvents add-on is available separately. It incorporates the Decision Manager decision modeling business user interface (supported on Windows and Linux), and the Rules Management Server (supported on all platforms supported by TIBCO BusinessEvents). TIBCO BusinessEvents Decision Manager Installation: Read this brief manual for installation instructions. A compatible version of TIBCO BusinessEvents must be installed before you install any add-on. TIBCO BusinessEvents Decision Manager Users Guide: This manual explains how business users can use decision tables and other decision artifacts to create business rules. It also covers configuration and administration of Rules Management Server, which is used for authentication, authorization, and approval processes. TIBCO BusinessEvents Decision Manager 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.

TIBCO BusinessEvents Data Modeling This TIBCO BusinessEvents add-on is available separately. It contains state models and database concept features. TIBCO BusinessEvents Data Modeling Installation: Read this brief manual for installation instructions. A compatible version of TIBCO BusinessEvents must be installed before you install any add-on. TIBCO BusinessEvents Data Modeling Developers Guide: This manual explains data modeling add-on features for TIBCO BusinessEvents. The database concepts feature enables you to model TIBCO BusinessEvents concepts on Database tables. The state modeler feature enables you to create state machines. TIBCO BusinessEvents Data Modeling 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.

TIBCO BusinessEvents Installation

Preface xiii

TIBCO BusinessEvents Views This TIBCO BusinessEvents add-on is available separately. It includes graphical dashboard components for run-time event monitoring. TIBCO BusinessEvents Views Installation: Read this manual for instructions on site preparation and installation. A compatible version of TIBCO BusinessEvents must be installed before you install any add-on. TIBCO BusinessEvents Views Developers Guide: This guide explains how to use TIBCO BusinessEvents Views to create meaningful metrics that are presented to business users in real-time for proactive decision making. TIBCO BusinessEvents Views Users Guide: This book explains how to monitor metrics in TIBCO BusinessEvents TIBCO BusinessEvents Views and how to represent the business processes graphically. TIBCO BusinessEvents Views 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.

Accessing TIBCO BusinessEvents Functions Reference Documentation

Reference documentation for functions, including those used in add-ons, is available in the HTML documentation interface for the TIBCO BusinessEvents documentation set, and as tooltips in TIBCO BusinessEvents Studio. To use the HTML-based functions reference from the file system do the following: 1. Browse to BE_HOME/ d o c / s t a n d a r d / h t m l and click i n d e x . h t m . The HTML documentation interface appears. 2. In the left panel, browse to Online References and in the right panel choose TIBCO BusinessEvents Functions Reference. The reference opens in a new tab. 3. Click the navigation links to browse to the functions as desired.

Other TIBCO Product Documentation

You may find it useful to refer to the documentation for the following TIBCO products: TIBCO ActiveSpaces TIBCO Hawk TIBCO Rendezvous TIBCO Enterprise Message Service TIBCO ActiveMatrix BusinessWorks

TIBCO BusinessEvents Installation

xiv

| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention
TIBCO_HOME ENV_HOME BE_HOME

Use 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 : \ t i b c o . Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. An environment home directory 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 : \ t i b c o . TIBCO BusinessEvents installs into a directory within an ENV_HOME. This directory is referenced in documentation as BE_HOME. The value of BE_HOME depends on the operating system. For example on Windows systems, the default value is C : \ t i b c o \ b e \ 5.0.

code font

Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use M y C o m m a n d 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 a d m i n . 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, M y C o m m a n d is enabled: MyCommand [e n a b l e | disable]

TIBCO BusinessEvents Installation

Preface xv

Table 1 General Typographical Conventions (Contd) Convention

italic font

Use Italic font is used in the following ways: To indicate a document title. For example: See TIBCO 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: M y C o m m a n d 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 2 Syntax Typographical Conventions Convention

[ ]

Use An optional item in a command or code syntax. For example:

MyCommand [optional_parameter] required_parameter

A logical O R that separates multiple items of which only one may be chosen. For example, you can select only one of the following parameters:
MyCommand param1 | param2 | param3

TIBCO BusinessEvents Installation

xvi

| Typographical Conventions
Table 2 Syntax Typographical Conventions Convention
{ }

Use A logical group of items in a command. Other syntax notations may appear within each logical group. For example, the following command requires two parameters, which can be either the pair p a r a m 1 and p a r a m 2 , or the pair p a r a m 3 and p a r a m 4 .
MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either p a r a m 1 or p a r a m 2 and the second can be either p a r a m 3 or p a r a m 4 :
MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be p a r a m 1 . You can optionally include p a r a m 2 as the second parameter. And the last parameter is either p a r a m 3 or p a r a m 4 .
MyCommand param1 [param2] {param3 | param4}

TIBCO BusinessEvents Installation

Preface xvii

Connecting with TIBCO Resources

This section provides links to helpful TIBCO resources.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO Documentation

After you join TIBCOmmunity, you can access the documentation for all supported product versions here: http://docs.tibco.com/TibcoDoc

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows. 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.

TIBCO BusinessEvents Installation

xviii Connecting with TIBCO Resources

TIBCO BusinessEvents Installation

|1
Chapter 1

Installation Requirements and Guidelines

This chapter lists software requirements and supported platforms. It also provides other information to ensure a successful installation of the TIBCO BusinessEvents software.
TIBCO BusinessEvents Express This guide is also used to document installation of the TIBCO BusinessEvents Expresss edition. The TIBCO BusinessEvents Express edition supports only In Memory object management. Content that requires cache functionality does not apply to TIBCO BusinessEvents Express edition.

Topics
Required and Optional Products, page 2 TIBCO BusinessEvents Components and Add-on Products, page 5 Upgrading TIBCO BusinessEvents, page 7 Supported Windows Platforms and Guidelines, page 8 Supported UNIX Platforms and Guidelines, page 10 Installation History Log Files, page 12

TIBCO BusinessEvents Installation

| Chapter 1

Installation Requirements and Guidelines

Required and Optional Products

Depending on the tasks you wish to perform, the following third-party products and additional TIBCO products listed in this section can be used with TIBCO BusinessEvents. The version of TIBCO BusinessEvents and all add-on products must match. When you upgrade TIBCO BusinessEvents, you must also upgrade all add-on products in use to the same version. Similarly, you cannot install a later version of an add-on onto an earlier version of TIBCO BusinessEvents. Add-ons must be at the same version as TIBCO BusinessEvents in order to work correctly.

Required and Optional Third-Party Products

TIBCO BusinessEvents provides JRE version 1.6.0, which is the required version. DBMS for (Optional) Backing Store For the optional backing store feature, the following DBMS software is supported: Oracle Oracle Database 10g Enterprise Edition Release 2 Oracle Database 11g Enterprise Edition Release 1 and 2 Oracle Real Application Clusters (RAC) 10g Release 2 Oracle Real Application Clusters (RAC) 11g Release 1 and 2 The Oracle Express Edition can also be used for non-production usage. Database driver o j d b c 6 . j a r for use with Sun Java JRE 6 (Oracle Thin Driver only) Microsoft SQL Server 2005 and 2008 Enterprise Edition with s q l j d b c 4 . j a r

Using Oracle Coherence as Alternative Cache Provider Only TIBCO BusinessEvents DataGrid is provided with TIBCO BusinessEvents. An Oracle Coherence cache provider option is available for customers who want to use their own licensed copy of Oracle Coherence software. Use of Oracle Coherence Version 3.6 and above is supported.

TIBCO BusinessEvents Installation

Required and Optional Products 3

Using an Existing Eclipse (or TIBCO Business Studio) Installation Using the bundled Eclipse software is recommended. However, you can optionally use an existing Eclipse installation. You can, for example, use the Eclipse installation provided with TIBCO Business Studio business modeling software. This option is not available with partial installers (commonly used for service pack releases). See Using an Existing Eclipse (or TIBCO Business Studio) Installation on page 16 for details. Using Copssh for TIBCO BusinessEvents Monitoring and Management TIBCO BusinessEvents Monitoring and Management (MM) is a provided component. It is one of the options available for deployment, monitoring, and management. (If TIBCO Administrator is used in your environment, you can use it instead.) Copssh is one of the options available to enable MM to perform remote start and deployment of TIBCO BusinessEvents engines running on Microsoft Windows. Copssh versions 3.1.3 and 3.1.4 are supported. Due to changes in the Copssh product, versions 4.0 and above do not work correctly with MM. LDAP Support for Optional Authorization Features You can optionally use authorization for TIBCO BusinessEvents Monitoring and Management, and also TIBCO BusinessEvents Decision Manager and TIBCO BusinessEvents Views add-ons. You can use file-based or LDAP-based authorization mechanisms. Supported LDAP products are: Oracle Directory Server Enterprise Edition 6.1 (formerly Sun Directory Server Enterprise Edition) Windows Server 2003 Active Directory

TIBCO BusinessEvents Installation

| Chapter 1

Installation Requirements and Guidelines

Optional TIBCO Products

TIBCO BusinessEvents does not require installation of other TIBCO products. Certain features require use of other TIBCO products. The next table lists products that are typically used with TIBCO BusinessEvents and the supported versions. Table 3 Optional TIBCO Products Component TIBCO ActiveMatrix BusinessWorks 5.8, 5.9 Purpose Optional. TIBCO ActiveMatrix BusinessWorks is a scalable, extensible, and easy to use integration platform that allows you to develop integration projects. Optionally, you can use ActiveMatrix BusinessWorks in integration projects. Optional. Can be used for deployment. Optional. Included in the TIBCO Runtime Agent distribution. Used for ActiveMatrix BusinessWorks integration projects. Optional. TIBCO Enterprise Message Service allows you to use the Java Messaging Services (JMS) as a message transport. Optional. Provides monitoring capability. Used (if available) by the TIBCO BusinessEvents Monitoring and Management component to provide machine-level health metrics. Note that the limited version of TIBCO Hawk bundled with TRA is sufficient for use with TIBCO Administrator and with TIBCO BusinessEvents Monitoring and Management. TIBCO Rendezvous 8.2.1 and higher TIBCO Runtime Agent 5.6.2, 5.7 Optional. TIBCO Rendezvous can be used as a message transport. Used with TIBCO Administrator and TIBCO ActiveMatrix BusinessWorks. Includes TIBCO Designer.

TIBCO Administrator 5.6, 5.7 TIBCO Designer 5.6.2, 5.7 TIBCO Enterprise Message Service 5.0 TIBCO Hawk 4.8.1 and higher

TIBCO BusinessEvents Installation

TIBCO BusinessEvents Components and Add-on Products 5

TIBCO BusinessEvents Components and Add-on Products

This section lists the product components and add-on products.

TIBCO BusinessEvents Standard Edition Components

TIBCO BusinessEvents Standard edition provides the following components.
Studio Eclipse-based component for designing TIBCO BusinessEvents

projects.
Eclipse Platform A provided Eclipse platform. If you do not use the provided

Eclipse installation, you must have a preexisting Eclipse 3.4.2 installation. See Using an Existing Eclipse (or TIBCO Business Studio) Installation on page 16 for more information. TIBCO BusinessEvents DataGrid Used for cache functionality. Cannot be separately installed or uninstalled. Monitoring and Management A configurable web-based user interface for monitoring and managing TIBCO BusinessEvents clusters.
Documentation TIBCO BusinessEvents documentation. The d o c folder contains an HTML and a PDF folder. If you do not install documentation, this folder is not included in the installation. Runtime The runtime engine. Cannot be separately installed or uninstalled.

TIBCO BusinessEvents Express Edition Components

TIBCO BusinessEvents Express edition provides the following components.
Studio Eclipse-based component for designing TIBCO BusinessEvents

projects.
Eclipse Platform A provided Eclipse platform. If you do not use the provided

Eclipse installation, you must have a preexisting Eclipse installation of a supported version. See Using an Existing Eclipse (or TIBCO Business Studio) Installation on page 16 for more information.
Documentation TIBCO BusinessEvents documentation. The d o c folder contains an HTML and a PDF folder. If you do not install documentation, this folder is not included in the installation. Runtime The runtime engine. Cannot be separately installed or uninstalled.

TIBCO BusinessEvents Installation

| Chapter 1

Installation Requirements and Guidelines

Add-on Products
When you install TIBCO BusinessEvents Standard edition, you can also install any add-on products you have purchased. Add-ons available in this release are shown below. TIBCO BusinessEvents Data Modeling TIBCO BusinessEvents Event Stream Processing TIBCO BusinessEvents Decision Manager TIBCO BusinessEvents Views

Install TIBCO BusinessEvents first, and only install add-ons that are the same version as TIBCO BusinessEvents. For TIBCO BusinessEvents Express edition, only TIBCO BusinessEvents Decision Manager is supported.

TIBCO BusinessEvents Installation

Upgrading TIBCO BusinessEvents 7

Upgrading TIBCO BusinessEvents

Before You Upgrade Read Chapter 4, Migrating Projects from Earlier Versions, on

page 33.

Standard Upgrade Procedures

Software from TIBCO uses three numbers to indicate whether the release is major, minor or a patch. For example, 5.0.0 indicates a major release, 5.4.0 indicates a minor release and 5.3.3 indicates a service pack release. The installer for a service pack release performs an automatic upgrade. For example, the installer would automatically upgrade TIBCO BusinessEvents 5.3.0 to 5.3.1 by overwriting the contents of the 5.3 directory. If you are upgrading TIBCO BusinessEvents to a new major or minor version, it is strongly recommended that you uninstall the earlier version of the product first and perform a fresh installation (full product installers only). Installing Over the Same Version Note that if you are reinstalling over the same version, if any files are currently locked (that is, in use), the installer marks the file for deletion in the install location. After installation if the installer prompts you to reboot your system, you must reboot before using the software.

TIBCO BusinessEvents Installation

| Chapter 1

Installation Requirements and Guidelines

Supported Windows Platforms and Guidelines

Supported Windows Platforms

The following is a list of supported platforms for Microsoft Windows: The TIBCO BusinessEvents DataGrid component is supported on all Windows platforms except Windows 7. Windows Server 2003 (x86 and x86_64) Windows Server 2008 (x86 and x86_64) Windows XP (x86) Windows Vista Business Edition (x86) Windows 7

Disk Space Requirements Disk space required for the installed product is between 530MB and 550MB depending on platform. In addition to the disk space required for the installed product, files created by the installer require about 500 KB of disk space in the users home directory.

Windows Installation Guidelines

Within a single cache cluster, you can use a mixture of 64bit and 32bit operating systems. Installer Account You must have administrator privileges for the machine on which the software is installed. If you do not have administrator privileges, the installer exits. You must then log out of the system and log in as a user with the required privileges, or request your system administrator to assign the privileges to your account.

TIBCO BusinessEvents Installation

Supported Windows Platforms and Guidelines 9

Installing from a Network Drive If you intend to install the product from a network drive, you must ensure that the account used for installation has permission to access the network drive. Installing on Windows 2000 Terminal Server There are two modes in terminal server, E x e c u t e and I n s t a l l . By default all users are logged on in E x e c u t e mode, which allows them to run the applications. When you want to install the software for use by everyone, the Administrator should change to I n s t a l l mode. The best way to install the software on Windows 2000 Terminal Server is to use the Add/Remove Programs control panel applet, because this automatically sets the mode to I n s t a l l during the installation and then back to E x e c u t e at the end. Alternatively, you can manually change your mode to I n s t a l l by typing C : \ >
change user /install

Change back to execute by typing C : \ >

change user /execute change user /query

Check your current mode by typing C : \ >

If you install in the E x e c u t e mode, the installation registry is maintained in your user home directory. If you install in the I n s t a l l mode, the installation registry is maintained in the %SystemRoot% folder.

TIBCO BusinessEvents Installation

10

| Chapter 1

Installation Requirements and Guidelines

Supported UNIX Platforms and Guidelines

TIBCO BusinessEvents Studio is supported only on Linux (and Windows) platforms. TIBCO BusinessEvents DataGrid is not supported on HP-UX and AIX platforms.

Supported UNIX Platforms

The following is a list of supported platforms for UNIX: Red Hat (x86) (32-bit & 64-bit) Red Hat Enterprise Linux 4.x, 5.x, and materially equivalent Linux distributions

SUSE (x86) SUSE Linux Enterprise 11 SUSE Linux Enterprise 10

Solaris X86_64 Solaris 10 (64-bit)

Solaris SPARC Solaris 10 (32-bit and 64-bit)

Hewlett-Packard: HP-UX 11i (v1, v2, v3) (PA-RISC) (32-bit and 64-bit) HP-UX 11i (v2, v3) (IA-64/Itanium) (64-bit)

IBM (POWER): AIX 6.1 (64-bit) AIX 5.3 (64-bit)

TIBCO BusinessEvents Installation

Supported UNIX Platforms and Guidelines 11

Disk Space Requirements Approximate disk space required for the installed product is as follows: 530MB for Linux 800MB for HP-UX and Solaris X86_64 830MB for Solaris SPARC 440MB for AIX In addition to the disk space required for the installed product, files created by the installer require about 500 KB of disk space in the users home directory.

UNIX Installation Guidelines

For platforms that support 64-bit mode, post installation configuration is required. See Configuration for 64-bit Mode on page 30. For HP-UX platforms, also see HP-UX on page 31. All 32-bit installers are supported on 64-bit platforms as 32-bit software. Installer Account The software can be installed by a regular (non-root) user and super-user (root). Different users can install the same product at different locations.
Installation of TIBCO BusinessEvents add-on products must be performed by the same user who installed TIBCO BusinessEvents Dependency checking will not

work correctly unless the same user installs all dependent products. Windowing Environment A windowing environment such as CDE (that is, X11 Windows) is required to run the installer in GUI mode. It is not required for a console installation or silent installation.

TIBCO BusinessEvents Installation

12

| Chapter 1

Installation Requirements and Guidelines

Installation History Log Files

Installation and uninstallation history is kept in log files in the . T I B C O directory within the installers user (or home) directory. The folder names use this format:
install_month-day-year.time uninstall_month-day-year.time

The installation log files record environment details such as the user that invoked the installer, hostname, operating system details, and so on.

TIBCO BusinessEvents Installation

| 13
Chapter 2

TIBCO BusinessEvents Installation

This chapter describes how to install this release using TIBCO Universal Installer.

Topics
Installation Overview, page 14 Using an Existing Eclipse (or TIBCO Business Studio) Installation, page 16 Installing TIBCO BusinessEvents, page 18 Verifying the Installation, page 22 Uninstalling TIBCO BusinessEvents, page 23

TIBCO BusinessEvents Installation

14

| Chapter 2

TIBCO BusinessEvents Installation

Installation Overview

TIBCO Environment and Default Installation Directory

The installer prompts you to specify the environment (TIBCO_HOME) where you want to install TIBCO BusinessEvents. Each TIBCO environment is isolated. You can install the same software into different environments safely, for example, for test, QA, and staging purposes. You can install multiple TIBCO products into the same environment. An environment has a name and a directory on disk. The directory is the root directory for all TIBCO products you want to install into this environment. When installing multiple TIBCO products into a single installation environment, ensure that all the products are compatible. Microsoft Windows The default installation location is the TIBCO_HOME where all TIBCO products are installed. Typically, TIBCO_HOME is c : \ t i b c o . The Start menu path to the executable files includes the environment as follows: Start > TIBCO > TIBCO_HOME > TIBCO BusinessEvents 5.0 The name is also appended to the name of Windows services created by the installer. UNIX The default installation directory depends on who performs the installation: For root users, the default installation directory is / o p t / t i b c o . For non-root users, the default installation directory is / <myhome>/ t i b c o , where <myhome> is the home directory of the user.

Limiting Access to TIBCO BusinessEvents Installations

In some enterprises, users are given limited access to software installations, such as TIBCO BusinessEvents. All users, however, require full rights to the Eclipse installation because certain files are written during normal use of BusinessEvents Studio.

TIBCO BusinessEvents Installation

Installation Overview 15

In this case you must install Eclipse separately, in areas where users have permission to write. Use of a separately installed Eclipse installation (instead of the Eclipse software provided with TIBCO BusinessEvents) may be required for other reasons too. See Using an Existing Eclipse (or TIBCO Business Studio) Installation on page 16.

TIBCO BusinessEvents Installation

16

| Chapter 2

TIBCO BusinessEvents Installation

Using an Existing Eclipse (or TIBCO Business Studio) Installation

This section is optional. It is also relevant only for releases with full installers. It is not relevant for releases with partial installers, such as service pack releases. Requirements and Guidelines TIBCO recommends using the Eclipse software bundled with the TIBCO BusinessEvents software. However, if you prefer to use your existing Eclipse software installation, or want to install Eclipse separately, or want to install TIBCO BusinessEvents for use with the TIBCO Business Studio business modeling software product, you must update the existing Eclipse installation with the required plug-ins. You can do this before or after installing TIBCO BusinessEvents. The Eclipse requirements are: Eclipse release 3.4.2 Eclipse Modeling Framework (EMF) release 2.4.2 Model Development Tools (MDT) UML release 2.2.2 The following Eclipse Orbit package plug-ins: Javax XML 1.3.4 Apache Commons Codec 1.3.0 Apache Commons Httpclient 3.1.0 Apache Commons Lang 2.3.0 Apache Xerces 2.9 Apache XML Resolver 1.2.0 Apache XML Serializer 2.7.1 To Use an Existing Eclipse Installation with TIBCO BusinessEvents 1. Download the above files from the Eclipse Foundation web site. 2. If you have not already done so, install the Eclipse release. 3. Extract the other components (EMF, MDT, and Eclipse Orbit package plug-ins) to the top-level directory of your Eclipse installation. 4. For partial installers (such as service packs) only: Re-initialize Eclipse in your existing TIBCO BusinessEvents installation before you install the current

TIBCO BusinessEvents Installation

Using an Existing Eclipse (or TIBCO Business Studio) Installation 17

release of TIBCO BusinessEvents. To do this, change directory to BE_HOME/ s t u d i o / e c l i p s e and execute the command:
studio -clean -initialize

5. Install TIBCO BusinessEvents for use with an existing Eclipse installation, as explained in this guide. Remember to select the Use my own Eclipse installation check box. (You can install TIBCO BusinessEvents before you install the Eclipse software if you prefer; but by step 6 in this procedure, both should be installed). 6. Copy the T I B C O B u s i n e s s E v e n t s - S t u d i o - p l u g i n s . l i n k file from BE_HOME/ s t u d i o / e c l i p s e / d r o p i n s _ c o n f i g u r a t i o n to Your_Eclipse/ l i n k s . 7. Configure the Your_Eclipse/ e c l i p s e . i n i file as follows: Ensure that the VM setting is done for Java 1.6 JVM. Path should appear in a new line:
vm

path to JRE 1.6

Add the following properties to - v m a r g s , each on a new line

- D B E _ H O M E = path to BE_HOME -Dstudio.wrapper.tra.file=<path to BE_HOME>/studio/eclipse/configuration/studio.tra - D J D K _ L I B = path to JRE

1.6/ l i b

8. Change directory to the Your_Eclipse location and run the command:

eclipse -clean initialize

9. Run the command e c l i p s e . Running this command loads Eclipse with the BusinessEvents Studio plug-ins.

TIBCO BusinessEvents Installation

18

| Chapter 2

TIBCO BusinessEvents Installation

Installing TIBCO BusinessEvents

Download the TIBCO BusinessEvents product package from http://www.download.tibco.com. To download the software, you need a username and password. If you did not receive a username and password, contact TIBCO Technical Support. You can install using one of the following modes, which are supported on all platforms. Install in GUI Mode Install in Console Mode Install in Silent Mode

If you will use an existing Eclipse installation See Using an Existing Eclipse (or

TIBCO Business Studio) Installation on page 16 for steps you may want to take before installing TIBCO BusinessEvents.
After installation is complete Perform any post-installation tasks as required. See

Chapter 3, Post Installation Tasks, on page 25.

Install in GUI Mode

The following procedure explains how to install the software in GUI mode. 1. Prepare to install as follows: a. Log in to the system on which you want to install TIBCO BusinessEvents. b. Extract the TIBCO BusinessEvents product archive file to a temporary directory then navigate to that directory. 2. Run TIBCOUniversalInstaller. 3. Review the information in the Welcome dialog and click Next. 4. The License Agreement dialog displays. Review the terms of the license agreement and, if you agree to them, click I accept the terms of the license agreement. Then click Next to continue with the installation. If you are also installing add-on products, you must accept each license separately. If you do not agree to the terms of the license agreement, click Cancel to exit from the installation process.

TIBCO BusinessEvents Installation

Installing TIBCO BusinessEvents 19

5. Select or create a TIBCO environment. For more details and guidelines see TIBCO Environment and Default Installation Directory on page 14. Do one of the following: Select Use an Existing TIBCO_HOME, select an environment from the list, and click Next. For a service pack, select the environment used by the prior release. Create a new environment. Browse to and select a directory, and provide a name for the environment. The name cannot contain special characters such as "*", "?", ">", "<", ":", "|", "/", "\", or quotes ("). 6. For full installers only, do one of the following: Select Typical and click Next. Select Custom installation and click Next. At the next screen, select components to be installed from the panel on the right and click Next. See TIBCO BusinessEvents Standard Edition Components on page 5 for guidelines. 7. The Eclipse Location dialog displays. Do one of the following. Click Next to accept the provided Eclipse installation (recommended). Select the Use my own Eclipse installation check box. See Using an Existing Eclipse (or TIBCO Business Studio) Installation on page 16 for additional configuration required. Specify the location of your Eclipse installation in the Eclipse Installation Location field, and click Next. The installer performs some basic checks and if it finds any problems with the Eclipse configuration that you specified, it displays messages. If you are installing TIBCO BusinessEvents before your own copy of Eclipse, you can ignore the messages and continue the installation. 8. The installer configures your installation choices, then the Pre-Install Summary dialog displays. Review the information in the dialog and make sure that it is correct. If you want to change any of your choices, click Back to step back through the dialogs to the appropriate point. You can then restart the installation process from that point. If you are satisfied with your choices, click Install. The installer now performs the necessary installation tasks. 9. When installation has completed, the Post Install Summary dialog displays. Click Finish to exit from the installer. There is a slight delay while the installer deletes temporary files.
TIBCO BusinessEvents Installation

20

| Chapter 2

TIBCO BusinessEvents Installation

Install in Console Mode

The following procedure explains how to install the software in console mode. 1. Open the physical media or download the TIBCO BusinessEvents product package. 2. Extract the TIBCO BusinessEvents product archive file to a temporary directory. 3. Using a console window, navigate to the temporary directory that contains the universal installer and run the installer using this command line:
TIBCOUniversalInstaller -console

4. Complete the installation by responding to the console window prompts.

Install in Silent Mode

The following procedures explain how to install the software in silent mode. Any errors that occur during installation are listed in the installation log file (see the User_Home/ . T I B C O directory. Configure the Installation Responses A configuration file, T I B C O U n i v e r s a l I n s t a l l e r . s i l e n t , is provided with the universal installer. Copy the file to another name (but keep the . s i l e n t extension) and use it to configure your installation choices. You must edit the file in a text editor and provide all non-default values as needed before launching the silent installation. For example, ensure that the i n s t a l l a t i o n R o o t and c r e a t e N e w E n v i r o n m e n t attributes are set correctly. The file includes comments to help you set the installation properties. Save the configuration file to the same directory where the universal installer file is located. It is recommended that you back up the original file or save your edited file to a different name. This file is known as the response file. Install in Silent Mode 1. Extract the TIBCO BusinessEvents product archive file to a temporary directory. 2. Using a console window, navigate to the temporary directory that contains the universal installer. 3. Run the installer:
T I B C O U n i v e r s a l I n s t a l l e r - s i l e n t - V r e s p o n s e F i l e = " myfile. s i l e n t "

TIBCO BusinessEvents Installation

Installing TIBCO BusinessEvents 21

If you are using the T I B C O U n i v e r s a l I n s t a l l e r . s i l e n t file, you need not supply the file name and can run T I B C O U n i v e r s a l I n s t a l l e r - s i l e n t . A line similar to the following is written to the installer log file when installation completes:
Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, The installation has completed. Please check the log file for additional information.

TIBCO BusinessEvents Installation

22

| Chapter 2

TIBCO BusinessEvents Installation

Verifying the Installation

TIBCO BusinessEvents and TIBCO BusinessEvents add-on product installations can be verified as follows.

Verifying TIBCO BusinessEvents Installation

After installation of TIBCO BusinessEvents and any of its add-on products, verify the installation as follows. To verify if the installation is successful, first check the file t i b c o _ u n i v e r s a l _ i n s t a l l e r . u s e r i d _ i n s t a l l . l o g , which is located in the . T I B C O directory of the user performing the installation: Errors in this file, or the existence of error files under this folder, indicates installation problems. Error files have the following format:
a n t T a s k _ E R R O R _ l o g _ p o s t - i n s t a l l _ mm-dd-yyy. n. l o g

If the log files dont indicate any errors, then open a simple example project in TIBCO BusinessEvents Studio, and also run the example at the command line. The example readme files explain how to run the examples at the command line, from the installed location. Check for errors on the command line or user interface. Absence of errors, and a normal engine start up indicate successful installation.

Verifying Add-On Product Installations

To verify that add-ons are installed, look for the list of add-ons in the folder TIBCO_HOME/ _ i n s t a l l I n f o . Every successfully installed add-on has a corresponding XML file under this folder. You can also check the install log file to confirm which add-ons are installed.

TIBCO BusinessEvents Installation

Uninstalling TIBCO BusinessEvents 23

Uninstalling TIBCO BusinessEvents

To uninstall TIBCO BusinessEvents do the following. This procedure uninstalls the entire TIBCO BusinessEvents installation, not just the service pack. It is not possible to uninstall only the service pack. 1. Do one of the following to start the uninstaller: Navigate to the TIBCO_HOME/ t o o l s / u n i v e r s a l _ i n s t a l l e r directory and run the T I B C O U n i v e r s a l I n s t a l l e r program. (Windows) From the Start menu, select Start > All Programs > TIBCO > TIBCO_HOME > Uninstall. (Windows) Use Add/Remove Programs from the Control Panel. 2. The Welcome screen appears. Click Next. 3. Do one of the following: To uninstall only a selection of products in this TIBCO home, click Custom Uninstall. Select the product or products you want to uninstall. Then click Next. See TIBCO BusinessEvents Standard Edition Components on page 5 for guidelines. To uninstall all TIBCO products in this TIBCO home (that were installed using the universal installer), click Typical Uninstall. Then click Next. 4. The Pre-Uninstall Summary screen appears. Click Uninstall. Uninstallation proceeds and then you see the Post-Uninstall Summary. 5. Click Finish to close the uninstaller window. 6. If you are prompted to do so, restart the computer. You may also want to manually delete any remaining files in the installation directory to completely remove the product. For information on the uninstallation log files, see Installation History Log Files on page 12.

TIBCO BusinessEvents Installation

24

| Chapter 2

TIBCO BusinessEvents Installation

TIBCO BusinessEvents Installation

| 25
Chapter 3

Post Installation Tasks

This chapter explains some post-installation steps you may have to perform in your installation. Also see Chapter 4, Migrating Projects from Earlier Versions, on page 33 for additional procedures you may have to do after installation.

Topics
Post Installation Tasks for All Platforms, page 26 Check and Update JVM Settings in Properties Files, page 27 All UNIX Installations Directory Permissions, page 29 Configuration for 64-bit Mode, page 30

TIBCO BusinessEvents Installation

26

| Chapter 3

Post Installation Tasks

Post Installation Tasks for All Platforms

This section explains changes that are required in the circumstances shown. Also see Check and Update JVM Settings in Properties Files on page 27 in case it pertains to your situation.

Migrating Projects
For all projects created using prior releases, you must perform migration steps. After you migrate, you must also rebuild the EAR files for the projects, as is always the case when you upgrade. See Chapter 4, Migrating Projects from Earlier Versions, on page 33 and carefully follow all instructions.

Re-Initialize Studio Plug-ins Registry after Add-on Software Installation

When you install add-on products after installing TIBCO BusinessEvents, you need to ensure that the correct plug-ins contributed by the add-ons are initialized. To do this, re-initialize the studio plug-ins registry before you start using TIBCO BusinessEvents Studio, as explained next. To Re-Initialize Studio Plug-ins 1. Open a command prompt 2. Change directory to BE_HOME/ s t u d i o / e c l i p s e . 3. Run the command
studio -clean -initialize

TIBCO BusinessEvents Installation

Check and Update JVM Settings in Properties Files 27

Check and Update JVM Settings in Properties Files

This task is required for full installations. It is not typically required for service pack installations. It is valid on all platforms. Check the engine properties file to ensure that all settings are appropriate for your platform. Set the Heap Size as Needed By default, the initial ( X m s ) and maximum ( X m x ) heap size are set to 1GB for both TIBCO BusinessEvents and TIBCO BusinessEvents Decision Manager. Change the settings as needed to meet your requirements. For TIBCO BusinessEvents, the settings are in the BE_HOME/ b i n / b e - e n g i n e . t r a file. For TIBCO BusinessEvents Decision Manager they are in the BE_HOME/ d e c i s i o n m a n a g e r / e c l i p s e / D e c i s i o n M a n a g e r . i n i file. For example, if you want to run both TIBCO BusinessEvents Decision Manager and TIBCO BusinessEvents on a machine with 1GB memory, you might reduce the initial heap size setting ( X m s ):
java.extended.properties=-server Xms512m -Xmx1024m

As another example, if you use a machine with more memory, and you work with very large tables in TIBCO BusinessEvents Decision Manager, you might increase the TIBCO BusinessEvents Decision Manager heap size accordingly. It can also be helpful to set the M a x P e r m S i z e as follows:
-XX:MaxPermSize=128m

Platform-Specific Settings Some of the JVM settings do not work for all platforms, and some platforms use additional, platform-specific parameters. For example: For 64 bit Sun JVM for Intel or AMD on Linux, use
JVM_LIB_PATH=%TIB_JAVA_HOME%/lib/amd64/server/libjvm.so

For 64 bit Sun JVM for Intel or AMD on Windows, use:

JVM_LIB_PATH=%TIB_JAVA_HOME%/lib/amd64/server/libjvm.dll

For AMD on Windows and 32 bit Sun JVM for Intel use:
JVM_LIB_PATH=%TIB_JAVA_HOME%/lib/i386/server/libjvm.dll

The IBM AIX platform uses parameters common to all JVMs, but does not use the - d 6 4 parameter. AIX also uses additional parameters (using the format, - X parameter).
TIBCO BusinessEvents Installation

28

| Chapter 3

Post Installation Tasks

Refer to the appropriate JVM reference manuals for the platform in question. For example, for AIX you could refer to the following resources. http://www.ibm.com/developerworks/java/jdk/aix/j564/sdkguide.aix64.html http://www.ibm.com/developerworks/java/jdk/aix/j532/sdkguide.aix32.html Note that on AIX, you can determine the mode in which JVM is running using the following simple Java program:
System.getProperty("com.ibm.vm.bitmode");

It returns the following values:

* 32 - the JVM is running in 32-bit mode * 64 - the JVM is running in 64-bit mode

TIBCO BusinessEvents Installation

All UNIX Installations Directory Permissions 29

All UNIX Installations Directory Permissions

This task is required for full installations. It is not typically required for service pack installations. This step is required on all UNIX platforms. If you use TIBCO BusinessEvents Decision Manager, refer to its installation guide for additional actions.

This section explains what directory permissions must be set to enable users to use the system.

Permissions for TIBCO BusinessEvents Directories

All TIBCO BusinessEvents users must have read, write, and execute permissions for the following directories:
bin Directory $TIBCO_HOME/be/5.0/bin

For example, if TIBCO BusinessEvents has been installed in / o p t / t i b c o , the user who installed TIBCO BusinessEvents should execute the following commands:
% chmod 777 /opt/tibco/be/5.0/bin/

(Other changes can be made using the c h o w n command as needed.) You can verify ownership and permissions using the long listing command, l s -l.

TIBCO BusinessEvents Installation

30

| Chapter 3

Post Installation Tasks

Configuration for 64-bit Mode

The following platforms allow you to run TIBCO BusinessEvents in 64-bit mode: AIX HP-UX Itanium HP PA-RISC Linux Solaris 10 SPARC Solaris 10 X86

See Supported UNIX Platforms and Guidelines on page 10 for versions supported. An additional step is required for the HP-UX platforms. See HP-UX on page 31).

To Configure for 64-bit Mode To configure TIBCO BusinessEvents for 64-bit mode you rename the provided 64 bit wrapper and configure the b e - e n g i n e . t r a and b e - r m s . t r a files. 1. Open the b e - e n g i n e . t r a file and the b e - r m s . t r a file for editing. In each file do the following: a. In the t i b c o . e n v . S T D _ E X T _ C P property, find % R V _ H O M E % / l i b and replace it with % R V _ H O M E % / l i b / t i b r v j . j a r. b. Ensure that the J V M _ L I B _ P A T H variable points to the appropriate JVM Server DLL or SO. For example: For 64 bit Sun JVM for AMD on Linux, use:
JVM_LIB_PATH = %TIB_JAVA_HOME%/lib/amd64/server/libjvm.so

For 64 bit Sun JVM for AMD on Windows, use:

JVM_LIB_PATH =%TIB_JAVA_HOME%/bin/amd64/server/libjvm.dll

2. In each file, you also may want to increase the heap size and memory usage of the Java VM by adding JVM arguments to the t i b c o . e n v . A P P _ A R G S property and by changing the t i b c o . e n v . H E A P _ S I Z E property. The following lines are example values for these properties:
tibco.env.APP_ARGS=-d64 -XX:MinHeapFreeRatio=52 -XX:MaxHeapFreeRatio=90 -XX:GCTimeRatio=19 tibco.env.HEAP_SIZE=2048M

TIBCO BusinessEvents Installation

Configuration for 64-bit Mode 31

3. Save the files. (Remember to update the b e - r m s . t r a , the b e - e n g i n e . t r a , and the files.)

HP-UX
If you are using an HP-UX platform, open the b e - e n g i n e . t r a file and remove the following entry from the property j a v a . e x t e n d e d . p r o p e r t i e s property:
-javaagent:%BE_HOME%/lib/cep-instrumentation.jar

(If this property is present, the executable fails to launch.) Enabling 64-bit Properties By default, the 32-bit j a v a . e x t e n d e d . p r o p e r t i e s are enabled.
java.extended.properties

Comment the 32-bit j a v a . e x t e n d e d . p r o p e r t i e s and enable the 64-bit in the TRA files in these folders:

BE_HOME/ b i n / b e - e n g i n e . t r a BE_HOME/ m m / b i n / b e - m m . t r a BE_HOME/ r m s / b i n / b e - r m s . t r a

TIBCO BusinessEvents Installation

32

| Chapter 3

Post Installation Tasks

TIBCO BusinessEvents Installation

| 33
Chapter 4

Migrating Projects from Earlier Versions

Also see Chapter 3, Post Installation Tasks, on page 25 for non-project related actions required for various situations. Read this chapter carefully and follow all migration steps that apply to your case.

Topics
Project Migration Overview, page 34 For Berkeley DB Object Management Users Only, page 35 Migration from 4.x to 5.0 Automatic Migration Changes, page 36 Migrating 4.x Projects, page 39 Migrating 3.x Projects, page 46 Understanding the CDD File (For 3.x Users), page 50 Importing a 3.x TIBCO Designer Project, page 52 Clean and Validate 3.x Projects, page 55 Oracle Types to JDBC Backing Store Migration, page 57

TIBCO BusinessEvents Installation

34

| Chapter 4

Migrating Projects from Earlier Versions

Project Migration Overview

Many of the actions you must take to migrate projects to the current release depend on the version you are migrating from, and the features you use. Some manual steps are required. More manual steps are required for earlier versions than for 4.x projects due to the changes in architecture. If you are upgrading from 4.0, first upgrade to 4.0.1 and then migrate to 5.0. See Migrating 4.x Projects on page 39, and referenced sections. If you are upgrading from 3.x, you can migrate directly to 5.0. See Migrating 3.x Projects on page 46, and referenced sections. If you are upgrading from a version earlier than 3.0, first upgrade to the latest 3.x version, following directions in the 3.x documentation.

Check Release Notes

Check the new features, changed functionality, and the deprecated features lists in Release Notes and take action accordingly.

TIBCO BusinessEvents Installation

For Berkeley DB Object Management Users Only 35

For Berkeley DB Object Management Users Only

Berkeley DB OM, formerly called Persistence OM, is an older form of data persistence and it is deprecated. If you still use it, it is strongly recommended that you migrate to Cache OM with backing store in this release. There is no direct migration path from the Berkeley DB OM database to a JDBC backing store. Migration is a two stage procedure: 1. As needed upgrade to the latest using the latest 3.x (or 4.x) version of TIBCO BusinessEvents. Those versions have a utility to migrate the data to the Oracle Types backing store schema. 2. Migrate from the Berkeley DB database to the legacy Oracle Types backing store. To complete this step, follow instructions in the TIBCO BusinessEvents Installation guide for the version you are using. 3. Migrate from the Oracle Types backing store to the JDBC backing store, following instructions in Oracle Types to JDBC Backing Store Migration on page 57. 4. Migrate the project to 5.0. If you are using the latest 4.x version, see Migrating 4.x Projects on page 39. If you are using the latest 3.x version, see Migrating 3.x Projects on page 46.

TIBCO BusinessEvents Installation

36

| Chapter 4

Migrating Projects from Earlier Versions

Migration from 4.x to 5.0 Automatic Migration Changes

The migration utility automatically does the following:
Migrates core Coherence functions to product neutral ones A set of core functions has been renamed (and additional internal changes have been made) so that these functions can be used with either the Coherence or the TIBCO BusinessEvents DataGrid cache provider. The renamed functions are in the Standard catalog C l u s t e r . D a t a G r i d category. See Table 4, Mapping of Coherence Functions to TIBCO BusinessEvents DataGrid Functions, on page 37 for details.

A TIBCO BusinessEvents Studio refactoring operation, and a TIBCO BusinessEvents Studio Tools command line option are available to do this for specific purposes other than general migration. See Migrating Core Coherence Functions for the TIBCO BusinessEvents Studio option and see Migrating Core Coherence Functions at the Command Line for the command-line option, both in TIBCO BusinessEvents Developers Guide.
Migrates the channel driver type Driver type is migrated from the 4.0 format to the

current format.
Migrates HTTP channel settings HTTP channel tuning settings are now maintained in the channel resource instead of the processing unit (PU) area of the CDD. During the migration process, you specify the CDD and within it the PU whose settings you want to migrate. Settings from the selected PU are applied to all HTTP channels. Migrates CDD file namespaces Namespace is changed to the following:
http://tibco.com/businessevents/configuration/5.0.

Migrates entity metadata properties to CDD domain object override settings In earlier versions, entity-specific configuration for cache and backing store was done using metadata properties (also known as extended properties). It is now done in the CDD only. The migration utility moves all relevant metadata property settings to the equivalent settings in the CDD Domain Objects Overrides area. An override is added for each entity type. You can later remove unnecessary entries as needed. (There is no change to configuration for metadata properties used by the TIBCO BusinessEvents Data Modeling add-on product.) Migrates localStorage Property to isSeeder property (partial migration) The property t a n g o s o l . c o h e r e n c e . d i s t r i b u t e d . l o c a l s t o r a g e is migrated to the cache-provider-neutral property b e . e n g i n e . c l u s t e r . i s S e e d e r. However, a change in design makes this property redundant. Cache storage is now set at the processing unit level, using a checkbox labeled Enable Cache Storage. It is not possible to set this checkbox at migration time. Note that without further action, if the i s S e e d e r property is set higher in the order of precedence than the processing unit, then the i s S e e d e r property is used at runtime. However, if the i s S e e d e r

TIBCO BusinessEvents Installation

Migration from 4.x to 5.0 Automatic Migration Changes 37

property is set lower in the order of precedence than the processing unit, then the checkbox value is used. To complete migration, remove the i s S e e d e r property and instead use the processing unit setting Enable Cache Storage in the project CDD file. Note that enabling cache storage on non-cache agents is not recommended for production. It can be useful for testing and demonstration purposes.
Site Topology, TIBCO BusinessEvents Version Field The value of the TIBCO BusinessEvents Version field in Cluster Settings and in Host Settings is updated to the current version. Adds CDD properties for TIBCO BusinessEvents Monitoring and Management authentication, which is a new feature in 5.0. The properties are added in these

locations:
BE_HOME/ m m / p r o j e c t / e m o n i t o r > M M . c d d > m m - c l a s s a g e n t class >

properties > m m / a u t h property group

ToBeMonitored_Project > project.cdd > Cluster properties > a u t h property group.

The properties are added to all project CDDs if a project has more than one. The following properties are added, with the default values as shown:
be.mm.auth.type=file b e . m m . a u t h . f i l e . l o c a t i o n = BE_HOME/ m m / c o n f i g / u s e r s . p w d j a v a . s e c u r i t y . a u t h . l o g i n . c o n f i g = BE_HOME/ m m / c o n f i g / j a a s - c o n f i g . c o n

Add-on Product Migration

Migrates TIBCO BusinessEvents Views default skin TIBCO BusinessEvents Views has a new look-and-feel. The default skin is migrated automatically. If you use this add-on product, you can view the default skin settings using the view-only System Elements resource. See TIBCO BusinessEvents Views Developers Guide for details about how you can use the System Elements when you define your own color schemes and skins. Migrates TIBCO BusinessEvents Decision Manager metadata location Metadata

information for decision tables was being stored in the (internal) . b e p r o j e c t file. Now it is stored in the decision table file itself. Table 4 Mapping of Coherence Functions to TIBCO BusinessEvents DataGrid Functions 4.x Coherence Category Function Name
C_CacheGetEntityById() C_CacheLoadConceptByExtId() C_CacheLoadConceptById() C_CacheLoadConceptIndexedByExtId() C_CacheLoadConceptsByExtId()

DataGrid Category Function Name

CacheGetEntityById() CacheLoadConceptByExtId() CacheLoadConceptById() CacheLoadConceptIndexedByExtId() CacheLoadConceptsByExtId()

TIBCO BusinessEvents Installation

38

| Chapter 4

Migrating Projects from Earlier Versions

Table 4 Mapping of Coherence Functions to TIBCO BusinessEvents DataGrid Functions (Contd) 4.x Coherence Category Function Name
C_CacheLoadEntity() C_CacheLoadEventByExtId() C_CacheLoadEventById() C_CacheLoadParent() C_CacheName() C_CacheReevaluate() C_ClassName() C_EnableCacheUpdate() C_Index() C_Lock() C_TransactionProperties C_UnLock()

DataGrid Category Function Name

CacheLoadEntity() CacheLoadEventByExtId() CacheLoadEventById() CacheLoadParent() CacheName() CacheReevaluate() ClassName() EnableCacheUpdate() Index() Lock() TransactionProperties() UnLock()

TIBCO BusinessEvents Installation

Migrating 4.x Projects 39

Migrating 4.x Projects

This section outlines how to migrate 4.x projects, after you install TIBCO BusinessEvents 5.0 (as explained in Chapter 1 through Chapter 3 of this guide). If you are using Berkeley DB Object Management, see For Berkeley DB Object Management Users Only on page 35 for preliminary steps to take in order to change to Cache OM. Task A Upgrade 4.0.0 Projects to 4.0.1 If you are running 4.0.0, first upgrade to 4.0.1. Open the 4.0.0 projects in TIBCO BusinessEvents Studio and save them. Task B Import Projects in TIBCO BusinessEvents Studio A command line utility to do the same actions is also provided. After importing using the command line utility an additional procedure is required before you can work with the project in TIBCO BusinessEvents Studio. See Importing a TIBCO BusinessEvents 4.x Project at the Command Line on page 42. For details about what is migrated, see Migration from 4.x to 5.0 Automatic Migration Changes on page 36. 1. After installing TIBCO BusinessEvents 5.0, start TIBCO BusinessEvents Studio using a different workspace from the workspace containing the 4.x projects. 2. Select File > Import > Existing TIBCO BusinessEvents Studio 4.0 Project and click Next. 3. Browse to and select the project root directory of the 4.x project you are migrating. 4. Do one of the following: Check the Copy project into workspace checkbox. This option copies the project into your current workspace. Uncheck the Copy project into workspace checkbox and specify an import location. 5. Do one of the following: If your project has no HTTP channels, click Finish (this is the only option). If your project has one or more HTTP channels, click Next.

TIBCO BusinessEvents Installation

40

| Chapter 4

Migrating Projects from Earlier Versions

6. If you clicked Next you see the Select Processing Unit dialog. Select the project CDD, and within it, the processing unit that contains the HTTP properties to be migrated. All CDD files in the project are touched by the migration (see Migration from 4.x to 5.0 Automatic Migration Changes on page 36 for details). However, only the CDD file specified here is used for HTTP channel property migration. An informational panel displays the settings that will be migrated.

Task C TIBCO BusinessEvents Views CDD Change If you use the TIBCO BusinessEvents Views add-on product, you may need to update the CDD for changes to the following dashboard agent properties: 4.x Property
be.http.docRoot

5.0 Property
be.agent.dashboard.http.docroot

The default is BE_HOME/ v i e w s / w e b - r o o t

TIBCO BusinessEvents Installation

Migrating 4.x Projects 41

4.x Property
be.http.docPage

5.0 Property
be.agent.dashboard.http.docpage

The default value is i n d e x . h t m l Because the replacement properties now have default values, you only have to add the properties if you need to set a non-default value. Do the following depending on your use case: If you have not changed the provided 4.x property values, and dont need to use a non-default value in 5.0, remove the 4.x properties from the CDD. If you changed the value for one or both of the above properties, rename the property or properties to the 5.0 name (as shown above). Do this in the dashboard agent properties area of the CDD, for all affected dashboard agents (or at a higher level as appropriate to the scope you want to use).

Task D Choose a Cache Provider and Configure Settings (Cache OM only) Beginning with TIBCO BusinessEvents 5.0.0, Oracle Coherence is no longer provided with TIBCO BusinessEvents. An internal component, TIBCO BusinessEvents DataGrid, is used by default. If you use cache OM, action is required: If you want to switch from Oracle Coherence to TIBCO BusinessEvents DataGrid, you must manually reconfigure the CDD file settings. See Configuring a TIBCO BusinessEvents DataGrid Cluster in TIBCO BusinessEvents Administration for details. If you want to continue using Oracle Coherence as the cache provider, you must acquire a licensed copy of Oracle Coherence software and do some configuration. See the Enabling Use of Oracle Coherence as the Cache Provider and Configuring Oracle Coherence Cluster Discovery sections in TIBCO BusinessEvents Administration for details. The property t a n g o s o l . c o h e r e n c e . d i s t r i b u t e d . l o c a l s t o r a g e is migrated automatically to the cache-provider-neutral property b e . e n g i n e . c l u s t e r . i s S e e d e r. However, a change in design makes this property redundant. Cache storage is now set at the processing unit level, using a checkbox labeled Enable Cache Storage. It is not possible to set this checkbox at migration time. To complete migration, remove the i s S e e d e r property and instead configure cache storage for non-cache agents as needed use the processing unit setting Enable Cache Storage in the project CDD file. Note that enabling cache storage on non-cache agents is not recommended for production. It can be useful for testing and demonstration purposes.

TIBCO BusinessEvents Installation

42

| Chapter 4

Migrating Projects from Earlier Versions

Task E Migrate Legacy Oracle-only Backing Stores to JDBC Backing Store The legacy Oracle-only (Oracle Types) backing store is no longer supported. If you were using the legacy Oracle-only (Oracle Types) backing store, you must migrate to the current implementation. See Oracle Types to JDBC Backing Store Migration, page 57. Task F (All Cases) Validate the Project in TIBCO BusinessEvents Studio It is recommended that you validate the project in TIBCO BusinessEvents Studio after migration, to help ensure that the project is correctly configured. Certain validation checks were added after 4.0. So validating the project may reveal issues that were not caught in the earlier release from which you migrated. Task G Rebuild EAR Files As with any upgrade, you must rebuild all EAR files created with an earlier version.

Importing a TIBCO BusinessEvents 4.x Project at the Command Line

This option is equivalent to the following menu option in TIBCO BusinessEvents Studio: File > Import > TIBCO BusinessEvents > Existing TIBCO BusinessEvents 4.0 Project, explained in Task B, Import Projects in TIBCO BusinessEvents Studio, on page 39. After you complete the procedures in this section, complete the migration tasks as shown following Task B, as needed for your project. When you use this command-line (or TIBCO BusinessEvents Studio) option to import 4.x TIBCO BusinessEvents Studio projects, the same migration actions are done as in the UI-based migration. See Migration from 4.x to 5.0 Automatic Migration Changes on page 36. Before you can use a 4.x project imported at the command-line in TIBCO BusinessEvents Studio you must do another procedure, explained in To Open a Project Imported at the Command Line in TIBCO BusinessEvents Studio on page 44. To Import an Existing 4.x Project at the Command Line 1. Navigate to BE_HOME/ s t u d i o / b i n / and open a command prompt.

TIBCO BusinessEvents Installation

Migrating 4.x Projects 43

2. Execute a command with the following format (all on one line) at a command prompt:
studio-tools -op importExistingProject [-h] -p CDDprojectPath] [ - u PUNameFromCDD]

studioProjDir [ - o targetProjDir] [ - c

For example:
studio-tools -op importExistingProject -p C:\FT\SomeProj -o c:\MyWorkspace\SomeProj -c COM.cdd -u Invproc

If HTTP channel properties are migrated (from a specified CDD and processing unit to all HTTP channel resources Advanced tab) you see a message like this:
M i g r a t i n g H T T P p r o p e r t i e s o f P r o c e s s i n g U n i t " PUName" f r o m C D D " CDDprojectPath" t o HTTPChannel(s) present in the project

When the import has completed successfully, you see a message in the command window like the following:
The existing 4.0 TIBCO BusinessEvents project has been successfully imported to c:\MyWorkspace\SomeProj.

Table 5, TIBCO BusinessEvents Studio Tools Options for Importing an Existing Project, provides detailed information about the options. Table 5 TIBCO BusinessEvents Studio Tools Options for Importing an Existing Project Option
-op importExistingProject -h -p

Description Specifies the i m p o r t E x i s t i n g P r o j e c t operation for importing a TIBCO BusinessEvents Studio project into the workspace. Optional. Displays help. Source project: absolute path to the project directory of the TIBCO BusinessEvents Studio project to be imported.

TIBCO BusinessEvents Installation

44

| Chapter 4

Migrating Projects from Earlier Versions

Table 5 TIBCO BusinessEvents Studio Tools Options for Importing an Existing Project (Contd) Option
-o

Description Optional. Absolute path to the target project directory, where the project is imported to. If you specify the source project directory name as the last element in the path, it is used as the target project directory. If you specify a different directory as the last element in the path, the directory is created if it does not exist, and the source project directory is imported within the specified target directory. If you do not specify a target project directory, the original project contents are updated. If the project to be imported is a TIBCO BusinessEvents version 4 project, it is no longer compatible with version 4 after the import. If the target location points to an existing project, the import does not proceed and this message displays:
The specified target location already exists and cannot be used.

-c

Optional. The CDD to use for migration actions. Project path of the CDD (path relative to the root directory of the source project). Optional but if specified - c must also be specified. Specifies the name of the PU (within the specified CDD) that contains settings to be migrated. HTTP channel settings from this PU are migrated to all HTTP channel resources in the project.

-u

To Open a Project Imported at the Command Line in TIBCO BusinessEvents Studio To open a project imported at the command line, you must add it as a new project. 1. Start TIBCO BusinessEvents Studio. In Windows, click Start > All Programs > TIBCO > YourEnvironment > TIBCO BusinessEvents 5.0 > TIBCO BusinessEvents Studio. 2. From the File menu select New > Project. You see the New Project Select a Wizard dialog. 3. Select TIBCO BusinessEvents > Studio Project and click Next. 4. In the Project Name field, enter the directory name where the imported project is located. (This is used as the project name.)

TIBCO BusinessEvents Installation

Migrating 4.x Projects 45

5. (If you imported the project to a directory in your default workspace, skip this step.) If the project directory is located outside the default workspace, uncheck the Use default location checkbox and browse to the parent directory of the project imported at the command line. 6. Click Finish. The project folders appear in the Studio Explorer view.

TIBCO BusinessEvents Installation

46

| Chapter 4

Migrating Projects from Earlier Versions

Migrating 3.x Projects

This section outlines how to migrate 3.x projects, after you install TIBCO BusinessEvents 5.0 (as explained in Chapter 1 through Chapter 3 of this guide). If you are migrating 3.0.0 projects that use the Oracle Types backing store, you must first upgrade your 3.0.0 installation to the latest 3.x version and update the Oracle Types backing store schema. After the schema update you can then migrate the data to the JDBC backing store, which you configure in the 5.0 version project. If you are using Berkeley DB Object Management, see For Berkeley DB Object Management Users Only on page 35 for preliminary steps to take in order to change to Cache OM.

Task A Import, Clean, and Validate the 3.x Project 1. Import the TIBCO Designer (3.x) project into TIBCO BusinessEvents Studio. See Importing a 3.x TIBCO Designer Project on page 52. If you will migrate from the Oracle Types backing store or from a Berkeley DB OM to the Cache OM with JDBC backing store, keep the 3.x project 2. In TIBCO BusinessEvents Studio select Project > Validate to validate the project and then review the issues in the Problems tab and in the Error Log tab and resolve any errors. See Clean and Validate 3.x Projects on page 55. Task B Configure Runtime Properties in the CDD File Most of the configuration that was done in TRA files is now done in the CDD file. Ensure that all valid 3.x runtime settings (except JVM and system level properties) are configured in the CDD. Some properties are not relevant in the current version, and additional properties not used in 3.x have been added to the product. You may have to add some properties manually to CDD property sheets. Here are some tips: Add runtime engine properties to the CDD file at the appropriate level for the scope of the property: Cluster level for cluster-wide scope. Processing Unit level for engine-wide scope in the specified type of engine (Processing Unit). You will have to think about your engines differently, as running different kinds of agent classes. Agent level to limit the scope to the agent class.
TIBCO BusinessEvents Installation

Migrating 3.x Projects 47

TIBCO BusinessEvents properties that were configured in the TIBCO Designer TRA file generally go in the TIBCO BusinessEvents Studio TRA file:
BE_HOME/ s t u d i o / e c l i p s e / c o n f i g u r a t i o n / s t u d i o . t r a

Remove the runtime properties that are now configured elsewhere from the TRA file and ensure that only JVM or system level properties remain. Leaving these properties in the TRA can cause problems at runtime.

See Understanding the CDD File (For 3.x Users) on page 50 for background information that helps you work with the CDD file. Task C Check that be-engine.xml Settings are in the CDD File You can change CDD file values at deploy-time without having to rebuild the EAR file. Therefore there is no need for the b e - e n g i n e . x m l file. (It was used to add properties to the TIBCO Administrator UI in order to make changes at deploy time.) Check that all the properties from your 3.x b e - e n g i n e . x m l that are valid in 5.0 are present in the CDD file. Task D Add Project Libraries (If Used) Version 3.x project libraries containing entities (concepts, events and so on) are not compatible with project libraries in release 4.0.0 and higher, because the format for entities changed in the 4.0.0 release. They are not migrated. (3.x project libraries that contain only shared resources will work in version 4.0.0 and up, but that is not a common use for project libraries. The format of shared resources remains the same in 5.0). If you want to continue to use the 3.x project libraries, recreate the libraries and add them to the 5.0 project build path after migration. Follow instructions in the section Working with Project Libraries, in Chapter 2, Project Tasks of TIBCO BusinessEvents Developers Guide. Task E Reconfigure TIBCO BusinessEvents-ActiveMatrix BusinessWorks Integration Projects (If Used) Configuration of TIBCO BusinessEvents-ActiveMatrix BusinessWorks integration projects has changed. If a 3.x project contains TIBCO ActiveMatrix BusinessWorks or TIBCO Adapter resources, plan to use two projects: a TIBCO Designer project for the TIBCO Designer resources, and a TIBCO BusinessEvents Studio project. See Chapter 21, ActiveMatrix BusinessWorks Integration in TIBCO BusinessEvents Developers Guide for details.

TIBCO BusinessEvents Installation

48

| Chapter 4

Migrating Projects from Earlier Versions

Task F Migrate 3.x Decision Manager Projects (If Used) If you want to continue to use decision tables, you must purchase the TIBCO BusinessEvents Decision Manager add-on product. You import the 3.x decision project (containing the decision tables) after you import the related 3.x TIBCO Designer project (see TIBCO BusinessEvents Decision Manager Users Guide). Task G Choose a Cache Provider and Configure Settings (Cache OM only) Beginning with TIBCO BusinessEvents 5.0.0, Oracle Coherence is no longer provided with TIBCO BusinessEvents. An internal component, TIBCO BusinessEvents DataGrid, is used by default. If you use cache OM, action is required: If you want to switch from Oracle Coherence to TIBCO BusinessEvents DataGrid, you must manually reconfigure the CDD file settings. See Configuring a TIBCO BusinessEvents DataGrid Cluster in TIBCO BusinessEvents Administration for details. If you want to continue using Oracle Coherence as the cache provider, you must acquire a licensed copy of Oracle Coherence software and do some configuration. See the Enabling Use of Oracle Coherence as the Cache Provider and Configuring Oracle Coherence Cluster Discovery sections in TIBCO BusinessEvents Administration for details. The property t a n g o s o l . c o h e r e n c e . d i s t r i b u t e d . l o c a l s t o r a g e is migrated automatically to the cache-provider-neutral property b e . e n g i n e . c l u s t e r . i s S e e d e r. However, a change in design makes this property redundant. Cache storage is now set at the processing unit level, using a checkbox labeled Enable Cache Storage. It is not possible to set this checkbox at migration time. To complete migration, remove the i s S e e d e r property and instead configure cache storage for non-cache agents as needed use the processing unit setting Enable Cache Storage in the project CDD file. Note that enabling cache storage on non-cache agents is not recommended for production. It can be useful for testing and demonstration purposes.

Task H Migrate Legacy Oracle-only Backing Stores to JDBC Backing Store The legacy Oracle-only (Oracle Types) backing store is no longer supported. If you were using the legacy Oracle-only (Oracle Types) backing store, you must migrate to the current implementation. See Oracle Types to JDBC Backing Store Migration, page 57.

TIBCO BusinessEvents Installation

Migrating 3.x Projects 49

Task I

(All Cases) Validate the Project in TIBCO BusinessEvents Studio

It is recommended that you validate the project in TIBCO BusinessEvents Studio after migration, to help ensure that the project is correctly configured. Certain validation checks were added after 4.0. So validating the project may reveal issues that were not caught in the earlier release from which you migrated. Task J Rebuild EAR Files As with any upgrade, you must rebuild all EAR files created with an earlier version.

TIBCO BusinessEvents Installation

50

| Chapter 4

Migrating Projects from Earlier Versions

Understanding the CDD File (For 3.x Users)

Beginning with the 4.0.0 release, most runtime properties and other deploy-time settings are configured using a structured XML file called the Cluster Deployment Descriptor (CDD). A big advantage of this change is that you can change CDD file values at deploy-time without having to rebuild the EAR file (the CDD file used is stored outside the EAR file). A multi-tab editor in TIBCO BusinessEvents Studio enables easy maintenance of this file. This section explains the role of the CDD file for the benefit of those migrating projects from 3.x.
The EAR file now includes all resources In the current architecture, you dont

select what resources to include in the EAR file. The EAR includes all project resources and can be very large. During runtime however, the resources are enabled (filtered) through the CDD Agent Classes and Collections tabs. Read this section before beginning your migration. Also read related topics in TIBCO BusinessEvents Architects Guide and TIBCO BusinessEvents Getting Started. See Property Migration Reference on page 62 for a list of 3.x runtime properties and their equivalent CDD settings or properties in the current version. Documentation about the CDD settings and properties is provided in the TIBCO BusinessEvents Administration guide.

Most Runtime Properties are Configured in the CDD File

3.x Configuration

In 3.x (and earlier), runtime properties were set using individual properties set in one or more TRA files. In some cases, runtime properties were set in TIBCO Designer, specifically in the BAR resource, and some were set in the TIBCO Designer TRA file. Now only JVM-level properties (those that need to be used before the engine starts up) are set in the b e - e n g i n e . t r a file. Properties that were set in the TIBCO Designer TRA file (d e s i g n e r . t r a ) are now generally set in the s t u d i o . t r a file:
BE_HOME/ s t u d i o / e c l i p s e / c o n f i g u r a t i o n / s t u d i o . t r a

5.0 Configuration

Other runtime properties are configured in the CDD file. The CDD file provides fields for all commonly used settings, and it has property sheets where you can add other properties as needed. The property sheets are available at various levels, cluster, processing unit, and agent, so that you can scope the effect of the property appropriately and provide overrides at lower levels.

TIBCO BusinessEvents Installation

Understanding the CDD File (For 3.x Users) 51

Processing Units (Engines) and Agent Classes are Configured in the CDD File
In the CDD, you configure processing units (equivalent to an engine at runtime). A processing unit references the agent or agents you want to include in the processing unit (engine) at runtime. At deploy time you specify which processing units to deploy. In 3.x agents were configured using individual properties in the TRA files. Each TRA file provided the configuration for one engine. Beginning with the 4.0.0 release, you configure all the processing units you need to deploy in a single CDD file. When you deploy an engine, you specify the processing unit to use. The processing unit configuration in the CDD determines which project resources and settings are used at runtime. Some agents and processing units are created for you when you import a 3.x project into Studio based on 3.x information available. After you import the project into TIBCO BusinessEvents Studio, edit the CDD file to fully configure the agents and processing units as needed.

Metadata Properties (Extended Properties) are Configured in the CDD File

The entity metadata properties (also known as extended properties) for cache and backing store are now configured in the CDD. Preloading configuration has also been simplified. This is explained in the migration sections.

TIBCO BusinessEvents Installation

52

| Chapter 4

Migrating Projects from Earlier Versions

Importing a 3.x TIBCO Designer Project

You can directly import 3.x projects using the TIBCO BusinessEvents Studio user interface and save it as a current version project. You can also import a 3.x project at the command line. Import from versions earlier than 3.x is not supported. After you import the project, see Clean and Validate 3.x Projects on page 55 for the next step.

Importing a 3.x Project into TIBCO BusinessEvents Studio

To import 3.x projects into TIBCO BusinessEvents Studio, follow the procedure below. To Import a 3.x Project in TIBCO BusinessEvents Studio 1. Start TIBCO BusinessEvents Studio. In Windows, click Start > All Programs > TIBCO > YourEnvironment > TIBCO BusinessEvents 5.0 > TIBCO BusinessEvents Studio. 2. From the File menu, select Import. You see the Import wizard Select dialog. 3. Select TIBCO BusinessEvents > TIBCO Designer and click Next. You see the TIBCO Designer Project Import Wizard.

4. In the Archive Location field, browse to the location of the TIBCO Designer project and select its EAR file or its v c r e p o . d a t file. 5. In the Project Name field, enter a name for the TIBCO BusinessEvents Studio project. The default value is the original project name.

TIBCO BusinessEvents Installation

Importing a 3.x TIBCO Designer Project 53

6. Specify a project location, or use the default workspace. 7. Click Finish. The progress bar displays while the import is done. The status bar at the bottom of the window also displays progress. When the import is complete, you see the project folders in the Studio Explorer view.

Importing a TIBCO BusinessEvents 3.x Project at the Command Line

This utility imports a TIBCO BusinessEvents 3.x (TIBCO Designer) project at the command line. Projects imported using this command-line utility do not run in the context of Eclipse (TIBCO BusinessEvents Studio). An additional step is required if you want to open the project in TIBCO BusinessEvents Studio, as explained below. To Import a 3.x Project at the Command Line 1. Navigate to BE_HOME/ s t u d i o / b i n / and open a command prompt. 2. Execute a command with the following format (all on one line) at a command prompt:
studio-tools -op importDesigner -d

designerProjDir [ - n studioProjName] - p studioProjDir

For example:
studio-tools -op importDesigner -d C:\FT\FT_Project -n FTImport -p c:\myWorkspace\FTImported

When the import has completed successfully, you see a message in the command window:
Imported the Designer Project successfully.

Table 6, TIBCO BusinessEvents Studio Tools Options for Importing 3.x TIBCO Designer Projects, provides detailed information about the options. See To Open a Project Imported at the Command Line in TIBCO BusinessEvents Studio, page 54 for a procedure you must do if you want to open the project in TIBCO BusinessEvents Studio. Table 6 TIBCO BusinessEvents Studio Tools Options for Importing 3.x TIBCO Designer Projects Option
-op importDesigner

Description Specifies the i m p o r t D e s i g n e r operation for importing a TIBCO BusinessEvents 3.x (TIBCO Designer) project.

TIBCO BusinessEvents Installation

54

| Chapter 4

Migrating Projects from Earlier Versions

Table 6 TIBCO BusinessEvents Studio Tools Options for Importing 3.x TIBCO Designer Projects (Contd) Option
-d

Description Absolute path to the TIBCO Designer project directory (the . d a t file can be included but is not required). Import of release 3.x projects is supported. Optional. Specifies the name of the TIBCO BusinessEvents 4.x project (TIBCO BusinessEvents Studio project). If not specified, the TIBCO BusinessEvents Studio 3.x project name is used. Absolute path to the TIBCO BusinessEvents 4.x project directory (the TIBCO BusinessEvents Studio project). The directories in the path are created if they do not exist.

-n

-p

To Open a Project Imported at the Command Line in TIBCO BusinessEvents Studio To open a project imported at the command line, you must add it as a new project. 1. Start TIBCO BusinessEvents Studio. In Windows, click Start > All Programs > TIBCO > YourEnvironment > TIBCO BusinessEvents 5.0 > TIBCO BusinessEvents Studio. 2. From the File menu select New > Project. You see the New Project Select a Wizard dialog. 3. Select TIBCO BusinessEvents > Studio Project and click Next. 4. In the Project Name field, enter the directory name where the imported project is located. (This is used as the project name.) 5. (If you imported the project to a directory in your default workspace, skip this step.) If the project directory is located outside the default workspace, uncheck the Use default location checkbox and browse to the directory of the project imported at the command line. 6. Click Finish. The project folders appear in the Studio Explorer view.

TIBCO BusinessEvents Installation

Clean and Validate 3.x Projects 55

Clean and Validate 3.x Projects

This section explains how to clean and validate a 3.x project, and how to fix errors.

Clean and Validate the Project

Executing Project > Clean also performs validation, if you check Project > Build Automatically. In this case you dont have to do step 2. After you import the 3.x project into TIBCO BusinessEvents Studio Explorer, do the following: 1. Highlight the project name in TIBCO BusinessEvents Studio and select Project > Clean. At the Clean dialog, click Clean projects selected below, and then select the imported project. Click OK. All build problems and build states are discarded. The project is rebuilt from scratch. 2. Highlight the project name in Studio Explorer and select Project > Validate to validate the project. You may see some common validation errors that are addressed in the following sections. If you see additional errors that you cant resolve, contact your TIBCO representative for assistance.

Fixing Ambiguous Reference Errors (Unqualified References)

During migration, duplicate name references can cause issues. If the project contains unqualified references to rules, rule functions, or ontology types, and any of the rules, rule functions, or ontology types have the same simple name, duplicate name validation errors will result. In the TIBCO BusinessEvents Studio Problems tab, you may see listings for these issues, such as the following:
Ambiguous reference. Reference must be qualified, as multiple elements exist with the same name [/sharedResources/Element, Rules/Element, Concepts/Element]

One source of this issue is that beginning with the 4.0.0 release, rules are separate resources, whereas in the 3.x product, they exist within ruleset resources.
To Resolve the Issue Qualify all such ambiguous references.

TIBCO BusinessEvents Installation

56

| Chapter 4

Migrating Projects from Earlier Versions

Fixing XSLT Mapper Errors

If you have used the XPath (XSLT) mapper in TIBCO Designer, there could be errors that prevent a clean validation of the project after it is imported. In 3.x, XSLT Mapper errors were not reported during project validation. This validation has been added, beginning with the 4.0.0 release. Therefore, any mapper errors must be fixed before project validation can be successful. These errors existed in the 3.x product, though they may not have caused any runtime problems.
To Resolve the Issue In TIBCO BusinessEvents Studio double-click those items in the Problems view. The rule editor displays the corresponding rule or rule function. In the editor. Check for red error indicators on lines containing function mapping. Where you see an error indicator on a line containing Mapper code, Ctrl-click the underlined argument text to open the Function Argument Mapper dialog. Click the Mapper Check and Repair (check-mark icon) button.

Some errors can be auto-fixed: Click the validate option (the check mark) in the mapper. You see the Mapper Check and Repair dialog. Select the items you want to fix and click OK. (Using auto-fix is harmless even if the errors cant be auto-fixed.) Then manually fix any errors that cant be autofixed. For example, errors such as undefined variable errors cant be fixed automatically.

Fixing Errors Due to Use of Words in Reserved Word List

As TIBCO BusinessEvents develops, the number of reserved words increases. For the current list of reserved words, check the section Keywords and Other Reserved Words in Chapter 17, Rule Language Grammar, of TIBCO BusinessEvents Developers Guide. Validation shows errors for use of keywords as identifiers:
Reserved keyword, cannot be used as an identifier

To Resolve the Issue If you use any of the listed words as identifiers, resource

names, or folder names, change them in your 5.0 project.

TIBCO BusinessEvents Installation

Oracle Types to JDBC Backing Store Migration 57

Oracle Types to JDBC Backing Store Migration

The Oracle-only (Oracle Types) backing store is not supported in 5.0.0 If you were using this backing store implementation in your prior version of TIBCO BusinessEvents, implement a JDBC backing store and migrate your data to it as explained in this section.

If you were using the JDBC backing store in any release, no migration is required. Migration steps depend on whether you are migrating from 3.0.0, or from a later 3.x release, or from a 4.x release, as indicated in the tasks below. During migration, you must keep the JDBC Connection resource for the existing Oracle-only backing store, and you must be able to connect to it. The data migration process uses two backing stores, the legacy backing store and the new JDBC backing store. However after migration, you'll have one backing store. Use of two backing stores is limited to migration procedures. If you plan to make any schema changes, make them after the backing store data is migrated successfully, following directions in TIBCO BusinessEvents Administration. Task A All Versions Back up your backing store data. Task B 3.0.0 Only: Upgrade to 3.x and Update the Legacy Backing Store Schema New TIBCO BusinessEvents metadata tables were added to the backing store schema in version 3.0.1. If you are upgrading from version 3.0.0, you first must upgrade to the latest 3.x version before you migrate data to a JDBC backing store. 1. Upgrade from 3.0.0 to the latest 3.x version. 2. If the deployed application is running, gracefully shut down all agents and cache servers before you proceed. 3. Login to the Oracle server as b e _ u s e r, password b e _ u s e r (or whatever username and password you are using, as set in the i n i t i a l i z e _ d a t a b a s e . s q l script). 4. Navigate to the location of the scripts (by default in BE_HOME/ b i n ) and open an SQLPlus prompt. Identify yourself as the user you logged in as. 5. At the SQL prompt, type the following to run the script:
TIBCO BusinessEvents Installation

58

| Chapter 4

Migrating Projects from Earlier Versions

@create_tables.sql

Running this script does not affect any existing tables (therefore there is no need to run b e - o r a d e p l o y . e x e ). Your database tables are now configured. Task C 3.x Only: Import Projects into TIBCO BusinessEvents Studio Import the project into TIBCO BusinessEvents Studio and ensure that the migrated project is configured correctly. See Migrating 3.x Projects on page 46 for full details. Task D Add a JDBC Backing Store In this task, you set up a new backing store, including creation of a new JDBC Connection resource. Do not remove the JDBC Connection resource for the Oracle-only backing store database from your project until you have completed all migration tasks. 1. Add the JDBC backing store, following instructions in Chapter 15, JDBC Backing Store Setup, which is in TIBCO BusinessEvents Administration. 2. It's a good idea to open your project again in TIBCO BusinessEvents Studioand test both the JDBC connections. If you need to make corrections to the connections, do so before you build the EAR. 3. When you have set up the new backing store, including the JDBC connection and CDD settings, Rebuild the EAR file. Task E Set Up the TIBCO BusinessEvents TRA File Open the BE_HOME/ b i n / b e - m i g r a t i o n . t r a file and specify appropriate values for the properties shown below, with example values. For notes on the properties see Backing Store Data Migration Property Reference on page 59.
# Oracle/JDBC Migration Properties be.migration.batchsize 1000 be.migration.workersize 16 be.migration.objecttable true be.migration.target.type jdbc # Database URLs # Source database: be.oracle.dburi.count 1 be.oracle.dburi.0 /Resources/myORCL.sharedjdbc be.oracle.dburi.pool.initial.0 5 be.oracle.dburi.pool.min.0 5 be.oracle.dburi.pool.max.0 10

TIBCO BusinessEvents Installation

Oracle Types to JDBC Backing Store Migration 59

# Target database: be.jdbc.dburi.count 1 be.jdbc.dburi.0 /Resources/myJDBC.sharedjdbc be.jdbc.dburi.pool.initial.0 5 be.jdbc.dburi.pool.min.0 5 be.jdbc.dburi.pool.max.0 10

Task F Run the Data Migration Process 1. Open a command prompt, navigate to BE_HOME/ b i n , and execute the following command:
be-migration -copy -ear

EARFile

Wait until the process is complete 2. If you set the property b e . m i g r a t i o n . o b j e c t t a b l e = f a l s e in Task E then you must manually migrate O B J E C T T A B L E table contents. (Use your DBMS product documentation for this task.) 3. You can now start the TIBCO BusinessEvents engine and use the JDBC backing store with the migrated data. Task G Remove Legacy Backing Store and JDBC Connection When you have tested the migration and are sure that all is working well, you can remove the legacy backing store JDBC connection and archive, or otherwise remove, the legacy backing store files.

Backing Store Data Migration Property Reference

Table 7 Oracle-Only to JDBC Backing Store Data Migration Property Notes

be.migration.batchsize

Defines the database batch size to be used during the migration process. The best size depends on the database configuration. Default is: 200

TIBCO BusinessEvents Installation

60

| Chapter 4

Migrating Projects from Earlier Versions

Table 7 Oracle-Only to JDBC Backing Store Data Migration Property Notes

be.migration.workersize

Defines how many concurrent threads to use during the migration process. Set to the number of processors available. Default is: 10
be.migration.objecttable

If the existing Oracle backing store contains a large amount of data, the migration process can take many hours to complete. If this is the case, you can shorten the process using this property. When this property is set to false, the migration process ignores the data contained in O B J E C T T A B L E table. Skipping this table can shorten the migration time considerably. If you skip migration of the O B J E C T T A B L E table, you must then copy this table from the Oracle to the JDBC backing store database using other tools (or simple SQL scripts). Default is true.
be.migration.target.type

Defines which type of schema to use for the new backing store. Values are:
jdbc: The JDBC backing store schema. Use this value for migrating from an Oracle

backing store to a JDBC backing store (the procedure documented in this section).
oracle: No longer valid as an option.

Default is jdbc.

TIBCO BusinessEvents Installation

| 61
Chapter 5

Property Migration Reference

This chapter contains a reference table to assist you in locating the 4.x properties or UI settings that correspond to 3.x properties. Note that many logging properties have been replaced and are not directly migrated.

Topics
Property Migration Reference, page 62

TIBCO BusinessEvents Installation

62

| Chapter 5

Property Migration Reference

Property Migration Reference

The main properties used in prior releases are listed on the left, with their current version equivalents on the right. Note that it may be possible for properties listed as going in Cluster tab > Properties to be added to a lower-level property sheet, generally the processing unit property sheet, as appropriate. See TIBCO BusinessEvents Administration for more details on configuring the Cluster Definition Descriptor (CDD) file.
Deprecated and Unused Properties Properties that are deprecated in this release or are not used in this release are noted below. A list of unused properties from older supported versions of TIBCO BusinessEvents is provided in Appendix A, Deprecated and Unused Properties, on page 75.

Table 8 Property Migration Reference (Sheet 1 of 13) 3.x (or 4.x) Property Agent Group Name (in BAR resource) 5.0 CDD Editor Agent Classes tab > AgentClassName > Agent Class Name Agent Classes tab > AgentClassName > Properties Agent Classes Tab > AgentClassName > Check for Duplicates Agent Classes tab > AgentClassName > Concurrent RTC Agent Classes Tab > AgentClassName > Properties Agent Classes Tab > AgentClassName > Properties Agent Classes Tab > AgentClassName > Properties Processing Units tab > PUName > Agents > Key Agent Classes tab > AgentClassName > Max Active

A g e n t . AgentGroupName. c a c h e O p s Q u e u e S i z e

A g e n t . AgentGroupName. c h e c k D u p l i c a t e s

A g e n t . AgentGroupName. c o n c u r r e n t w m

A g e n t . AgentGroupName. d b O p s B a t c h S i z e

A g e n t . AgentGroupName. d b O p s Q u e u e S i z e

A g e n t . AgentGroupName. d b t h r e a d c o u n t

A g e n t . AgentGroupName. k e y

A g e n t . AgentGroupName. m a x A c t i v e

TIBCO BusinessEvents Installation

Property Migration Reference 63

Table 8 Property Migration Reference (Sheet 2 of 13) 3.x (or 4.x) Property
A g e n t . AgentGroupName. p r i o r i t y

5.0 CDD Editor Processing Units tab > PUName > Agents table > Priority Agent Classes Tab > AgentClassName > Properties Agent Classes Tab > AgentClassName > Properties Agent Classes tab > AgentClassName > Max Size Cluster tab > [OM Type - Cache] > Backing Store > Connection > URI Agent Classes tab > Cache Agent > Properties Agent Classes tab > Cache Agent > Properties Agent Classes tab > AgentClassName > Eviction Time Agent Classes Tab >
QueryAgentClassName Properties

A g e n t . AgentGroupName. r e c o v e r y P a g e S i z e

A g e n t . AgentGroupName. t h r e a d c o u n t

A g e n t . AgentGroupName. l 1 C a c h e S i z e be.agent.query.localcache.maxelements be.oracle.dburi.0 be.jdbc.dburi.0

(No longer used)

be.agent.cache.specialom

be.agent.cache.specialom.maxthreads

be.agent.query.localcache.evictseconds

be.agent.query.localcache.prefetchaggressive

be.backingstore.dburi.pool.initial.0

Cluster tab > Backing Store > Connection > Initial Size Cluster tab > Properties (Backing store properties) Cluster tab > Properties (Backing store properties) Cluster tab > Properties

be.backingstore.dburi.pool.inactivityTimeout.0

(Applicable only if Oracle strategy is selected)

be.backingstore.dburi.pool.waitTimeout.0

(Applicable only if Oracle strategy is selected)

be.jdbc.readtimeout (No longer used) be.backingstore.readtimeout

(Applicable only if Oracle strategy is selected)

TIBCO BusinessEvents Installation

64

| Chapter 5

Property Migration Reference

Table 8 Property Migration Reference (Sheet 3 of 13) 3.x (or 4.x) Property
be.oracle.dburi.pool.enforce.0 be.jdbc.dburi.pool.enforce.0 be.oracle.dburi.pool.initial.0 be.jdbc.dburi.pool.initial.0

5.0 CDD Editor (No longer used) (No longer used) Cluster tab > [OM Type - Cache] > Backing Store > Enforce Pools Cluster tab > [OM Type - Cache] > Backing Store > Connection > Initial Size Cluster tab > [OM Type - Cache] > Backing Store > Connection > Max Size Cluster tab > [OM Type - Cache] > Backing Store > Connection > Min Size Agent Classes tab > AgentClassName > Properties Agent Classes tab > AgentClassName > Properties Cluster tab > Database Concepts > Check Interval Cluster tab > Database Concepts > Retry Count Cluster tab > Database Concepts > Database URIs Cluster tab > Database Concepts > Inactivity Timeout Cluster tab > Database Concepts > Initial Size Cluster tab > Database Concepts > Max Size Cluster tab > Database Concepts > Min Size

be.oracle.dburi.pool.max.0 be.jdbc.dburi.pool.max.0

(No longer used)

be.oracle.dburi.pool.min.0 be.jdbc.dburi.pool.min.0

(No longer used)

be.channel.tibjms.queue.disabled

be.channel.tibjms.topic.disabled

be.dbconcepts.connection.check.interval

be.dbconcepts.connection.retry.count

be.dbconcepts.dburi

be.dbconcepts.pool.inactivityTimeout

be.dbconcepts.pool.initial

be.dbconcepts.pool.max

be.dbconcepts.pool.min

TIBCO BusinessEvents Installation

Property Migration Reference 65

Table 8 Property Migration Reference (Sheet 4 of 13) 3.x (or 4.x) Property
be.dbconcepts.pool.PropertyCheckInterval

5.0 CDD Editor Cluster tab > Database Concepts > Property Check Interval Cluster tab > Database Concepts > Wait Timeout Deprecated Agent Classes Tab > Agent class type: Cache

be.dbconcepts.pool.waitTimeout

be.engine.cacheServer

be.engine.cacheServer.channel.disable

Processing Units tab > PUname > Properties Not used

be.engine.cluster.cleanup

Cluster tab > Properties (backing store related) Cluster tab > Object Management (Cache) > Entity Cache Size Cluster tab > Object Management (Cache) > Object Table Cache Size Cluster tab > Domain Objects > Default > Is Cache Limited Cluster tab > Domain Objects > Overrides > Entity URI > Is Cache Limited

be.engine.limited.cache.back.size.limit

be.engine.limited.objectTable.back.size.limit

be.engine.cluster.isCacheLimited

b e . e n g i n e . c l u s t e r . EntityClassName. p r e l o a d

Cluster tab > Domain Objects > Overrides > URI > Preload Entities Cluster tab > Domain Objects > Overrides > URI > Preload Fetch Size Agent Classes > Inference Agent > Properties For TIBCO BusinessEvents Decision Manager

b e . e n g i n e . c l u s t e r . EntityClassName. p r e l o a d . f e t c h s i z e

be.engine.cluster.externalClasses.classLoader

TIBCO BusinessEvents Installation

66

| Chapter 5

Property Migration Reference

Table 8 Property Migration Reference (Sheet 5 of 13) 3.x (or 4.x) Property
be.engine.cluster.externalClasses.path

5.0 CDD Editor Agent Classes tab > Inference Agent > Properties For TIBCO BusinessEvents Decision Manager

be.engine.cluster.hasBackingStore

Cluster tab > [OM Type - Cache] > Backing Store > Enabled Cluster tab > [OM Type - Cache] > Backing Store > Cache Aside Cluster tab > Properties Limited cache is used by default if backing store is enabled. Related setting: Entity metadata > Is Cache Limited

be.engine.cluster.isCacheAside

be.engine.cluster.isCacheLimited

be.engine.cluster.isObjectCacheFullyLoaded be.engine.cluster.minCacheServers

Cluster tab > Properties Cluster tab > [OM Type - Cache] > cache-agent-quorum Deprecated Processing Unit > Properties True by default.

be.engine.cluster.multiEngineOn

be.engine.cluster.multisite be.engine.cluster.preload

Not used Not used. UI supersedes need for this property. See other Preload properties.

TIBCO BusinessEvents Installation

Property Migration Reference 67

Table 8 Property Migration Reference (Sheet 6 of 13) 3.x (or 4.x) Property
b e . e n g i n e . c l u s t e r . EntityClassName. p r e l o a d be.engine.cluster.preload.handles be.engine.cluster.preload.fetchSize

5.0 CDD Editor Due to redesign, the properties do not all map exactly to the current UI. Entity metadata properties were also used to define preloading behavior. They are no longer used. Cluster tab > [OM Type - Cache] > Domain Objects (Default and override settings): Preload Entities, Preload Handles, Preload Fetch Size.

be.engine.cluster.smtimeout.pollInterval be.engine.cluster.smtimeout.refreshAhead be.engine.cluster.recovery.distributed

Cluster tab > Properties Cluster tab > Properties No longer used. Recovery is always distributed. Cluster tab > Properties Processing Unit > Hot Deploy Agent Classes tab > Inference Agent > Properties (in b e - e n g i n e . t r a file) Cluster Tab [OM Type - Berkeley DB] > Agent Class > Properties Cluster Tab > [OM Type Berkeley DB] > Database Environment Directory Cluster Tab > [OM Type Berkeley DB] > Properties Cluster Tab > [OM Type Berkeley DB] > Property Cache Size

be.engine.coherence.useAutomatedRecovery be.engine.hotDeploy.enabled be.engine.kernel.unifiedExtIdMap

be.engine.name b e . e n g i n e . o m . b e r k e l e y d b . c a c h e w e i g h t . agent

be.engine.om.berkeleydb.dbenv

be.engine.om.berkeleydb.internalcachepercent

be.engine.om.eventcache.defaultmaxsize

TIBCO BusinessEvents Installation

68

| Chapter 5

Property Migration Reference

Table 8 Property Migration Reference (Sheet 7 of 13) 3.x (or 4.x) Property
b e . e n g i n e . o m . e v e n t c a c h e . m a x s i z e . agent

5.0 CDD Editor Agent Classes Tab > Inference Agent > Properties Cluster tab > Properties (No longer used) Cluster tab > Domain Objects > Default > Preload Fetch Size Deprecated Deprecated Deprecated Deprecated Deprecated Deprecated Agent Classes tab > Agent Class > Properties HTTP channel resource > Advanced tab > Compression HTTP channel resource > Advanced tab > Enable DNS Lookups HTTP channel resource > Advanced tab > Document Page For TIBCO BusinessEvents Views:
be.agent.dashboard.http.doc page

be.engine.profile.delimiter be.engine.tangosol.oracle.prefetch

be.ft.cluster.name be.ft.enabled be.ft.failback.waitmilliseconds be.ft.failover.waitmilliseconds be.ft.nodename be.ft.priority be.hawk.microagent.name

be.http.compression

be.http.dnsLookups

be.http.docPage

TIBCO BusinessEvents Installation

Property Migration Reference 69

Table 8 Property Migration Reference (Sheet 8 of 13) 3.x (or 4.x) Property
be.http.docRoot

5.0 CDD Editor HTTP channel resource > Advanced tab > Document Root For TIBCO BusinessEvents Views:
be.agent.dashboard.http.doc root

be.http.maxKeepAliveRequests

HTTP channel resource > Advanced tab > Max KeepAlive Requests Processing Units tab > AgentClassName > Http Properties > Max Processors HTTP channel resource > Advanced tab > Max HTTP Header Size HTTP channel resource > Advanced tab > Max HTTP Post Size HTTP channel resource > Advanced tab > Max HTTP Save Post Size HTTP channel resource > Advanced tab > Max Spare Threads HTTP channel resource > Advanced tab > Min Spare Threads HTTP channel resource > Advanced tab > Compressible Mime Types HTTP channel resource > Advanced tab > Restricted User Agents

be.http.maxProcessors

be.http.maxHttpHeaderSize

be.http.maxPostSize

be.http.maxSavePostSize

be.http.maxSpareThreads

be.http.minSpareThreads

be.http.compressableMimeType

be.http.restrictedUserAgents

TIBCO BusinessEvents Installation

70

| Chapter 5

Property Migration Reference

Table 8 Property Migration Reference (Sheet 9 of 13) 3.x (or 4.x) Property
be.http.useBodyEncodingForURI

5.0 CDD Editor HTTP channel resource > Advanced tab > Use Body Encoding for URI Class loader is implicitly selected depending on other backing store configuration choices. Cluster tab > [OM Type - Cache] > Backing Store > Type Cluster tab > [OM Type - Cache] > Backing Store > Strategy Cluster tab > Properties (Backing store properties. Note: replaced by
be.backingstore.readtimeout

be.jdbc.cacheLoaderClass com.tibco.be.jdbcstore.BECoherenceJdbcStore com.tibco.be.oracle.BECoherenceOracleStore

No longer used.
be.jdbc.database.type

be.jdbc.dburi.strategy.0

be.jdbc.readtimeout (No longer used)

see in this table.)

be.jms.reconnect.msgCodes

Agent Classes tab > Inference Agent > Properties Agent Classes tab > AgentClassName > Properties Not used. Not used. Not used. (For query agents) No longer used. See TIBCO BusinessEvents Query Developers Guide for new configuration. Cluster tab > Properties See
be.backingstore.commitSize

be.jms.reconnect.timeout

be.locale.country be.locale.language be.locale.variant be.network.mode.standalone

be.oracle.commitSize

TIBCO BusinessEvents Installation

Property Migration Reference 71

Table 8 Property Migration Reference (Sheet 10 of 13) 3.x (or 4.x) Property
be.oracle.dburi.active.0 be.oracle.dburi.pool.inactivityTimeout.0

5.0 CDD Editor Not used No longer used See be.backingstore. dburi.pool.inactivityTimeout.0

be.oracle.dburi.pool.waitTimeout.0

No longer used. See be.backingstore. dburi.pool.waitTimeout.0

be.oracle.debug be.trace.layout.class.arg

No longer used. Collections > Log Configuration > configname > Custom Line Layout > Arguments Collections > Log Configuration > configname > Custom Line Layout > Class Collections tab > Log Configurations> Files section > Append Collections tab > Log Configurations> Files section > Enable Collections tab > Log Configurations > Files section > Name Collections tab > Log Configurations > Roles The format has also changed. See TIBCO BusinessEvents Administration for details.

be.trace.layout.class.name

be.trace.log.append

be.trace.log.enable

be.trace.log.fileName

be.trace.roles

be.trace.term.enable

Collections tab > Log Configurations > Send to Terminal section > Enable

TIBCO BusinessEvents Installation

72

| Chapter 5

Property Migration Reference

Table 8 Property Migration Reference (Sheet 11 of 13) 3.x (or 4.x) Property
be.trace.log.maxnum

5.0 CDD Editor Collections tab > Log Configurations > Files section > Max number Collections tab > Log Configurations > Max size

Note: TIBCO BusinessEvents 3.x used this property and not

engine.Log.MaxNum. be.trace.log.maxsize

Note: TIBCO BusinessEvents 3.x used this property and not

engine.Log.MaxSize. A g e n t . AgentGroupName. c a c h e T x n . u p d a t e C a c h e

Agent Classes tab > AgentClassName > Properties Cluster Tab [OM Type - Berkeley DB] > Checkpoint Interval Cluster tab > Properties (May be more likely at agent class level) Agent tab > Shared Queue > Workers Agent tab > Shared Queue > Size Agent Classes tab > AgentClassName > Properties Agent Classes tab > Inference Agent > Properties Cluster Tab [OM Type - Berkeley DB] > Database Environment Directory Cluster Tab [OM Type - Berkeley DB] > Delete Retracted Objects from Database Cluster Tab [OM Type - Berkeley DB] > Do Not Recover on Restart Deprecated Deprecated

Checkpoint Interval (in BAR resource)

com.tibco.cep.runtime.channel.payload.validation

com.tibco.cep.runtime.scheduler.default.numThreads

com.tibco.cep.runtime.scheduler.queueSize com.tibco.tibjms.connect.attempts

com.tibco.tibjms.naming.security_protocol

Database Environment Directory (in BAR resource)

Delete Retracted Objects from Database (in BAR resource)

Do not Recover on Restart (in BAR resource)

Engine.FT.ActivationDelay Engine.FT.ActivationInterval

TIBCO BusinessEvents Installation

Property Migration Reference 73

Table 8 Property Migration Reference (Sheet 12 of 13) 3.x (or 4.x) Property
Engine.FT.GroupName Engine.FT.HeartbeatInterval Engine.FT.UseFT Engine.FT.Weight Engine.Log.Dir

5.0 CDD Editor Deprecated Deprecated Deprecated Deprecated Collections tab > Log Configurations Agent Classes tab > Agent Class > Properties Cluster tab > Properties Cluster tab > Properties Cluster Tab [OM Type - Berkeley DB] > Property Cache Size Cluster Tab [OM Type - Berkeley DB] > Checkpoint Ops Limit No longer used. Autoassigned. Cluster tab > General > Cluster Name (Also used for TIBCO BusinessEvents DataGrid cache provider cluster name) Cluster tab > Properties Cluster tab > Properties. Cluster tab > Object Management (Cache) > Number of Backup Copies Process Units tab > Enable Cache Storage

Hawk.AMI.DisplayName

java.net.preferIPv4Stack objectTable.back.size.limit

Property Cache Size (in BAR resource) Schedule a checkpoint if outstanding DB ops greater than (in BAR resource)
tangosol.coherence.cacheconfig tangosol.coherence.cluster

tangosol.coherence.clusteraddress tangosol.coherence.clusterport tangosol.coherence.distributed.backupcount

tangosol.coherence.distributed.localstorage

(In 5.0, also used for TIBCO BusinessEvents DataGrid property be.engine.cluster.isSeeder)

TIBCO BusinessEvents Installation

74

| Chapter 5

Property Migration Reference

Table 8 Property Migration Reference (Sheet 13 of 13) 3.x (or 4.x) Property
tangosol.coherence.distributed.threads tangosol.coherence.localhost tangosol.coherence.localport tangosol.coherence.log

5.0 CDD Editor Cluster tab > Properties. Cluster tab > Properties Cluster tab > Properties Processing Units tab > PUName > Properties Processing Units tab > PUName > Properties Processing Units tab > PUName > Properties Cluster tab > Properties Cluster tab > Properties Cluster tab > Properties Cluster tab > Properties. Used for special handling of null properties and values.

tangosol.coherence.log.level

tangosol.coherence.log.limit

tangosol.coherence.ttl tangosol.coherence.wkan tangosol.coherence.wkan.port tibco.be.property.datatype.null.value

tibco.bwengine.name

Processing Units tab > PUName > Properties Cluster/PU/Agent level properties

tibco.clientVar.<GlobalVariable>

TIBCO BusinessEvents Installation

| 75
Appendix A

Deprecated and Unused Properties

The following TIBCO BusinessEvents engine properties were deprecated or made obsolete (not used) in an earlier release of TIBCO BusinessEvents. Properties newly deprecated or not used in the current release are noted in Chapter 5, Property Migration Reference, on page 61. Table 9 Deprecated and Unused Engine Properties (Sheet 1 of 3) Property Description

be.backingstore.dburi.schema.0

Obsolete property. Used by the Oracle Types backing store, a feature removed in version 5.0.0.
be.engine.cluster.cacheType

Deprecated property. Ignored if present. In 3.0.0, this property specifies which of the following provided caching schemes to use: d i s t - u n l i m i t e d - b s , d i s t - l i m i t e d - b s , or d i s t - u n l i m i t e d - n o b s ( d e f a u l t ) In releases after 3.0.0, various properties are used to internally select the correct caching scheme, for example, b e . e n g i n e . c l u s t e r . i s C a c h e L i m i t e d and
be.engine.cluster.hasBackingStore

See TIBCO BusinessEvents Administration for more details.

be.engine.om.recovery.threads

Not used in this release. Ignored if present.

be.ft.cluster.name

Deprecated property.
be.ft.enabled

Deprecated property.

TIBCO BusinessEvents Installation

76

| Appendix A

Deprecated and Unused Properties

Table 9 Deprecated and Unused Engine Properties (Sheet 2 of 3) Property Description

be.ft.failback.waitmilliseconds be.ft.failover.waitmilliseconds

Deprecated Properties. These properties were introduced in a 2.x release to define a wait period, ensuring that cache was fully initialized before failing over to a secondary or failing back to the recovered primary.
be.ft.node.name

Deprecated property.
be.ft.priority

Deprecated property.
be.locale.country

Sets the country code to use for localization. Use upper case. Uses the ISO 3166 standard.
Note: TIBCO BusinessEvents is not fully localized in this release.
be.locale.language

Sets the language code to use for localization. Uses the ISO 639 standard.
Note: TIBCO BusinessEvents is not fully localized in this release.
be.locale.variant

Optional extension to the locale language, for example, if you set b e . l o c a l e . l a n g u a g e to en, you might set b e . l o c a l e . v a r i a n t to US, which is interpreted as e n _ U S
Note: TIBCO BusinessEvents is not fully localized in this release.
com.tibco.be.jdbcstore.BECoherenceJdbcStore com.tibco.be.oracle.BECoherenceOracleStore

The above properties specified the cache loader class for backing stores. Later there was a Cache Loader Class setting, removed in 5.0. Now the cache loader class value is set internally.

TIBCO BusinessEvents Installation

Deprecated and Unused Properties 77

Table 9 Deprecated and Unused Engine Properties (Sheet 3 of 3) Property Description

be.trace.publish.enable be.trace.publish.subject be.trace.publish.daemon be.trace.publish.network be.trace.publish.service

Deprecated properties. The above properties are ignored by the engine. Instead use current settings in the CDD. See the Collections Tab Log Configurations Settings section in TIBCO BusinessEvents Administration for the current logging properties.
be.trace.log.dir be.trace.enable

Deprecated properties. The above properties are still used by the engine if found in the TRA or CDD file. However, do not use these properties. Instead use current settings in the CDD. See the Collections Tab Log Configurations Settings section in TIBCO BusinessEvents Administration for the current logging settings.
Engine.Log.MaxNum Engine.Log.MaxSize

These properties are set by TIBCO Administrator during deployment. Dont set them in your projects.
Engine.FT.UseFT Engine.FT.Groupname Engine.FT.Weight

Deprecated properties. Were used for In Memory OM fault tolerance in 3.x. Instead, configure for Cache OM, but use the Memory Only mode for all objects. See also b e . f t . n o d e n a m e which was used for the same purpose.
tangosol.coherence.cacheconfig

Not needed except as advised by TIBCO Support for customization purposes.

TIBCO BusinessEvents Installation

78

| Appendix A

Deprecated and Unused Properties

TIBCO BusinessEvents Installation

| 79

Index

Numerics
64-bit mode, configuration 30

A
access to TIBCO BusinessEvents installations, limiting 14 after installing on HP-UX 31 Agent.AgentGroupName.cacheOpsQueueSize 62 Agent.AgentGroupName.cacheTxn.updateCache 72 Agent.AgentGroupName.checkDuplicates 62 Agent.AgentGroupName.concurrentwm 62 Agent.AgentGroupName.key 62 Agent.AgentGroupName.l1CacheSize 63 Agent.AgentGroupName.maxActive 62 Agent.AgentGroupName.priority 63 Agent.AgentGroupName.recoveryPageSize 63 Agent.AgentGroupName.threadcount 63 AIX, configuring for 64-bit mode 30

B
BE_HOME xiv be.agent.cache.specialom 63 be.agent.cache.specialom.maxthreads 63 be.agent.dashboard.http.docpage 68 be.agent.dashboard.http.docroot 69 be.agent.query.localcache.evictseconds 63 be.agent.query.localcache.maxelements 63 be.agent.query.localcache.prefetchaggressive 63 be.backingstore.dburi.0 63 be.backingstore.dburi.pool.inactivityTimeout.0 63 be.backingstore.dburi.pool.initial.0 63 be.backingstore.dburi.pool.waitTimeout.0 63, 71, 71

be.backingstore.dburi.schema.0 (legacy) 75 be.backingstore.readtimeout.0 63 be.channel.tibjms.queue.disabled 64 be.channel.tibjms.topic.disabled 64 be.dbconcepts.connection.check.interval 64 be.dbconcepts.connection.retry.count 64 be.dbconcepts.dburi 64 be.dbconcepts.pool.inactivityTimeout 64 be.dbconcepts.pool.initial 64 be.dbconcepts.pool.max 64 be.dbconcepts.pool.min 64 be.dbconcepts.pool.PropertyCheckInterval 65 be.dbconcepts.pool.waitTimeout 65 be.engine.cacheServer 65 be.engine.cacheServer.channel.disable 65 be.engine.cluster.cacheType (deprecated) 75 be.engine.cluster.cleanup 65 be.engine.cluster.EntityClassName.preload 67 be.engine.cluster.EntityClassName.preload.fetchsize 6 5 be.engine.cluster.EntityClassName.preload.preload 65 be.engine.cluster.externalClasses.classLoader 65 be.engine.cluster.externalClasses.path 66 be.engine.cluster.hasBackingStore 66 be.engine.cluster.isCacheAside 66 be.engine.cluster.isCacheLimited 65, 66 be.engine.cluster.isObjectCacheFullyLoaded 66 be.engine.cluster.minCacheServers 66 be.engine.cluster.multiEngineOn 66 be.engine.cluster.preload 66 be.engine.cluster.preload.fetchSize 67 be.engine.cluster.preload.handles 67 be.engine.cluster.recovery.distributed 67 be.engine.cluster.smtimeout.pollInterval 67 be.engine.cluster.smtimeout.refreshAhead 67 be.engine.coherence.useAutomatedRecovery 67 be.engine.hotDeploy.enabled 67 be.engine.kernel.unifiedExtIdMap 67 be.engine.limited.cache.back.size.limit 65, 65
TIBCO BusinessEvents Installation

80

| Index
be.engine.name 67 be.engine.om.berkeleydb.cacheweight.agent 67 be.engine.om.berkeleydb.dbenv 67 be.engine.om.berkeleydb.internalcachepercent 67 be.engine.om.eventcache.defaultmaxsize 67 be.engine.om.eventcache.maxsize.rule_session 68 be.engine.om.recovery.threads (not used) 75 be.engine.tangosol.oracle.prefetch 68 be.ft.cluster.name (deprecated) 75 be.ft.enabled (deprecated) 75 be.ft.failback.waitmilliseconds (deprecated) 76 be.ft.failover.waitmilliseconds (deprecated 76 be.ft.node.name (deprecated) 76 be.ft.priority (deprecated) 76 be.http.docRoot 69 be.jdbc.cacheLoaderClass 70 be.jdbc.database.type 70 be.jdbc.dburi.0 63 be.jdbc.dburi.pool.enforce.0 64 be.jdbc.dburi.pool.max.0 64 be.jdbc.dburi.pool.min.0 64 be.jdbc.dburi.pool.strategy.0 70 be.jdbc.initial.0 64 be.locale.country 76 be.locale.language 76 be.locale.variant 76 be.network.mode.standalone 70 be.oracle.dburi.pool.enforce.0 64 be.oracle.dburi.pool.max.0 64 be.oracle.dburi.pool.min.0 64 be.oracle.pool.initial.0 64 be.trace.enable (not used) 77 be.trace.log.append 71 be.trace.log.dir (not used) 77 be.trace.publish.daemon (not used) 77 be.trace.publish.enable (not used) 77 be.trace.publish.network (not used) 77 be.trace.publish.service (not used) 77 be.trace.publish.subject (not used) 77 nessEvents Installation viii Concurrent RTC 62 customer support xvii

E
Enforce Pools 64 engine.cluster.isSeeder 36, 41, 48 Engine.FT.Groupname (deprecated) 77 Engine.FT.UseFT (deprecated) 77 Engine.FT.Weight (deprecated) 77 Engine.Log.MaxNum (not used) 77 Engine.Log.MaxSize (not used) 77 ENV_HOME xiv Eviction Time 63

F
functions documentation, accessing xiii

H
heap size settings 27 history installation on UNIX 12 HP-UX 31 configuring for 64-bit mode 30

I
Initial Size 63, 64 initialize_database.sql 57 Installation Directory 14 installation on Windows 2000 Terminal Server 9 required and optional TIBCO products 2

C
changes from the previous release of TIBCO BusiTIBCO BusinessEvents Installation

Index 81

installation on UNIX 64-bit configuration 30 after installing, all UNIX Platforms 29 guidelines 11 history 12 installer account 11 installation on Windows guidelines 8 installer account 8 installer installer account (UNIX) 11 installer account (Windows 8

R
required TIBCO products for BusinessEvents installation 2

S
Solaris 10 configuring for 64-bit mode 30 support, contacting xvii supported UNIX platforms 10 supported Windows platforms 8

J
java.net.preferIPv4Stack 73

T
tangosol.coherence.cacheconfig 77 tangosol.coherence.distributed.backupcount 73 tangosol.coherence.distributed.localstorage 36, 41, 48, 73 tangosol.coherence.distributed.threads 74 tangosol.coherence.localhost 74 tangosol.coherence.localport 74 tangosol.coherence.log 74 tangosol.coherence.log.level 74 tangosol.coherence.log.limit 74 tangosol.coherence.ttl 74 technical support xvii TIBCO BusinessEvents uninstalling 23 upgrading 7 TIBCO_HOME xiv

L
limiting access to TIBCO BusinessEvents installations 14 Linux configuring for 64-bit mode 30

M
Microsoft Windows supported platforms 8

N U
network drive, installing from (Windows) 9 uninstalling BusinessEvents 23 UNIX supported platforms 10 windowing environment for installation 11 upgrading BusinessEvents 7
TIBCO BusinessEvents Installation

82

| Index
W
Windows 2000 Terminal Server, installing on 9

TIBCO BusinessEvents Installation