TIBCO Architecture Fundamentals Program Overview

April 11, 2006 Paul Asmar Vice President, Global Architects

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services. This document is provided for informational purposes only and its contents are subject to change without notice. TIBCO makes no warranties, express or implied, in or relating to this document or any information in it, including, without limitation, that this document, or any information in it, is error-free or meets any conditions of merchantability or fitness for a particular purpose. This document may not be reproduced or transmitted in any form or by any means without our prior written permission.

Program Agenda
S Architecture Discussion
S Architecture and Services Overview S Architecture Challenges S Leveraging the TIBCO Architecture Method S Enterprise SOA S Tools Demonstration

S Implementing Enterprise Services with TIBCO

S Services Infrastructure S Services Identification, Implementation and Orchestration S Service Deployment S Scalability/Fault Tolerance S Lifecycle Management

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

What Is an SOA?
S An architecture that enables IT to compose applications from services, and that promotes greater reuse and flexibility S Benefits of SOA:
S Simplify Leverage assets, deliver new functionality more easily S Open Reduce costs, risk and vendor lock-in S Accelerate Rollout new functionality faster (Agility)

S Enabling technologies for SOA:

S Services Service development, deployment, management S Events Capture, process and deliver events S Integration Adapters and integration services S Mediation ESB S Processes Orchestration
TIBCO USER CONFERENCE / 2006
3

TIBCO USER CONFERENCE / 2004

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Architecture Evolution: How We Got to SOA Through Messaging and Integration Big Iron Client-Server 85-95 Pre-1985
Monolithic 2-tier
RPC, Messaging

Web Apps 95-01

3-tier (UI/logic/data) EAI (processes) Web servers Java/J2EE/JMS

SOA 01 N-tier services UDDI/SOAP/WSDL ESB Technology

Services Processes Events

Mediation Events Mediation Events

Processes

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCOs View of SOA

Automate and streamline business processes

Improve operational visibility and responsiveness

Accelerate projects, initiatives, and go-to-market cycles

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Architecture Fundamentals Part 1: Architecture Discussion

April 11, 2006 Paul Brown Principal Software Architect

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services. This document is provided for informational purposes only and its contents are subject to change without notice. TIBCO makes no warranties, express or implied, in or relating to this document or any information in it, including, without limitation, that this document, or any information in it, is error-free or meets any conditions of merchantability or fitness for a particular purpose. This document may not be reproduced or transmitted in any form or by any means without our prior written permission.

Architecture Discussion: Objective and Topics S Describe fundamental principles for architecting TIBCO projects and experience supporting tools and methods
S Architecture and Services Overview S Architecture Challenges S Leveraging the TIBCO Architecture Method S Enterprise SOA S Tools Demonstration

+
TIBCO USER CONFERENCE / 2004

=
7

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Architecture and Services Overview

S Architecture and Services Overview
S What Is Architecture? S The Scope of Architecture S The Business Process Connection S Services

S Architecture Challenges S Leveraging the TIBCO Architecture Method S Enterprise SOA S Tools Demonstration

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

What Is Architecture?
S Architecture is the characterization of the physical structure and the logical organization of a system
S Physical Structure Components and their physical arrangement S Software on machines, machines on networks S Machines, networks, and minor components form the infrastructure S Logical Organization Component roles and responsibilities with respect to the business process(es) the system is intended to support S Who performs what work, when, and under what conditions? S Who owns what information, how is it accessed and distributed? S Who monitors, manages, and reports on the overall work process?

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

What Are We Designing?

S A large-scale system-of-systems
S The major components are systems in their own right S Each independently performs useful functions for the enterprise S We are integrating these systems to improve the overall business S The business processes (by definition) span multiple systems S We have limited (if any) control over the major systems themselves S Yet we are responsible for getting them to work together S The only tool we have to work with is communications with those systems S To move data S To coordinate work S To obtain status S To monitor and manage the process

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

10

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Architecture Has Broad Scope

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

11

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Business Process Design Impacts Architecture

S Business processes make design assumptions about what systems can and should be doing: functions provided, interfaces needed, data and process management
S Inappropriate assumptions lead to ugly system designs and ungainly business processes S For best results, work process design should be a collaborative effort between business and technical people S Focus on finding a good marriage between business needs and technical realities S Achieve business goals S Practical and cost effective from a technology perspective S Make sure both sides are aware of care and feeding activities S e.g., administering credentials/qualifications, maintaining reference data

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

12

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Business Processes and Architecture Are Inseparable

S Business process defines the interplay between:
S The people using the system S The systems themselves S The information used in the work process components (traditional architecture)

TOT A L
People Processes

S Architecture defines the roles of system components with respect to the work processes, information and people:
S Which components participate in which activities

H I T CT U E

S Which components manage which pieces of information S Which components are involved in which human interactions

A good architecture demands a clear understanding of these relationships!

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

13

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

RE

Information

Systems

AR

What Is the TIBCO Architects Job?

S Design a system that:
S Supports the work processes S Provides the expected benefit S Can be delivered within the project cost and schedule guidelines S Does this with acceptable risks in: S Work process disruption S Ability to achieve the benefit S Ability to execute within cost and schedule guidelines
Negative None

Hurts Business Process

Doesn't Justify Cost

Good

Positive

Architecture Benefit Meter

If you find that you cant get there from here, blow the whistle loud and early! Saving time and resources leaves more options open.
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

14

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

What the Architect Must Know about the Business

S S What is the Business Process and how will it change?
S e.g., Automate order entry so customers can enter their own orders

What are the expected quantifiable benefits?

S Improve order processing productivity by 20% to support anticipated acquisitions without hiring additional personnel

What are the cost and schedule constraints?

S The business requires the capability within 9 months at a cost not to exceed $450K in order to complete the planned acquisition

How does the business process handle breakdowns?

S If the credit check service is unavailable, accept low-value orders without checking and manually approve high-value orders

What is the risk if the business process breaks down?

S If the productivity benefit falls below 10%, the company will operate at a loss; or if the system is not available 99.9% of the time the productivity benefit will be lost

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

15

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Services
S What is a service?
S A commonly used unit of functionality S e.g. Sales Order Management S Packaged for consistent re-use S Becomes a de-facto standard

S The goal is to save money!

S Standardize the function so that what the next project (process) needs is already there

S Most functionality already exists

S In one system, but accessed many ways S In multiple systems

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

16

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Typical Service Architecture

S A service is a reusable unit of functionality with standardized interfaces S A business service is a unit of business process functionality exposed as a service so that it is available to a wider audience
O O O O O

Using Component
Using Component
Native semantics for operation and data Native technology for operation and data
O O

