P. 1
28292547 TIBCO Business Works Concepts

28292547 TIBCO Business Works Concepts

|Views: 128|Likes:
Published by Ram Kishore

More info:

Published by: Ram Kishore on Aug 09, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

10/29/2011

pdf

text

original

Sections

  • TIBCO BusinessWorks Documentation
  • Conventions Used in This Manual
  • How to Contact TIBCO Customer Support
  • Chapter 1 Business Integration
  • The Challenge of Application Integration
  • Integration Benefits
  • Integration Platform Requirements
  • Business Integration Scenario
  • Problem Definition
  • Addressing the Challenge
  • Example Scenario Runtime Implementation
  • The TIBCO BusinessWorks Integration Platform
  • •TIBCO BusinessWorks Key Components
  • TIBCO BusinessWorks Key Components
  • Figure4 TIBCO BusinessWorks components
  • Security
  • Architecture
  • •Fundamentals
  • Fundamentals
  • •Support for Standards on page12
  • Integrated Development Environment
  • Design-Time Architecture
  • Projects
  • Resources
  • Run-Time Architecture
  • TIBCO BusinessWorks Features
  • Messaging
  • Adapters
  • Business Process Modelling
  • Schemas and Data Mapping
  • Understanding Schemas
  • Figure13 XML files conforming or not conforming to XSD
  • Schemas in TIBCO BusinessWorks
  • Manual Activities
  • Deployment Configuration and Management
  • Run-Time Management and Monitoring
  • Figure14 Components Option in TIBCO Administrator
  • Chapter 2 TIBCO BusinessWorks Methodology
  • Introduction
  • Production
  • Phase 1: Analysis
  • Phase 2: Domain Setup and Installation
  • Planning the Domain
  • Installing TIBCO BusinessWorks Components
  • Planning and Configuring User Access
  • Phase 3: Services Configuration
  • Adapter Configuration Overview
  • Web Services Overview
  • Services Used by the Example
  • Phase 4: Process Design
  • Overview
  • Activities Used by the Example
  • Phase 5: Deployment Configuration and Deployment
  • Phase 6: Production
  • Chapter3 Phase 1: Analysis
  • Step 1: Define and Delimit the Problem
  • Step 2: Identify Processes
  • Step 3: Identify Components
  • •Shared Resources
  • •Services and Corresponding Activities
  • Shared Resources
  • Services and Corresponding Activities
  • ManualWork Activities
  • Transitions and Conditions
  • Mapping
  • Exceptions
  • Step 4: Describe Business Events and Objects
  • Step 5: Design Business Processes
  • Step 6: Consider Domain Setup
  • Chapter4 Phase 2: Domain Setup and Installation
  • TIBCO Administration Domain
  • TIBCO Administration Server
  • TIBCO Run-Time Agent
  • Installing TIBCO BusinessWorks
  • No
  • Installation Components
  • Administration Component
  • Design-Time Component
  • Installing Adapters
  • Chapter5 Phase 3: Services Configuration
  • Introduction: TIBCO BusinessWorks Services
  • Service Characteristics
  • Invocation Modes
  • Service Types
  • Web Services
  • Adapter Service Configuration Steps
  • Step 1: Installing the Adapter
  • Step 2: Setting up the Design-Time Adapter
  • Step 3: Configuring the Run-Time Adapter
  • Step 4: Accessing the Adapter Service From the Process
  • Chapter6 Phase 4: Business Process Design
  • Business Processes
  • Process Design Steps
  • Step 1: Define Shared Resources
  • Step 2: Create Process Definitions
  • Step 3: Add a Process Starter
  • Step 4: Add Activities
  • Step 5: Optionally, Add Manual Work Activities
  • Step 6: Create Transitions Between Activities
  • Adding Transitions
  • Step 7: Perform Mapping and Transformation for Each Activity
  • Step 8: Optionally, Group Activities As Needed
  • Step 9: Test the Process
  • Chapter7 Phase 5: Deployment
  • TIBCO BusinessWorks Project Phases
  • Deployment Steps
  • Step 1: Create and Populate the Administration Domain
  • Assign Software to Different Hardware Resources
  • Authorize Users for Different Tasks
  • Step 2: Create and Test Your Project
  • Step 3: Add Deployment Configuration Information
  • Step 4: Deploy Your Project
  • What Happens When You Deploy A Project
  • Deploying and Undeploying Projects
  • Chapter8 Phase 6: Production
  • Monitoring and Management Options
  • User Management
  • Roles
  • Authorization
  • Domain Monitoring and Management
  • Machines
  • Inventory
  • Components
  • Deployment Monitoring and Management
  • Glossary
  • Index

TIBCO™ BusinessWorks Concepts

Software Release 2.0.0 November 2002

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 TIBCO BUSINESSWORKS CONCEPTS DOCUMENT). 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. Technologies described herein are covered by existing patents and pending patent applications. TIBCO technology is protected under US patent number 6,003,011. TIB, TIBCO, Information Bus, The Power of Now, TIBCO Rendezvous, TIBCO AlertServer, TIBCO Adapter SDK, TIBCO AdapterAdministrator, TIBCO Repository, and TIBCO Hawk are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, J2EE, JMS 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 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. Copyright © 2001-2002 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

| iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO BusinessWorks Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typeface Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x x x xi xi xii

Chapter 1 Business Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
The Challenge of Application Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Integration Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Integration Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Business Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Addressing the Challenge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Example Scenario Runtime Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 The TIBCO BusinessWorks Integration Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 TIBCO BusinessWorks Key Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 TIBCO Administration Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Design-Time Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Run-Time Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 TIBCO BusinessWorks Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Business Process Modelling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Schemas and Data Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Manual Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Deployment Configuration and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Run-Time Management and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 2 TIBCO BusinessWorks Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Phase 1: Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

TIBCO BusinessWorks Concepts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activities Used by the Example . . . . . . . . . . . . . . Mapping . . . Installing TIBCO BusinessWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 3: Services Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 30 31 32 33 33 34 34 35 35 36 37 38 Chapter 3 Phase 1: Analysis . . . Step 4: Describe Business Events and Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 6: Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ManualWork Activities . . . . . . . . . . . . . . . . . . Transitions and Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning the Domain . . . . . . . . . . . . . . . Installing TIBCO BusinessWorks Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 50 51 52 53 54 Chapter 5 Phase 3: Services Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: Setting up the Design-Time Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Web Services Overview. . . . . . . . .iv | Contents Phase 2: Domain Setup and Installation . . . . . . . . . . . . . . . . . . . . . . Step 1: Installing the Adapter . . . . . TIBCO BusinessWorks Concepts 56 56 56 57 58 59 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6: Consider Domain Setup . . . . . . . . . . . Invocation Modes. . . . . Step 5: Design Business Processes . . TIBCO Run-Time Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Characteristics . . . . . . . . . . . . . . . . . . . . . Services and Corresponding Activities . . . . . . . . . . . . . . . . . Services Used by the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Introduction: TIBCO BusinessWorks Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: Identify Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 5: Deployment Configuration and Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning and Configuring User Access . . . . . . . . TIBCO Administration Server. . . . . . . . . . Step 3: Identify Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 TIBCO Administration Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adapter Service Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adapter Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 41 42 42 42 43 43 44 44 45 46 47 Chapter 4 Phase 2: Domain Setup and Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 4: Process Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Step 1: Define and Delimit the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . 65 Introduction . . . . . . . . . . . . . . . . . . . . .Contents v | Step 3: Configuring the Run-Time Adapter . . . . . . . . . . . . . . Step 4: Add Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain Monitoring and Management . . . . . . . . . . . . . . . Step 2: Create Process Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying and Undeploying Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Chapter 6 Phase 4: Business Process Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: Create and Test Your Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 8: Optionally. . . . . . . . Step 6: Create Transitions Between Activities . Monitoring and Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4: Deploy Your Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Manual Work Activities . . . . . . . . . . . . . . Step 1: Define Shared Resources . . . . . . Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authorization. . . . . . Step 7: Perform Mapping and Transformation for Each Activity. . . . . . . . . . . . . . . . . . . Authorize Users for Different Tasks . . . . . . . . . . . . . . Step 9: Test the Process . . . . . . . . . . . . . . . . Assign Software to Different Hardware Resources. . . TIBCO BusinessWorks Project Phases . . . . Step 3: Add a Process Starter . . . . . . . . Deployment Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Processes . . . . . . . 92 92 93 94 94 94 95 95 96 96 98 98 98 TIBCO BusinessWorks Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Create and Populate the Administration Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3: Add Deployment Configuration Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Happens When You Deploy A Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inventory . . . . . . . . . . . . . . . . . Group Activities As Needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 66 67 68 69 70 71 72 74 75 76 77 Chapter 7 Phase 5: Deployment . . . . . . . . . User Management . . . . . . . . . . . . . . . . . . . . . . . . . . Components . . . . . . . . . . . . . . 80 81 82 83 83 84 85 86 89 89 90 Chapter 8 Phase 6: Production. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5: Optionally. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Design Steps . . . . . . . . . . . . . Deployment Monitoring and Management . . . . . . . . . . . . . . 62 Step 4: Accessing the Adapter Service From the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Processes . . . . . . . . . . 79 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . 111 TIBCO BusinessWorks Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi | Contents Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Index . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Installing TIBCO BusinessWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Example scenario data flow . . . . . . . . . . . . . . . . . . . . 84 Adding a deployment configuration to the project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Adding a service to an adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Example scenario components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Adding activities that access adapter services. . . . . . . . . 20 Example process . . . . . . . . . . . . . . 23 Components Option in TIBCO Administrator . . . . . . . . 22 XML files conforming or not conforming to XSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Process instances created from a process definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Example scenario run-time implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 TIBCO BusinessWorks components . . . . . . . . . . . . . . . 68 Adding process definitions to your project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Domain setup for example program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Figures vii | Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 TIBCO BusinessWorks communication throughout the enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 TIBCO administration domain . . . . . . . . . 15 Resources in project tree and design panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 TIBCO BusinessWorks Concepts . . . . . . . 71 Project development phases . . . . . . . . . . . . . . . . . . . 69 Adding a process starter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 TIBCO Designer main window . . . . . . . . . . 9 Components of a TIBCO administration domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Business process flow . . . . 66 Shared resources in your project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Installing an adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 TIBCO BusinessWorks project and resources . . . . . . . . . . . . . . . . . . . . . . . . . 54 Adding an adapter to the project . . . . . . . . . . . . . . . . . . . . 18 Adapter data flow . . . . . . . . . . . . . . . . . . . . . . 70 Adding activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . 97 Viewing Process Definition information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Inventory Option in TIBCO Administrator . . . . 98 TIBCO BusinessWorks Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Adding recovery options . . . . . . . . . . . . . . . . . . . . . 88 Communication inside a TIBCO administration domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Machines Option in TIBCO Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Components Option in TIBCO Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii | Figures Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Adding a process engine to the deployment configuration . . . . . . . . . . . . . . . .

Topics • • • Related Documentation. and on conventions used in TIBCO manuals. related documentation.| ix Preface This preface gives some information on the TIBCO™ documentation set. page xii TIBCO BusinessWorks Concepts . page xi How to Contact TIBCO Customer Support. page x Conventions Used in This Manual.

and monitoring a TIBCO BusinessWorks process. You will therefore find the documentation for those products useful: • TIBCO Designer documentation. TIBCO BusinessWorks Business Palette Reference This manual describes each of the palettes available in TIBCO BusinessWorks. TIBCO BusinessWorks Release Notes Read the release notes for a list of new and changed features. TIBCO Administrator documentation. TIBCO BusinessWorks Installation Read this manual for information on installing one or more components of TIBCO BusinessWorks and setting up a TIBCO BusinessWorks domain. edit. and test business processes using TIBCO BusinessWorks. TIBCO Administrator is the monitoring and managing interface for new-generation TIBCO products such as TIBCO BusinessWorks. • • • • Other Documentation TIBCO BusinessWorks is bundled with other products. deploying. TIBCO Adapter product documentation • • TIBCO BusinessWorks Concepts . TIBCO Designer is an easy to use graphical user interface for design-time configuration of TIBCO applications. TIBCO Designer includes online help for each palette.x | Preface Related Documentation TIBCO BusinessWorks Documentation In addition to this manual. the following documents are part of the TIBCO BusinessWorks documentation set: • TIBCO BusinessWorks Quick Start This manual steps you through a very simple example of designing. TIBCO BusinessWorks Business Process Design Guide This manual describes how to create. This document also contains lists of known issues and closes issues for this release.

For example: "Select homedir/runexample. Italic text is used in three ways: • • • In code examples. This font is also used for emphasis in code examples. for example. Menu>Submenu. The accompanying text may be especially helpful. Typeface Conventions This manual uses the following typeface conventions: Example monospace Use This monospace font is used for program output and code example listings and for file names. Note. or choose Edit from the menu. for example. Tip. etc.. TIBCO BusinessWorks Concepts . click OK.bat". For document titles For emphasis monospace bold Italic Bold Bold text indicates actions you take when using a GUI. Warning. for text that should be replaced with an actual value. configuration file parameters. commands. Submenus and options of a menu item are indicated with an angle bracket. Be sure you read the accompanying text for important information. This bold monospace font indicates characters in a command line that you must type exactly as shown. and literal programming elements in running text. file names. The accompanying text describes a condition that severely affects the functioning of the software.Conventions Used in This Manual xi | Conventions Used in This Manual This manual uses the following conventions.

xii | Preface How to Contact TIBCO Customer Support For comments or problems with this manual or the software it addresses. TIBCO BusinessWorks Concepts . You must have a valid maintenance or support contract to use this site. please contact TIBCO Product Support at: http://support. you can request one. If you do not have a username.tibco.com Entry to this site requires a username and password.

This chapter discusses what is required of an integration platform. page 19 TIBCO BusinessWorks Concepts . Topics • • • • • The Challenge of Application Integration. deploy. and a web-based GUI for monitoring and managing run-time components. page 2 Business Integration Scenario. and run integration projects. TIBCO BusinessWorks includes a graphical user interface (GUI) for defining business processes. and how TIBCO BusinessWorks meets these requirements. page 12 TIBCO BusinessWorks Features.|1 Chapter 1 Business Integration TIBCO BusinessWorks is a scalable. and easy to use integration platform that allows you to develop. an engine that executes the process. page 8 Architecture. page 4 The TIBCO BusinessWorks Integration Platform. extensible.