Service Interface
Native Interface Provider of Functionality Traditional Object/ Component Approach

Either Company or Application-Specific Semantics for the operation depending on the level of service abstraction. Company standard semantics for data Company standard technology for operation and data Native semantics for operation and data Native technology for operation and data

Service

Native Interface Provider of Functionality Service Approach

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

17

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Business and Infrastructure Services Differ!

S Business Services encapsulate portions of business processes
S e.g. Place Sales Order or Invoice Customer S The requirements come from the business community S The users are future business processes

S Infrastructure Services encapsulate portions of system processes

S e.g. Report error or Make Audit Entry S The requirements come from the technical community S The users are future technical projects

Different organizations are involved!

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

18

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

The Reusability Challenge

S How do we design for future usages?
S Today we enter orders in person, via paper, by phone, on-line, S Whats next via Blackberry? Automatic re-order? S Your CPG firm decides to sell branded clothing as a promotion! S Orders now need sizes, colors, etc.

S Insight is required when conceptualizing a service

S What might change in the future? S Evolutionary changes organic growth S Revolutionary changes buying your biggest competitor, new markets S How do these changes challenge existing functionality? S Which alternatives are worth investing in?

Who can provide this insight in your organization?

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

19

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

You Will Never Build a Perfect Service!

S Be happy if you get close enough that the changes are minor
S e.g. adding a field here or there

S Plan for service evolution

S Infrastructure must allow the simultaneous deployment of both old and new service versions S Service users can gradually convert to the new version

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

20

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Architecture Challenges
S Architecture and Services Overview S Architecture Challenges
S Traditional organizational structures S Organizations and Services S The Real Situation... S Project roles S Impact of component availability

S Leveraging the TIBCO Architecture Method S Enterprise SOA S Tools Demonstration

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

21

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

The Organizational Issue in the Architecture Puzzle

S Architectural responsibilities are often organizationally fragmented
S Systems S Technical Architects S Network Architects S Technology selection groups
People Processes

S S S S

Information
S Data Architects

Processes
S Business Analysts
Information Systems

People
S Organizations doing the work

Someone must be responsible for making sure these pieces work together

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

22

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Organizations in 3-Tier Development

Business Owner Business User User Interface Developers Major System Owner Database Administrator
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

23

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Organizations in 2-System Integration

Workflow

End-Point System
TIBCO USER CONFERENCE / 2004

Integration Components

End-Point System
24

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Organizations and Services

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

25

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

The Real Situation Looks More Like This

Customer Support Rep Customer Manager Analyst

Standards & Security

Business Activity Monitoring & User Integration

Operations

Workflow & Process Automation Connectivity Enterprise Backbone

Warehouse Business Partner Logistics Business Partner

Peoplesoft

SAP

Clarify

Traditional IT Organizational Boundaries

TIBCO USER CONFERENCE / 2004

Partner Management

TIBCO USER CONFERENCE / 2006

26

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Who Defines the Development Process?

Gatekeeper Gatekeeper Gatekeeper Gatekeeper Gatekeeper Gatekeeper

Business Process Architecture Charter Requirements Integration Test System Architecture QA Production

Development

Who manages the process? Who owns the risk?

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

27

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Key Project Roles

S The Management Team
S Business Executive Sponsor S Ensures business cooperation - has authority over all business owners involved S Owns the budget for business services S Responsible for the ROI from business services S IT Executive Sponsor S Ensures IT cooperation - has authority over all IT organizations involved S Owns the budget for infrastructure services S S

S The Project Team

S Project Manager S Responsible for resources and schedule S There may be more than one development project! S Services development S Using system development Business Process Architect S Responsible for determining if/how service fits into business process S Responsible for business ROI justification System Architect S Responsible for determining how the service will be implemented S Responsible for infrastructure ROI justification

Each Role is Critical to Success!

TIBCO USER CONFERENCE / 2006

TIBCO USER CONFERENCE / 2004

28

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

People Get Things Done

S Humans are tolerant of faults:
S One person asks another to perform work (the request) S Performer assumes responsibility (the promise) S Performer delivers the requested result S Requestor evaluates result and provides feedback
4: F eedbac k 1: Reques t Reques tor 2: P rom is e 3: Re s ult P erform er

S Either party can respond flexibly to breakdowns in the process

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

29

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Systems Lack Human Flexibility

S Systems only do what they have been designed to do S Traditional integration employs only one-way communications
Requesting System Design and Support Staff 4: Feedback 5: Designed-for Breakdown 1: Request Requesting System 2: Promise 3: Result Performing System 6: Designed-for Breakdown Performing System Design and Support Staff

S Omitting the other communications gives up virtually all means of detecting breakdowns!

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

30

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Traditional EAI
Initiating Application Target Application

Service A

Service B

Source System

Machine A

Machine B

Target System

S Successive steps of information movement and processing may look like a processbut traditional EAI does not treat it like a managed process
There is no breakdown detection in the overall process!
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

31

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Impact of Component Availability

S Component availability determines process availability
Component Availability Resulting Process Availability for a 10step Process 90.0% 34.9% 99.0% 90.4% 99.9% 99.0%

High-availability components require timely breakdown recovery

Repair Time to Maintain 99.9% Component Availability 1.2 minutes 10 minutes 43 minutes 8.77 hours

Component Failure Frequency Daily Weekly Monthly Yearly

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

32

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Leveraging the TIBCO Architecture Method

S Architecture and Services Overview S Architecture Challenges S Leveraging the TIBCO Architecture Method
S Positioning architecture in the project lifecycle S Making architecture development efficient S When do questions get addressed?

S Enterprise SOA S Tools Demonstration

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

33

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Positioning Architecture in the Project Life Cycle

Budget for Project

Business Benefit, Cost and Schedule Expecations

Define Requirements

Business Process Definitions & Other Requirements

Synthesize Architecture

Knowlege Gained from Using System

Component Structure and Responsibilities

Specify Components

Component Specifications
Design, Implement, and Test Components

Unit-tested Components
Assemble and Test System

Working System
Deploy and Use System

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

34

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

sksiR lacinhceT evloseR dna yfitnedI ,sevitanretlA larutcetihcrA etaulavE

sesahP txeN nalP ,ytilibisaeF tcejorP ssessA

tnemssessA ytilibisaeF laitinI

noisiceD OG tcejorP

sksiR ssenisuB evloseR dna yfitnedI ,sevitanretlA ssecorP ssenisuB etaulavE

tsoC evitalumuC

stniartsnoC ,sevitanretlA ,sevitcejbO ssecorP ssenisuB enimreteD :stnemeriuqeR ezylanA dna rehtaG

TIBCO USER CONFERENCE / 2004

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO USER CONFERENCE / 2006

Making Architecture Development Efficient

35

noitaretI txeN ot timmoC dna weiveR

TIBCO Architecture Method

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

36

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

When Do Questions Get Addressed?

Business Process Synthesis Architecture Synthesis
Defined by the Architecture

Question? Who
(what participant)

Defined by the Activity and Unit of Work

Defined by the Business Process

X
(internal or external to the system)

X
(within the system)

What Why When Where How

X X X X X
(logical) 37

X
(physical)

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Architecture Method Phases

Business Process Analysis
Y Use cases selected and prioritized Y Business activity models Y Components, responsibilities, communication needs Y Network deployment topology Y Communications mechanisms Y Information management policies Y Component activity coordination Y Parallel processing Y Security Y Monitoring

Architecture Synthesis

Architecture Evaluation

Y Evaluate performance capabilities Y Evaluate ability to accommodate both evolutionary and drastic changes Y Evaluate standards compliance Y Define testing and operations guidelines Y Document architecture
38

Define Tests and Document

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Business Processes Identification and Grouping

S S S Identify business processes
S Group into use cases by common expected result

Identify key scenarios for use cases

S We want to know the major business processes and variations

Estimate business impact and risk, occurrence rates, determine required completion times
S To understand the volume or performance demand on the system

S S

Identify scenario complexity (system, human involvement)

S To understand which use cases place significant demands on resources

Business Process Ranking

S Processes with the highest business risk, highest complexity, and most demanding performance requirements are ranked highest

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

39

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Use Case Example: ATM Transaction

Make Deposit

Transfer Funds Bank Customer

Check Balance

Withdraw Cash

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

40

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Uncover Supporting Use Cases

Use common sense - ask about functions you know have to be there somewhere (adding new system users, new business customers, etc.)
TIBCO USER CONFERENCE / 2006
41

TIBCO USER CONFERENCE / 2004

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Business Process Characteristics

Use Case Business Peak Variation in Allowed Average Data Volume Process Execution Peak Rate Over Completion Execution Per Execution (Scenario) Rate Time Time Rate Peaks at lunch hour 32/ second Peaks during morning and evening commute 0.1/ second Peaks at lunch hour 1/ second Peaks during morning and evening commute 1 every 4 Peak during first few weeks of hours rollout 5/ minute Uniform during working day, gap at lunch 100/ hour Peaks at lunch hour 1/second 3 minutes 30 seconds 16,000/ day 139,000/ day 1KB 1KB

Withdraw At teller Cash At ATM

Make Deposit

At teller At ATM

3 minutes 30 seconds

1,600/ day 1KB 4,800/ day 1KB

Install ATM Machine

4 hours 2 minutes

2/ month

1.5MB

Service ATM Machine

333/ day

20KB

Issue ATM Card

5 minutes

400/day

1 KB

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

42

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Ranking Business Processes

Peak Rate/ Second 1 or less 10 100 1,000 10,000 or over Peak Rate Rank 1 2 3 4 5

Data Size (Bytes) 100 or less 1K 10K 100K 1MB or more

Data Size Rank 1 2 3 4 5

Coupling Between Participants Independent systems, no integration Data integration

Triggering of Work

Location of Process Definition

Factors Driving System Complexity - All inputs must be provided by users and output delivered to users - Data structure definitions and communications mechanisms are shared - Data movement must be triggered and coordinated with work.

Complexity Rank 1

Initiated by human External to the interaction system.

Risk to business if process is not successfully executed No measurable impact Minor productivity loss, minor impact on ability to demonstrate regulatory compliance, bottom line impact not discernable Intermediate productivity loss, some measurable impact on ability to comply with regulations, some measurable impact on bottom-line Major productivity loss, inability to comply with regulations, major impact on bottom-line Catastrophic unrecoverable business failure, loss of life

Business Impact Rank 1 2

Process integration

Initiated by external events such as human interaction or communications. Data movement does not trigger work

External to the system.

Initiated by external events and/or communications with other system components

Process definition is implicit in the pattern of communications that trigger work in components

- Coordinating work performed in one component with work performed in others. - Detecting and reporting breakdowns in the process - Representing the process and its variations - Assigning work to resources at runtime - Defining processes at runtime.

Monitored processes and workflow

Initiated by external events and/or communications with other system components

Process definition is explicitly represented in the monitor or workflow engine

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

43

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Business Process Ranking

Business Frequency Data Size Complexity Risk Rank Rank Rank Rank Process (Scenario) Withdraw At teller 1 2 2 4 At ATM 2 2 3 4 Cash Make At teller 1 2 2 4 At ATM 1 2 3 4 Deposit Install ATM Machine 1 5 2 3 1 3 2 4 Service ATM Machine Issue ATM Card 1 2 3 3 Use Case

Overall Rank 16 48 16 24 30 24 18

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

44

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Selected Business Process Scenario

Customer: Person ATM System Bank

S Withdraw Cash from ATM

S Responsibilities for process activities are modeled by placement in swim lanes S Swim lanes represent roles of participants

insert card and enter PIN (card data, PIN) validate PIN prompt for transaction select "Withdraw Cash (selected transaction) (prompt)

prompt for amoun (prompt for amount) obtain disbursal authorization Success?

enter amount (amount)

(disbursal request) grant disbursal authorization (disbursal authorization)

(cash) remove cash (removal notice) remove card and receip

Yes Dispense Cash report funds delivered print receipt and return card