Figure 1 TIBCO BusinessWorks communication throughout the enterprise . An integration platform should allow you to design the business process.) TIBCO BusinessWorks Concepts . etc. that is. An enterprise may need to integrate back-office systems with the Internet. File. etc. or any of the above with legacy or ERP (Enterprise Resource Planning) systems. Integration Benefits The integrated enterprise works seamlessly. trading partners and exchanges. This capability allows you to use TIBCO BusinessWorks to integrate all aspects of your enterprise. Siebel. The business process should transparently receive and send data throughout the enterprise and beyond. the flow of data. databases. The illustration below shows how TIBCO BusinessWorks connects to applications of different types. employees become more productive and the integrated system yields a significant return on investment. database ERP applications (SAP R/3.NET J2EE Trading partners Legacy and custom applications Exchanges Mainframes EJB. With less time spent on administrative and manual tasks. This return increases as the company grows. Different departments and groups share communications and can together respond quickly to customer needs. CORBA.2 | Business Integration The Challenge of Application Integration Application integration is one of the most pressing challenges of today’s enterprise. a purchase order management system with the customer service management system.

If the integration platform is easy to use. • Short deployment cycle—The integration project must be ready to go to production within a realistic timeframe and deploying from development to a running project must go smoothly. the company itself becomes responsible for maintenance and updates. When the project is complete.The Challenge of Application Integration 3 | Integration Platform Requirements To be successful. Cost of ownership is greatly reduced because the expertise is already there. your integration platform must meet the following requirements. Ease of use—Integration projects are often developed by outside companies or consultants. Extensibility also means that the project must be flexible and adaptable so you can potentially adapt it to multiple departments in the same company. Scalability and extensibility—The project must be scalable (respond to increasing demand) and extensible (allow integration of new applications or addition of new business processes). and employees usually face a steep learning curve. • • TIBCO BusinessWorks Concepts . the project can be developed in house.

4 | Business Integration Business Integration Scenario To illustrate some of the functionality available as part of TIBCO BusinessWorks. then extracting the shipping information from the shipping log using the Order ID. then discusses the run-time implementation. the department responsible for purchase order management has received orders by telephone and has manually entered them into a PeopleSoft Order Management system. the rest of this manual uses a simple example scenario presented in this section. So far. add information about shipping date and time to each item. Because a high volume of sales cannot be handled efficiently with this setup. The information should be retrieved interactively from the shipping company’s web site via the Internet. and because currently information available to the customer service department is incomplete. Before order fulfillment. Management decides to make the following changes: • • • • Make order entry possible via a secure web server outside the firewall which communicates with an application server that supports JMS. Problem Definition EasyWare Incorporated is a manufacturer of computer hardware. customers do not receive notification when items are shipped and customer service representatives must access the shipping information in a two-step process: first extracting the Order ID from the PeopleSoft system. As a result. require approval by a credit check specialist for orders over $10 000. An additional concern is that shipping information is not included in the Order Management system. customer satisfaction becomes an issue. Add a Siebel customer service system that receives information about each purchase order. Before the order is entered into the Siebel system. Customer service representatives can then have easy access to all ordering information. TIBCO BusinessWorks Concepts . The section starts with a problem definition. Individual aspects of the integration project are discussed in later chapters. but finds that not all information they need is available there. The customer service department uses the information in the PeopleSoft system as well.

including the PeopleSoft Order ID and the shipping information. After careful deliberation. reducing complexity for the end user. at the same time. Design The goal of the integration project allow EasyWare to receive orders either by telephone—with direct access to PeopleSoft as before—or from an application server. The business process accesses the shipping schedule by connecting to the shipper’s web site using SOAP. A PeopleSoft adapter enters the web order into the PeopleSoft system and receives an order from the PeopleSoft system that includes an Order ID. The PeopleSoft Order Management system continues to be used. but data can be entered manually as before or can arrive from the Internet via the application server. the system must integrate with the Siebel customer service system. TIBCO BusinessWorks Concepts . This results in the following components of the integration project: • • At the center is the business process. In addition. the IT department decides to prepare a prototype using TIBCO BusinessWorks. A Siebel adapter enters the complete order. • • • Figure 2 shows the components that are needed. The process is on hold until approval has been made.Business Integration Scenario 5 | Addressing the Challenge The challenge faced by EasyWare is to add the new capabilities to the business process while. which interacts with the different services using the appropriate messaging protocol. into the Siebel system. A ManualWork activity sends the order to the credit check specialist. This part of the process is a request-response service.

if approval arrives. 3. the process continues. A TIBCO BusinessWorks JMS order document. the order is sent out for credit check. which was supplied in XML to a format PeopleSoft expects and the PeopleSoft adapter submits the order to the PeopleSoft Order Management system. Otherwise. TIBCO BusinessWorks transforms the order. the customer is informed immediately and the order placed on indefinite hold. 5. Orders arrive from the distributors on the Internet. 2. Queue Receiver activity receives the incoming 4. the project would proceed as follows (numbered steps match the numbers in Figure 3): 1. When it accepts the order.6 | Business Integration Figure 2 Example scenario components Siebel (Customer Service) Adapter Peoplesoft (Order Management) WWW Adapter Internet Order Entry Application Server Business Process Internet Shipping Schedule SOAP Service Credit check manual step Example Scenario Runtime Implementation At run-time. The PeopleSoft system accepts or rejects the order. 6. it includes an Order ID. TIBCO BusinessWorks Concepts . If the order amount is greater than $10 000. The orders are processed by a customized order capture system built on top of an application server. When the credit check is not successful.

The Siebel adapter adds a new customer service record to the Siebel system. Figure 3 Example scenario run-time implementation WWW Siebel (Customer Service) Peoplesoft (Order Management) Sales order + ID 5 Internet 2 Application Server JMS 1 Order Entry Sales order 4 Adapter Adapter RV 7 Messaging system 6 RV 7 SOAP Internet Business process (coordinator) Credit check manual step RV 3 Shipping Schedule TIBCO BusinessWorks Concepts . TIBCO BusinessWorks checks the shipping schedule using a web service activity and adds the ship date to the order. including the Order ID and the shipping information. to a Siebel adapter. 8. TIBCO BusinessWorks sends the information about the order.Business Integration Scenario 7 | 7.

deployment configuration. process design. • • • • TIBCO BusinessWorks was designed using a plug-in architecture. TIBCO Administrator supports security administration as well as monitoring and management of processes and machines. The TIBCO Runtime Agent (TRA) runs on each machine and executes scripts. Optionally. and deployment of the integration project in one easy to use interface. TIBCO Administrator consists of the TIBCO Administration Server and the web browser based TIBCO Administrator GUI. Rapid development and deployment are the results. TIBCO BusinessWorks Concepts . You can use TIBCO Designer in test mode to incrementally verify your design during development. plug-in modules can be added to TIBCO BusinessWorks. As a result. The TIBCO BusinessWorks engine runs the business processes in test mode and at run-time. sends alerts. and performs recovery as specified.8 | Business Integration The TIBCO BusinessWorks Integration Platform This section introduces the TIBCO BusinessWorks integration platform by discussing the following topics: • • TIBCO BusinessWorks Key Components TIBCO Administration Domain TIBCO BusinessWorks Key Components TIBCO BusinessWorks key components work together as follows: • The TIBCO Designer graphical user interface (GUI) supports adapter configuration. The illustration below shows how the components work together. TIBCO BusinessWorks interacts with TIBCO InConcert in its implementation of ManualWork activities.

Figure 5 illustrates an administration domain and its contents. Components within an administration domain can communicate with systems outside the domain. This section discusses the TIBCO administration domain. Administration Domain Overview A TIBCO administration domain is a collection of users. all process engines and adapters continue to run. Note that when the Administration Server goes down. and TIBCO BusinessWorks components that a TIBCO Administration Server monitors and manages. but the administration domain is the administrative boundary of an enterprise integration project. the associated security implementation. machines. There is only one Administration Server for each administration domain. and how you monitor and manage the domain.The TIBCO BusinessWorks Integration Platform 9 | Figure 4 TIBCO BusinessWorks components TIBCO Designer GUI Runtime environment TIBCO Administrator GUI TRA Machine1: PeopleSoft subscriber Process engine 1 proc1 proc2 . Mon ito Man r and age TIBCO BusinessWorks Concepts y plo De ... and run-time monitoring and management... TIBCO Administration Server Development Runtime TIBCO Administration Domain The TIBCO administration domain combines the benefits of a distributed run-time environment with centralized design-time deployment. TRA Machine2: Siebel publisher Process engine 2 proc3 proc4 .

You can. all machines within an administration domain are expected to be in the same network subnet. TIBCO BusinessWorks Concepts . however. By default. See Projects on page 15. and monitored from there. set up your system to use TIBCO Rendezvous rvrd and can then use TIBCO BusinessWorks across subnets. User and Access Information—User and authorization information is specified with the TIBCO Administrator GUI and stored in the domain data store. Projects—A project is created and deployed with the TIBCO Designer GUI. 4. the project becomes visible in the TIBCO Administrator GUI and its components can be started. A machine can be added to an administration domain when a TIBCO BusinessWorks component or adapter is installed. 2. Machines—Each TIBCO administration domain contains one or more machines. 5. Components—Component software includes the TIBCO BusinessWorks engine and adapters. stopped.10 | Business Integration Figure 5 Components of a TIBCO administration domain Domain Machine A 3 TIBCO Administration Server 1 User & Access Information 4 Projects 5 Machine & Component Information Process Engine 2 PeopleSoft Adapter 2 Machine B 3 Siebel Adapter 2 Machine C 3 A TIBCO administration domain consists of these elements. Once deployed. numbered correspondingly in Figure 5: 1. See Security below. 3. TIBCO Administration Server—Each administration domain has one and only one TIBCO Administration Server.

Using the TIBCO Administrator GUI. users with full administrative privileges can define which users should have access to which part of the system. TIBCO BusinessWorks Concepts . add. An administrator gives users access rights to the functionality of the product they need.The TIBCO BusinessWorks Integration Platform 11 | Security The TIBCO Administration Server supports centralized authentication and authorization. Authorization—Permission to view or execute. • • Authentication—The verification of the identity of a person or process. Only authorized users may start or stop process engines or adapters. access rights are given to view or to write to projects at design time from TIBCO Designer or to view or to manage modules from the TIBCO Administrator console. Monitoring and Managing the Domain The TIBCO Administrator GUI allows you to monitor and manage the different elements of the administration domain if you are authorized to do so. This includes viewing component status and throughput and looking at traces. • • • • View. which can also be exported to a file. For example. only authorized users may create and save a server-based project to the domain data store. This fine-grained user authorization scheme allows you to customize the system to your company’s needs. Monitor deployments. Monitor and manage the machines in the administration domain. This includes stopping and starting process engines and adapters. For example. Manage deployments. TIBCO BusinessWorks supports authentication and authorization for both data stores and components (process engines or adapters) in the administration domain. and delete users and assign access privileges to each user. The TIBCO Administration Server controls that access.

Support for standards also removes dependency on one company’s services and makes applications from different companies interact more easily. A standards-based integration platform supports you best as you add applications to your enterprise or need to communicate with new business partners. Standards are essential as you are planning for the future of the project because standards facilitate updates. EJB. and integration development will be faster and easier. TIBCO BusinessWorks supports the most widely used standards for the different aspects of an integration project: • • • • • • J2EE Compliant—JMS. page 14 Run-Time Architecture. XSD. TIBCO BusinessWorks Concepts . HTTPS Messaging—JMS. TIBCO Rendezvous Data Description—Native support for DTD. WSDL). HTTP. JNDI Protocols—Web services (SOAP. page 17 Fundamentals The TIBCO BusinessWorks architecture is based on the following set of fundamentals: • • • Support for Standards Your integration platform must support standards for several reasons. Some the applications you use may already be using standards. It discusses these topics: • • • Fundamentals Design-Time Architecture.12 | Business Integration Architecture This section explains the TIBCO BusinessWorks architecture at design time and run-time. and TIBCO AE Schema Data Representation and Expressions—Native support for XML. XPath Data Transformation—XSLT Support for Standards on page 12 Integrated Development Environment on page 13 Extensibility and Scalability on page 13 TIBCO BusinessWorks also supports a plug-in for B2B interactions.

that is. which process runs on which engine and which service accesses which adapter instance. 2. The users authorized to handle the manual activities can be specified in TIBCO Administrator. Extensibility and Scalability As your enterprise grows. TIBCO BusinessWorks Concepts . When you deploy the project. Optionally. and run-time environment are tightly integrated even though the run-time environment supports a distributed architecture. You configure the adapter. You can use the TIBCO Designer in test mode to debug the process definitions in your integration project. 4. At design time. 5.Architecture 13 | Integrated Development Environment Your integration project must be supported by an integrated development environment that spans all phases of the project. Working in a distributed fashion. TIBCO BusinessWorks has been designed to be extensible and scalable. you add machines to the domain. The TRA also updates the TIBCO Administration Server with information about the new configuration. and design your business processes. then deploy the adapter service on the machine of your choice. deployment. As you acquire new applications for your enterprise. You can then monitor and manage all processes using TIBCO Administrator. modify your process definition. 1. you install the appropriate adapters into the domain. that information is then used by InConcert. such as adapters. you use TIBCO Designer to configure services. you deploy the different adapter services and business processes on different machines in the administration domain. the TIBCO BusinessWorks TRA component sends scripts and other information about the processes to be run to the individual machines. the process design. With TIBCO BusinessWorks. When the business process applications’ volume increases. Scalability to support higher volume and extensibility to support additional applications or a larger number of process engines or adapter instances become paramount. new applications are added and volume of data increases. then exported to TIBCO InConcert. You can use the TIBCO Designer deployment palettes to deploy processes to process engines and to deploy adapter services to adapters on the individual machines. When you deploy the project. 3. you can configure manual activities using TIBCO Designer. You can start the processes using the TIBCO Administrator GUI.

and so on. See the TIBCO Designer User’s Guide for more information. Read File or Send Mail) into the design window and joining the activities using transitions. add breakpoints. which contain the design-time components of an integration project. supply values for variables. The TIBCO Designer GUI is discussed in more detail in the TIBCO Designer User’s Guide. You design a business process by dragging activities (e.g. You can provide input. The TIBCO Designer test mode allows you to debug the business process. TIBCO Designer Layout The TIBCO Designer main window has four panels.14 | Business Integration Design-Time Architecture At design time. you work with the TIBCO Designer GUI to configure adapter services and design business processes. Figure 6 TIBCO Designer main window Project tree panel Design panel Palette panel Configuration panel TIBCO BusinessWorks Concepts .

In TIBCO Designer. consists of several components: • • • • • A JMS shared resource (JMS Connection) Two process definitions (ProcessOrder and ProcessSoap) A shared resource used by the SOAP activity (ShippingSchedule) A Siebel adapter and a PeopleSoft adapter (SBLAccount and PSoft_ReqRep) A deployment configuration for the project (Deployment Configuration) For a description of the example scenario that was used as the basis for this project. and deployment information. see Business Integration Scenario on page 4. This includes services (producers and consumers of information). The ProcessNewComputer project. any business logic that may be applied to that information. shown in the project tree panel in Figure 7.Architecture 15 | Projects A project consists of resources that contain the functionality needed for your integration. you click the project folder to display the project’s resources. Figure 7 TIBCO BusinessWorks project and resources ProcessNewComputer project TIBCO BusinessWorks Concepts .

or a specific adapter instance. you can deploy the project from TIBCO Designer and the appropriate information is sent to each machine. Figure 8 Resources in project tree and design panel i Resources in project tree Resources in design panel Palettes Context-sensitive palettes organize resources into related groups. A TIBCO Designer resource corresponds to an object in a TIBCO application. such as an FTP activity. Afterwards. You can assign different processes to different process engines and and adapter services to adapters installed on machines in the administration domain. The main window shown in TIBCO Designer Layout on page 14 has eight palettes in the palette panel. TIBCO BusinessWorks Concepts . You drag and drop resources from the palette into the design panel to add them to your project.16 | Business Integration Resources Resources are the components of a project. Which palette is displayed depends on the currently opened resource and on your preferences. Deployment The Deployment palette allows you to add a deployment configuration to the project tree. a process definition.

Figure 9 Process instances created from a process definition Process Definition 1 Process Instance 1-1 State Process Instance 1-2 State Process Instance 1-3 State Event Source Engine JMS Queue Receiver While different process instances are running.Architecture 17 | Run-Time Architecture When the integration project is deployed. Enter data into a PeopleSoft Order Management system and data into a Siebel customer service system via the appropriate adapters. a File Poller or an Adapter Subscriber activity waiting for incoming data. and can collect tracing information for later analysis. the TIBCO Administrator GUI allows monitoring of the running project at different levels of detail. data from a PeopleSoft Order Management System via the appropriate adapter. In Figure 9. any alerts that were scheduled during deployment configuration are sent to the specified recipient by the TIBCO Administration server. Users can access TIBCO Administrator using the TIBCO Administrator GUI. A process starter could be. • • All components are monitored and managed via TIBCO Administrator. which also provides security and repository management. For the example discussed in this manual. When data arrives. You start each component individually from the TIBCO Administrator GUI. Send certain orders out for credit approval and receive approval or refusal. process instances are created by process starters. the process engine could perform these tasks: • Receive data from an application server via JMS. a JMS Queue Receiver activity creates an instance of the process definition to which it belongs each time it receives input. TIBCO BusinessWorks Concepts . the process starter creates a process instance using the process definition to which it belongs. In addition. After all adapters and process engines have been started. the different process engines and adapters are ready to run on the machines in the administration domain. and the activities in the process are executed in sequence. for example. and data from a shipping service via SOAP.

18 | Business Integration Figure 10 Example scenario data flow Siebel Customer Service Adapter Publication Service PeopleSoft Order Management Adapter Subscription Service Business Process Shipping Information Web Service Credit Check ManualWork actvity InConcert Administration Server Security Repository Monitoring TIBCO BusinessWorks Concepts .

the messaging system must queue that message and continue to operate. Requirements vary throughout the day and throughout the business year. Distributed architecture—A distributed. and you cannot afford performance degradation at the time when business increases. and HTTP. loosely coupled system is much more likely to support the fault-tolerance you require than a monolithic system that depends on one centralized server. and the system must be fault tolerant. Supported protocols include TIBCO Rendezvous. High throughput—High throughput without performance degradation is needed. The system should have these characteristics: • Guaranteed delivery and fault tolerance—Message delivery must be guaranteed. you need a messaging system that can reliably handle the volume of messages that will be sent and received. If a message cannot be delivered because the recipient was unavailable. • • • • • • Messaging Adapters Business Process Modelling Schemas and Data Mapping Deployment Configuration and Management Run-Time Management and Monitoring Messaging To support your integration project at run-time. Scalability—As your business grows. The queued message must then be redelivered as appropriate. JMS. • • • TIBCO BusinessWorks is based on messaging standards with proven track records. TIBCO BusinessWorks Concepts . you want to be able to update your business integration in a simple and cohesive way. Furthermore.TIBCO BusinessWorks Features 19 | TIBCO BusinessWorks Features This section discusses some TIBCO BusinessWorks features. The messaging system must support this scalability. you want to be able to connect your integration project with other departments using a similar system.

) The illustration below shows how a Siebel customer service system communicates with the business process using an adapter publication service and the business process communicates with the PeopleSoft Order Management system using an adapter subscription service. TIBCO BusinessWorks Concepts . What are Adapters? Adapters translate information into the appropriate format: • • • Adapters receive information from a source application and publish it to the business process in a shared format. Adapters can also be set up to work in a client/server mode (using remote operations.20 | Business Integration Adapters Business information is distributed among different business applications (such as SAP R/3 or PeopleSoft) or available from databases or files. Adapters subscribe to information from a business process and translate it to a format the target application can understand. Figure 11 Adapter data flow I Siebel Customer Service PeopleSoft Order Management Adapter Publication Service Adapter Subscription Service Business Process In TIBCO BusinessWorks. adapters provide services to activities inside the business process. Adapters help make this information available to the business process by "adapting" the applications to a common messaging system.

You can therefore easily see if one of the adapters is a bottleneck in the business process flow. see Phase 3: Services Configuration on page 55. Siebel. and others. These adapters can then be used in process design and run as part of the integration project. TIBCO BusinessWorks Concepts . TIBCO BusinessWorks fully integrates with the following adapters: • • Technology adapters—Includes adapters that access files or databases. TIBCO BusinessWorks includes second-generation adapters that are based on the same technology but have the following new features: • Easy Configuration With Design-Time Adapter—All adapters included with TIBCO BusinessWorks use a unified GUI that simplifies adapter configuration. These activities interact with each of the standard adapter services.TIBCO BusinessWorks Features 21 | Adapter Features Companies in a wide range of industries have successfully used TIBCO adapters to integrate different packages and custom applications. For more information. SAP R/3. Other TIBCO Adapters can be loaded into TIBCO Designer and configured using the Generic Adapter Configuration resources. be installed into the administration domain or monitored and managed via TIBCO Administrator. They cannot. Application adapters—Includes adapter for PeopleSoft. however. the TIBCO Administrator GUI monitors each adapter in its own panel. For example. Easy Deployment and Monitoring—When you are ready to deploy your project. Easy Inclusion in Business Processes—The business process can communicate with adapters by using activities found in the adapter palette. A Design-Time Adapter allows you to directly access the source application from the TIBCO Designer GUI and specify the data the business process needs. At run-time. the Publish to Adapter activity sends a message to an adapter subscription service. the TIBCO Designer deployment palette allows you to assign each adapter to its own machine. • • TIBCO BusinessWorks Adapters A fully integrated TIBCO BusinessWorks adapter can be installed into a TIBCO administration domain and later monitored and managed from the TIBCO Administrator GUI.

For example. TIBCO BusinessWorks Concepts . A transformation tool that lets you map the output of one activity to the input of subsequent activities. timers. A complete set of commonly used activities such as File Read.22 | Business Integration Business Process Modelling The business processes describe the actual flow of data inside the enterprise. Conditional transitions supporting XPath syntax. Grouping of activities. An easy-to-use design-time process debugger. TIBCO BusinessWorks allows you to view and manipulate the data coming from and going into each service or activity using XML schemas. Figure 12 Example process Schemas and Data Mapping Different applications in your enterprise use different data representations. a purchase order in a PeopleSoft system differs from a purchase order in a Siebel customer service system. FTP activities. and the TIBCO BusinessWorks Process Design Guide. you use the TIBCO Designer GUI to design and test your processes. Write. etc. File and File Create. In TIBCO BusinessWorks. Features include: • • • • • • Configuration of adapter services. See Phase 4: Business Process Design on page 65. a set of email activities. The illustration below shows a simple process that is part of the example scenario in the design window.

0" encoding="UTF-8"?> <oderid>ACME25 </orderid> Schemas are especially useful if you are deploying a complex system. while an alphanumeric Order ID is rejected.. The input schema (required or optional) defines input values for an activity.org/2000/10/XMLSchema" targetNamespace = "http://www. The process data is the list of available data for that activity. Schemas are used by the running application but are not included in the code. Figure 13 XML files conforming or not conforming to XSD XSD <?xml version = "1. you can define the schema for adapters and view and manipulate the schema for each activity in the business process. then discusses "Schemas in TIBCO BusinessWorks...w3. you can view the available process data and define the input schema for each activity.tibco. XML XML XML <?xml version="1. Schemas in TIBCO BusinessWorks In the TIBCO Designer GUI.0" encoding="UTF-8"?> <oderid>345</orderid> <?xml version="1. TIBCO BusinessWorks Concepts .0" encoding="UTF-8"?> <oderid>350187 </orderid> <?xml version="1.TIBCO BusinessWorks Features 23 | This section first gives a brief introduction to schema (Understanding Schemas)." Understanding Schemas The example below shows a simplified XSD (XML Schema Definition) that includes an Order ID element restricted to integer data.. Incoming XML documents that use integers for the Order ID are allowed.com/namespaces/AESchema" . The use of schemas makes it possible to enforce that outgoing and incoming data strictly comply with the prespecified data description. <element name = "OrderID" type = "integer"> .0" encoding = "UTF-8"?> <schema xmlns = "http://www. For business process activities.

download documents associated with a task. TIBCO BusinessWorks Concepts . the order is assigned to a pool of users for approval. One user accepts the request. You perform deployment configuration with the TIBCO Designer’s easy to use drag and drop interface as follows: 1. Deployment Configuration and Management The TIBCO Designer deployment palette allows you to perform deployment configuration and deploy your project. In our example. See Step 7: Perform Mapping and Transformation for Each Activity on page 75 (Chapter 6). the work is marked as not approved and the process completes. Assign services and process engines to these machines. Users and groups are defined either in TIBCO InConcert or TIBCO Administrator (and then later exported to TIBCO InConcert). If errors were reported in the manual work. change the status of the task. In that case. An activity that assigns work creates a TIBCO InConcert job. Manual Activities TIBCO BusinessWorks includes a ManualWork palette with activities that you can add to your business processes when the process requires user interaction for completion. an additional credit check is required. and then the status of the request is checked. The job can be viewed and modified using TIBCO BusinessWorks web interface to manual tasks. TIBCO BusinessWorks allows you to: • • • • • assign a task to a pool of users. 2. orders under $10 000 were processes automatically. Identify the machines that implement the integration project. Data mapping is discussed in detail in the TIBCO BusinessWorks Process Design Guide. then the work is still in the users’ queue. For orders over 10 000. so the process waits for the completion of the manual work. If no errors were returned. the manual approval times out. or wait for the completion of a task. and you do not need detailed knowledge of XPath for simple conditions. and approves or rejects it.24 | Business Integration You can map the process data to the input data using a drag and drop interface. The ManualWork palette works with TIBCO InConcert. You can specify conditional mapping using XPath. If no one accepts the request. check the status of the task.

At runtime. some auto-correction upon failure (for example. which means prepare it to run. TIBCO BusinessWorks Concepts . and an interface that allows comprehensive access to the current state of the project. run-time monitoring. 5. in which different processes run on different machines. TIBCO BusinessWorks supports a distributed deployment environment. End-to-end business process monitoring. The TIBCO Administration Server supports security. TIBCO BusinessWorks allows you to deploy multiple engines as part of a fault-tolerant group. You then monitor and manage the processes using a web-browser based GUI that you access remotely. Facilities must include a notification mechanism. Only authorized users should have access to management functions. the engine running in standby mode can take over if the primary engine experiences problems. Run-Time Management and Monitoring After your integration project has been deployed. This includes the following features: • • • User authorization and authentication. management and monitoring are key factors for its success. including starting and stopping adapter instances and process engines. and process and system management via the TIBCO Administrator GUI. — Create customized logs that could include number of business processes. throughput. and so on. If required. This is discussed in more detail in Phase 5: Deployment on page 79. both engines are started and one runs in standby mode.TIBCO BusinessWorks Features 25 | 3. Component management. — Receive alerts if parts of the project are overloaded or if a failure occurred. and network status. Specify alert conditions and recipients. processes. — Track components such as adapter services or process engines. — Automatically restart failed processes. The engines in the group should be configured for JDBC-based checkpointing. • Systems management. Specify failure recovery options. restarting a machine or process). TIBCO BusinessWorks combines the advantages of running in a distributed environment without a single point of failure with the advantage of monitoring and managing the different components in a centralized fashion. 4. — Monitor system performance. Deploy the project.

26 | Business Integration • Tracing. Figure 14 Components Option in TIBCO Administrator See Phase 6: Production on page 91 for more information. Privileged users can view additional information or stop or start the component. Each deployed component in the domain is displayed. view any log file. debug. after a certain time. The screen below shows the TIBCO Administrator Components option. TIBCO BusinessWorks Concepts .). regardless of the machine on which the associated component is running. — Specify which information you want to view (info. — From any machine in the administration domain. etc.

page 30 Phase 3: Services Configuration. page 28 Phase 1: Analysis. page 37 Phase 6: Production. Having a well-defined methodology helps new users come up to speed quickly and allows different developers to work together more easily. page 35 Phase 5: Deployment Configuration and Deployment. page 38 TIBCO BusinessWorks Concepts . This chapter gives an overview of TIBCO BusinessWorks methodology.| 27 Chapter 2 TIBCO BusinessWorks Methodology A TIBCO BusinessWorks integration project is developed in phases. page 33 Phase 4: Process Design. page 29 Phase 2: Domain Setup and Installation. Topics • • • • • • • Introduction.

Note that as a rule. an adapter service. Analysis Define & analyze problem Domain Setup Install software & configure domain Services Configuration Configure adapters Process Design Implement & test business processes Deployment Deploy to runtime engine Production Manage & monitor deployments TIBCO BusinessWorks Concepts . A more detailed discussion for each phase is then given in a separate chapter. and services configuration only once. using examples from the example scenario as appropriate (see Business Integration Scenario on page 4). then iterate through the other phases until you have arrived at the optimal configuration. After you’ve configured adapter services and business processes. • • • Using TIBCO Designer. you perform analysis. • Following the phases in sequence results in a fast deployment that closely meets the specifications. installation.28 | TIBCO BusinessWorks Methodology Introduction TIBCO BusinessWorks components are designed to support development in phases and to let you seamlessly move from one phase to another. You can then access the adapter service from activities inside the business process. for example. You assign each adapter and process engine to a machine in the administration domain and deploy the project to the run-time environment. you configure services. you can use TIBCO Designer to assign adapter services to adapters and processes to process engines. You can then start and the adapters and process engines using the TIBCO Administrator GUI and manage and monitor them from there. This section gives an overview of each phase.

most expansions are straightforward. one could consider expansion to include direct communication with a business partner. which states your project’s goals clearly. In the example scenario. error handling. the process is accessing two adapter services (PeopleSoft and Siebel). However. The analysis should include consideration of expansion possibilities.Phase 1: Analysis 29 | Phase 1: Analysis Problem definition and analysis is the critical first phase in an integration project. • TIBCO BusinessWorks Concepts . Because of the TIBCO BusinessWorks distributed architecture. What are the transports being used? In the example. By clearly identifying and analyzing the problem. As a rule. and an application server. etc. The design team can use these objects during project design. The application service is accessed via JMS. An engineering analysis goes a step further and identifies the components of the integration project. the adapter services are accessed using TIBCO Rendezvous. the web service that supplies shipping information. Here are some questions that are commonly asked during analysis: • What are the services my business process will access? In the example. it is tempting to start development right away. See Phase 1: Analysis on page 39 (Chapter 3). it makes sense to start with a business analysis that includes a problem definition. Because the TIBCO BusinessWorks graphical user interface is so easy to use. TIBCO BusinessWorks implicitly supports analysis and design by offering a set of objects representing services and activities as the basis for the project flow. you avoid pursuing dead-end design paths and the steps to solve the problem become apparent. detailed problem analysis results in a faster over-all development process. the process flow. The web service is accessed via SOAP.

If not. all machines within an administration domain are expected to be in the same network subnet. however. During deployment testing and production. you must specify the administration domain to which a machine belongs. Before installing the software. Domain setup is different during development and during deployment testing and production. Which components (adapters or process engines) should run on which machine? Where should I run my TIBCO Administration Server? Who are the users that need to make changes to the project? For which component does each user need to make changes (e. all machines that need to share work should be part of the same administration domain. Ask yourself these questions: • For development environments.g. This section gives an overview of planning the administration domain setup and installing the components. you should therefore determine what resources should belong to a administration domain. one TIBCO Administration Server manages the project and the ACL (Access Control List). • During development. each developer may install an Administration Server and set up an administration domain on their machine and develop and test the project there. What machines do I need to run my project? By default. You can. • Planning the Domain When you install a TIBCO BusinessWorks component. do I need to share work with other developers? If so.30 | TIBCO BusinessWorks Methodology Phase 2: Domain Setup and Installation A TIBCO administration domain is the set of software and hardware resources used by your integration project. See TIBCO Administration Domain on page 9 for an overview. set up your system to use TIBCO Rendezvous rvrd and can then use TIBCO BusinessWorks across subnets. this machine can have its own administration domain. start or stop an adapter)? Who are the users that need to view information about the running project? Which component(s) does each user need to view? • • • • • TIBCO BusinessWorks Concepts . Only authorized users can create and save projects or start and stop processes.

Phase 2: Domain Setup and Installation 31 | • How will the project handle load balancing and fail-over? While the current release of TIBCO BusinessWorks does not explicitly support load balancing and fail-over. 2. The PeopleSoft and Siebel adapters run on machine 2. The PeopleSoft and Siebel systems run outside the administration domain. 3. Install the TIBCO Administration Server and specify the administration domain name. The process engine runs on machine 3. and the administration user and password. The illustration below shows a possible administration domain setup for the example scenario: • • • • The TIBCO Administration Server runs on machine 1. Install other TIBCO BusinessWorks components such as process engine(s) or TIBCO Designer instances into the administration domain. Install adapters into the administration domain. Figure 15 Domain setup for example program PeopleSoft system PeopleSoft adapter Siebel adapter Process engine Siebel system Administration Domain TIBCO Administration Server Installing TIBCO BusinessWorks Components A flexible installer allows you to install one or more TIBCO BusinessWorks components on each machine following these steps: 1. This includes both architecture of your project and cost projections as the project grows. TIBCO BusinessWorks Concepts . you should plan your administration domain to support those features when they become available in the near future.

TIBCO BusinessWorks Concepts . Planning and Configuring User Access It may also be useful at this stage to plan which users should be allowed access to which components. components (adapters and process engines). You add users to the administration domain and specify access privileges for each user via the TIBCO Administrator GUI. you can select any of machine in the administration domain and include it in a deployment configuration. From TIBCO Designer.32 | TIBCO BusinessWorks Methodology The administration domain is used by the different TIBCO BusinessWorks components. From TIBCO Administrator. and process instances in the administration domain. authorized users can monitor machines.

The adapter service can then be used by the activities in your business process and later be invoked at run-time. TIBCO BusinessWorks Concepts . SAP R/3. and accessed using the SOAP Request-Reply activity. even if several users access different adapter instances of that adapter type. a Publish to Adapter activity expects an adapter subscriber service that receives the data being published. you must identify the adapter services precisely. With configuration complete. their location. • This section gives an overview of adapter configuration see Phase 3: Services Configuration on page 55. from an application such as PeopleSoft. For example. from a database. Each type of adapter has its own DTA. for more information. and so on. Adapter subscriber service—Receives data from the source application and sends them to the business process. from a legacy source. Only one DTA needs to run in a network. Adapter server service—Acts as a server in a request-response interaction. The services can then be accessed from the TIBCO BusinessWorks process. To configure an adapter first provide connection information. The following service types are supported: • • • • Adapter publisher service—Sends data from the source application to the business process. you save the adapter service configuration. This includes connection parameters such as the names of the host application. Web services can be configured from TIBCO BusinessWorks or externally. Adapter client service—Acts as a client in a request-response interaction. It then discusses the services used by the example. A Design-Time Adapter (DTA) allows you to access the metadata provided by the adapter at design time. for example. Adapter Configuration Overview Adapters services send data to and receive data from your business process. You then configure a service with the appropriate adapter and save it as part of your project. Data can come. and so on. When designing and implementing the integration project. or from the Internet.Phase 3: Services Configuration 33 | Phase 3: Services Configuration TIBCO BusinessWorks uses different types of services that can be accessed from within the process: • Adapter services are configured using TIBCO Designer and the Design-Time Adapter (DTA).

For additional information. The Shipping web service is configured externally. The adapter is accessed via an Invoke an Adapter Request-Response Service activity. Queue To access the PeopleSoft Order Management system. see the SOAP palette activities and the WSDL file activity in the TIBCO BusinessWorks Process Design Guide. Web Services Overview TIBCO BusinessWorks can function both as a server and a client in a web services interaction. Services Used by the Example The example needs to access four services from which it retrieves or to which it sends information: • • The application server is configured externally. see Phase 3: Services Configuration on page 55.34 | TIBCO BusinessWorks Methodology For more introductory information. It is accessed via a JMS Receiver. To access the Siebel customer service system. you configure a PeopleSoft request-response adapter. A Publish to Adapter activity can then connect the process to the adapter subscriber service. you configure a Siebel adapter subscriber service. It is accessed via a SOAP Request Reply activity. The User’s Guide for each adapter contains detailed set-up information for that adapter. • • TIBCO BusinessWorks Concepts .

It then briefly discusses the activities used in the example scenario. Different activities. Activities can access data from an adapter service. for example. Most processes have one main process. Manual Activities interact with TIBCO InConcert and allow a pool of users to accept outstanding tasks. You can set breakpoints and provide required input as needed. which starts with a process starter activity. and send the data elsewhere. The process can choose from different execution paths depending on certain criteria. You can also see the values of variables as they are passed through the different activities in the process. TIBCO BusinessWorks Concepts . For example. approval of certain orders. it is possible to use the activities in the Manual Work palette. Grouping allows you to create loops. to have one error condition for the group. • • • • An integral part of process design must be testing. Activities can be grouped. This section starts with an overview. manipulate the data. or to group activities as transactions that commit to a database only when all activities in the group are completed. Activities are added to the process. For additional information. if the amount of a purchase order exceeds a certain number. or adding content to a file. see the TIBCO BusinessWorks Palette Reference. querying a database. These loops can be used. See Phase 4: Business Process Design on page 65 (Chapter 6) for more information. a SOAP Event Source activity or a Receive Mail activity can function as process starters. for example. If the business process requires user interaction. Examples include sending email.Phase 4: Process Design 35 | Phase 4: Process Design The flow of business data in your enterprise can be captured by business processes. Overview The TIBCO Designer GUI supports defining business processes with these major elements: • • Each process has a starting and ending point. for example. An process can call different subprocesses as it executes. you could add an additional credit check. TIBCO Designer includes a test mode that allows you to run any of the processes in your project at design-time.

36 | TIBCO BusinessWorks Methodology Activities Used by the Example The example includes all the services (see Services Used by the Example on page 34). A Manual Work activity handles the credit check approval. TIBCO BusinessWorks Concepts . In addition • • A Send Mail activity sends an email to the customer if shipping the order is delayed.

— Specify startup options for each component (command-line process starter or NT service). startup scripts and other information about the different components are sent to the machines to which the components were assigned. The project data store (repository) and the TIBCO Administration Server are updated with the new deployed components. The component or adapter is then visible and accessible at design-time via the TIBCO Designer GUI and at run-time via the TIBCO Administrator GUI. After you have installed the TIBCO Administration Server. Deployment configuration is performed using TIBCO Designer and includes these tasks: — Assign processes and adapter services to different process engines and adapters installed on the machines in the administration domain. — If desired. Specify more than one process engines. • When deployment configuration is complete. As part of that process. • Phase 5: Deployment on page 79 (Chapter 2). you install all components into the same administration domain. you deploy the project. The secondary engines will run in standby mode until they are needed. any machine on which you install a TIBCO BusinessWorks core component or an adapter can be added to the administration domain. which should be running on different machines and use JDBC for checkpointing. — Specify recovery options and alerts for engines and adapters. TIBCO BusinessWorks Concepts .Phase 5: Deployment Configuration and Deployment 37 | Phase 5: Deployment Configuration and Deployment The TIBCO administration domain supports a simple installation and deployment paradigm: • During installation. discusses deployment in more detail. set up your deployment for fault tolerance.

View a domain inventory of all TIBCO products installed in the administration domain.38 | TIBCO BusinessWorks Methodology Phase 6: Production In the production phase. create users for the administration domain and assign them permissions to perform certain activities. Start and stop process engines and adapters. see the TIBCO BusinessWorks Administrator’s Guide. TIBCO Administrator can be used for these tasks: • User Management—Manage the ACL. for example. For detailed information. gives an overview of the most important components of the GUI. TIBCO BusinessWorks Concepts . your project’s components are running on the different machines in the administration domain. Authorized users can monitor the administration domain. Domain Monitoring—View the machines in the administration domain and their CPU and disk usage. Deployment Monitoring and Management—View the status of components and generate tracing information. and all processes. all machines. Recovery is performed automatically as previously specified as part of the deployment configuration. Change the ACL as needed. using the web browser based TIBCO Administrator GUI. • • Phase 6: Production on page 91.

page 40 Step 2: Identify Processes. page 45 Step 5: Design Business Processes. This chapter gives a brief introduction to elements of the analysis phase that typically require special attention. page 41 Step 3: Identify Components.| 39 Chapter 3 Phase 1: Analysis During the analysis phase. Analysis Define & analyze problem Domain Setup Install software & configure domain Services Configuration Configure adapters Process Design Implement & test business processes Deployment Deploy to runtime engine Production Manage & monitor deployments Topics • • • • • • Step 1: Define and Delimit the Problem. page 46 Step 6: Consider Domain Setup. the different departments participating in the integration project must come to a clear understanding of the requirements. page 47 TIBCO BusinessWorks Concepts . page 42 Step 4: Describe Business Events and Objects.

Before you start. For example. the order is sent and all order information. You can only succeed if you understand the scope of the problem. 3. 8. 6. and the deployment parameters. If shipping is delayed. it includes an ID for the order. EasyWare receives orders for computer hardware. it is therefore critical that you have a definition of the problem that is as clear and precise as possible. Each order is automatically entered into the PeopleSoft Order Management system. an email is sent to the customer. the business process checks the shipping schedule.40 | Phase 1: Analysis Step 1: Define and Delimit the Problem The ultimate success or failure of your business integration depends on how clear you are about the problem you are trying to solve. and to allow later expansion for other ways to place orders. 7. The business process receives the incoming order document via JMS. Each order is processed by a customized order capture system built on top of an application server. including the generated Order ID and the shipping information. a working definition of the example scenario could be the following: 1. Otherwise. which is available from an external vendor’s web site. 2. When the PeopleSoft Order Management system acknowledges acceptance of the order. 4. the components involved. Conversion to PeopleSoft format is required. The Siebel system creates a new customer service record based on the information. The goal is to allow customers to place orders through a web site. 5. is entered into a Siebel system. TIBCO BusinessWorks Concepts . Next.

The main process listens for incoming data from the application server. The CheckShippingSchedule process accesses the web site of the shipping company and sends an email to the customer if shipping is delayed.Step 2: Identify Processes 41 | Step 2: Identify Processes A clean design of a complex process consists of a main process that calls subprocesses as needed. in the company’s Siebel customer service system. The problem defined above lends itself to the creation of a process for each task that is performed. 2. 1. It returns the purchase order and the Order ID to the main process. 4. the main process calls the other processes in sequence. When a purchase order arrives. You can use TIBCO Designer to create the four processes and have the main process call the other processes in the appropriate sequence. TIBCO BusinessWorks Concepts . including the Order ID generated by PeopleSoft and the shipping information. The AddtoCustMgmt process enters the order. This process could also update the status of the order in the Order Management system. 3. The AddtoOrderMgmt process enters the order into the PeopleSoft Order Management system.

Web services—Web services are external to TIBCO BusinessWorks but are supported by several activities that are part of TIBCO BusinessWorks. TIBCO BusinessWorks Concepts . a WSDL File shared resource is used by SOAP activities and a JDBC Connection shared resource is used by JDBC activities. A PeopleSoft adapter receives a request and sends data back to the process. Services and Corresponding Activities The business process uses services to retrieve or send data. You can also access documentation for an activity from TIBCO Designer using the What is This option from the right-button menu of the corresponding resource’s menu. To enable this communication. The business process uses a JMS Queue Receiver activity that receives the order. • • • • • Shared Resources Services and Corresponding Activities Transitions and Conditions Mapping Exceptions Many components are activity resources. A complete list of all activities is included in the TIBCO BusinessWorks Process Design Guide. For the problem at hand. • The example discussed in this manual requires the following activities: • • An application server sends the incoming orders over JMS.42 | Phase 1: Analysis Step 3: Identify Components After you have identified the processes. you can use TIBCO adapters. This section discusses some potential components. Shared Resources Some activities use shared resources. you must understand the components of the process. For example. a request-response adapter service is well suited. Adapters can be configured using TIBCO Designer. There are two kinds of services: • Adapter services—The source and target applications your enterprise uses cannot directly talk to each other or to TIBCO BusinessWorks.

the result of the credit check outcome could determine the next activity. Mail Other activities include a Send if shipping is delayed. the Assign Work activity is appropriate for implementing the interaction. • • Request-Response A web service provided by the shipping company is invoked through a SOAP Request Response activity. Transitions and Conditions Transitions go from each activity in the process to the next activity. activity that sends an email to the customer ManualWork Activities The activities in the ManualWork palette are useful for automated business processes that have a few steps which require user interaction. In order to use the activities in the Manual Work palette. TIBCO InConcert must have been installed and users must have been created with TIBCO Administrator and exported to InConcert. for example. See Step 5: Optionally. A positive credit check could result in a different email and placement of the order. In many cases. including the Order ID assigned by PeopleSoft. A negative credit check could result in an email to the customer. For a detailed discussion. A Siebel subscriber adapter service receives the order from a Publish to Adapter activity and enters the order. TIBCO BusinessWorks Concepts . Each activity must have at least one incoming and at least one outgoing transition. Each activity can potentially be called from several other activities or can conditionally call several activities. if a credit check were included in a business process. a Modify Work activity that allows administrators to perform actions on a work item. Other activities in the palette include. see the TIBCO BusinessWorks Palette Reference. For example. into the Siebel customer service system.Step 3: Identify Components 43 | The business process uses an Invoke an Adapter Service activity to interact with the adapter. Add Manual Work Activities on page 72 for some additional information.

44 | Phase 1: Analysis Mapping For each activity in the process there is an appropriate input. or a superset of the incoming process data. integration automation might actually result in decreased productivity because a lot of time is spent on dealing with exceptions. and ultimately deliver a more robust system faster. For example. For the employees of your company. you can make them part of the business process. or data may need to be modified. graceful exception management will result in a noticeable increase in productivity. At times. however. the Send Mail activity uses the customer email address and the Order ID but ignores the shipping address which is also part of the order. TIBCO BusinessWorks Concepts . the Send Mail activity needs input that includes information about the customer and the Order ID. Very often. If exceptions are included in your initial design. Decide on exception handling standards across business phases to make it easier to identify exceptions and understand how they are related. If exception handling is flawed. an activity requires a subset. TIBCO BusinessWorks lets you map the process data to the input of the activity. For example. you should include as much information about exceptions as possible. Exceptions As you analyze your business problem. To give each activity the appropriate input. the output of one activity directly maps into the input of the next activity in the process.

you must describe the events and objects in more detail. At this stage of the analysis. This includes: • • • Know the required data format at each place in the process (and how to get it). you identified the business objects and events. Understand what appropriate actions in case of a business or system-level error could be. TIBCO BusinessWorks Concepts . Know the required data content (and how to get information that is not directly available).Step 4: Describe Business Events and Objects 45 | Step 4: Describe Business Events and Objects Early in the analysis.

Data flow includes both flow of data for the non-exception case and for exception cases. Custom java activities can be used to perform more complex transformation. putting the value from one field into another. PeopleSoft may store phone numbers in a 10-digit format. Data flow may involve mapping. that is.46 | Phase 1: Analysis Step 5: Design Business Processes After you have identified and described the components of the process. For example. It could also involve transformation. Part of massaging the data for each system requires transformation. you determine what the system should do in case of an exception. You can set up transformation using the mapper included with TIBCO Designer. • TIBCO BusinessWorks Concepts . you can prepare the actual design of the business process. while Siebel may use parentheses or dashes as part of the phone number. translating data from one format to another. After you have identified the possible exceptions. This includes: • Activities involved. Data flow. For example. the purchase order is received from a JMS Queue Receiver activity and a Publish to Adapter activity sends the purchase order to a PeopleSoft adapter subscriber service. • Exception flow. that is.

Step 6: Consider Domain Setup 47 | Step 6: Consider Domain Setup After you’ve completed the design of your business process. you should consider the domain setup required to support it. — How many versions of the TIBCO BusinessWorks engine at runtime? If you want to run in fault tolerant mode. TIBCO BusinessWorks Concepts . you should plan on appropriate hardware resources to support it. For example: • • What hardware is required to run the project? Is security an issue that might influence platform choice? What TIBCO software components to you expect to install? — How many versions of TIBCO Designer and the TIBCO BusinessWorks engine during design time.

48 | Phase 1: Analysis TIBCO BusinessWorks Concepts .

page 52 Installing Adapters. page 50 Installing TIBCO BusinessWorks.| 49 Chapter 4 Phase 2: Domain Setup and Installation TIBCO BusinessWorks allows you to progress from project design to deployment and production with minimal configuration and setup. it is important that you understand setup of a TIBCO administration domain and installation of different TIBCO products into the administration domain. For more information. Analysis Define & analyze problem Domain Setup Install software & configure domain Services Configuration Configure adapters Process Design Implement & test business processes Deployment Deploy to runtime engine Production Manage & monitor deployments Topics • • • TIBCO Administration Domain. see TIBCO BusinessWorks Administrator’s Guide. This chapter gives an overview of domain setup and installation. page 54 TIBCO BusinessWorks Concepts . To guarantee that the transitions will be trouble-free.

including the TIBCO Administration server. TIBCO Administration Domain on page 9 gives an overview of a domain’s elements. and pick up alerts sent by those Runtime Agents. which is assisted by a TIBCO Runtime Agent running on each machine in the domain. add deployed projects and machines to a domain. • The advantage of an administration domain is that the components of your integration project automatically know about each other. Manage engines or adapters running in fault-tolerant mode if fault-tolerant setup has been performed.50 | Phase 2: Domain Setup and Installation TIBCO Administration Domain A TIBCO administration domain is a set of hardware and software resources. They can be monitored as a group. that is. Typically. The server is installed only on one machine in the environment and can be accessed with the browser-based TIBCO Administrator GUI. on one machine and develops and tests the project there. Start an stop process engines and adapters. for final testing and production. Later. Manage storage for server-based projects. is shared across the administration domain. TIBCO BusinessWorks supports both authentication and authorization of users that want view access or full access to the run-time components. access to both processes and data stores. The administration domain is managed by a TIBCO Administration Server. TIBCO Administration Server The TIBCO Administration Server manages the administration domain. Manage registration. Send appropriate information to each machine’s TIBCO Runtime Agent when a project is deployed. Understanding the domain before installing the software is important because the domain is set up during installation. the set-up depends on the phase of the project: • During early stages. that is. The Administration Server’s main responsibilities are the following: • Enforce security for the domain. Security. each developer typically installs the complete TIBCO BusinessWorks package. the development team uses one TIBCO Administration Server which manages different components (engines and adapters) running on different machines. • • • • • TIBCO BusinessWorks Concepts .

• Supplies the run-time environment. a TIBCO Runtime Agent (TRA) is automatically installed. That information is then visible via TIBCO Administrator. — The agent is responsible for starting and stopping processes that run on a machine according to the deployment information. — The agent monitors the machine. The TRA has two main functions: • Supplies an agent that is running in the background on each machine. all shared libraries including third-party libraries. TIBCO BusinessWorks Concepts . that is.TIBCO Administration Domain 51 | TIBCO Run-Time Agent When you install a TIBCO BusinessWorks component or a fully integrated TIBCO ActiveEnterprise adapter on a machine.

Figure 16 Installing TIBCO BusinessWorks Install Admininistration Server No Install component Install software Admininistration domain exists? No Want to join? Yes Yes Install component Add component to domain TIBCO BusinessWorks Concepts . If you want to create a new domain. After that. you assign the machine on which you install the component or adapter to the domain. During installation. you can install design-time components. you must first install the administration component on one machine to establish a TIBCO administration domain. During installation. If you install two Administration Servers into the same domain. and adapters. the TRA is installed automatically on that machine. The following diagram illustrates this. failures at design-time and run-time will result. run-time components. you must install an Administration server on the machine from which you create it. or create a new domain. such as TIBCO Designer.52 | Phase 2: Domain Setup and Installation Installing TIBCO BusinessWorks When you install TIBCO BusinessWorks. and install components there. you are prompted for the name of the domain. Each time you install either a TIBCO BusinessWorks component or a fully integrated adapter on a machine. on a second machine. You can either join an existing domain. be sure to deselect the administrative component. When you install TIBCO BusinessWorks components.

Selecting the design-time component also installs TIBCO Designer Process Design and Deployment palettes. If you install two TIBCO Administration Servers on one machine and attempt to create two separate domains on that machine. failures at design-time and run-time will result. the TIBCO Designer GUI is installed.Installing TIBCO BusinessWorks 53 | Installation Components When you install TIBCO BusinessWorks. Runtime Component When you select the run-time component. you are prompted for the name of the administration domain and the name and password for the administration user. TIBCO BusinessWorks Concepts . the TIBCO BusinessWorks engine is installed. Each machine can belong to only one TIBCO administration domain. The GUI allows you to configure adapters and business processes and to deploy projects. Design-Time Component When you select the design-time component during installation. you are prompted to choose one or more of the following components: Administration Component The administration component consists of the TIBCO Administration Server and the tomcat engine. When you install the administration component.

the adapter interacts with the running process and can be monitored using TIBCO Administrator. You must install a TIBCO Administration Server and that server must be running before you install the adapter into an administration domain. When you install a fully integrated adapter. They are configured with a custom TIBCO Designer palette.54 | Phase 2: Domain Setup and Installation Installing Adapters The TIBCO BusinessWorks process engine can work together with any TIBCO adapter. • When you install a fully integrated adapter. It also shows that you can run the adapter in standalone mode if desired. you have the option of installing TIBCO Designer as part of the installation. you can choose to install it stand-alone or as part of a TIBCO administration domain. and password. The illustration below shows how you must install TIBCO BusinessWorks to create an administration domain if none exists or if you do not want to join the one that is currently available. you are prompted for the domain name. Figure 17 Installing an adapter Yes No Want to create one? No Install TIBCO BusinessWorks Run standalone Install adapter Administration domain exists? Want to join? Run standalone Yes Yes Install adapter Add adapter to domain No TIBCO BusinessWorks Concepts . If you select to join a domain. user. At run-time. Each adapter is shipped separately. There are two types of integration between adapters and TIBCO BusinessWorks: • Fully integrated adapters can be installed into a TIBCO administration domain. Any TIBCO adapter can be configured using the TIBCO Designer Generic Adapter palette and can interact with TIBCO BusinessWorks at run-time.

Analysis Define & analyze problem 2. Deployment Deploy to runtime engine 7. page 62 Step 4: Accessing the Adapter Service From the Process. page 56 Step 1: Installing the Adapter. Adapters ensure that the different applications in your enterprise can communicate in real time.| 55 Chapter 5 Phase 3: Services Configuration The first phase in the actual business integration development is configuration of adapter services. 1.Domain Setup Install software & configure domain 5. page 63 TIBCO BusinessWorks Concepts . Process Design Implement & test business processes 6. page 60 Step 3: Configuring the Run-Time Adapter.Configuration Configure adapters Topics • • • • • Introduction: TIBCO BusinessWorks Services. Production Manage & monitor deployments 3. page 59 Step 2: Setting up the Design-Time Adapter.

56 | Phase 3: Services Configuration Introduction: TIBCO BusinessWorks Services In TIBCO BusinessWorks. communication flows in both directions. In a request-response service. TIBCO BusinessWorks supports web services for interaction with the Internet and adapter services for interaction with files. For example. all components of the business process stop. HTTP. TIBCO Rendezvous Data syntax. If the server goes down. The complete interaction consists of two point-to-point messages—a request and a TIBCO BusinessWorks Concepts . the system no longer works. If one machine goes down. Each service is configured separately and can be deployed on a different machine. JMS. services are responsible for publishing or subscribing to business data in a decoupled yet reliable manner. where all components of a business process are running on one server. for example WSDL/SOAP or AE Services Transport. The business process receives data from a service and routes data to a service. The business process coordinates the services in the appropriate way. a process could contain a Publish to Adapter activity that accesses an adapter subscriber service. Examples of services are could be a SendPurchaseOrder activity or a RequestShippingInformation activity. Service descriptions are stored with the TIBCO Administration Server. or different ERP (Enterprise Resource Planning) applications. a service-centric architecture supports self-contained services. • • A one-way operation is executed once and does not wait for a response. for example. Enterprise integration platforms typically use a tightly coupled architecture. Service Characteristics The following characteristics are associated with a service: • • • • Service interface. This loosely-coupled architecture makes it easy to change individual components as needed. for example DTD or XSD schema Invocation Modes Services can be invoked in several ways. for example. all other parts of the process can still run. If any component in the system changes. In contrast. databases. A request-response operation is executed once and waits for one response. XML or ActiveEnterprise message format Data schema.

Service Types TIBCO BusinessWorks includes both web services and adapter services. Communication is in one direction (publisher to subscribers). usually the arrival or creation of data. a subscription service receives data from the business process. WSDL is an XML-formatted language used to describe a Web service's capabilities as collections of communication endpoints capable of exchanging messages. or WSDL. Enterprise application adapters—Allow you to interact with enterprise applications such as Siebel. The activities you need are included in the SOAP palette. Subscription means incoming information is processed on an as-needed basis. Web services are accessed by SOAP activities. Adapter services allow you to communicate with enterprise applications or interact with other incoming and outgoing data. Publication and subscription are driven by events.Introduction: TIBCO BusinessWorks Services 57 | response. You can use TIBCO BusinessWorks both to set up a web services server or to set up a web services client. potentially multiple times. They include: • • Technology adapters— Allow publication to and subscription from files and databases. The interaction is only considered complete after the response has arrived. • • Publication (notification) means an operation sends information on an as-needed basis. Web Services TIBCO BusinessWorks supports Web Services Description Language. Adapter services are accessed by activities available in the TIBCO Designer ActiveEnterprise Adapter palette that you can add to your business process. potentially multiple times. TIBCO BusinessWorks Concepts . SAP R/3. and PeopleSoft. Adapter Services Adapter services allow your business process to publish data or subscribe to data used by the enterprise. A publication service sends data to the business process.

58 | Phase 3: Services Configuration Adapter Service Configuration Steps Configuring an adapter service consists of these steps. discussed in this chapter: • • • • Step 1: Installing the Adapter on page 59 Step 2: Setting up the Design-Time Adapter on page 60 Step 3: Configuring the Run-Time Adapter on page 62 Step 4: Accessing the Adapter Service From the Process on page 63 TIBCO BusinessWorks Concepts .

TIBCO BusinessWorks therefore does not include adapters in its base package. specify the name of the TIBCO administration domain and specify the administrative user and password for the administration domain.Step 1: Installing the Adapter 59 | Step 1: Installing the Adapter Different business processes have to connect to different enterprise applications. specify the (already existing) TIBCO administration domain and the administrative user and password. As part of the installation. See TIBCO Administration Domain on page 50. You must establish the TIBCO administration domain and it must be running and accessible before you install the adapter. Install TIBCO BusinessWorks. A TIBCO administration domain is a set of hardware and software resources. TIBCO BusinessWorks Concepts . Install the adapter. Instead. Adapter installation therefore consists of these steps: 1. The administration domain is set up to include one or more machines. a palette for that adapter becomes available from TIBCO Designer the next time you start it. 2. During installation. After installation. you install the adapter you need separately and add it to the TIBCO administration domain during installation.

Figure 18 shows how you would drag a Siebel Adapter Configuration into the design panel. After you have established design-time connection parameters. In the project tree panel. TIBCO BusinessWorks Concepts . double-click the adapter. Specify connection information for the application you want to access so your design-time adapter can connect. the Services palette is displayed. you can use the TIBCO Designer GUI to specify schema information from the adapter. Launch the TIBCO Designer GUI. In the palette panel. To set up the design-time adapter. Figure 18 Adding an adapter to the project Drag the adapter resource into the design panel 3. 2. Select the adapter palette and drag an adapter resource from the palette panel into the design panel and name the adapter service. then select its Adapter Services folder to open it. follow these steps: 1. The appropriate adapter palettes should now be included. 4. The adapter service has been named SiebelPublisher.60 | Phase 3: Services Configuration Step 2: Setting up the Design-Time Adapter The TIBCO Designer GUI allows you to connect with the source or target application for the adapter at design time using a design-time adapter.

Specify the data the adapter should publish or subscribe to interactively. start the design-time adapter.Step 2: Setting up the Design-Time Adapter 61 | 5. Figure 19 Adding a service to an adapter Drag the adapter service into the design panel 6. Drag an adapter service. TIBCO BusinessWorks Concepts . 8. 7. a publisher service. From a command prompt. from the palette panel into the design panel. Save the adapter. for example. The configuration panel is updated to allow you to configure the service.

see the documentation for that adapter. or different information.62 | Phase 3: Services Configuration Step 3: Configuring the Run-Time Adapter With the design-time adapter running. You can either specify the same information as that used by the design-time adapter. You configure each adapter service separately using the tabs in the configuration panel as follows: • Specify run-time connection information using the Runtime Connection tab. TIBCO Designer allows you to specify simple tracing to a file or standard out using the configuration panel directly. • If your adapter uses advanced features. TIBCO BusinessWorks Concepts . available via Help > Help For from TIBCO Designer. For additional information about adapter configuration. Define adapter services and choose schema from the pop-up list provided via the design-time adapter. you can specify a different host machine or user name or password. • Specify tracing information if desired. such as tracing to a network sink. For example. You can also specify advanced tracing. The exact process for defining services may vary slightly depending on the adapter you are using. such as Advisory activities. you can configure the run-time adapter. you can configure them using the Advanced folder of the adapter.

Creating a process is explained in Phase 4: Business Process Design on page 65. You have the following choices: — Publish to Adapter—Publishes data from the process to an adapter. Invoke an Adapter Request-Response Service—Communicates client) with an adapter request-response service. then open the ActiveEnterprise palette. Figure 20 Adding activities that access adapter services Adapter 2. a Publish to Adapter activity interacts with a Siebel subscriber. Drag the activity that accesses the service you need into the design panel. which subscribes to data coming from the process and passes the data to the target application. you can access adapters as follows: 1. TIBCO BusinessWorks Concepts . you can access it from the process definition.Step 4: Accessing the Adapter Service From the Process 63 | Step 4: Accessing the Adapter Service From the Process After you have configured the adapter service. Once a process is part of your project. Adapter Subscriber—Subscribes — — to incoming data published by the (as a adapter. Select the process definition. In the example above.

Wait for Adapter Message—Waits for the receipt of a message from the publication service of the specified adapter. 4. Save your project. TIBCO BusinessWorks Concepts . Respond to Adapter Request—Sends a response to an adapter for a previously received request. Wait for Adapter Request—Waits for the receipt of a request from a request-response invocation service. 3. Specify the adapter information in the configuration panel.64 | Phase 3: Services Configuration — — — — Adapter Request-Response Server—Starts a process based on the receipt of a request from an adapter.

| 65 Chapter 6 Phase 4: Business Process Design This chapter discusses business process design. page 72 Step 6: Create Transitions Between Activities. page 76 Step 9: Test the Process. page 70 Step 4: Add Activities. page 71 Step 5: Optionally. You can also display information about each resource by choosing its What is This right-button menu command in TIBCO Designer. Analysis Define & analyze problem Domain Setup Install software & configure domain Services Configuration Configure adapters Process Design Implement & test business processes Deployment Deploy to runtime engine Production Manage & monitor deployments Topics • • • • • • • • • • Introduction. Group Activities As Needed. page 69 Step 3: Add a Process Starter. Business process design is discussed in more detail in the TIBCO BusinessWorks Process Design Guide. page 75 Step 8: Optionally. you create your business process using predefined activities and add conditions and mapping as appropriate. page 68 Step 2: Create Process Definitions. Using the TIBCO Designer GUI. page 66 Step 1: Define Shared Resources. page 77 TIBCO BusinessWorks Concepts . Add Manual Work Activities. page 74 Step 7: Perform Mapping and Transformation for Each Activity.

66

| Phase 4: Business Process Design
Introduction
In an integrated enterprise, business processes manage the flow of information between different data sources and destinations. The business processes receive information, process it if needed, and hand it off as appropriate.

Business Processes
In many companies, the business rules that tie enterprise applications together are handled by custom-written code or even by manual processes. TIBCO BusinessWorks allows you to establish this data flow using activities available in the TIBCO Designer process design palettes. You design the process using predefined activities and can execute your process without writing a lot of custom code. The following diagram illustrates a business process flow that describes the business rules between the various systems in an enterprise. Figure 21 Business process flow
Process Order
IF arrived, THEN IF order ID returned, THEN IF shipping available, THEN SHIP ORDER ELSE hold order & send email update Cust Mgmt system

Manage Order Entry
IF arrived, THEN return order ID ...

Manage Shipping Update Cust. Mgmt System
IF order, THEN enter order enter order ID enter shipping information IF request, THEN IF schedule < 2 days THEN return OK IF schedule > 2 days THEN return HOLD

TIBCO BusinessWorks Concepts

Introduction 67

|

Process Design Steps
Process design consists of a number of steps discussed in this chapter. • • • • • • • • • Step 1: Define Shared Resources on page 68 Step 2: Create Process Definitions on page 69 Step 3: Add a Process Starter on page 70 Step 4: Add Activities on page 71 Step 5: Optionally, Add Manual Work Activities on page 72 Step 6: Create Transitions Between Activities on page 74 Step 7: Perform Mapping and Transformation for Each Activity on page 75 Step 8: Optionally, Group Activities As Needed on page 76 Step 9: Test the Process on page 77

The steps discussed in this chapter do not necessarily have to be performed in this order. For example, you could define shared resources as needed or add transitions each time you add an activity

TIBCO BusinessWorks Concepts

68

| Phase 4: Business Process Design
Step 1: Define Shared Resources
Shared resources allow activities to share information. For example, you can define a JDBC Connection resource, then use it in any of the JDBC activities in your business process. You may also choose to define the process and create shared resources as needed. Shared resources are available in the Shared palette and include and so on.

Configuration

Rendezvous Transport, JDBC Connection, JMS Connection,

To define a shared resource, follow these steps: 1. In the palette panel, select the Shared
Configuration

palette.

2. Drag and drop the icon for the resource you need from the palette panel to the design panel. 3. Name the resource and specify its configuration information in the configuration panel, then click Apply. You can now use the shared resource in any activity that requires it. For example, the JMS Queue Receiver activity the example uses to connect to the application server requires a JMS Connection shared resource. Figure 22 Shared resources in your project

TIBCO BusinessWorks Concepts

It sends an email to the customer if shipping is delayed. activities are added in sequence. otherwise enters the order into the Siebel system right away. which is called ProcessOrder. Subprocesses also potentially allow reuse of business process components. you create process definitions by dragging Process Definition resources from the palette panel to the design panel. You name each process definition and give the process a description. For complex business processes. then transitions are added as appropriate. then add activities to the process. • TIBCO BusinessWorks Concepts . then calls the ShippingSchedule process: The ShippingSchedule process retrieves information about the shipping schedule from the Shipping web site and adds shipping information to the order. Figure 23 Adding process definitions to your project For simple business processes. When it arrives. Our example program includes several different processes: • In the main process.Step 2: Create Process Definitions 69 | Step 2: Create Process Definitions In TIBCO Designer. the main process first interacts with the Order Management system. it makes sense to design a main process and several subprocesses. a JMS Queue Receiver waits for input. Using subprocesses makes your process easier to understand and debug.

Figure 24 Adding a process starter Note that the default Start activity that is included with each process you instantiate is not a process starter. A Start activity must be called explicitly from another process.70 | Phase 4: Business Process Design Step 3: Add a Process Starter A process starter waits for input from an external process and creates a process instance each time the input arrives. For example. In our example. Drag the process starter into the design panel. 4. The process starter activity replaces the default Start activity. TIBCO BusinessWorks Concepts . the JMS Queue Receiver is the process starter. follow these steps: 1. Select the palette for the process starter in the palette panel. A process starter could also be polling a directory and start whenever a file is added. then click Apply. Choose the process to which you want to add the process starter 2. 3. To add a process starter. Specify configuration information. the process could be waiting for a document that arrives from an application server using JMS.

for example. but activities can also perform internal processing. If the palette is not visible. When you select a process definition. A general-purpose Java Code activity allows you to write and execute standard Java code to perform custom processing within your process definition. To add an activity to the process definition in TIBCO Designer. Each palette has a set of activities that can be performed for that palette. the ActiveEnterprise Adapter palette has activities that can publish messages to a specified adapter or invoke an operation by way of an adapter. Select the appropriate palette. For example. 3. The JMS palette includes activities such as JMS Queue Sender and JMS Queue Receiver. make sure you have selected the appropriate parent resource and make sure the palette has not been closed. Drag the activity into the design panel. Figure 25 Adding activities TIBCO BusinessWorks Concepts . follow these steps: 1. Select the activity and specify configuration information about it. activities become available on the various TIBCO Designer palettes. Activities are generally operations that interface to external systems. 2.Step 4: Add Activities 71 | Step 4: Add Activities Activities are the individual units of work within a process definition. the originator and address for a Send Mail activity.

This activity allows you to download a document from an existing manual work task into a process variable. Workflow Connection— The connection to the TIBCO InConcert workflow server. The functionality is implemented by two shared configuration resources and four activities: Shared Configuration Resources • Workflow Schema—The data associated with a ManualWork task. Microsoft Word. An example of a document is a loan application that must be attached to a credit request. This server is used to track and manage manual tasks. int. TIBCO BusinessWorks Concepts . Documents can be uploaded or downloaded to a manual work task by way of the web interface TIBCO BusinessWorks provides for managing manual work tasks. The document may be any type. A workflow schema supports string. and document data types.72 | Phase 4: Business Process Design Step 5: Optionally. The process definition can either wait for the user to complete the work or it can continue processing and later query for the status of the task. Add Manual Work Activities The activities in the Manual Work palette are useful for automated business processes that have a few steps that require user interaction. This is the data a user needs to complete the task. • Get Work Status—Retrieves the current status of a task that was previously created with the Assign Work activity. • Download Document—Manual work schemas can contain elements to hold documents. Normally you use this activity to determine if the task has been completed or if there are any errors. This could include handling of unexpected situations or other activities such as credit approval or handling of customers from abroad if the company usually deals with local customers. and so on. for example. A user then acquires the task. The user can change any of the data associated with a task. date. and completes the work. views the data supplied by the activity. PDF. • Manual Work Activities • Assign Work—Creates a new task (with associated data) and assigns it to the specified pool of users.

Step 5: Optionally. Add Manual Work Activities 73 | • Modify Work—This activity allows administrator users to change the status of an existing task created with the Assign Work activity to one of the following: — Update — modifies the data associated with an uncompleted task — Complete — completes the task — Reassign — reassigns the task to a pool of users • Wait for Completion—Waits for the completion of the task for the specified period f. TIBCO BusinessWorks Concepts . This is useful if the timeout for the Assign Work activity has passed and you wish to wait for an additional amount of time.

You use XPath syntax to define conditions.74 | Phase 4: Business Process Design Step 6: Create Transitions Between Activities You use transitions to connect activities to form a process flow. Arrows are unidirectional. you can group them using the GUI. A transition is represented by an arrow between two activities. TIBCO BusinessWorks Concepts . Adding Transitions To add transitions. If it does not. If your process definition includes cyclical subprocesses (loops). After an activity completes. For example. if the shipping schedule indicates a delay in shipping the order. all transitions whose conditions are met are taken. you want to notify the customer and enter the information into the customer service system. Conditions A transition can optionally specify a condition. Control flow in a process definition must proceed sequentially beginning with the starting activity and ending with the End activity. you just enter the information into the customer service system. The condition determines whether a transition is taken when an activity completes processing. click the transition tool on the menu bar to draw transitions between activities. You can have transitions from one activity to many other activities. and you cannot draw a transition to a previously executed activity.

and the correct XPath expression appears automatically. TIBCO BusinessWorks Concepts . you map the process data to the activity input. However. Then open a blank text document and choose Paste. Normally. The XSLT is displayed in your text document. you can right-click on any node in the input schema and choose Copy from the popup menu.Step 7: Perform Mapping and Transformation for Each Activity 75 | Step 7: Perform Mapping and Transformation for Each Activity As data flow through your business process. When you specify the input schema for an activity. You do not need detailed knowledge of XPath to create simple expressions. if you are familiar with XSLT and you wish to see the actual code. The activity input is the list of input values that are required or optional for the activity. you can drag and drop items from the process data schema to the activity input schema. you do not need to examine the XSLT code generated by the mappings. For example. an email is sent upon return to the main process. The email address information could be mapped from the original order to the mail activity’s input fields. For the most part. TIBCO Designer displays the available process data and the activity’s input represented as schema trees. You can conditionally map the process data to the input using XPath expressions. • For each activity. when the ShippingSchedule process fails. • The process data is the list of available data items within the process at the point where the activity is located (an activity has access to all output data from any activity that is executed before it in the process definition). On the Input tab of each activity. the specification is represented internally as Extensible Stylesheet Language Transformation (XSLT) code. different activities require different components of the data. Each item in the activity input schema has an expression field for specifying the contents of the item.

Create sets of activities that participate in a transaction. • • TIBCO BusinessWorks Concepts .catch block in Java. Create sets of activities that are to be repeated. Group Activities As Needed Groups are used to specify related sets of activities.. This type of group is similar to a try.76 | Phase 4: Business Process Design Step 8: Optionally. Activities within the group that can take part in a transaction are processed together or rolled back. depending upon whether the transaction commits or rolls back. Grouping allows you to create loops. The main uses of groups are the following: • Create a set of activities with only one condition for the group. This allows instead of trying to individually catch errors on each activity.. You can repeat the activities once for each item in a list. or if an error occurs. until a condition is true.

Step Into SubProcesses. In test mode. When your process definition operates as expected. the next step in your integration project. You must exit test mode to make changes. For example.Step 9: Test the Process 77 | Step 9: Test the Process Once the process definition is complete. if the process starter is listening for a TIBCO Rendezvous message. in more detail. you cannot change your process definition. If your started multiple process instances. 4. in the TIBCO BusinessWorks Administrator’s Guide. Once you are in test mode. Use the toolbar buttons (Pause Testing. The activity’s current data is displayed on the Input and Output tabs. Once the engine is started. 5. 2. Select the process definition you wish to test in the project panel. Click the Start/Resume Testing icon to create a process instance from the displayed process definition. Click the Start Test Mode icon on the toolbar. Set breakpoints in the process definition at points where you wish to stop a running process and examine its state. Start/Resume Testing) to either continue through the process instance or to stop the current process instance. a TIBCO BusinessWorks engine is started to perform the processing specified in the process definition. select the desired process instance from the list of processes in the toolbar. you can go on to deployment. Entering the testing environment starts a TIBCO BusinessWorks engine. you can perform preliminary testing from TIBCO Designer. publish a message on the expected subject. the test mode icon displays on the toolbar to let you know you are in test mode. This starts a TIBCO BusinessWorks engine that will execute the processes. If necessary. TIBCO BusinessWorks Concepts . 6. Start a process by creating an event that the process starter is expecting. 7. 8. Testing a process definition typically involves these steps: 1. The engine starts process instances based on the process definitions stored in your project. Stop Testing. Examine the process data by selecting any of the activities in the process. supply input data to the process starter. The testing environment displays the running process definitions and highlights the currently executing activity. which is discussed in Phase 5: Deployment on page 79 and. Step to Next Activity. 3. The TIBCO BusinessWorks testing environment allows you to step through your process models and find sources of errors.

78 | Phase 4: Business Process Design TIBCO BusinessWorks Concepts .

page 89 TIBCO BusinessWorks Concepts .| 79 Chapter 7 Phase 5: Deployment For the success of your integration project. page 83 Step 2: Create and Test Your Project. page 80 Step 1: Create and Populate the Administration Domain. Analysis Define & analyze problem Domain Setup Install software & configure domain Services Configuration Configure adapters Process Design Implement & test business processes Deployment Deploy to runtime engine Production Manage & monitor deployments Topics • • • • • Introduction. Because TIBCO BusinessWorks uses the TIBCO administration domain and allows you to perform deployment configuration from the TIBCO Designer GUI. page 85 Step 3: Add Deployment Configuration Information. ease of deployment is at least as important as ease of design. For more information. This chapter gives an overview of the deployment of a TIBCO BusinessWorks integration project. page 86 Step 4: Deploy Your Project. see the TIBCO BusinessWorks Administrator’s Guide. deployment is a relatively simple task.

TIBCO BusinessWorks Concepts . • • You use the TIBCO Designer GUI to assign process engines and adapters to the different machines in the administration domain. administrator must manually keep a record of the different configurations that were tested. The administrator must tweak the configuration files for different components on different machines.80 | Phase 5: Deployment Introduction When you have completed and tested the first prototype of your integration project in the development environment. in contrast. In a traditional business integration project. you are ready to deploy it to a testing environment. allows you to use the TIBCO Designer GUI to create a deployment configuration and then deploy the project. You then click the Deploy button and TIBCO Designer saves the project and sends scripts and other information to each machine that has been assigned a component. To optimize the configuration. TIBCO BusinessWorks. domain configuration is a labor-intensive process that is likely to require multiple iterations before all components are in place.

All components now become visible in the TIBCO Administrator GUI (but are not started). The built-in test mode is used for preliminary testing and debugging of the business process(es). the developer starts each component (adapter and process engine). Using TIBCO Designer. The TIBCO Administration Server sends all necessary information to the individual machines. and deployment info 4 Deployment project with adapters deployed project 1. processes.Introduction 81 | TIBCO BusinessWorks Project Phases When process design is complete and all testing from the TIBCO Designer GUI results in success. As a result. all process starters are waiting for the events that cause them to create process instances. the developer configures adapter services and saves the project with configured adapters. Figure 26 Project development phases 1 Services Configuration 2 Process Design project with adapters and processes 3 Deployment Configuration project with adapters. the developer configures activities for the business process(es) and saves the project. From TIBCO Designer. 4. 3. the developer prepares the deployment configuration by assigning each adapter and each business process engine to a machine in the administration domain. 2. the project is ready for deployment. Using TIBCO Designer. At this stage. TIBCO BusinessWorks Concepts . Different adapters could potentially be configured by different developers and included in one project. The illustration below shows how a project moves through the development and deployment phases. From TIBCO Administrator. Using TIBCO Designer. which now includes process definition(s). the developer deploys the project. the developer moves from the TIBCO Designer development GUI to the TIBCO Administrator run-time GUI and performs these tasks: 1.

you undeploy the project and redeploy it from TIBCO Designer. the developer can monitor the different processes running on the different machines. the project can be modified and saved from TIBCO Designer. In that case. Using TIBCO Administrator.82 | Phase 5: Deployment 2. Deployment Steps The rest of this chapter discusses all steps required for a successful deployment in more detail: • • • • Step 1: Create and Populate the Administration Domain on page 83 Step 2: Create and Test Your Project on page 85 Step 3: Add Deployment Configuration Information on page 86 Step 4: Deploy Your Project on page 89 TIBCO BusinessWorks Concepts . Instead. the TIBCO BusinessWorks engine creates a process instance. If appropriate. Each time an event arrives that triggers a process starter. 3. If you make changes in the deployment configuration. you stop and start the modified process to have the changes take effect. redeployment is not required. which uses the associated process definition to process the incoming data.

TIBCO Administrator. and can be changed as business increases. You can then deploy the project from TIBCO Designer onto your own machine and perform early testing there. Assign Software to Different Hardware Resources Software components include the TIBCO BusinessWorks components (TIBCO Designer. A project cannot be deployed to machines in two different TIBCO administration domains. The administration domain is set up when TIBCO BusinessWorks is installed to include one or more machines. and the business processes on a third machine. A TIBCO administration domain is a set of hardware and software resources. TIBCO BusinessWorks engine) and adapters integrated with TIBCO BusinessWorks. • TIBCO BusinessWorks Concepts . and a machine cannot belong to two different TIBCO administration domains (just as it cannot belong to two network domains). you may decide to install all software components on one machine. During development. You may decide to run the TIBCO Administration Server on one machine.Step 1: Create and Populate the Administration Domain 83 | Step 1: Create and Populate the Administration Domain A project is always deployed to machines in one administration domain. projects are saved inside the domain. you should set up a TIBCO administration domain that is similar to the administration domain you expect to use during production. When you are ready for production testing. the adapters on a second machine. • During development and early testing. The number of machines you choose depends on the processing power your project needs.

TIBCO BusinessWorks supports authentication and authorization for both data stores and components (business processes or adapters) in the administration domain. or stop process engines or adapters from the TIBCO Administrator GUI. Only authorized users may view. start. Figure 27 TIBCO administration domain Domain Machine A TIBCO BusinessWorks Engine TIBCO Adapter for PeopleSoft Machine B TIBCO Adapter for Siebel Machine C TIBCO Administration Server TRA TRA TRA Authorize Users for Different Tasks The second part of administration domain configuration is user management. That means: • • Only authorized users may access or save a server-based project to the domain data store from the TIBCO Designer GUI.84 | Phase 5: Deployment The picture below illustrates a sample TIBCO administration domain. TIBCO BusinessWorks Concepts . A user with full administrative privileges can create users and authorize them for different components of the system.

Step 2: Create and Test Your Project 85 | Step 2: Create and Test Your Project You create and test your project using the TIBCO Designer GUI. as discussed in the previous chapters. it is then administered by the TIBCO Administration Server and available throughout the administration domain. You must save your project as a server-based project for deployment. It is recommended you save your project as a server-based project. you can prepare a deployment configuration using the TIBCO Designer deployment palette. TIBCO BusinessWorks Concepts . When you are satisfied with your project and want to test it in a distributed environment.

2. The Administration Server updates the configuration panel so all machines in the administration domain become selectable from a pop-up menu. drag a Deployment Configuration resource from the Deployment palette into the design panel. Choose a machine from the pop-up menu and click Apply. you can add additional Machine resources the same way. TIBCO BusinessWorks Concepts . From the Deployment palette. 3. This information helps you decide which processes to assign to which machine. 1. Figure 28 Adding a deployment configuration to the project If other machines are registered in your administration domain.86 | Phase 5: Deployment Step 3: Add Deployment Configuration Information After you have created and tested the project. Select the Deployment Configuration resource. When you drag a machine into the design panel. You do so using the TIBCO Designer Deployment palette. Using TIBCO Designer. drag a Machine resource into the design panel. you must assign each component (adapter or business process) to a machine. its characteristics are displayed in the configuration panel.

Fault-tolerant setup is discussed in the TIBCO BusinessWorks Palette Reference and also available via online help. On second failure. You can also specify recovery options. Figure 29 Adding a process engine to the deployment configuration 5. Optionally. — Specify which engine should be the primary and secondary servers. a process should just be restarted. manual. or disabled) if you run the component as a service. you could specify that on first failure. 6. For each adapter or process engine. TIBCO BusinessWorks Concepts .Step 3: Add Deployment Configuration Information 87 | 4. Select an adapter or process engine from the project tree and assign it to a machine by dragging it into the design panel. — Set up a JDBC Recovery Storage for each engine. you can select a startup type (automatic. For example. you can set up the deployment in Fault-Tolerant mode: — Set up process engines on multiple machines. the process should be restarted and an email should be sent.

which now includes configuration information. Save your project.88 | Phase 5: Deployment Figure 30 Adding recovery options 7. You are now ready to deploy your project. TIBCO BusinessWorks Concepts .

Step 4: Deploy Your Project 89 | Step 4: Deploy Your Project After you have configured the deployment configuration. DO NOT modify the script and other files. Select the deployment configuration and click the Deploy icon Designer toolbar. As a result: — An icon for this deployment becomes visible from the TIBCO Administrator GUI. — Rulebases that describe the error recovery and alert behavior. — Monitoring for the state of each component starts. TIBCO BusinessWorks Concepts . TIBCO BusinessWorks registers the deployed project with the Administration Server. • TIBCO BusinessWorks prepares and distributes to each machine: — A startup script to launch the process on that machine. TIBCO BusinessWorks performs these tasks: • • TIBCO BusinessWorks saves the project as a server-based project. the machines in the domain are updated to show the components that were deployed. you deploy the project from TIBCO Designer. After this information has been sent to each machine. — In the TIBCO Administrator GUI. your deployment may become inconsistent. in the TIBCO What Happens When You Deploy A Project When you click the Deploy icon. you can start the project components from the TIBCO Administrator GUI. If you do.

Before you uninstall or reinstall TIBCO BusinessWorks. You do not need to undeploy and redeploy a project unless you have made changes to the deployment configuration changed the authorized user of a component. Select the Deployment Configuration for the project in TIBCO Designer.90 | Phase 5: Deployment Deploying and Undeploying Projects A deployed project can be monitored and managed from TIBCO Administrator. To undeploy a project: 1. 2. you must stop all TIBCO BusinessWorks processes and must undeploy all projects. Just save the project from TIBCO Designer and stop and start the component in which the change was made. You can a undeploy project to remove it from the display. Click the Undeploy icon in the toolbar. TIBCO BusinessWorks Concepts .

page 94 Domain Monitoring and Management. This chapter gives an overview of available functionality. page 92 User Management. The TIBCO Administration Server and the TIBCO Administrator GUI together support your deployed TIBCO BusinessWorks products at run-time. page 95 Deployment Monitoring and Management.| 91 Chapter 8 Phase 6: Production During the production phase. Analysis Define & analyze problem Domain Setup Install software & configure domain Services Configuration Configure adapters Process Design Implement & test business processes Deployment Deploy to runtime engine Production Manage & monitor deployments Topics • • • • Introduction. page 98 TIBCO BusinessWorks Concepts . you monitor and manage TIBCO BusinessWorks deployments.

Machines outside the administration domain can view the TIBCO Administrator GUI using a web browser. • The first machine runs the Administration Server.92 | Phase 6: Production Introduction After the integration development team has configured and deployed the integration project. Architecture TIBCO Administrator consists of the TIBCO Administration Server and the TIBCO Administrator GUI. The second machine runs two adapters. alerts. • The illustration below shows an administration domain with 3 machines in the domain. Start and shutdown commands are sent from the Administration Server to the appropriate TRA. which in turn starts or stops the process. and the process instances and components running on each machine and makes them available via the TIBCO Administrator GUI. • The Administration Server receives information about CPU and memory usage. see the TIBCO BusinessWorks Administrator’s Guide. This chapter gives an overview of the architecture and of the user management. All three server components run as a single process. The information entered in the GUI is sent by the Administration Server to the TRA on the machine running the adapter. the process engine is managed by the Administration Server via the TRA. • • TIBCO BusinessWorks Concepts . The adapters are started via the TIBCO Administrator GUI. The TRA starts and stops the adapter and also sends information about component and machine status to the Administration Server for access via the GUI. Each user sees only the components for which s/he is authorized. and deployment management options. you can use the TIBCO Administrator GUI for monitoring and management. Just like the adapters. which contains an embedded Repository Server for managing data stores. The TIBCO Administrator GUI allows users to start and shut down components. The third machine runs a process engine. The Administration Server includes an application server component for HTTP communications and a repository server component for data store management. administration domain monitoring and management. For more detailed information. The Administration Server interacts with each machine in the administration domain via the TIBCO Runtime Agent (TRA) running on that machine.

View trace files and throughput. Domain Monitoring and Management—View the status of machines and components running on machines in the domain. TIBCO Administrator allows you to remotely access all deployments in your administration domain. Deployment management—View all running components and stop and restart them as needed. which includes the TIBCO Administration Server and the TIBCO Administrator GUI. Depending on your security privileges.Introduction 93 | Figure 31 Communication inside a TIBCO administration domain Process Engine Administrator GUI WWW HT TP Administrator GUI WWW Repository Server Administration Server TRA HTTP Adapter 1 TRA Adapter 2 Monitoring and Management Options At run-time. TIBCO BusinessWorks Concepts . you may be able to perform one or more of the following tasks. • • • These aspects of monitoring and management are supported by TIBCO Administrator. then give each user view or execute privileges for TIBCO Administrator GUI elements or project repositories (data stores). • User Management—Add users and passwords to the administration domain for authentication. Deployment monitoring—Monitor the status of each deployment component (process engine and adapter) and process instance and the status of the machines executing them. Start and stop components as needed.

94

| Phase 6: Production
User Management
The TIBCO Administrator User Management module allows authorized users to specify security options for a TIBCO administration domain. Security has two components: Authentication. Specify users and passwords. Authorization. Give users access to individual components in the TIBCO administration domain. By default, the administrative user for the administration domain has privileges to create users and assign privileges. That user can create additional users with the same full access privileges if appropriate. TIBCO Administrator also allows you to export users to TIBCO InConcert for manual activities management.

Roles
TIBCO Administrator allows you to create a roles tree and assign users to one or more roles. You can then perform authorization on a per-role basis. This capability is critical, for example, if a large number of users need read access to information about running projects but only a few users should be authorized to start and stop the project.

Authorization
TIBCO Administrator allows privileged users to authorize users for GUI Access or Data Access (or both). • GUI access is given on a per-tab basis. For each tab you can select in the TIBCO Administrator GUI, you can specify which users are allowed read or write privileges. Data access is given on a per-data store basis. A repository data store is associated with each project. You can set various levels of access (read, write, variables) for data stores of each deployed project and for the system data store.

TIBCO BusinessWorks Concepts

Domain Monitoring and Management 95

|

Domain Monitoring and Management
The Domain module allows you to monitor and manage the administrative domain. You have these choices: Machines—Lets you view the machines in the domain, any alerts for each machine, and processes running on each machine. Inventory—Lets you view the currently installed TIBCO products and product versions. Components—Lets you view deployed components and associated information and start and stop components

Machines
The Machines option allows privileged users to view all domains in the administration domain. Privileged users can monitor all machines, services, and processes in the administration domain at the same time. This allows administrators to see overloaded or underutilized machines and potentially reassign processes to different machines. Information for machines includes Max uptime and operating system. Alerts are included at each level of the display, so the administrator knows with one glance that, for example, one part of your system is experiencing a problem. Privileged users can select individual machines to view additional, more detailed information such as virtual memory usage, CPU usage, etc., all TIBCO processes running on the machine, or all processes running on the machine. Here’s an example screen for a domain that includes only one machine: Figure 32 Machines Option in TIBCO Administrator

TIBCO BusinessWorks Concepts

96

| Phase 6: Production
Inventory
The Inventory option allows privileged users to view all installed TIBCO products in the administration domain and product version, when and where the products were installed, etc. Here’s an example screen for a domain that includes only one machine: Figure 33 Inventory Option in TIBCO Administrator

Components
The Components option allows privileged users to view each component deployed in the administration domain and includes information about the component, such as its status and Fault-Tolerant Group (if any). Privileged users can also stop and start components. Components include, for example TIBCO BusinessWorks process engines or TIBCO Adapter instances deployed to the TIBCO administration domain.

TIBCO BusinessWorks Concepts

Domain Monitoring and Management 97 | Figure 34 Components Option in TIBCO Administrator TIBCO BusinessWorks Concepts .

You can configure tracing to include or exclude selected activities. The module displays a separate icon for each deployment. you can view all active processes. you can view the activities in the process definition and information about them. Components—Allows you to view component details and set up tracing. TIBCO BusinessWorks Concepts . You can also save tracing information to a log. In each deployment. TIBCO Administrator tracing facilities allow for detailed analysis and provide debugging and throughput information. Here’s a simple example: Figure 35 Viewing Process Definition information Components Allows you to view component details and set up tracing. If you select a process definition.98 | Phase 6: Production Deployment Monitoring and Management The TIBCO Administrator deployment module allows privileged users to monitor and manage components on a per-deployment basis. you can choose from these options: Business Processes—Allows you to view process engines and associated active (running) processes. Business Processes The Business Processes option of each deployment allows you to select the process engine and each process definition associated with the engine. If you select the engine.

Examples are sending e-mail. sending information to an SAP adapter. TIBCO BusinessWorks Concepts . and other process instances will be distributed across the production platform. querying a database. TIBCO BusinessWorks adapters interact with enterprise applications such as PeopleSoft. One of the applications in your enterprise. after production deployment. Multiple projects can be in the same domain. Conditions are specified on transitions to determine whether to take the transition to the next activity or not.| 99 Glossary A ActiveEnterprise One of the three product families from TIBCO Software Inc. as well as databases or files. XPath which allows you to specify a custom condition using an XPath expression. C Condition A condition can be used to control the flow of activities in a process diagram. SAP R/3. The domain initially contains one or more machines. OracleApps and Siebel. a set of deployed projects. Administration Domain Consists of a set of machines on which TIBCO software components are deployed. Configuration Panel In TIBCO Designer. Activity An activity is a specific task in a business process definition. the configuration panel allows you to fill in values for the fields in the objects of your project. and otherwise. you assign the various project components (process and services) to the physical locations where they will run for test or production purpose. the adapter service instances. The other two are ActivePortal™ and ActiveExchange™ (see www. writing a file. In TIBCO Designer. You can monitor the components of all deployed projects in a domain from the TIBCO Administrator console. and to perform mapping. Later. Adapter Adapters make it possible to communicate and update business information that originates from diverse sources and resides on diverse host systems within an organization. When you install TIBCO BusinessWorks. each activity is represented by a resource and can be added to the process definition from its palette. you specify a TIBCO Administration Domain. the domain contains the services and process engines running on those machines. For example.tibco. and a single database for authentication and authorization. D Deployment During the deployment phase of your integration project. CRM Customer Relationship Management system. Condition types include: always.com for details). See also Process Definition.

100 | Glossary Design panel In TIBCO Designer. A non-XML schema file that contains a formal description of the vocabulary and structure of the elements in an associated XML file. A process definition is just a special type of activity. Associated with a service is a service interface. and data schema. This includes components like business processes. generates. A DTD may also provide some content information. Each machine may belong to only one TIBCO Administration Domain. and processes business data in a decoupled yet reliable manner. you drag resources from the palette panel into the design panel to create instances of that resource for your business process definition. Project tree panel One of the panels in TIBCO Designer. R M Machine A computer on which TIBCO Software components are installed. Process definition Specifies the business process flow using activities. adapter services. Process instance Running instance of a process definition Process starter Starts a process based on an external event.g. The project tree shows a hierarchy of all objects (adapters. S Service P Palette A TIBCO Designer palette is a collection of resources that you can use to populate your project. etc. For example.) in your project. data syntax. A TIBCO BusinessWorks service retrieves. e. G Activity Group A grouping of activities in a process definition. transport. DTD Document Type Definition. machines. DTDs serve the same function as XML schema documents (XSDs). activities. You create and save projects using TIBCO Designer and later deploy the project. Project A TIBCO BusinessWorks project is a collection of all the components of your EAI solution. Resource In TIBCO Designer. resources are the objects you can drag and drop into the design panel. Some groups specify process control logic. you can therefore use a process definition as an activity. use an adapter palette to add an adapter and a publisher to a project. TIBCO BusinessWorks Concepts . arrival of a file or a message from an adapter. The business process receives data from a service and sends data to a service. engine instance(s). The DTD for an XML document is the combination of the internal and external subsets described by the document type declaration.

XSLT XML Stylesheet Language Transformation. WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.Glossary 101 | SOAP Simple Object Access Protocol. (See http://www. TIBCO Designer uses XPath as the language for defining conditions and transformations. Each activity in a process definition must have a transition to it.w3. A complete description of XPath is available at http://www. XPath XPath is a scripting language developed by the World Wide Web Consortium (W3C) for addressing parts of XML documents. SOAP is a lightweight protocol for the exchange of information in a decentralized. TIBCO Administrator TIBCO Administrator is a browser-based interface for monitoring and managing TIBCO deployments. An XSD file defines the structure and elements in a related XML file. their security. The operations and messages are described abstractly. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it.org/TR/SOAP/) W WSDL Web Services Definition Language. TIBCO Designer A GUI tool that allows you design your integration project. XSLT is a recommendation of the World Wide Web Consortium TIBCO BusinessWorks Concepts . additional tabs become available. (See http://www. It provides basic manipulation functions for strings. In TIBCO Designer. a transition is represented by an arrow between activities.org/TR/wsdl) T X Tab A related set of entities and functions that are visible when you select one tab in the TIBCO Administrator GUI. You use TIBCO Designer for adapter configuration. and a convention for representing remote procedure calls and responses.xsd. and administration domains. XSL Transformations (XSLT) is a standard way to describe how to transform (change) the structure of an XML (Extensible Markup Language) document into an XML document with a different structure. distributed environment. numbers and Booleans. process design. and deployment.org/TR/xpath. Transition Transitions indicate the flow of processing.w3. and then bound to a concrete network protocol and message format to define an endpoint. TIBCO Administrator organizes the information using tabs. XSD XML Schema Definition.w3. The suffix of an XSD document is . Related concrete endpoints are combined into abstract endpoints (services). As components are installed. or the activity is not executed when the process executes. a set of encoding rules for expressing instances of application-defined datatypes.

102 | Glossary TIBCO BusinessWorks Concepts .

TIBCO Software Inc. End User License Agreement 103

|

TIBCO Software Inc.
READ THIS END USER LICENSE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THE SOFTWARE, YOU AGREE TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT DOWNLOAD OR INSTALL THE SOFTWARE AND RETURN IT TO THE VENDOR FROM WHICH IT WAS PURCHASED. RETURNS BY THE ORIGINAL PURCHASER WITHIN THIRTY (30) DAYS OF THE PURCHASE DATE WILL RECEIVE A FULL REFUND. Upon acceptance, the following shall govern your use of the Software except to the extent all or any portion of the Software (a) is subject to a separate written agreement, (b) includes a separate “click-on” license agreement as part of the download or installation process, or (c) is provided by a third party under the terms set forth in an addendum at the end of this Agreement, in which case the terms of such addenda shall control over inconsistent terms with regard to such portion(s). License Grant. The Software is the property of TIBCO or its licensors and is protected by copyright and other laws. While TIBCO continues to own the Software, TIBCO hereby grants to Customer a limited, non-transferable, non-exclusive, license to use the number of Permitted Instances set forth in the Ordering Document, in machine-readable, object code form and solely for Customer’s internal business use. Restrictions. Customer agrees not to (a) make more copies than the number of Permitted Instances plus a reasonable number of backups; (b) provide access to the Software to anyone other than employees, contractors, or consultants of Customer; (c) sublicense, transfer, assign, distribute to any third party, pledge, lease, rent, or commercially share the Software or any of Customer’s rights under this Agreement; (d) use the Software for purposes of providing a service bureau, including, without limitation, providing third-party hosting, or third-party application integration or application service provider-type services, or any similar services; (e) use the Software in connection with ultrahazardous activities, or any activity for which failure of the Software might result in death or serious bodily injury to Customer or a third party; or (f) directly or indirectly, in whole or in part, modify, translate, reverse engineer, decrypt, decompile, disassemble, make error corrections to, create derivative works based on, or otherwise attempt to discover the source code or underlying ideas or algorithms of the Software. Beta and Evaluation Licenses. Notwithstanding the foregoing, if the Software is being provided for demonstration, beta testing, or evaluation purposes, then Customer agrees (a) to use the Software solely for such purposes, (b) that the Software will not be used or deployed in a production environment, and (c) that such use shall automatically terminate upon the earlier of thirty days from the date Customer receives the right to install the Software, or Customer’s receipt of notice of termination from TIBCO. Additional Licenses. If Customer desires to increase the number of Permitted Instances, Customer may request the same by submission of an additional Ordering Document and upon acceptance by TIBCO, Customer shall be permitted to deploy such additional Permitted Instances, all of which shall otherwise be subject to the terms of this Agreement. Technical Support. Provided Customer has paid applicable support fees (not included with Software fees unless separately listed), TIBCO shall provide support for generally available TIBCO Software on an annual basis commencing on the Purchase Date, as follows (“Support”): Customer shall designate as technical support contacts

End User License Agreement
that number of Customer’s employees as are permitted under the level of Support purchased (contacts are changeable upon 48-hours prior written notice to TIBCO). Each contact may contact TIBCO for problem resolution during TIBCO’s published support hours corresponding to the level of Support fees paid. Upon notice from a contact of a Software problem which can be reproduced at a TIBCO support facility or via remote access to Customer’s facility, TIBCO shall use reasonable efforts to correct or circumvent the problem according to its published support objectives. TIBCO reserves the right to make changes only to the most currently available version. TIBCO will use reasonable efforts to support the previously released version of the Software for a maximum of six months. Software may be transferred to another site or operating system only upon written notice to TIBCO and subject to TIBCO’s transfer policies and fees then in effect. Software may be transferred without notice or additional cost from one machine to another at the same site if the second machine runs the same operating system software and otherwise there is no increase in the Permitted Instances. TIBCO shall have no obligation to support the Software (i) for use on any computer system running other than the operating system software for which the Software is approved (as set forth in the Software documentation) and licensed hereunder, or (ii) if Customer has modified the Software in breach of this Agreement. TIBCO shall have no obligation to modify any version of the Software to run with any new versions of any operating system, or any other third party software or hardware. If Customer purchases Support for any Software, Customer must purchase the same level of Support for all copies of the Software for which it is licensed. Support may be extended for one year periods on the anniversary of each Purchase Date at the standard amounts set forth in its price list, for as long as TIBCO offers Support. Customer may reinstate lapsed support for any then currently supported Software by paying all Support fees in arrears and any applicable reinstatement fee. Upgrades, patches, enhancements, bug fixes, new versions and/or new releases of the Software provided from time to time under Support shall be used only as replacements to existing Permitted Instances, and shall not be deemed to increase that number, and use thereof shall be governed by the terms of this Agreement, except for the first paragraph of the Limited Warranty and any right of return or refund. Consulting Services. Customer may request additional services (“Services”) either in an Ordering Document, or by a separate mutually executed work order, statement of work or other work-request document incorporating this Agreement (each, a “Work Order”). Unless otherwise expressly agreed to in a Work Order, all Services and any work product therefrom shall be (a) performed on a time and materials basis, plus meals, lodging, travel, and other expenses reasonably incurred in connection therewith, (b) deemed accepted upon delivery, and (c) exclusively owned by TIBCO (except for confidential information of Customer identified to TIBCO in the Ordering Document), including all right, title and intellectual property or other right or interest therein. Each Work Order is intended to constitute an independent and distinct agreement of the parties, notwithstanding that each shall be construed to incorporate all applicable provisions of this Agreement. Fees for Services shall be due and payable in United States dollars net30 from the date of TIBCO’s invoice.

TIBCO BusinessWorks Concepts

104

| TIBCO Software Inc. End User License Agreement
Limited Warranty. If Customer obtained the Software directly from TIBCO, then TIBCO warrants that for a period of thirty (30) days from the Purchase Date: (i) the media on which the Software is furnished will be free of defects in materials and workmanship under normal use; and (ii) the Software will substantially conform to its published specifications. This limited warranty extends only to the original Customer hereunder. Customer’s sole and exclusive remedy and the entire liability of TIBCO and its suppliers under this limited warranty will be, at TIBCO’s option, repair, replacement, or refund of the Software and applicable Support fees, in which event this Agreement shall terminate upon payment thereof. This warranty does not apply to any Software which (a) is licensed for beta, evaluation, testing or demonstration purposes for which TIBCO does not receive a license fee, (b) has been altered or modified, except by TIBCO, (c) has not been installed, operated, repaired, or maintained in accordance with instructions supplied by TIBCO, (d) has been subjected to abnormal physical or electrical stress, misuse, negligence, or accident, or (e) is used in violation of any other term of this Agreement. Customer agrees to pay TIBCO for any Support or Services provided by TIBCO related to a breach of the foregoing on a time, materials, travel, lodging and other reasonable expenses basis. If Customer obtained the Software from a TIBCO reseller or distributor, the terms of any warranty shall be as provided by such reseller or distributor, and TIBCO provides Customer no warranty with respect to such Software. EXCEPT AS SPECIFIED IN THIS LIMITED WARRANTY, THE SOFTWARE, SUPPORT AND SERVICES ARE PROVIDED “AS IS”, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, SATISFACTORY QUALITY OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE, ARE HEREBY EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW. NO WARRANTY IS MADE REGARDING THE RESULTS OF ANY SOFTWARE, SUPPORT OR SERVICES OR THAT THE SOFTWARE WILL OPERATE WITHOUT ERRORS, PROBLEMS OR INTERRUPTIONS, OR THAT ERRORS OR BUGS IN THE SOFTWARE WILL BE CORRECTED, OR THAT THE SOFTWARE’S FUNCTIONALITY OR SERVICES WILL MEET CUSTOMER’S REQUIREMENTS. NO TIBCO DEALER, DISTRIBUTOR, AGENT OR EMPLOYEE IS AUTHORIZED TO MAKE ANY MODIFICATIONS, EXTENSIONS OR ADDITIONS TO THIS WARRANTY. Limitation of Liability. IN NO EVENT WILL TIBCO BE LIABLE FOR ANY LOST DATA, LOST REVENUE, LOST PROFITS, DAMAGE TO REPUTATION, BUSINESS INTERRUPTION, OR ANY OTHER INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, PUNITIVE, EXEMPLARY OR ANY SIMILAR TYPE DAMAGES ARISING OUT OF THIS AGREEMENT, THE USE OR THE INABILITY TO USE THE SOFTWARE, OR THE PROVISION OF ANY SUPPORT OR SERVICES, EVEN IF TIBCO HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL TIBCO'S LIABILITY TO CUSTOMER, WHETHER IN CONTRACT, TORT (INCLUDING ACTIVE OR PASSIVE NEGLIGENCE), BREACH OF WARRANTY, CLAIMS BY THIRD PARTIES OR OTHERWISE, EXCEED THE PRICE PAID BY CUSTOMER UNDER THE APPLICABLE ORDERING DOCUMENT. THE FOREGOING LIMITATIONS SHALL APPLY EVEN IF THE ABOVE-STATED REMEDY OR LIMITED WARRANTY FAILS OF ITS ESSENTIAL PURPOSE. BECAUSE SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO CUSTOMER. Confidentiality. Aspects of the Software, Support and Services, including the specific design and structure thereof, constitute trade secrets and/or copyrighted material of TIBCO and Customer agrees not to disclose, provide, or otherwise make available the same in any form to any third party. Customer agrees to implement reasonable security measures to protect trade secrets and copyrighted material and to affix to all copies of Software or other confidential or trade secret information, appropriate TIBCO copyright, confidentiality, and proprietary notices. Export. TIBCO SOFTWARE CONTAINS ENCRYPTION TECHNOLOGY. You may not download or otherwise export or reexport the Software or any underlying information or technology except in full compliance with all United States and other applicable laws and regulations. None of the Software or underlying information or technology may be downloaded or otherwise exported or reexported (i) into (or to a national or resident of) Cuba, Iraq, Libya, Sudan, North Korea, Iran, Syria or any other country to which the U.S. has embargoed goods; or (ii) to anyone on the U.S. Treasury Department's list of Specially Designated Nationals or the U.S. Commerce Department's Table of Denial Orders. By downloading or using the Software, you are agreeing to the foregoing and you are representing and warranting that you are not located in, under the control of, or a national or resident of any such country or on any such list. Government Use. If the Customer is an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the Software, or any related documentation of any kind, including technical data or manuals, is restricted in accordance with Federal Acquisition Regulation ("FAR") 12.212 for civilian agencies and Defense Federal Acquisition Regulation Supplement ("DFARS") 227.7202 for military agencies. The Software is commercial computer software and commercial computer software documentation. Use of the Software and related documentation by the Government is further restricted in accordance with the terms of this Agreement, and any modification thereto. Interoperability. To the extent required by law, at Customer’s request, TIBCO shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of TIBCO's applicable fee. Customer agrees to observe strict obligations of confidentiality with respect to such information. Acceptance; Integration. An Ordering Document shall be deemed accepted only by issuance of a TIBCO invoice and solely for purposes of administrative convenience. None of the terms of the Ordering Document (other than the Software product name, number of Permitted Instances, level of Support, description of Services, and fees due in connection therewith), shall apply for any reason or purpose whatsoever, regardless of any statement on any Ordering Document to the contrary, unless countersigned by TIBCO. This Agreement constitutes the entire agreement between the parties with respect to the use of the Software, Support and Services, and supersedes all proposals, oral or written, and all other representations, statements, negotiations and undertakings relating to the subject matter hereof. All future orders of Software, Support or Services by Customer from TIBCO shall be deemed to occur under the terms of this Agreement (with or without reference to this Agreement), unless expressly superseded by a signed written Agreement between the parties.

TIBCO BusinessWorks Concepts

TIBCO Software Inc. End User License Agreement 105

|

Term and Termination. Customer may terminate this Agreement at any time by destroying all copies of the Software. This Agreement will terminate immediately without notice from TIBCO if Customer fails to comply with any of its provisions if not cured within fifteen days of such failure, or and, upon such termination, Customer must cease using and return or destroy all copies of the Software. Customer’s obligation to pay accrued charges and fees as well as the sections entitled “Confidentiality”, “Limited Warranty” and “Limitation of Liability” shall survive any such termination. Authority. You hereby represent and warrant that you have full power and authority to accept the terms of this Agreement on behalf of Customer, and that Customer agrees to be bound by this Agreement. General. Fees on the Ordering Document (all to be paid on the latter of thirty days from Invoice by TIBCO or the date set forth in the Ordering Document) do not include sales, use, withholding, value-added or similar taxes, and Customer agrees to pay the same, excluding therefrom taxes related to TIBCO’s income and corporate franchise tax. Customer agree to pay all reasonable costs incurred (including reasonable attorneys’ fees) in collecting past due amounts under this Agreement. No delay in the performance of any obligation by either party, excepting all obligations to make payment, shall constitute a breach of this Agreement to the extent caused by force majeure. Customer hereby grants TIBCO and its independent auditors the right to audit Customer’s compliance with this Agreement. If any portion of this Agreement is found to be void or unenforceable, the remaining provisions shall remain in full force and effect. This Agreement shall be governed by and construed in accordance with the laws of the State of California, United States of America, as if performed wholly within the state and without giving effect to the principles of conflict of law. The state and/or federal courts in San Francisco, California, shall have exclusive jurisdiction of any action arising out of or relating to this Agreement. The United Nations Convention on Contracts for the International Sale of Goods is excluded from application hereto. If any portion hereof is found to be void or unenforceable, the remaining provisions of this Agreement shall remain in full force and effect. Definitions. In connection with this Agreement, the following capitalized terms shall have the following meaning: “Agreement” means this End User License Agreement; “Customer” means the original purchaser or licensee of the Software and any permitted successors and assigns; “Development” means used for software development purposes only; “Enterprise” means an unlimited number of Permitted Instances for a period of one year from the Purchase Date (unless otherwise set forth in the Ordering Document), at which time existing licenses convert to perpetual and Customer may not thereafter deploy additional Permitted Instances, and in any event, shall (during the one-year unlimited deployment period) exclude any entity which acquires, is acquired by, merged into, or otherwise combined with Customer if, upon such combination, the combined annual revenues or head count is greater by ten percent (10%) than exists as of the Purchase Date (and Customer hereby agree to provide TIBCO with notice of the number of Permitted Instances deployed at the end of such one-year period within thirty days thereafter); “Fab” means unlimited use for shop-floor manufacturing applications at a Site; “Workstation” shall mean a single end-user computer that is generally intended to be accessed by one person at a time; “Ordering Document” means any purchase order or similar document or agreement requesting Software, Support or Services; “Permitted Instance(s)” means the number of copies of Software running on a Server Instance, Workstation, User, or Development basis, on a designated Platform, as set forth in an Ordering Document, including, without limitation, Enterprise, Site and Fab licensing; “Platform” means the operating system set forth in an Ordering Document; “Purchase Date” means the date of the Ordering

Document; “Server Instance” means a computer performing common services for multiple Desktop machines; “Site” means an unlimited number of Permitted Instances at a specific physical address set forth in the Ordering Document (or, in the absence of any address, at Customer’s corporate headquarters); “Software” means the software products listed in an Ordering Document (except as provided in the second paragraph hereof), in whole and in part, along with their associated documentation; “TIBCO” means TIBCO Software Inc.; and “User” means the number of named users with access to the Software. Copyright © 1997-2002 TIBCO Software Inc. ALL RIGHTS RESERVED.

ADDENDA: Third Party License Agreements NOTICE: Included with the TIBCO Software is certain source and/or object code software developed and licensed by third parties ("Third Party Software"). Third Party Software is licensed and supported exclusively under the terms and conditions of the license terms which accompany such Third Party Software, as set forth next.

TIBCO BusinessWorks Concepts

limited license to reproduce internally and use Java(TM) 2 SDK Enterprise Edition Version 1. Reference Implementation SUPPLEMENTAL LICENSE TERMS These supplemental license terms ("Supplemental Terms") add to or modify the terms of the Binary Code License Agreement (collectively. the "Agreement"). unless in writing and signed by an authorized representative of each party.7201 through 227. OR FOR SPECIAL. 4. No modification of this Agreement will be binding. 3. exceed the amount paid by you for Software under this Agreement. Any action related to this Agreement will be governed by California law and controlling U. Java(TM) 2. acknowledgment. If Software is being acquired by or on behalf of the U. Upon Termination. federal law.101 and 12. No right. Termination. 6. title or interest in or to any trademark. This Agreement is effective until terminated. RESTRICTIONS. you may not modify. EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 7. as evidenced by a copy of the receipt. unless omission would frustrate the intent of the parties. other than a single copy of Software for archival purposes. proposals. HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY. Export Regulations. Severability. Sun grants you a non-exclusive. Government Restricted Rights. U. but not limited to. Sun disclaims any express or implied warranty of fitness for such uses. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. INABILITY TO USE SOFTWARE. you may not make copies of Software. DISCLAIMER OF WARRANTY. IF YOU DO NOT AGREE TO ALL THESE TERMS. Enterprise Edition (J2EE). or other communication between the parties relating to its subject matter during the term of this Agreement. TO THE EXTENT NOT PROHIBITED BY LAW. INCLUDING ANY IMPLIE WARRANTY OF MERCHANTABILITY.106 | Third Party Software License Agreements Third Party Software License Agreements The following are the software licenses for the Third Party Software provided in connection with the software. Government prime contractor or subcontractor (at any tier). IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY. by the number of users and the class of computer hardware for which the corresponding fee has been paid. SELECT THE "DECLINE" BUTTON AT THE END OF THIS AGREEMENT. this is in accordance with 48 CFR 227. Government or by a U. you must destroy all copies of Software. non-transferable.S. licensed or intended for use in the design. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Agreement. You acknowledge that Software is not designed. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. then the Government’s rights in Software and accompanying documentation will be only as set forth in this Agreement. IF THE SOFTWARE IS ACCESSED ELECTRONICALLY. Your exclusive remedy and Sun’s entire liability under this limited warranty will be at Sun’s option to replace Software media or refund the fee paid for Software. logo or trade name of Sun or its licensors is granted under this Agreement. including. Inc. representations and warranties and prevails over any conflicting or additional terms of any quote. 9. or reverse engineer Software. or otherwise.S. Integration. tort (including negligence).S. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Sun grants you a non-exclusive and non-transferable license for the internal use only of the accompanying software and documentation and any error corrections provided by Sun (collectively "Software"). BY OPENING THE SOFTWARE MEDIA PACKAGE. 5. Sun Microsystems. this Agreement will remain in effect with the provision omitted.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2. service mark.3_01. or in any license contained within the Software. 2. If any provision of this Agreement is held to be unenforceable. whether in contract. INCIDENTAL OR PUNITIVE DAMAGES. operation or maintenance of any nuclear facility. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE. This Agreement is the entire agreement between you and Sun relating to its subject matter. Sun warrants to you that for a period of ninety (90) days from the date of purchase. It supersedes all prior or contemporaneous oral or written communications. ALL EXPRESS OR IMPLIED CONDITIONS. UNLESS SPECIFIED IN THIS AGREEMENT. Section 2 (Java(TM) Technology Restrictions) of these Supplemental Terms. CONSEQUENTIAL. Subject to the terms and conditions of this Agreement. These Supplemental Terms shall supersede any inconsistent or conflicting terms in the Agreement. Version 1. Unless enforcement is prohibited by applicable law. re-export. Software Internal Use and Development License Grant.212 (for non-DOD acquisitions). LICENSE TO USE. You may terminate this Agreement at any time by destroying all copies of Software. ARISING OUT OF OR RELATED TO THE USE OF OR TIBCO BusinessWorks Concepts . 11. PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF PURCHASE FOR A REFUND OR. PROFIT OR DATA. the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. construction. 8. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export. LIMITATION OF LIABILITY. decompile. Software is confidential and copyrighted. Except as specifically authorized in any Supplemental License Terms. INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. order. EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Except for the foregoing. in which case this Agreement will immediately terminate. or import as may be required after delivery to you. FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED. LIMITED WARRANTY. Software is provided "AS IS".3.S. 1. In no event will Sun’s liability to you. YOU AGREE TO THE TERMS OF THIS AGREEMENT. 10. Governing Law. Binary Code License Agreement READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE OPENING THE SOFTWARE MEDIA PACKAGE. REPRESENTATIONS AND WARRANTIES.x. No choice of law rules of any jurisdiction will apply. 1. INDIRECT.

This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. "sun" or similar convention as specified by Sun in any naming convention designation. operation or maintenance of any nuclear facility. Any use you make of the Sun Marks inures to Sun’s benefit. Except as specifically authorized in any Supplemental License Terms. Trademarks and Logos. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. SELECT THE "DECLINE" BUTTON AT THE END OF THIS AGREEMENT. Java Technology Restrictions.S. Software is confidential and copyrighted. Inc. Software may contain source code that is provided solely for reference purposes pursuant to the terms of this Agreement. 4. JINI.0. Export Regulations. service mark. REPRESENTATIONS AND WARRANTIES. 5. 4. Termination. you must promptly publish broadly an accurate specification for such API for free use by all developers. or in either party’s opinion be likely to become. Upon Termination. EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. or subpackages that are in any way identified as "java". FORTE. Your exclusive remedy and Sun’s entire liability under this limited warranty will be at Sun’s option to replace Software media or refund the fee paid for Software. then the Government’s rights in Software and accompanying documentation will be only as set forth in this Agreement. No right. the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. complete and unmodified. logo or trade name of Sun or its licensors is granted under this Agreement. and iPLANET trademarks and all SUN. "javax". as evidenced by a copy of the receipt. IF THE SOFTWARE IS ACCESSED ELECTRONICALLY. LIMITED WARRANTY. re-export. FORTE. and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www. you may not modify. HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY. Source code may not be redistributed unless expressly provided for in this Agreement. FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED.Third Party Software License Agreements 107 | internally the binary form of the Software. EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun’s liability to you. JAVA. If Software is being acquired by or on behalf of the U. service marks. 7. For inquiries please contact: Sun Microsystems. licensed or intended for use in the design. JINI.java. 3. Sun disclaims any express or implied warranty of fitness for such uses. JAVA. tort (including negligence). and iPLANET-related trademarks. INCIDENTAL OR PUNITIVE DAMAGES. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY. 3. provided that you do not redistribute the Software in whole or in part. interfaces. LIMITATION OF LIABILITY. You acknowledge that Software is not designed. by creating additional classes within the JPI or otherwise causing the addition to or modification of the classes in the JPI. title or interest in or to any trademark. INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. DISCLAIMER OF WARRANTY. U. YOU AGREE TO THE TERMS OF THIS AGREEMENT. 901 San Antonio Road. whether in contract.1 Sun Microsystems. Source Code. exceed the amount paid by you for Software under this Agreement. developing and testing your Java applets and applications ("Programs"). SOLARIS. 2. the subject of a claim of infringement of any intellectual property right.com/policies/trademarks. TO THE EXTENT NOT PROHIBITED BY LAW. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE. Sun warrants to you that for a period of ninety (90) days from the date of purchase. you must destroy all copies of Software. You may terminate this Agreement at any time by destroying all copies of Software. CONSEQUENTIAL. either separately or included with any Programs. In the event that you create an additional class and associated API(s) which (i) extends the functionality of the Java Platform. 5. decompile. identified as classes contained within the "java" package or any subpackages of the "java" package).S. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. ALL EXPRESS OR IMPLIED CONDITIONS.sun.html) for the availability of runtime code which may be distributed with Programs. 8. This Agreement is effective until terminated. PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF PURCHASE FOR A REFUND OR. or import as may be required after delivery to you. UNLESS SPECIFIED IN THIS AGREEMENT. or authorize your licensees to create additional classes. Except for the foregoing. or reverse engineer Software. Java Runtime Availability. INDIRECT.sun. and (ii) is exposed to third party software developers for the purpose of developing additional software which invokes such additional API. You acknowledge and agree as between you and Sun that Sun owns the SUN. Unless enforcement is prohibited by applicable law. SOLARIS. ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE. INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY. OR FOR SPECIAL. RESTRICTIONS. You may not modify the Java Platform Interface ("JPI". LICENSE TO USE. PROFIT OR DATA. BY OPENING THE SOFTWARE MEDIA PACKAGE. 6. California 94303 (LFI#100107/Form ID#011801) JavaTM APIs for XML Processing (JAXP) 1. Termination for Infringement. Sun grants you a non-exclusive and non-transferable license for the internal use only of the accompanying software and documentation and any error corrections provided by Sun (collectively "Software"). or otherwise. Software is provided "AS IS".S. Refer to the appropriate version of the Java Runtime Environment binary code license (currently located at http://www. other than a single copy of Software for archival purposes. by the number of users and the class of computer hardware for which the corresponding fee has been paid. Government prime contractor or subcontractor (at any tier). 1. construction. 2. Inc. Government or by a U. IF YOU DO NOT AGREE TO ALL THESE TERMS. You may not create.com/jdk/index. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export. 6. logos and other brand designations ("Sun Marks"). Government Restricted Rights. for the sole purpose of designing. Binary Code License Agreement READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE OPENING THE SOFTWARE MEDIA PACKAGE. this is in accordance with 48 CFR TIBCO BusinessWorks Concepts . Either party may terminate this Agreement immediately should any Software become. you may not make copies of Software. Palo Alto.

in which case this Agreement will immediately terminate. You may not modify. logos and other brand designations including the Coffee Cup logo and Duke logo ("Java Marks"). 2. Integration.jar". order. For inquiries please contact: Sun Microsystems. federal law. In exchange for the licenses granted in Paragraphs 1. License to Distribute. Redistribution and use in source and binary forms.sun. Severability. (ii) In the event that you create an additional class and associated API(s) which (a) extends the functionality of a Java Environment.108 | Third Party Software License Agreements 227. Java Platform Interface. to defend and indemnify Sun and its licensors from and against any damages. you agree: a. in the event that you create an API(s) which: (i) extends the functionality of a Java platform. and (e) agree to indemnify. 10. except with respect to the Service Bundles. You acknowledge and agree as between you and Sun that Sun owns the Java trademark and all Java-related trademarks. (i) You may not modify the Java Platform Interface ("JPI". and c. as specified by Sun in any naming convention. proposals. non-transferable. you must promptly and broadly publish an accurate specification for such API for free use by all developers. 4.jar" without the archive file "parser. with or without modification.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2. unless omission would frustrate the intent of the parties. that arise or result from the use or distribution of any and all Programs. or in any license contained within the Software. or subpackages that are in any way identified as "java"." "javax" or "sun" packages.7201 through 227. All rights reserved. VERSION 1.jar" but with a parser implementation that is compliant with the JAXP specification and do not distribute additional software intended to replace any components of the archive file "jaxp. the "Agreement"). Sun grants you a non-exclusive. distribute or use the source code for any other purpose. that. (iii) You may not create. 2 and 3 above.101 and 12. this Agreement will remain in effect with the provision omitted. This Agreement is the entire agreement between you and Sun relating to its subject matter. settlement amounts and/or expenses (including attorneys’ fees) incurred in connection with any claim. 1. unless in writing and signed by an authorized representative of each party.0 SUPPLEMENTAL LICENSE TERMS These supplemental license terms ("Supplement") add to or modify the terms of the Binary Code License Agreement (collectively.jar" ("XML JAR Files") to third party end users solely as a component of your Programs provided that you: (a)(i) distribute the XML JAR Files complete and unmodified in their original Java Archive file. 6. and (ii) agree to indemnify. hold harmless. Capitalized terms not defined in this Supplement shall have the same meanings ascribed to them in the Agreement. and (b) do not remove or alter any proprietary legends or notices contained in or on the Software. including attorney’s fees. 5. interfaces or subpackages that are contained in the "java. 11. alternatively (ii) distribute the archive file "jaxp. or. or authorize your licensees to create additional classes. b.com/policies/trademarks. contained in the Software in the archive files "jaxp. identified as classes contained within the "java" package or any subpackages of the "java" package). 3. in binary form. (d) agree to incorporate the most current version of the XML JAR Files that was available from Sun no later than 180 days prior to each production release of your Program. lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software. Any action related to this Agreement will be governed by California law and controlling U. 9. No modification of this Agreement will be binding. not to create. royalty-free limited license to reproduce and distribute the classes Java(TM) API for XML parsing classes. No choice of law rules of any jurisdiction will apply. Any use you make of the Java Marks inures to Sun’s benefit. log4.jar Version 1. that arise or result from the use or distribution of any and all Programs. by creating additional classes within the JPI or otherwise causing the addition to or modification of the classes in the JPI. or authorize your licensees to create. including attorney’s fees. you must promptly publish broadly an accurate specification for such API for free use by all developers. Inc. Palo Alto.212 (for non-DOD acquisitions). and do not distribute additional software intended to replace any component(s) of the XML JAR Files.jar" and "parser. Trademarks and Logos. It supersedes all prior or contemporaneous oral or written communications. non-transferable. 901 San Antonio Road. are permitted provided that the following conditions are met: TIBCO BusinessWorks Concepts . additional classes. costs. acknowledgment. representations and warranties and prevails over any conflicting or additional terms of any quote. either separately or included in any Program except as authorized for the Java(TM) API for XML parsing JAR Files as specified in Section 2 below. royalty-free limited license to use the Software in binary form for the development of Java(TM) API for XML Parsing compatible parsers (the "Programs") and reproduce and distribute the Programs to third party end users provided that you: (i) do not redistribute the Software in whole or in part.1 Copyright (C) 1999 The Apache Software Foundation. Requirements. Sun grants to you a limited license to view only the source code included in Software for purposes of internal evaluation only. Sun grants you a non-exclusive. Limited License for Source Code. California 94303 JAVA(TM) DEVELOPMENT OPTIONAL PACKAGES JAVA(TM) API FOR XML PARSING. service marks. liabilities. hold harmless. If any provision of this Agreement is held to be unenforceable.3 The Apache Software License. interfaces. "javax" or "sun" or similar as specified by Sun in any class file naming convention designation.1. These Supplement terms shall supersede any inconsistent or conflicting terms in the Agreement. Governing Law. and (ii) is distributed to third party software developers for the purpose of developing software which invokes such additional API. or similarly named package. and (b) is exposed to third party software developers for the purpose of developing additional software which invokes such additional API.S. and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www. (c) only distribute the XML JAR! Files pursuant to a license agreement that protects Sun’s interests consistent with the terms contained in the Agreement. or other communication between the parties relating to its subject matter during the term of this Agreement. and defend Sun and its licensors from and against any claims or lawsuits. Version 1. License to Develop. and defend Sun and its licensors from and against any claims or lawsuits.

INCIDENTAL. this acknowledgment may appear in the software itself.apache. =============================================== This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999. BUT NOT LIMITED TO. if any. 3. Redistribution and use in source and binary forms. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE." Alternately. if any. Products derived from this software may not be called "Apache". this list of conditions and the following disclaimer. THIS SOFTWARE IS PROVIDED ‘ ‘ AS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES.1 Copyright (c) 2000 The Apache Software Foundation.apache. 2. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www. without prior written permission of the Apache Software Foundation. OR CONSEQUENTIAL DAMAGES (INCLUDING. WHETHER IN CONTRACT. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. please see <http://www.apache. please see <http://www. Redistributions of source code must retain the above copyright notice. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.org. with or without modification. The end-user documentation included with the redistribution. THIS SOFTWARE IS PROVIDED ‘ ‘ AS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES.apache. LOSS OF USE. must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www. SPECIAL. 4.org.0a The Apache Software License. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.org/>.2. 5. SPECIAL.org/). IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT. if and wherever such third-party acknowledgments normally appear. Inc. must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www. this acknowledgment may appear in the software itself. INCIDENTAL. INCLUDING." Alternately. OR PROFITS. 4. with or without modification. BUT NOT LIMITED TO. are permitted provided that the following conditions are met: 1. Redistributions in binary form must reproduce the above copyright notice. For more information on the Apache Software Foundation.. INDIRECT. For written permission. please contact apache@apache." TIBCO BusinessWorks Concepts . WHETHER IN CONTRACT. nor may "Apache" appear in their name. Redistribution and use in source and binary forms. BUT NOT LIMITED TO. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation.1 Copyright (c) 1999-2000 The Apache Software Foundation. 3. EXEMPLARY. 4. DATA. this list of conditions and the following disclaimer. The end-user documentation included with the redistribution. The names "Apache" and "Apache Software Foundation".D10 The Apache Software License. Version 1. 5. pertools. For written permission.jar Version 1. INCLUDING. nor may "Apache" appear in their name.org/>. STRICT LIABILITY. please contact apache@apache. 2.com.org/). 3. if and wherever such third-party acknowledgments normally appear. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. DATA. BUT NOT LIMITED TO. this acknowledgment may appear in the software itself. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. The end-user documentation included with the redistribution. For written permission. this list of conditions and the following disclaimer. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. INDIRECT. without prior written permission of the Apache Software Foundation.2. Redistributions in binary form must reproduce the above copyright notice. Version 1. The names "log4j" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Redistributions of source code must retain the above copyright notice. http://www. 2. EXEMPLARY. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT.org. Redistributions of source code must retain the above copyright notice. OR PROFITS. Xalan-J 2.org/). OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.ibm. LOSS OF USE. All rights reserved. STRICT LIABILITY. Alternately. Products derived from this software may not be called "Apache". are permitted provided that the following conditions are met: 1.Third Party Software License Agreements 109 | 1. All rights reserved. For more information on the Apache Software Foundation. please contact apache@apache. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. if and wherever such third-party acknowledgments normally appear. Redistributions in binary form must reproduce the above copyright notice. International Business Machines. "Jakarta-Oro" must not be used to endorse or promote products derived from this software without prior written permission. OR CONSEQUENTIAL DAMAGES (INCLUDING. if any.apache.

OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. INDIRECT. INCIDENTAL. LOSS OF USE. BUT NOT LIMITED TO. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. are permitted provided that the following conditions are met: 1. SPECIAL. =================================================== This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. BUT NOT LIMITED TO. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT. Cryptix 3. INCLUDING. IN NO EVENT SHALL THE CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT. Portions of this software are based upon software originally written by Daniel F. OR PROFITS. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. We appreciate his contributions. BUT NOT LIMITED TO. DATA.2. Savarese. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. DATA.0 Cryptix JCE Cryptix General License Copyright © 1995-2001 The Cryptix Foundation Limited. STRICT LIABILITY.org/>. TIBCO BusinessWorks Concepts . EXEMPLARY.Redistributions in binary form must reproduce the above copyright notice. without prior written permission of the Apache Software Foundation. WHETHER IN CONTRACT. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.apache. WHETHER IN CONTRACT. this list of conditions and the following disclaimer. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. OR PROFITS. EXEMPLARY. please see <http://www. STRICT LIABILITY. THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES. 2. LOSS OF USE. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.110 | Third Party Software License Agreements 5. SPECIAL. OR CONSEQUENTIAL DAMAGES (INCLUDING. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. with or without modification. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. INCIDENTAL. For more information on the Apache Software Foundation. INCLUDING. Products derived from this software may not be called "Apache" or "Jakarta-Oro".Redistributions of source code must retain the copyright notice. nor may "Apache" or "Jakarta-Oro" appear in their name. BUT NOT LIMITED TO. INDIRECT. All rights reserved. Redistribution and use in source and binary forms. THIS SOFTWARE IS PROVIDED ‘ ‘ AS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES. OR CONSEQUENTIAL DAMAGES (INCLUDING.

44. 21 accessing from process 63 configuring 62 design-time adapter 60 features 21 installing 54. 83 administration server 50. 74 configuration adapter service 58 deployment 24. 63 configuration steps 58 adapters 20. 86 overview 33 run-time adapters 62 conventions used in this manual xi creating administration domain 83 creating process definitions 69 creating projects 85 creating transitions 74 customer support xii D data mapping 22. 94 analysis 29 business events 45 problem definition 40 application integration 2 architecture 12 design-time 14 run-time 17 assigning software 83 authentication 11 authorization 11 B business integration elements 19 business processes 22. 75 data transformation 75 debugging projects 85 deployed projects management 11 monitoring 11 TIBCO BusinessWorks Concepts . 50.| 111 Index A activities accessing services 42 adding 71 data mapping data 75 data transformation 75 grouping 76 transitions 74 adapter service 57. 59 overview 20 run-time adapter 62 adding activities 71 adding deployment configuration information 86 adding process starter 70 adding transitions 74 administration component 53 administration domain 9. 66 design 46 modelling 22 C components identifying 42 run-time 53 conditional transitions 74 conditions 43.

59 overview 30 TIBCO BusinessWorks 52 integrated development environment 13 integration 2 benefits 2 platform requirements 3 invocation modes 56 M management run-time 25 managing deployed projects 11 manual activity 5. 66 design steps 67 identifying 41 starter 70 testing 77 G grouping activities 76 I identifying components 42 identifying processes 41 InConcert 13 TIBCO BusinessWorks Concepts . 24 mapping 22. 46. 13. 50 creating 83 setup 30 installation adapters 54.112 | Index deployment 37 configuration 24 configuration information 86 introduction 80 steps 82 design 35 business processes 46 steps 67 design-time adapter 60 design-time architecture 14 development environment IDE 13 domains 9. 44. 75 messaging 19 methodology introduction 28 modelling of business process 22 monitoring introduction 92 projects 11 run-time 25 E exceptions 44 extensibility 13 F fault tolerance 37 fault-tolerance 25 features adapters 21 P palettes overview 16 populating administration domain 83 problem definition 40 process definitions 69 process modelling 22 process starter 70 processes 66 design 35.

94 TIBCO Administrator 8 TIBCO BusinessWorks adapters 21 installing 52 introduction 8 TIBCO BusinessWorks services introduction 56 TIBCO Designer 8 TIBCO InConcert 8. 11 user management 94 sending messages 19 server 50. 13. 98 S scalability 13 schema 22. 52 tracing 98 transformation 75 transitions 43. 94 services activities 42 adapter 63 characteristics 56 configuration 33 introduction 56 types 57 web services 57 setting up design-time adapter 60 shared resources 68 software resources 83 standards 12 starter 70 support. 24 TIBCO BusinessWorks Concepts . 24 TIBCO Runtime Agent 8 TIBCO run-time agent 51 TRA 8. contacting xii U user management 94 W web services 57 workflow 5. 50 TIBCO administration server 50. 23 security 8.Index 113 | production 38 projects 15 creating 85 extensibility 13 life cycle 81 scalability 13 testing 85 T technical support xii testing processes 77 testing projects 85 TIBCO Administration Domain 52 TIBCO administration domain 9. 74 R resources 16 shared 68 software 83 run-time agent 51 run-time architecture 17 run-time components 53 run-time management 25 run-time monitoring 25. 51.

114 | Index TIBCO BusinessWorks Concepts .

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->