(dispensing notification) record withdrawal transaction (notification acknowledgement

(card, receipt)
45

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Important Concepts and Relationships

Units of work and other deliverables are another way to help define the scope
Person 1..* customer Account Account +accountNumber:Strin 1..* provides service for 0..* transactsWi 1 Bank 1..* services 1 has Bank Server

Just one account per ATM card?

1 0..* ATM Card +PIN:String 0..* accepts 1..* accepted by

0..*

is serviced by

ATM System 0..* providesServicesThrough

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

46

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Extended Scenario Showing Architecture

Customer: Person insert card and enter PIN (card data, PIN) validate PIN prompt for transaction select "Withdraw Cash (selected transaction) (prompt) ATM Machine ATM Server Bank

prompt for amount (prompt for amount) obtain disbursal authorization Success?

enter amount (amount)

(disbursal request) Determine Bank and Forward (disbursal authorization)

(forwarded request) grant disbursal authorization (disbursal authorization)

(cash) remove cash (removal notice) remove card and receip

Yes Dispense Cash report funds delivered print receipt and return card

(dispensing notification) Determine Bank and Forward (notification acknowledgement)

(forwarded notificaton) record withdrawal transaction (notification acknowledgemn

(card, receipt)
47

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Proposed Topology
S Initial topology design can be a simplified representation of the actual deployment topology
S Important thing is to identify LAN segments and WAN connections
ATM Mahchines ATM_Machine 0..* ATM Server: ATM_Server 1 Bank Servers: Bank_Server 0..*

<<lanSegment>> ATM Machine Lan

<<lanSegment>> ATM System LAN

<<lanSegment>> Bank LAN

<<wanSegment>> ATM WAN

<<wanSegment>> Bank WAN

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

48

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Architecture Evaluation
The ability of the architecture to perform adequately The feasibility of implementing the architecture within the cost and schedule guidelines The ability of the architecture to evolve over time The ability of the architecture to accommodate unusual situations Compliance with enterprise standards and architecture

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

49

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Enterprise SOA
S Architecture and Services Overview S Architecture Challenges S Leveraging the TIBCO Architecture Method S Enterprise SOA
S Governance S Mindset S Organization S Technical

S Tools Demonstration

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

50

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Governance Is Essential
S For deciding what ought to be a service
S Ensuring ROI S Limiting speculative service development

S For ensuring those with appropriate insight participate in specifying the service S For ensuring information about services is appropriately disseminated to potential users S For ensuring that services get used and not re-invented S For coordinating service operation with dependent systems

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

51

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Mindset Issues
S Services are not about technology
S Services are about cost-effectiveness S Focus should be on what reusable functionality is needed S Technology issues are secondary

S Every interface isnt a service!

S Services involve overhead, both at design and run-time S Granularity of work must outweigh the overhead S Must demonstrate potential for reusability (commonality) S Identify the multiple users of the service S Make sure that the functionality is, indeed, the same!

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

52

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Organizational Challenges

Who defines the service? Who pays for it?

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

53

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Technical Challenges

Is it even possible to use the same service everywhere?

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

54

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Technical Best Practices

S Standardize your service delivery mechanisms
S Do it thoughtfully - these will become your standards mistakes will be expensive to correct S You may not get to a single standard! S You get the ROI from minimizing the variations

S S

Include event notification as well as request/reply in your thinking! Use standards where applicable and appropriate
S Avoid rolling your own (re-inventing an existing wheel) S Recognize that standards are not yet mature S e.g. WS-Notification and WS-Eventing S Modular WS- standards ease the evolution

Cover the full CRUD cycle in every service!

S Design Create, Read, Update, and Delete for all entities S Partial coverage almost always requires massive rework to complete, even in the interface design

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

55

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

The Standards Dont Cover it All!

S Many standards require infrastructure investments
S WS-Security, WS-Policy require a credentialing infrastructure

S UDDI standardizes the mechanics of accessing information about services, but not the content
S Your own policies and practices must manage the content

S WSDL will not tell you the design intent of the service
S When you should or should not use the service

S You probably want to control and manage the actual access to services
S Both for capacity planning and for access control purposes S You need processes for this

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

56

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Keys to Services Success

Keep the big picture in focus
S Its about ROI

Make sure those with insight participate in service definition and investment decisions Assign key responsibilities
S Business Process Architect, Systems Architect, Project Manager

Provide the authority to make them effective

S Business Executive Sponsor, IT Executive Sponsor

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

57

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Tools Demonstration
Architecture and Services Organizational Challenges Leveraging the TIBCO Architecture Method Enterprise SOA Tools Demonstration
S Load analysis

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

58

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Load Analysis Technique and Tool Demo

S Identify the scenarios that account for a majority of the work S Synthesize the architecture for those scenarios
S Component activities, communications, topology

S Evaluate the peak loading

S Of the processes/machines S Of the network segments

S Interpret the loading in terms of hardware requirements

S Machine sizing and configuration S Network bandwidth

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

59

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Architecture Fundamentals

April 11, 2006

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services. This document is provided for informational purposes only and its contents are subject to change without notice. TIBCO makes no warranties, express or implied, in or relating to this document or any information in it, including, without limitation, that this document, or any information in it, is error-free or meets any conditions of merchantability or fitness for a particular purpose. This document may not be reproduced or transmitted in any form or by any means without our prior written permission.

Fundamentals of TIBCO Architecture Part 2: Implementing Enterprise Services with TIBCO

April 11, 2006 Paul Asmar Vice President, Global Architects Medha Samant Senior Global Architect

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services. This document is provided for informational purposes only and its contents are subject to change without notice. TIBCO makes no warranties, express or implied, in or relating to this document or any information in it, including, without limitation, that this document, or any information in it, is error-free or meets any conditions of merchantability or fitness for a particular purpose. This document may not be reproduced or transmitted in any form or by any means without our prior written permission.

Implementing Enterprise Services with TIBCO Objective and Topics Formulate strategies for implementing TIBCO products supporting the SOA vision
S Services Infrastructure S Services Design, Implementation and Orchestration S Services Deployment S Scalability / Fault Tolerance S Lifecycle Management

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

62

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Integration Backbone & ESB Reference Architecture

TIBCO Integrated Services Environment (ISE) Services Construction & Orchestration

Custom Apps J2EE/.NET Packaged App
Adapter

Mainframe
Adapter

Trading Partner Services

Data Integration ETL & JDBC

New Service

Existing Service

WS

WS

TIBCO Integration Backbone & ESB

Core ESB Services Web Services SOAP WSDL Intelligent Service Data Runtime Mediation Routing Container Subject XSLT Content Multi-Protocol Message Translation HTTP MQSeries Any JMS TIBCO EMS TIBCO Rendezvous
S S S

Event Services

Cross Referencing Security

S

Exception Handling

Transactions
S S

XA

JTA

SSL

WSS

Audit & Logging

TIBCO Repository

UDDI Registry

Security & Policy

Services Lifecycle Management & Assurance TIBCO Management & Monitor TIBCO USER CONFERENCE / 2006

TIBCO USER CONFERENCE / 2004

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

S S

TIBCO Portal Services

TIBCO Rich Clients

Presentation Services

63

What Is an Enterprise Service Bus?

S S Gartner coined the term ESB Definitions vary wildly
S A product (Gartner, Sonic, ) S Technology that supports ED-SOA (TIBCO, Forrester) S A pattern (IBM, who just launched 2 ESB products) S Optionally contains content-based routing, multi-protocol support, registry, identity management, process orchestration (vendors, customers)

What is consistent? ESB supports:

S JMS-based asynchronous messaging S Support for Web services and registries S Routing and standards based transformation

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

64

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Services Infrastructure
S Services Infrastructure
S Messaging backbone S Transport level monitoring and security S WS Security

S Services Identification, Implementation and Orchestration S Services Deployment S Scalability and Fault Tolerance S Change Management

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

65

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Enterprise Messaging Service

Supports JMS specification v1.1 Store-and-forward architecture Robust, highly-scalable performance Numerous TIBCO enhancements that retain compliance with the specification
C-based server for performance

JMS JMS Client Client

Pure Java client library for portability

EMS EMS Server Server

Store File

JMS JMS Client Client

Multiple servers may be combined for load-balancing and fault-tolerance

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

66

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO EMS Features

S Security Authorization and access control, SSL S Administration S Fault tolerant server pairs S Server routing S Bridging between destinations S Flow control mechanisms S C, C#, Java client APIs S Rendezvous, SmartSockets bridging S Integration with 3rd party naming services (JNDI) S Integration with 3rd party application servers
S JBoss, WebSphere, WebLogic, etc.
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

67

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

EMS Server Routing

S Provides load balancing and improved WAN performance S Persistent messages are written to disk at each server S Servers forward messages to peers only when there is client interest

Server

Route

Server

App

App

App

App

App

App

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

68

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

EMS Routing Examples

Topic messages can travel one hop or multiple hops (from the first server) Queue messages can travel only one hop to the home queue, and one hop form the home queue
A C

B
TIBCO USER CONFERENCE / 2004

D
69

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

EMS Overlapping Zones Example

EMS EMS Client Client

San Francisco

1-Hop Zone London

Multi Hop Zone

1-Hop Zone
EMS EMS Client Client

EMS EMS Client Client

1-Hop Zone New York

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

70

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

EMS Destination Bridges

S Administratively controlled bridging between client destinations
S Any combination of queues and topics may be bridged S Sample use cases: S Unobtrusively logging messages to a database S Monitoring messages sent to a load-balanced queue
Queue Receiver

Sender

Bridge

Queue Receiver

Load-balanced workers

Topic Subscriber Topic Subscriber Administrative observers

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

71

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Rendezvous
Distributed architecture
S Reliable UDP/PGM multicast, broadcast, unicast on the LAN S TCP-connected software routers for WANs
Host A Host B Host C Host D

RV App RV lib

RV App RV lib

RV App RV lib

RV App RV lib

RV App RV lib

rvd

rvd

rvd

rvd may be auto started by applications

LAN

rvrd
WAN

rvrd

LAN

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

72

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Rendezvous Features

S Different QoS
S Reliable S Guaranteed

S 1-of-n delivery (distributed queues) S Fault tolerant application groups S WAN routing
S RVRD RV Routing Daemon S RVRD peer-to-peer data compression

S Daemon configuration via HTTP S Routing daemon subject weights and path costs

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

73

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO SmartSockets
S Mature, stable provider-based publish subscribe S Best-effort and guaranteed quality-of-service S Real-time monitoring of infrastructure and applications S Rich internet application support S Key markets: Finance & Aerospace
RTservers
RTclient RTclient RTclient

RTclient

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

74

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Hybrid Messaging Architecture

JMS JMS Client Client C C Client Client .NET .NET Client Client

Java Java Application Application Server Server MDB EJB

SmartSockets

TIBCO Enterprise Messaging Service

TIBCO Rendezvous TIBCO TIBCO Administrator Administrator

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

75

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Messaging Option Considerations

TIBCO Enterprise Message Service
When you want standards-based integration When message security is a high priority When you must integrate with Java applications and/or J2EE app server When you must integrate with applications that already support JMS

TIBCO Rendezvous
When a high fan-out is required When the network structure is changing fast When minimum administration overhead is required When excessive auditing and tracing is NOT required

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

76

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Efficient Messaging Design

S Solid and consistent destination naming scheme S Messages should be self-describing S Scaling and load-balancing should be considered as part of design S Be careful about using out of box configuration
S Proper configuration and tuning is required to ensure reliability and performance of the messaging subsystem

S Persistent messages should only be used when required S Slow consumers can cause performance degradation in the message layer S Age out messages and use exception handler to deal with old messages
S EMS persistence is not a database

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

77

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Services Infrastructure Tuning

S EMS Server
S Pre-allocate file storage S Set max message memory S Enable message swapping S Adjust queue level pre-fetch S Set reserve_memory in case of emergency S Disable un-necessary message tracing, console trace and log trace

S EMS Client
S Make use of EMS routing as per your network layout S Use message bridging for slow topic consumers S Use features such as message compression, message expiry, when appropriate S Disable non-mandatory JMS headers S Use flow control S Avoid extensive use of message selectors S Choose delivery mode and acknowledgement modes wisely

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

78

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Distributed Monitoring Architecture

App
Apps Apps Apps Apps Apps Apps Log file

JMX
Hawk Hawk Agent Agent Hawk Hawk Agent Agent Hawk Hawk Agent Agent

AMI
Hawk Hawk Agent Agent

Rule Bases

TIBCO Messaging

Hawk Display

TIBCO Admin

EM Advisor

Custom Console

Tivoli Adapter

SNMP Publisher

Event Service

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

79

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Administrator
S User Management
S Users S Roles S Authentication

S Resource Management
S Machines S Applications S Domains

S Application Management
S Configuration S Deployment S Monitoring
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

80

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Monitoring Domain

S Managed by a TIBCO Administration Server
S Responsible for maintaining server-based projects

S Multiple administration domains may exist on one server

S Each domain must have an associated master server

S Stores user and group information in the domain data store

S Can also sync with LDAP server for users and groups
S SunONE Directory Server, MS Active Directory, Novell eDirectory

S By default, all machines that belong to a domain are expected to be on the same network subnet
S Can use RVRD if access across subnets is required

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

81

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

EMS Administration
EMS Administration Utility
S Command-line interface

TIBCO Administrator
S Web-based GUI

Custom interface using API

S Provided by EMS (not the JMS spec)

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

82

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Managing EMS with TIBCO Administrator

S Use the Domain Utility to add servers S View information on EMS Server:
S Queues / Topics S Settings / Statistics S Connections S Producers, Consumers S Routes, Durables S Etc.

S Edit common server settings, manage queues, topics, and other functionality

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

83

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Monitoring EMS with TIBCO Hawk

S EMS ships with Hawk Microagent
S tibemsadmin.hma

S Provides methods for monitoring and managing EMS Server

S HawkController class for monitoring and managing S HawkListener class for monitoring

S Example methods
S Get users, get connections S Get topics, routes, queues S Etc.

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

84

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Using EMS for Hawk Network Transport

HMA (AMI App)

RV Network 127.0.0.1

rvd

Agent

tcp

EMS tibemsd

tcp

Hawk Console

rvd

Agent

S Using the loopback address as the RV network parameter isolates all RV traffic the local machine
HMA (AMI App)

S RV is now packaged with Hawk and does not require a separate installation

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

85

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Infrastructure Security Requirements

S Authentication
S Reliably determining the identity of communicating party

S Authorization
S Granting permission to access a resource

S Encryption
S Scrambling the information so that only someone knowing the appropriate secret can obtain original information (through decryption)

S SSL Secure Socket Layer

S Protocol for transmitting encrypted data by a way of the Internet or internal network

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

86

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Security in TIBCO EMS

S SSL communication between
S Java client and tibemsd server S C client and tibemsd server S COBOL client and tibemsd server S tibemsadmin tool and tibemsd server S Two routed servers S Two fault-tolerant servers

S Access control on each destination Permissions are checked

S On creation of publisher and subscriber on the destination S On send and receive of each message

S Support for external hardware accelerators

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

87

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Security in TIBCO RV
S SSL between
S RV app and daemon
S RVSD

S Routing daemon neighbors

S RVSRD

S Browser and daemon

S https

Single firewall

Double firewall
TIBCO USER CONFERENCE / 2006
88

TIBCO USER CONFERENCE / 2004

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Security in TIBCO Administrator

S User Management
S Role-based Access Control (RBAC) S Management of authentication, roles and users

S Resource Management
S Monitoring of machines and applications in TIBCO Domain

S Application Management
S Creation, configuration, deployment and monitoring of applications

S Directory Synchronization
S Secure (encrypted and authenticated) synchronization with LDAP

S Remote Administration
S HTTPS interface for administration, metadata and deployment configuration

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

89

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Secure Communications

https

User, Role Management Access Control

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

90

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Web Service Security in TIBCO BusinessWorks

S BW 5.3 supports WS-Security 1.0 S Can encrypt elements of a SOAP message without encrypting entire message S WS-Security implemented using two shared resources:
S WS-Security Policy S WS-Security Policy Association

S Policy-based security means rules can be added or changed without having to modify existing services

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

91

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

WS-Security Policy
S Defines security policy that can be applied to a security subject:
S Authentication Policy S Username Password Token S X.509 Token S Integrity Policy Based on XML signature S Username Password Token S X.509 Token S Confidentiality Policy Based on XML encryption S X.509 Token S Timeout Policy S Adds timestamp to SOAP message S Provides mechanism to reject message based on timestamp

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

92

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

WS-Security Policy Association

S Allows association of WS-Security policies to a security subject S Security subjects can have Inbound, Outbound, Inbound Fault, and Outbound Fault security policies S Inbound tab allows users to define signature and encryption policy for message parts that need to be verified for inbound SOAP message S Outbound tab allows users to define signature and encryption policy for outbound SOAP message parts

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

93

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Services Identification, Implementation and Orchestration

S Services Infrastructure S Services Identification, Implementation and Orchestration
S Services identification S Process design S Implementing Web Services S Service engine architecture S Service orchestration

S Services Deployment S Scalability / Fault Tolerance S Lifecycle Management

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

94

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Common Services on ESB

S Common Services are reusable components that
S S S S S Are self-contained Have well-defined interface Provide consistent behavior and functionality across invocations Use standards to ensure interoperability and adaptability across the enterprise Are manageable and discoverable through a common framework

What benefits do they provide?

S S S S Reduce application development effort and complexity Enforce consistency Provide significant cost savings Minimize overall project risk

Two types:
S S Infrastructure Services Auditing, Exception Handling, Cross-referencing Business Services Tax Lookup, Product Pricing, Sales Order Validation

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

95

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Service Identification
Top-Down Approach
1. 2. 3. 4. 5. Develop a Business Process Map Map Applications to Business Process Develop Interface Wire Diagrams Identify Patterns Implement Services a) All-new service b) Wrapped service c) Composite service 4. 2. 3. 1.

Bottom-Up Approach
Audit existing IT assets a) Examine applications boundaries and business objects b) Look for CRUD in data producers and consumers Identify infrastructure services Document functionality exposed by each S S Business Unit, Geographic location

Document organizational interfaces Customers, Partners, Suppliers

poor identification of shared

infrastructure expensive and time consuming
TIBCO USER CONFERENCE / 2006

can fail to capture the current

business needs can waste time on areas of lesser business importance
96

TIBCO USER CONFERENCE / 2004

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Business Justification for SOA Projects

S Project S

by project (hidden)

S Enterprise S S

strategic investment

Build lots of little SOAs Part of doing business S Electronic commerce S Customer Care S Provisioning / Fulfillment

Pooling of multiple common project expenses Alignment with strategic business goals S Mergers and Acquisitions S New product or service offering S 360 Degree view of customer S Reduction of IT expenses S Six Sigma Initiative

S Project by project (visible)

Build a single SOA incrementally S Fix existing Customer Dissatisfaction S Poor visibility S Slow execution S Quality problems S Faster Time to Market S Pre-packaged services S S S

Regulatory imperative Long-term TCO argument Insurance policy / Risk Mitigation

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

97

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO BusinessWorks 5.3

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

98

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Distinct BusinessWorks Environments

Design
S Define processes S Configure services S Test and debug S Generate EAR
TIBCO Designer

Runtime
S Configure applications S Deploy S Manage and monitor S Administer
BW Engine
TIBCO Administrator
Domain Server
Users, Resources Project Repository

Web Server

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

99

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Designer
Adapters, Services, Processes, Deployment, Management

Graphical Process Modeling

Fully Integrated Test Environment

Drag-n-Drop DragAccess to Resources

Native Standards based XSLT Mapper

Intuitive graphical design environment streamlines Intuitive graphical design environment streamlines time and cost of development and training time and cost of development and training
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

100

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Standards Leadership and Support

Area
Reliable Messaging Events Alerts/ Notifications

Spec
WS-ReliableMessaging WS-Eventing WS-Notifications

TIBCO Leadership
S Member of WS-Reliable Exchange Technical Committee S Co-author of spec (with Microsoft, IBM and BEA) S Co-author of spec (with Microsoft and BEA) S Co-author and member of Technical Committee S Spec split into WS-BaseNotification, WS-BrokeredNotification and WS-Topics S TIBCO driving consolidation of WS-Eventing and WS-BaseNotification S Actively driving WS-Addressing Working Group S Charter and voting member of OASIS Technical Committee S Demonstrated WS-Security Interop at Gartner LA Summit S Member of OASIS Technical Committee S WSDM spec ratified as standard and supported by TIBCO products S Member of OASIS Technical Committee and key contributor S Key Working Group participant (contributed expertise in pub/sub messaging) S Pushed for inclusion of sophisticated message exchange patterns S Key Working Group participant S Have obtained 100% interoperability S Member of Expert Group S Member of OASIS Technical Committee S Member of OASIS Technical Committee

Addressing Security Management & Monitoring Orchestration Description Transport Java Business Integration Transactions Security

WS-Addressing WS-Security WSDM (Distributed Management) WS-BPEL WSDL 2.0 SOAP 1.2 JBI (JSR 208) WS-TX (Transactions) WS-SX (SecureExchange)

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

101

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Enabling Asynchronous Services SOAP over JMS S SOAP envelope wrapped in a JMS message S What is the value?
S Reliable message transport with guaranteed delivery S Secure client communications S Synchronous and asynchronous services
S Request/Reply and one-way invocation

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

102

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Designing for Reusability

S Use a standard BW Template customized for your project needs S Use naming standards for services, processes, adapters, shared resources and libraries S Store template under a version control environment S This leads to:
S Common look and feel across projects S Easy to import/export components S Improved reusability

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

103

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

BW Runtime Engine
S Able to handle a continuous stream of services and processes, each with dozens of activities, in an operating environment with finite critical resources
S i.e., memory, CPUs, threads, connections

S S S S S S S S

Schedule jobs and give each an equal opportunity to execute Provides XML data transformation and validation service Evaluate the transitions (XPath) and control the flow Perform connection/session management with recovery/retries Engine crash and job recovery Exception management and logging Enables management and monitoring services Reduces the need for custom coding of services

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

104

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

BW 5.3 Engine Architecture

Process Starters Ready/blocked state Thread Pool (for Job execution) T1 Job Pool (in memory) Dispatch Queue (ready jobs) T2 T3

Binding|XSLT|Validate Activity Binding|XSLT|Validate Activity Binding|XSLT|Validate Activity

T-N Binding|XSLT|Validate Activity

Queue

3 Max Threads ...

Checkpoint

5
Step Count

7 Flow
Limit Or paged

4 Activation ...
Limit Recover Reactivate

JVM
6
Heap size

1
Connections/ Sessions

2
Max Jobs by type Paged Jobs Checkpoint database

*Circled numbers are tunable parameters.

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

105

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Engine Tuning Parameters

S Flow limit is important when tuning for high-volume message arrival and big jobs (memory-intensive) S Max Jobs is good for big jobs with delays in processing (e.g., request / reply) S Sequencing is best handled in the process design itself using sequencing keys
S No longer need to use max jobs / activation limit

S Heap and max threads depend on hardware

S For example, on a 4 CPU machine:
S Having 4 BW engines with 8 threads each is better than 1 engine with 32 threads

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

106

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Transactions
S A transaction is a logical unit of work
S Group multiple operations into an atomic execution unit

S Operations within a transaction are indivisible

S Either all or none is executed

Begin Transaction
Delete Data Publish Message Insert Data

Database-1 JMS Database-2

End Transaction
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

107

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

BW Transaction Manager
S Transaction demarcation is provided by the Group resource S Transaction is implicitly started at the beginning and terminated at the end of the transaction group S Zero coding facility, just drop the activities inside the group S XA Transaction support for JDBC, JMS, iProcess engine, AE Plug-in

Oracle

JMS

Microsoft SQL Server

108

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

BW 5.3 Features for Services

S Multiple operations per service S Better SOA Orientation in UI S One-click WS wizard S Generate implementation template from WSDL wizard S WSS: XML DSig and XML Encryption S SOAP/JMS Topic Support S WS-I Certification S UDDI Export at design and deployment time

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

109

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Service Orchestration
The concept of a flow or process exists at many levels Business Process Management B2B Collaboration Human Workflow Form Flow

Distributed Transactions Business Process Automation Transactions Message Exchange Patterns Sequencing
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

110

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

BusinessWorks for Service Orchestration

S S

BusinessWorks orchestrates services to form a complete business process Same design / development / deployment / monitoring environment

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

111

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

WS-BPEL
S What is WS-BPEL?
S Defines a syntax for the choreography of existing Web Services. Dependent on WSDL, XML Schema, XPath, etc.

S Features
S Ability to combine block-structured and graph-structured paradigms S Ability to specify compensation of faulted scopes S Event handling S Late Binding

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

112

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

BusinessWorks and BPEL

S BPEL is not

S a way to export BW Processes in a Portable Format S a handoff format, from Business Analyst to Implementer
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

113

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Exporting a Typical BPM Process to WS-BPEL

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

114

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Services Deployment
S Services Infrastructure S Services Design, Implementation and Orchestration S Services Deployment
S Deployment Model S Manual and Automated S UDDI

S Scalability / Fault Tolerance S Lifecycle Management

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

115

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Deployment Model TIBCO Administrator 5.3

S DB or file for storing domain data S Local or server-based for deploying application data
7,%&2 'HVLJQHU
UDH /0; 5$6 5$3
DB OR File

Domain Data

7,%&2 $GPLQLVWUDWRU

Application Data

%: (QJLQH

7,%&2 $GDSWHU

%: (QJLQH

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

116

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

TIBCO Application Deployment

S Deployment process includes:
S Binding services to machines S Hawk rulebase uploading S Service instance configuration
S e.g. JVM properties

S Fault Tolerance

S Two ways to deploy applications:

S Manual using TIBCO Administrator GUI S Command-line deployment for automation

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

117

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Deployment Using TIBCO Administrator

Deployed Project

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

118

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Deployment Using Scripts

S Need for scripted deployment
S Minimize the need to use administration GUI (i.e., human interaction) S Ability to export entire deployment into an XML file S Ease of re-deployment

S buildear Utility to create application archive

S From an entire project, or S From a specific resource within a project

S AppManage Utility to upload, configure, deploy, start and stop applications using script

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

119

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Publishing Services to UDDI

S BW 5.3 and Administrator 5.3 support UDDI
S Publishing to registry S Look up from registry

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

120

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Scalability / Fault Tolerance

S Services Infrastructure S Services Identification, Implementation and Orchestration S Services Deployment S Scalability / Fault Tolerance
S Service load balancing S Service fault tolerance

S Lifecycle Management

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

121

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

BW Engine Load Balancing

S Static
S Manually configured during deployment S Deploy applications to different engines

S Dynamic
S Process design using process starters:
S JMS Queue Receiver S RVDQ Subscriber

S Controlled at runtime by messaging system in coordination with BW engine

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

122

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Load Balancing Using RVDQ

S At design-time, RVDQ transport is configured and used by BW process S At deployment, engines configured in DQ group S At runtime, scheduler dynamically distributes workload; workers process assigned tasks
Worker 10 Scheduler 40
As si

DQ Group
gn Tas k

Worker 30

Worker 20

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

123

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

EMS Load Balancing

S Load balanced Queue receivers
JMS JMS Producer Producer

JMS Queue JMS Queue Receiver Receiver

EMS EMS Server Server

JMS Queue JMS Queue Receiver Receiver JMS Queue JMS Queue Receiver Receiver

S Load balanced multiple servers

JMS JMS Client Client JMS JMS Client Client JMS JMS Client Client
JMS Client JMS Client Server1 | |Server2 Server1 Server2
TIBCO USER CONFERENCE / 2004

EMS EMS Server1 Server1

EMS EMS Server2 Server2

JMS JMS Client Client JMS JMS Client Client

TIBCO USER CONFERENCE / 2006

124

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

EMS Fault Tolerance

Shared State
Dual-ported SCSI, SAN, NAS, etc.

Non-Active Active Server

Heartbeats (may be redundant)

Backup Active Server

App

App

App

App

App

App

Client connections re-established Sharedconnections obtained ClientActive server fails Shared state lock disrupted Backup server relinquished Heartbeats activates state lock stop

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

125

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

BW Engine Fault Tolerance

S Warm stand-by (backup in wait state) S Uses RVFT to detect BW process engine failures
S Primary/Secondary S Peer-to-Peer

S Persistent data transferred via database or file system

S Checkpoints S Persistent shared variables

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

126

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Cluster Deployment Considerations

S Understand the underlying clustering software fail-over capabilities:
S Virtual IP addressing S Redundant data stores S Mounting shared drives S Implementation of cluster packages

S Besides component fail-over, the system state also needs to be recovered:

S Persistent message data stores, log files, BW checkpoints, etc.

S Do not confuse TIBCO built-in fault tolerance techniques with what is provided by clustering software
S Avoid multiple controlling mechanisms if possible

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

127

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Lifecycle Management
S Services Infrastructure S Services Design, Implementation and Orchestration S Services Deployment S Scalability / Fault Tolerance S Lifecycle Management
S Project environments S Services lifecycle

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

128

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Environments Supporting Project Lifecycle

Domain Dev A Domain Dev B Domain Dev C

Development & Unit Test

S Multiple developers S Own domains S Project synched to VCS

Integration Test / QA
S Multiple machines S Single domain S Mirrors production environment
VCS
fsaf

Domain QA

fadsfafdsa

Production
Domain Prod

S Multiple machines
fadsfafdsa

S Single domain

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

129

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Environment Planning
S Frequency and size of information flow (including projected growth):
S Average and peak rates of transactions S Average and peak rates of messages S Average message size

S How messages are distributed among components and machines

S Help determine any latency requirements for components

S Response time requirements S Storage capacity needs:

S Amount of persistent messages queued in messaging layer S Amount of runtime data kept (e.g. logs, information stored in databases)

S Fault Tolerance requirements

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

130

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Capacity Planning Recommendations

S Based on capacity and fail-over requirements:
S Calculate roughly how many BW engines are required S Determine messaging infrastructure requirements (e.g. # EMS servers) S Understand adapter requirements (e.g. SAP, Siebel, ADB)

Calculate rough estimates for CPU and RAM requirements:

S Rule of thumb: # BW engines per machine should not exceed # CPUs (up to 2x) S Memory requirements can be estimated once components are determined

Assess network load requirements based on size and frequency of messages

S Determine if network bandwidth can support the underlying infrastructure

Derive a capacity test plan:

S To test estimates early on in the development cycle S For end to end performance testing in QA environment

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

131

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Version Control
S BW supports version control to increase reusability and productivity by sharing project objects among developers S A typical BW multi-developer project can be divided into different functional groups and mapped to the folder structures in the BW project template
S Check-in / out project components using supported RCS S Visual Source-Safe, Perforce, ClearCase, XML Canon S Check-in / out project components using other RCS tools S Open project in Designer with File Sharing option selected S Developer can only work on objects with assigned privileges

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

132

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Design-time Version Control Support

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

133

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Overview of Environment Migration

Development
Project V-file structure

QA
Extract EAR files
EAR SAR PAR AAR

Production
Extract EAR files
EAR SAR PAR AAR

Build and debug project in TIBCO Designer

Configure Global Variables

Configure Global Variables

Project stored in VCS

Deploy into QA environment

Deploy into Production environment

Generate EAR files for deployment

Run components in QA

Run components in Production

Project Lifecycle
TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

134

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Use of Global Variables

S All environment related parameters should be global variables
S Infrastructure related parameters S Network services and ports, EMS Server configuration, destinations, etc. S End system parameters S Application login IDs, server connection parameters, etc. S File and database parameters S Directory and file location, database connection, etc.

TIBCO USER CONFERENCE / 2004

TIBCO USER CONFERENCE / 2006

135

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Services Lifecycle
Refer to Implementation Project Life Cycle starting with Requirements Phase Start Build & Deploy Service
Deliverables: Propose New or Change to Service Service Proposal Develop Service Spec and Estimates Service Specification Design, Build, and Test Service Design Artifacts Deploy Service and Service Usage Info Deployable Components Service Discovery Artifacts Service Access Procedures Service Ready Services Librarians

Gates: Gate Keeper:

Proposal Approval It Steering Committee

Project Approval IT Steering Committee

Deployment Approval Enterprise Architecture

Service Change Required

Link Service
Deliverables: Gates: Gate Keeper:

Identify Service to Be Used None None None

Request Service Access Service Access Request

Implement Service Access None

Utilize Service Service Metrics None None

Operate Service

Schedule Service Start

A governance process that spans the entire Services Life Cycle is needed!
Service Access Approval None Services Librarians None Start Service
Service Ready to be Started

Schedule Service Shutdown

Stop Service

Deliverables: Gates: Gate Keeper:

Service Start Schedule Start Schedule Approval Services Librarians

Condition Requiring Shutdown None None

Service Shutdown Schedule Shutdown Schedule Approval Services Librarians

None None None

Retire Service
Deliverables: Gates:

Request Services Retirement Service Retirement Request Service Retirement Approval

Retire Service Service Retirement Announcement None None

End 136

TIBCO USER CONFERENCE / 2004

IT Steering Committee Gate Keeper: TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services.

Fundamentals of TIBCO Architecture Thank You for Your Attendance

April 11, 2006

TIBCO USER CONFERENCE / 2006

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services. This document is provided for informational purposes only and its contents are subject to change without notice. TIBCO makes no warranties, express or implied, in or relating to this document or any information in it, including, without limitation, that this document, or any information in it, is error-free or meets any conditions of merchantability or fitness for a particular purpose. This document may not be reproduced or transmitted in any form or by any means without our prior written permission.