Tib Adsbl Concepts

7/22/2019 Tib Adsbl Concepts

1/62

TIBCO ActiveMatrixAdapter for

Siebel

ConceptsSoftware Release 6.0April 2010


2/62

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDEDOR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITEDADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLEDSOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FORANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF ALICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSEAGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USERLICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THESOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARELICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATEDIN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMSAND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND ANAGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright laws andtreaties. No part of this document may be reproduced in any form without the written authorization of TIBCOSoftware Inc.

TIB, TIBCO, TIBCO Adapter, TIBCO ActiveMatrix, Predictive Business, Information Bus, The Power of Now,TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Administrator, TIBCO Designer, TIBCORuntime Agent, TIBCO Hawk, TIBCO Enterprise Message Service, TIBCO Designer Add-in for TIBCO Business

Studio, TIBCO ActiveMatrix Service Grid, TIBCO ActiveMatrix Service Bus, TIBCO ActiveMatrixBusinessWorks Service Engine, TIBCO ActiveEnterprise, and TIBCO Business Studio are either registeredtrademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of SunMicrosystems, Inc. in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALLOPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAMETIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A

SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BEINCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKEIMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED INTHIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDINGBUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright 1998-2010 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information


3/62

TIBCO ActiveMatrix Adapter for Siebel Concepts

Contents | iii

Contents

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

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

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

TIBCO ActiveMatrix Adapter for Siebel Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Third-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

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

How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

What is an Adapter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Adapter Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Adapter Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Adapter Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Publication Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Subscription Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Request-Response Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Request-Response Invocation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Adapter Services Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Choosing an Adapter Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 TIBCO ActiveMatrix Adapter for Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Siebel eBusiness Applications Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Siebel Multi-layered Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Siebel Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Adapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Adapter Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

How the Adapter Interfaces with the Siebel Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Adapter Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Publication Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Subscription Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20


4/62


iv | Contents

Request-Response Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Request-Response Invocation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Schema Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 3 Adapter Infrastructure Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

TIBCO Runtime Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

TIBCO Domain Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

TIBCO Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

TIBCO Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

TIBCO Administration Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

TIBCO Administration Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

TIBCO Administrator GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

TIBCO ActiveMatrix BusinessWorks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

TIBCO Hawk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Adapter Microagents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ActiveMatrix Resource Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Composite Element Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Service Assembly Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

TIBCO ActiveMatrix Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

TIBCO ActiveMatrix Administrator Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Enterprise and Environment Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Service Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45


5/62


Figures |v

Figures

Figure 1 Adapters Provide a Bridge for Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Figure 2 Choosing an Adapter Service: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Figure 3 Choosing an Adapter Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 4 Multi-layered Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Figure 5 Logical Architecture for Integration With Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 6 Typical Publication Service Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Figure 7 Typical Subscription Service Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 8 Typical Request-Response Service Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 9 Typical Request-Response Invocation Service Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Figure 10 TIBCO Designer Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Figure 11 TIBCO Administrator GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Figure 12 TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 13 Component Property Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Figure 14 Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 15 Service Assembly Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Figure 16 TIBCO ActiveMatrix Administration Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 17 TIBCO ActiveMatrix Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41


6/62


vi | Figures


7/62


Tables |vii

Tables

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

Table 2 Syntax Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Table 3 Adapter Services Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6


8/62


viii | Tables


9/62


| ix

Preface

This document introduces the fundamentals of TIBCO ActiveMatrix Adapter forSiebel, including what the adapter is and how it works.

Topics

Related Documentation, page x

Typographical Conventions, page xii

How to Contact TIBCO Customer Support, page xv


10/62


x | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO ActiveMatrix Adapter for Siebel Documentation

The following documents form the TIBCO ActiveMatrix Adapter for Siebeldocumentation set:

TIBCO ActiveMatrix Adapter for Siebel Concepts Read this manual to

familiarize yourself with the product and its uses.

TIBCO ActiveMatrix Adapter for Siebel Installation Read this manual to learnhow to install the adapter on your operating system.

TIBCO ActiveMatrix Adapter for Siebel Configuration and Deployment Read thismanual for instructions on how to create, configure, and deploy adapterprojects.

TIBCO ActiveMatrix Adapter for Siebel Examples Read this manual to workthrough the examples provided with the adapter.

TIBCO ActiveMatrix Adapter for Siebel Release Notes Read this document forinformation about new features, deprecated features, and known and closedissues.

The following documents form the TIBCO ActiveMatrix Adapter Service Enginefor Siebel documentation set:

TIBCO ActiveMatrix Adapter Service Engine for Siebel Installation Read thismanual to learn how to install TIBCO ActiveMatrix Adapter Service Engine forSiebel.

TIBCO ActiveMatrix Adapter Service Engine for Siebel Configuration andDeployment Read this manual for instructions on how to create, configureand deploy adapter projects.

TIBCO ActiveMatrix Adapter Service Engine for Siebel Examples Read this

manual to work through the examples provided with the adapter.

TIBCO ActiveMatrix Adapter Service Engine for Siebel Release Notes Read thisdocument for information about new features, deprecated features, andknown and closed issues.

Other TIBCO Product Documentation

You may find it useful to read the documentation for the following TIBCOproducts.


11/62


Preface |xi

TIBCO Designer

TIBCO Administrator

TIBCO ActiveMatrix Administrator TIBCO ActiveMatrix BusinessWorks

TIBCO ActiveMatrix BusinessWorks Service Engine

TIBCO Rendezvous

TIBCO Enterprise Message Service

TIBCO Hawk

TIBCO Adapter SDK

TIBCO Runtime Agent

TIBCO Business Studio

Third-Party Documentation

You may also find it useful to read the Siebel Bookshelf, available from SiebelSystems Inc.


12/62


xii | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

Many TIBCO products must be installed within the same home directory. Thisdirectory is referenced in documentation as TIBCO_HOME. The value ofTIBCO_HOMEdepends on the operating system. For example, on Windows

systems, the default value is C:\tibco.

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

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

Use MyCommandto start the foo process.

bold code

fontBold code font is used in the following ways:

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

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

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

italic font Italic font is used in the following ways:

To indicate a document title. For example: See TIBCO BusinessWorks Concepts. To introduce new terms. For example: A portal page may contain several

portlets. Portletsare mini-applications that run in a portal.

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


13/62


Preface |xiii

Keycombinations

Key names separated by a plus sign indicate keys pressed simultaneously. Forexample: Ctrl+C.

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

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

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

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

Table 1 General Typographical Conventions (Contd)

Convention Use

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical ORthat separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3


14/62


xiv | Typographical Conventions

{ } A logical group of items in a command. Other syntax notations may appearwithin each logical group.

For example, the following command requires two parameters, which can beeither the pair param1and param2, or the pair param3and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parametercan be either param1or param2and the second can be either param3or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters.The first parameter must be param1. You can optionally include param2as thesecond parameter. And the last parameter is either param3or param4.MyCommand param1 [param2] {param3 | param4}

Table 2 Syntax Typographical Conventions (Contd)

Convention Use

P f |


15/62


Preface |xv

How to Contact TIBCO Customer Support

For comments or problems with this manual or the software it addresses, pleasecontact TIBCO Support as follows.

For an overview of TIBCO Support, and information about getting startedwith TIBCO Support, visit this site:

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

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

https://support.tibco.com

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

xvi | How to Contact TIBCO Customer Support
http://www.tibco.com/services/supporthttps://support.tibco.com/https://support.tibco.com/http://www.tibco.com/services/support


16/62


xvi | How to Contact TIBCO Customer Support

|1


17/62


|1

Chapter 1 Introduction

This chapter introduces adapters by explaining their functions and services.

Topics

What is an Adapter?, page 2

Adapter Components, page 3

Adapter Key terms, page 4

Adapter Services, page 5

Choosing an Adapter Service, page 7

2 | Chapter 1 Introduction


18/62



What is an Adapter?

To deploy the best solution for each aspect of your business, you usually have topurchase applications from several different application vendors. Unfortunately,vendors typically have their own way to format and expose data. Thereforeintegrating the various applications across your enterprise poses significantchallenges.

An adapter provides a bridge between an application and your TIBCOintegration environment. Using a no-coding approach to integration, TIBCOAdapters enable packaged applications, databases, and other technologies to

become active participants in the enterprise information flow, regardless of theirdata formats or communication protocols. Integration of new applications doesnot require programming skills and does not interfere with existinginfrastructure.

Adapters isolate the application from more complex actions. Messagetransformation and business process automation can be handled once the data ispublished to the TIBCO infrastructure.

As is shown in the figure below, adapters allow data to be exchanged amongdifferent technologies.

Adapters are available for off-the-shelf applications from leading vendors.Each adapter integrates with at least one, and usually several, of the interfacesexposed by the vendor application.

Database adapters enable an enterprises database to initiate important

business processes based on exception data they identify. Database adaptersalso make data available to the enterprise.

Mainframe adapters enable real-time two way communication betweenthemselves and the rest of a companies business applications and databases.

Adapters can also enable integration with component or object developmentmodels and other messaging technologies.

Figure 1 Adapters Provide a Bridge for Data

Adapter Components |3


19/62


p p |

Adapter Components

The adapter can run either as a standalone process or as a service. When run as aservice, the adapter participates in the Service Oriented Architecture (SOA)environment.

The adapter components are:

Standalone

Using this component you can create adapter projects which run as astandalone process. This adapter component is referred to as the standaloneadapter.

Standalone adapter projects are created and configured using TIBCO Designerand deployed using TIBCO Administrator.

Adapter Service Engine

Using this component you can create and configure adapter projects that canbe deployed as a service in the TIBCO ActiveMatrix environment. This

adapter component is referred to as the adapter service engine.

Adapter service engine projects are created using TIBCO Business Studio anddeployed using TIBCO ActiveMatrix Administrator.

The adapter component is wired with other composite elements in theActiveMatrix SOA Project.

Existing standalone adapter configurations can also be deployed as services.

Throughout this book, references to an adapter include both the standalone andadapter service engine components.



20/62


|

Adapter Key terms

The following key terms are used when describing adapter interactions in thismanual.

Apaletteis a standalone adapter component that contains the screens used togather input at design-time when configuring an adapter with a service. Thepalette is accessed via TIBCO Designer.

Aprojectis a collection of all configured adapter resources. Aprojectcontainsconfiguration information for one or more adapter instances. A local project is

typically used at design-time for testing adapter instances. For production, aproject is typically managed by an administration server provided by theTIBCO Administrator for the standalone adapter and TIBCO ActiveMatrixAdministrator for the adapter service engine.

An .earof an application contains global variables with values set atdesign-time by the standalone adapter. The global variables can be changedduring deployment at the application level, service level, or service instancelevel.

Service Oriented Architecture (SOA) is a software architecture in whichapplications and data are decomposed into discrete, operationallyindependent services, which can be executed in a highly distributed manner.

A business objectis the representation of the data model of the entities that theadapter service engine connects to. The business objects are downloadedduring the design phase and are used by the adapter services.

A containeris an ActiveMatrix runtime entity that hosts componentimplementations and service bindings.

A service assemblyis an ActiveMatrix deployment package. It contains serviceunits and a descriptor that indicates the container into which each service unitis to be deployed. The suffix of a service assembly file is.saf.

The ActiveMatrix services are described in documents expressed in WebServices Description Language (WSDL). The WSDL documents specify the

messages that are required to access a service.

During any service interaction, each service will adopt one of two roles:provider or consumer. A serviceproviderpublishes a WSDL document thatdescribes the services it offers. A service consumeruses the WSDL document todetermine the available services and the messages required to access theservices. A message exchange pattern(MEP) defines the sequence andcardinality of messages sent between the provider and the consumer.

Adapter Services |5


21/62


|

Adapter Services

Adapters are responsible for making information from different applicationsavailable to other applications across an enterprise. To do so, an adapter isconfigured to provide one or more of the following services:

Publication Service

An adapterpublication servicerecognizes when business events happen in avendor application, and asynchronously sends out the event data in realtime tointerested systems in the TIBCO environment.

For example, an adapter can publish an event each time a new customer accountis added to an application. Other applications that receive the event can thenupdate their records just as the original application did.

Subscription Service

An adapter subscription serviceasynchronously performs an actionsuch asupdating business objects or invoking native Application ProgrammingInterfaces (APIs)on a vendor application. The adapter service listens to external

business events, which trigger the appropriate action.

Referring to the previous example, an adapter subscription service can listen forcustomer record creation events (happening in an application and published tothe TIBCO infrastructure) and update another application.

Request-Response Service

In addition to asynchronously publishing and subscribing to events, an adaptercan be used for synchronously retrieving data from, or executing transactionswithin, a vendor application. After the action is performed in the vendorapplication, the adapter service sends a response back to the requester with either

the results of the action or a confirmation that the action occurred. This entireprocess is called request-response, and it is useful for actions such as adding ordeleting business objects.

In the next example, an adapter receives a request message from the TIBCOinfrastructure and sends it to an application. The adapter gets a response from theapplication and returns it.



22/62


Request-Response Invocation Service

An adapter request-response invocationservice is similar to the request-responseservice, except that the roles are reversed. The vendor application is now the

requester or initiator of the service, instead of the provider of the service. Theadapter service acts as a proxy, giving the vendor application the ability to invokesynchronously functionality on an external system.

For example, if the adapter sends a request message from application Y toapplication X, after it processes the message, application X returns the message tothe adapter, which sends the response back to application Y.

Adapter Services Summary

The next table summarizes the services introduced in this section.

Table 3 Adapter Services Summary

Service Initiator Target Event Mode

Publishing service

(sends to target)

Vendorapplication

TIBCOinfrastructure

Asynchronous

Subscribing service

(gets from initiator)

TIBCOinfrastructure

Vendorapplication

Asynchronous

Request-response service

(gets from initiator, waits for response thensends response to target)

TIBCOinfrastructure

Vendorapplication

Synchronous

Request-response invocation service

(sends to target, waits for response, then sendsresponse to initiator)

Vendorapplication

TIBCOinfrastructure

Synchronous

Choosing an Adapter Service |7


23/62


Choosing an Adapter Service

A business integration scenario drives the choice of one adapter service oranother. This section provides a simple flow chart that helps you to choose theservice to use. Not all adapters provide all services and some adapters mayprovide additional services not listed here.

Consider the following environment that involves application X, an adapter, andanother application:

Figure 2 Choosing an Adapter Service: Example

In this scenario, data must be exchanged between the application X and anotherapplication. The other application could be a customer management system, suchas PeopleSoft, or another TIBCO application, such as TIBCO ActiveMatrix

BusinessWorks.

To decide which adapter service to configure in the adapter, start by finding outwhere the scenario beginswhat triggers it. Is the scenario triggered by an eventinside application X, or inside the other application?

For example, when a new customer account is created in application X, must theaccount information also be propagated via the adapter to the other application?Or does a batch business process in TIBCO ActiveMatrix BusinessWorks needinformation from application X to generate some report?

This question is the starting point of the decision chart provided below:

Subnet

TIBCO Adapter for

Application X

Application X

Machine A

Other

Application

Machine B



24/62


Figure 3 Choosing an Adapter Service

Working through the decision chart, if the business process is the creation of acustomer record in application X and if many other applications need to beupdated when the event occurs, but no acknowledgements are required, theadapters publication service should be used.

where is

process

initiated?

application X

must

response

required?

application X another application

update another

application

obtain information

from another application

business process

starts

update one or

many

publication servicerequest-response

invocation service

many

subscription

service

request-response

service

No Yes

acknowledgem

ent required?

only one

no Yes

TIBCO ActiveMatrix Adapter for Siebel |9


25/62


Chapter 2 TIBCO ActiveMatrix Adapter for Siebel

This chapter provides an overview of Siebel eBusiness Applications and explainsTIBCO ActiveMatrix Adapter for Siebel in more detail.

Topics

Siebel eBusiness Applications Overview, page 10

Adapter Overview, page 13

Adapter Services, page 19

Schema Support, page 24

10 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel


26/62


Siebel eBusiness Applications Overview

Siebel Systems provide the most comprehensive family of multi-channeleBusiness applications and services. Siebel eBusiness Applications enableorganizations to create a single source of customer information. This facilitatesselling, marketing, and servicing customers across multiple channels, includingthe web, call centers, field, resellers, retail, and dealer networks.

This section describes the Siebel core architecture. The Siebel architecture allowsTIBCO ActiveMatrix Adapter for Siebel to operate on all Siebel core and industryapplications, independent of the underlying database platform.

Siebel Multi-layered Architecture

Siebel eBusiness Application uses a multi-layered architecture as the foundationfor building Siebel applications. The Siebel application architecture consists of thefollowing layers:

User Interface Objects Layer

Business Objects Layer

Data Objects Layer

Relational Database Management System (RDBMS)

Figure 4 Multi-layered Architecture

A Siebel application uses an object definition to implement one piece of thesoftware, either a user interface, an abstract representation, or a direct database

representation construct. An object definition consists of properties whichcharacterize the software construct that the object definition implements.

Siebel eBusiness Applications Overview |11


27/62


Object definitions in a given layer depend on definitions in the next lower layer,and are insulated from other layers in the architecture. For example, you canmake changes to a Siebel application without changing the underlying databasestructure. Similarly, you can extend the Siebel database schema withoutimpacting the Siebel application.

A standard Siebel application provides a core set of object definitions, which youcan use as the basis for your own tailored application.

Siebel Enterprise provides an application configuration tool called Siebel Tools,which enables you to customize Siebel applications by modifying and creatingobject definitions.

User Interface Objects Layer

The User Interface Objects Layer defines the visual elements with which usersinteract. The Business Objects Layer insulates it from the Data Objects layer andthe underlying database.

Business Objects Layer

The following are the major object types in the Business Objects Layer:

1. Business Component Represents a fundamental business entity in theenterprise, which consists of multiple fields that characterize it. For example,Contact, Business Address, or Activity.

2. Business Object Represents a major functional area in the enterprise, whichconsists of a collection of one or more related business components. Forexample, the Opportunity Business Object consists of Opportunities andrelated Contacts, Activities, Products, and Issues.

3. Integration Objects



28/62


Siebel integration objects allow integration metadata to be represented in SiebelBusiness Objects as common structures that the EAI infrastructure canunderstand. These are logical objects representing multiple Business Objects in asingle entity.

Data Objects Layer

Object definitions in the Data Objects Layer provide a logical representation of theunderlying physical database (constructs like 'table', 'column', and 'index'), andare independent of the installed RDBMS.

Relational Database Management System

This is a third party system. Siebel supports IBM DB2, MS SQL Server, and Oracledatabases. For details on versions and platforms, refer to the Supported Platformssection of the Siebel Bookshelf accompanying your Siebel Application.

Siebel Workflow

This is a process that allows an organization to identify the flow of datathroughout the enterprise, and pass data to and from external applications usingSiebel eBusiness Application Integration (EAI).

Adapter Overview |13


29/62


Adapter Overview

TIBCO ActiveMatrix Adapter for Siebel enables exchange of data between aSiebel system and other external systems through the TIBCO environment inreal-time.

The adapter defines a Business Event Specification to describe how data is sentinto and sent out of the Siebel system. The Business Event Specification isconfigured according to the Siebel Business Object model.

Adapter Features

The adapter provides a rich set of features, which offer maximum flexibility forconfiguration and deployment in real-life usage scenarios. The salient features arelisted below:

Support for Integration Object Schema Using XML TagsThe adaptersupports the downloading of Integration Object Schema either with XML tagsor with field names for Publication and Subscription Services.

Support for Return of Status Keys for Integration ObjectsThe adapter nowsupports the return of Status Keys for an INSERT, UPDATE, UPSERT orDELETE operation on Integration Objects. The Status Keys need to beconfigured for every Integration Object in Siebel (Refer Siebel Bookshelfformore information on Status Keys).

Support for Dynamic Substitution of Parameters in HTTP Business ServiceThe adapter now supports the dynamic substitution of EAI TIBCO HTTPAgent Business Service parameters during invocation. The parameters, whichare supported for dynamic substitution, are HTTP Timeout and HTTP AgentServer. During Request-Response invocation, the HTTP Timeout parametercan be set within the request. The Business Service waits for the HTTP replyfrom the adapter for a specified duration before timing out. This parameter, ifspecified in the request, overrides the parameter specified in the BusinessService user properties.

The HTTP Agent Server parameter can be set within the user properties. TheBusiness Service invokes the adapter server using this parameter. Thisparameter, if specified in the request, overrides the parameter specified in theBusiness Service user properties.

Support for Asynchronous Workflow InvocationThe adapter now supportsinvocation of workflow asynchronously. The adapter returns the Request Id ofthe asynchronous workflow request. This is applicable for Subscription and

Request-Response Services.



30/62


Supports for return of Output Parameters for Workflow InvocationTheadapter now returns all the parameters of the workflow output after theworkflow invocation. This is applicable for Subscription andRequest-Response Services.

Adapter Services The adapter provides Publication, Subscription,Request-Response, and Request-Response Invocation services. Basicconfiguration templates are provided in TIBCO Designer, which you can useto configure adapters and services to control your enterprises data. Theservices are described in detail in section Adapter Services on page 5.

Support for Siebel Database on Microsoft Windows and UNIXAs Siebeldata is accessed via the Siebel Object Interface, the Siebel Business Rules arepreserved regardless of the underlying database platform.

Ability to use Multiple Levels of Siebel Business ComponentsThe adaptercan be configured to use multiple levels of Siebel business components fromSiebel Business Objects.

Ability to Invoke Siebel Business Service The adapter can invoke SiebelBusiness Service. The adapter can invoke any method in a Siebel BusinessService after receiving a message from the TIBCO environment.

Ability to Invoke Siebel Workflow Processes The adapter can invoke SiebelWorkflow processesin real time. The adapter can invoke a process throughthe Siebel Workflow Process Manager after receiving a message from the

TIBCO environment.

Support for Siebel Integration ObjectsSiebel Integration Objects aresupported on both the inbound and the outbound side. You can create schemafor integration objects using TIBCO Designer.

Ability to Publish using Non-Siebel Business Component FunctionalityYou can use the Non-Siebel Business Component function, provided bySiebel, to send data before committing it to the Siebel Database.

Support for Universal Application Network The adapter meets UniversalApplication Network (UAN) standards for the following adapter services:




The multiple levels of Siebel business components can only be used in ahierarchical structure.



31/62


Detection of Lost Siebel Data ConnectionDetection of Siebel DataConnectivity failure is provided along with the ability to re-establish theconnection and prevention of message loss.

Multithreading The adapter supports a static number of threads. The numberof threads is specified at the time of configuration. The number of connectionsto the application server equals the number of threads. With multiple threads,the adapter processes multiple messages concurrently.

Easy-to-use GUITIBCO Designer GUI is available for configuring andmaintaining the adapter.

Support for TIBCO Rendezvous and JMS (Java Message Service)Support

for multiple message transports. TIBCO Rendezvous or TIBCO EnterpriseMessage Service can be used to transport messages to and from the adapter.

TIBCO Rendezvous supports the following quality of services:

Reliable (RV) - This ensures that each multicast or broadcast message isreceived as long as the physical network and packet recipients are working,and the loss of a message is detected.

Certified-delivery (RVCM) - Ensures that a message will be delivered atleast once. This guarantees that every certified message reaches itsintended recipient in the order sent.

Distributed Queue (RVCMQ) - This is designed to deliver a message toone-of-many Subscription services. It has incorporated the features of bothCertified Messaging and Fault Tolerance.

TIBCO Enterprise Message Service supports the following connection types:

Queue - Queue messaging has one sender and one receiver per message.The receiver receives the message whether or not the receiver is active atthe time the message is sent.

Topic - In a Topic message system, senders address messages to a topic.Many senders can publish on a single topic, and a single sender can publishto many receivers. Receivers subscribe to topics, and receive messages onthose topics.



32/62


How the Adapter Interfaces with the Siebel Application

The adapter is a bidirectional gateway between a Siebel application and theTIBCO environment. The distributed architecture of the adapter facilitates

seamless integration into Siebel enterprise. The following figure is a high levelview of how the adapter is integrated with Siebel in the TIBCO environment.

Figure 5 Logical Architecture for Integration With Siebel

The following Siebel application interfaces are used by the adapter.

Siebel VB and Siebel eScript The VB and eScripts are used in the adapterto add validation logic while giving input to the Business Services.

Java Data Bean Interface Java Data Bean Interface provided by Siebel isused to get and set data into the Siebel application. The adapter uses Java DataBean as one of the modes of communicating with the Siebel application.

Siebel Business Service Siebel provides Business Services for moving andconverting the data formats between Siebel and other external applications.The adapter uses custom made Business Services to invoke the outboundrequests from Siebel. It also uses a Siebel provided Business Service, EAISiebel Adapterto get and set integration objects into the Siebel application.

Multithreading

The adapter provides the flexibility to run concurrent events by running multiplethreads for both inbound (Request-Response Service and Subscription Service)and outbound services (Publication and Request-Response Invocation Service).The threads created for outbound services are responsible for receiving the

Message

Siebel

Application

TIBCO

ActiveMatrix

Adapter for

Siebel

TIBCO Environment



33/62


HTTP/HTTPS requests from Siebel and cannot be used for processing inboundsessions. Similarly, threads used for inbound services cannot be used foroutbound service event execution. Both HTTP and HTTPS share the samethreadpool.

The threads to process inbound events are configured at the session level and notat the service level. For example, if you configure two threads for a RVCMSession,a total of two threads are created for processing the events which are using thissession. In a typical configuration, one session could be used by a SubscriptionService as well as Request-Response service. In that case, the same thread canprocess both types of events.

Connection Pooling

The adapter has the capability of connection pooling. During connection pooling,there is a one-to-one mapping between the threads and the Siebel connection.This means that the number of connections to Siebel is the same as the number ofthreads. The thread uses the same connection with Siebel till it is terminated.

Consider a scenario where there are two Publication Service instances usingRVCM, two Subscription Service instances using RVCMQ and two SubscriptionService instances configured using TIBCO Rendezvous messaging format. Thefollowing default sessions are created in the adapter: DefaultRVCMSession,DefaultRVCMQSessionand DefaultRVSession.

Assume that:

You have specified HTTP threadCount(outbound) as 2, inbound thread countas3 and threadCountfor DefaultRVCMQSessionas 2.

You have not specified any threadCountvalue for DefaultRVCMSessionandDefaultRVSessionin the Multithreadingtab.

The adapter creates the connections based on the following calculation:

2 (HTTP Thread Count) + 2 (DefaultRVCMQSession) + 3 (default Inbound threadcount for DefaultRVCMSession) + 3 (default Inbound thread count forDefaultRVSession) + 1 backup connection object (which is not shown in theconnection pool size displayed on the adapter console) = 11.

If there are no Subscription Services in a session, you should explicitly set thedispatcherCountfor that session to 0so that the adapter does not createconnections (inbound) for that session. Otherwise, as shown in the abovecalculation, the adapter creates inbound connections for that session.



34/62


Relation between Max Jobs and Adapter Threads

TheMax Jobsat the Siebel server level refers to the Maximum number of tasksavailable in the Siebel Object Manager. It should be configured in such a way that

it is always greater than the threadCount(inbound + outbound) specified for theadapter.

Reconnection Mechanism

The adapter uses a reconnection mechanism to handle the network glitches orSiebel server timeout related issues. You can configure the numbers of times theadapter will attempt to connect to the Siebel server.

The reconnection mechanism starts whenever the adapter faces a Siebelapplication error while processing an event. It performs a dummy operation withthe existing connection to check whether the connection is valid or not. If thisconnection check is successful, the adapter displays an error for that event withthe proper error message. The adapter does not attempt to recreate the connectionpool.

If the operation is unsuccessful, the adapter activates the reconnection

mechanism. The adapter tries to reconnect to the Siebel server as many times asyou have configured it to retry. If it exceeds the parameter No of attemptsbefore suspending services, the adapter suspends the Subscription Services.Thereafter, the adapter will continue with the reconnection attempts till it crossesthe parameter configured for Number of attempts before stopping theadapter. If the adapter is still not able to reconnect, it stops. If the adapter is ableto reconnect, it drops all the existing connections from the pool and recreates thecomplete connection pool.

While recreating the connection pool, the adapter exits if it fails to establish thefirst connection. But, if the adapter is able to create one or more connections, itdoes not exit, but waits for the events.

Adapter Services |19

Ad t S i


35/62


Adapter Services

In TIBCO terminology, an adapter offers servicesto the host application and to theTIBCO environment. A service broadly encapsulates routing rules for messageshandled by the service and also custom configuration information. TIBCOActiveMatrix Adapter for Siebel provides the following adapter services:

Publication Service




Communication parameters, Siebel connectivity parameters, and otherparameters can be configured for these adapter services using TIBCOsconfiguration tool, TIBCO Designer.

The following sections describe how these adapter services interact with a Siebelenvironment to provide message connectivity.

Publication Service

The adapter receives data from a Siebel application, converts the data to a TIBCOmessage, and sends the message to the TIBCO environment.

Figure 6 Typical Publication Service Flow

Message

Publish a SiebelBusiness Event

Siebel

Application

TIBCO

ActiveMatrix

Adapter for

Siebel

Publication Service

TIBCO Environment


Publication Service Features


36/62


Publication Service Features

The basic features of the Publication Service are as follows:

Enables the adapter to directly interact with the Siebel application using the

built in HTTP(S) Listener.

Enables the adapter to read message from JMS queue added by the adaptersSiebel JMS Business Service for publication.

Publishes using TIBCO Rendezvous or JMS as the mode of transport.

Queries Siebel Business Components and publishes them.

Allows user defined message field names representing native Siebel fieldnames.

Publishes Siebel System fields including created, created by, updated andupdated by fields.

Publishes Siebel fields in Siebel formatted output forms.

Publishes non-Siebel business components.

Publishes Integration Objects

Example Scenario

The Publication Service can publish business components received from theSiebel system. For example, the Siebel system can be configured to send outrecords when an account is created in Siebel. For instance, when an account iscreated, Siebel can be configured to send (via HTTP(S)) a notification to theadapter, which will then publish it in the TIBCO environment.


The adapter gets a message from the TIBCO environment and sends the messageto the Siebel application.


Figure 7 Typical Subscription Service Flow


37/62


Figure 7 Typical Subscription Service Flow

Subscription Service Features

The basic features of the Subscription Service are as follows:

Inserts and updates Siebel Business Component objects

Invokes Siebel Workflow using a subscribed event

Subscribes to TIBCO messages using TIBCO Rendezvous or JMS as the modeof transport

Supports interfacing with Siebel Workflow and Integration Objects.

Example Scenario

An external system publishes a message with Order Invoiceinformation. Thismessage is then transformed to a TIBCO message by an intermediate applicationand then published to the adapter. The transformation step involves conversion

of the message so that it adheres to a schema recognized by the adapter. Theadapter subscribes to this message and updates the Order Invoiceinformationinto the Siebel system.


The adapter gets a request from the TIBCO environment and sends the request tothe Siebel application. When a response is returned to the adapter from the Siebelapplication, the adapter sends the response to the TIBCO environment.

Message

Subscribe to aSiebelBusiness Event

Siebel

Application

TIBCO

ActiveMatrix

Adapter for

Siebel


TIBCO Environment


Figure 8 Typical Request-Response Service Flow


38/62


Figure 8 Typical Request Response Service Flow

The adapter supports Request-Response scenarios by acting like an RPC (RemoteProcedural Call) server. When the adapter receives a request, it takes the rawrequested data, converts it into formatted Siebel schema, and sends it to Siebelusing a designated Siebel interface.

Request-Response Service Features

The basic features of the Request-Response Service are as follows:

Queries Siebel Business Components

Inserts or updates Siebel Business Components

Invokes Siebel workflow processes Inserts or updates integration objects

Queries integration objects

Allows scalable, high throughput and load balanced message processing viathe TIBCO Rendezvous Distributed Queues (RVCMQ) Protocol

Example Scenario

An external system querying for customer information invokes an operation inthe Siebel adapter configuration. The adapter passes on the request to the Siebelsystem, fetches customer information from the CustomerBusiness Componentand sends a reply to the external system.

TIBCO Environment

Siebel

Application

Request

Message

Operating as anRPC Server

Reply

Message

PRC Client such as

TIBCO

BusinessWorks

TIBCO

ActiveMatrix

Adapter for

Siebel




39/62


Request Response Invocation Service

The adapter gets a request from the Siebel application and sends the requestthrough the TIBCO environment. When a response is returned from the TIBCO

environment, the adapter sends the response back to the application.

Figure 9 Typical Request-Response Invocation Service Flow

Request-Response Invocation Service Features

The basic features of the Request-Response Invocation Service are as follows:

Queries Siebel Business Component objects by invoking external TIBCORequest-Response Services.

Can be invoked through the SendReceivemethod of the provided customSiebel Business Service, EAI TIBCO HTTP AgentBusiness Service.

Supports sending and receiving complete integration objects.

Supports querying integration objects and returning integration objects from

external systems.

Example Scenario

The Siebel system may be configured to query for the CustomerBusinessComponent from an external system. The Siebel system invokes the adapter,which sends out a request and receives a reply from the external system. Theadapter then sends the reply to the Siebel system.

Third-party application

TIBCO environment

TIBCO ActiveMatrix

Adapter for Siebel

Siebel application

Request

messageResponse

message


Schema Support


40/62


Schema Support

The adapter uses schema to describe data received from or sent to the TIBCOenvironment.

Schemas are useful in various situations, for example:

When several developers collaborate on an adapter application, aspecification document normally defines the data model for several relatedadapter applications. Inside the TIBCO framework, you can instead define aschema to serve as the data model and update it as needed.

When the data model of the Siebel application changes, developers do nothave to redesign the business process.

Using Schemas in conjunction with the various mapping tools available in theTIBCO environment, you can transfer data across applications withincompatible data formats.

Schemas for the Siebel Application are configured based on the Siebel BusinessLayer Definition. TIBCO Designer connects to the Siebel Business Layer using the

design-time connectionand fetches the Siebel Schema definition. The adapterconfiguration is built using this definition.

Adapter Infrastructure Tools |25

Chapter 3 Adapter Infrastructure Tools


41/62


Chapter 3 Adapter Infrastructure Tools

This chapter introduces the required and optional TIBCO infrastructure tools thatwork with an adapter.

Topics

TIBCO Runtime Agent, page 26

TIBCO Designer, page 27

TIBCO Administrator, page 28

TIBCO ActiveMatrix BusinessWorks, page 31

TIBCO Hawk, page 32

TIBCO Business Studio, page 34

TIBCO ActiveMatrix Administrator, page 39

26 | Chapter 3 Adapter Infrastructure Tools

TIBCO Runtime Agent


42/62


g

The TIBCO Run-time Agent (TRA) provides basic connectivity between theadapter and other TIBCO infrastructure tools. The TRA is required on anymachine on which an adapter is installed. The TRA runs on each machine onwhich an adapter runs and executes scripts, sends alerts, and performs recoveryas specified.

The TRA has two main functions:

Supplies an agent that runs in the background on each machine.

The agent is responsible for starting and stopping processes that run on amachine according to the deployment information.

The agent monitors the machine. That information is then visible via theTIBCO Administrator GUI.

Supplies the run-time environment, that is, all shared libraries includingthird-party libraries required by the adapter.

TIBCO Domain Utility

The TRA contains the TIBCO Domain Utility, which is used to manage thecomponents available on a TIBCO administration domain. The utility allows youto:

Add or remove a machine to a TIBCO administration domain.

Add or remove the TIBCO Enterprise Message Service server plug-in to aTIBCO administration domain.

Change TIBCO Rendezvous parameters. Changing TIBCO Rendezvousparameters is an advanced option performed only by users familiar withTIBCO Rendezvous. If you perform this task, you must perform it on eachmachine in the TIBCO administration domain, then restart the TIBCOAdministration Server.

Change TIBCO administration domain credentials. Changing domaincredentials is an advanced option. You must perform it on the machine wherethe TIBCO Administration Server is installed.

Remove a secondary TIBCO Administration Server.

Enable TIBCO administration domain and security management on amachine where TIBCO Administrator has been installed.

Migrate previous TIBCO Administrator installations.

TIBCO Designer |27

TIBCO Designer


43/62


TIBCO Designer provides the design-time environment for configuring astandalone adapter project. Using Designer, you create a project, add adapterservices to it with a simple drag-and-drop interface, and specify the configurationinformation for each adapter service.

Before using TIBCO Designer, make sure you read the TIBCO Designer helpdocumentation.The documentation can be accessed from the menu bar viaTIBCO Designer Help > Designer Help. The next diagram shows the TIBCODesigner interface.

The standalone adapter adds a palette to the TIBCO Designer environment whichprovides the adapter-specific resources

Figure 10 TIBCO Designer Main Window


TIBCO Administrator


44/62


TIBCO Administrator provides user, resource, and application managementmodules for adapters.

User Management.This module allows you to set permissions for adapterusers. You define authentication, users and groups, and assign access controllists to users. This includes security for server-based projects at design-timeand for deployed applications at runtime.

Resource Management.This module allows you to monitor machines and allrunning applications in a TIBCO administration domain. Alerts can becreated, for example, to notify an administrator if the number of processes ordisk usage exceed a certain level.

Application Management.This module allows you to upload EnterpriseArchive (EAR) files, and create, configure, and deploy adapters. This consoleis also used to start and stop adapters.

Load balancing.An adapter can be served by a primary and secondaryTIBCO Administration Server. The primary server allows read and writeoperations, while the secondary server supports read operations. Load

balancing is implemented through the use of the TIBCO Rendezvousdistributed queue protocol (RVDQ) and therefore is not available for HTTP.

To get the load balancing benefit with HTTP, you must either use an IPredirector or explicitly point to a backup server to be used when a server fails.See your IP Redirector or HTTP Server documentation for information onhow to do this.

Failure recovery.You can use a load-balanced TIBCO Administration Serverfor failure recovery. In a completely trusted environment, you can instead usea database back-end for your server and use checkpoints in the database forfailure recovery.

TIBCO Administration Domain

A TIBCO administration domain is installed only if you have also installed theUser Management module.

A TIBCO administration domainis a collection of users, machines, and componentsthat an administration server manages. There is only one Administration Serverfor each administration domain. Components within an administration domaincan communicate with systems outside of the domain, but the domain is theadministrative boundary of your enterprise integration project.

TIBCO Administrator |29

Each TIBCO administration domain contains one or more machines. By default,all machines within an administration domain are expected to be in the same


45/62


all machines within an administration domain are expected to be in the samenetwork subnet. You can, however, set up your system to use TIBCO Rendezvousrvrd and can then use the components across subnets. See the TIBCO

Administrator Server Configuration Guidefor details.

Each machine can belong to only one TIBCO administration domain. This issimilar to a Microsoft Windows network domain where your machine can also

belong to only one network domain.

TIBCO Administration Server

The TIBCO Administrator Server provides a central storage and distributionpoint for configuration and schema data needed by an adapter. The server isincluded in both Administrator editions.

Each administration domain has one and only one TIBCO Administration Server.The TIBCO Administration Serveris the machine process that handles the storedprojects and user requests to manage the TIBCO administration domain.

The TIBCO Administrator Server contains its own web server (Apache Tomcat)that can be accessed via the TIBCO Administrator GUI for configuration andmonitoring information.

The TIBCO Administration Server supports centralized authentication andauthorization. Using the TIBCO Administrator GUI, users with fulladministrative privileges can define who has access to projects that are managed

by the repository server.

TIBCO Administrator GUI

You can access the TIBCO Administration Server using the web-based TIBCOAdministrator GUI. The GUI allows you to create user profiles and assign accessto projects managed by the Administration Server. You can invoke the GUI fromany machine in a TIBCO administration domain. The next diagram shows theGUI.


Figure 11 TIBCO Administrator GUI


46/62


TIBCO ActiveMatrix BusinessWorks |31

TIBCO ActiveMatrix BusinessWorks


47/62


TIBCO ActiveMatrix BusinessWorks is a scalable, extensible, and easy to use

integration platform that allows you to develop integration projects. TIBCOActiveMatrix BusinessWorks includes a graphical user interface for defining

business processes and an engine that executes the processes.

In TIBCO ActiveMatrix BusinessWorks, adapter services are responsible forpublishing or subscribing to business data in a decoupled yet reliable manner.The business process receives data from an adapter service and routes data to anadapter service.

TIBCO ActiveMatrix BusinessWorks provides the following activities for use withadapters:

Publish to AdapterPublishes data from the process to an adapter, whichsubscribes to data coming from the process and passes the data to the targetapplication.

Adapter SubscriberSubscribes to incoming data published by the adapter.

Invoke an Adapter Request-Response ServiceCommunicates (as a client)with an adapter request-response service.

Adapter Request-Response ServerStarts a process based on the receipt of arequest from an adapter.

Respond to Adapter RequestSends a response to an adapter for a previouslyreceived request.

Wait for Adapter MessageWaits for the receipt of a message from thepublication service of the specified adapter.

Wait for Adapter RequestWaits for the receipt of a request from arequest-response invocation service.

See the TIBCO ActiveMatrix BusinessWorks documentation for moreinformation.

TIBCO ActiveMatrix BusinessWorks Service Engine

The product provides an ActiveMatrix container to deploy ActiveMatrixBusinessWorks projects using TIBCO ActiveMatrix Administrator. TIBCOActiveMatrix BusinessWorks supports service oriented processing with the use ofservice resources, partners, and partner bindings.

See the TIBCO ActiveMatrix BusinessWorks Service Engine documentation formore information.


TIBCO Hawk


48/62


TIBCO Hawk monitors and manages distributed applications and systems

throughout the enterprise. System administrators can monitor applicationparameters, behavior, and loading activities for all nodes in a local or wide-areanetwork and take action when pre-defined conditions occur. In many cases,run-time failures or slowdowns can be repaired automatically within seconds oftheir discovery, reducing unscheduled outages, and slowdowns of critical

business systems.

TIBCO Hawk features include:

Extensive monitoring capabilities at the operating system and applicationlevels including process data, disk, and CPU utilization, network statistics,log, and system files.

Built-in routines within other TIBCO ActiveEnterprise components allow forproactive management. Problems can be found and fixed before failures canoccur.

Hawk Application Management Interface (AMI) routines can be embeddedwithin custom adapters, allowing active management of those adapters by theHawk micro-agent

Distributed micro-agents support autonomous network behavior so localmanagement and problem resolution can continue during an outage

Fault-tolerance is achieved through the independent operation of Hawkagents, which continue to perform local tasks even in the event of network

failureTIBCO Hawk consists of several components: a console display, a centralrepository for storage of configuration objects, agents, and microagents whosemonitoring duties are defined by the rule bases.

Agents monitor local conditions and take action or publish alert informationthat appears in the TIBCO Hawk display.

Microagents act as an interface to the managed objects and are invoked

through their supported methods.

Adapter Microagents

Each adapter includes a standard and custom microagent. The microagentsprovide:

Business level statisticsstatistics that report the progress of the adapter as itinteracts with the vendor application. For example, in a database adapter such

TIBCO Hawk |33

statistics might indicate whether objects were successfully or unsuccessfullyinserted, updated, or deleted in the database.


49/62


Queries that return information about the state of the adapter. This can be animportant tool for seeing the internal of an adapter and debugging it ifsomething appears wrong. For example, specific queries can returninformation about threads, internal queues, or connections to the targetsystem. Using these methods, one might be able to identify certain bottlenecksor gauge how successfully an adapter is scaling with respect to the currentenvironment.

Updates to the adapter runtime parameters. This includes retrieving thecurrent runtime parameters and setting new runtime parameters without

restarting the adapter. An example of this is getting and setting the pollinginterval. Updating a runtime parameter through the Hawk microagent onlyaffects the setting of the instance that is running.


TIBCO Business Studio


50/62


The TIBCO ActiveMatrix development tools consist of TIBCO Business Studio

and a set of ActiveMatrix plug-ins. For introductory information on TIBCOBusiness Studio, refer to the Workbench User Guidein the TIBCO Business Studioonline help. To view the online help, select Help > Help Contents.

Figure 12 TIBCO Business Studio

The screen contains the following area and views:

Menu See Help > Help Contents > Workbench User Guide.

Tool bar See Help > Help Contents >Workbench User Guide.

Project Explorer Displays a tree containing all the project resources such asproject folders, shared resource definition files, WSDL files, composite files,service assembly files, and so on.

Editor Displays editors for the objects currently being edited. You can switchbetween editors by clicking the tabs at the top of the Editor area. The

Composite Editor contains a canvas on which you can drop elements and apalette that organizes the elements that you can add to the composite. Othereditors allow you to configure shared resources and service assemblies.

Outline Provides a overview of the Composite Editor canvas. You can easilynavigate from one part of a composite to another.

The Outline view also displays a content tree structure that contains thecomposite element inside the composite. In this view you can delete the

TIBCO Business Studio |35

contents of the composite. When you select a composite element in theOutline tree, the corresponding artifact in the composite becomes selected.


51/62


Views Appears under the Editor Area and contains the following views:

Properties Displays property sheets for editing composites and compositeelements. When you select a composite or composite element in theComposite Editor canvas, this view shows the properties of the selectedobject in a vertical tabbed notebook.

Problems Displays validation and other errors.

Registries Lists UDDI registries and the WSDL files returned fromsearching for a registry.

You can open a view by selecting Window > Show View > View.

ActiveMatrix Resource Wizard

The starting point for creating all types of ActiveMatrix projects and assets is theActiveMatrix Resource Wizard. The resource wizard allows you to select wizardsto create:

Adapter service engine projects

ActiveMatrix sample projects

ActiveMatrix SOA projects

Composites

Mediation flows

Service assemblies


Composite Element Editors

Composite elements are configured in property sheets accessed through the


52/62


p g p p y gProperties view.

Figure 13shows the an example of the Properties view.

Figure 13 Component Property Sheet

TIBCO Business Studio |37

Debugger

The TIBCO Business Studio debugger provides a testing environment for


53/62


stepping through composite elements and determining the sources of errors.Figure 14shows the debugger in the process of debugging a sample HelloWorldcomposite. Breakpoints have been set before and after the Java componentexecutes, and the debugger is stopped at the first breakpoint. In the Variablesview on the top-right, the value of the request is being examined.

Figure 14 Debugger


Service Assembly Editor

In order to be deployed, composites must be transformed into service units andi bli Fi 15 h l i bl di i


54/62


service assemblies. Figure 15shows a sample service assembly editor view.

Figure 15 Service Assembly Editor

TIBCO ActiveMatrix Administrator |39

TIBCO ActiveMatrix Administrator


55/62


ActiveMatrix provides TIBCO ActiveMatrix Administrator for enterprise,

environment, and service management. ActiveMatrix Administrator supportsboth graphical and command-line interfaces.

The following sections provide an overview of TIBCO ActiveMatrixAdministrator. To get a quick introduction to the use of the administration tools,see TIBCO ActiveMatrix Service Grid Getting Started. For detailed informationabout the administration tools, see TIBCO Hawk Administrators Guide.

TIBCO ActiveMatrix Administrator Architecture

Figure 16shows ActiveMatrix Administrator components, and the relationshipbetween ActiveMatrix Administrator, other servers, and ActiveMatrix machinesand nodes.


Figure 16 TIBCO ActiveMatrix Administration Architecture

AMA Client Machine


56/62


The TIBCO ActiveMatrix Administrator administration architecture consists ofthe following components:

TIBCO ActiveMatrix Administrator Server Gathers management data fromnodes, responds to requests from the ActiveMatrix Administrator graphicaland command-line UIs, interacts with the authentication realm server toauthenticate users, and interacts withTIBCO Management Daemon to manage

nodes.

TIBCO ActiveMatrix Administrator Cluster Groups one or more ActiveMatrixAdministrator servers. ActiveMatrix Administrator servers within a clustershare a database and authentication realm and are kept synchronized.

ActiveMatrixDatabase Stores ActiveMatrix administration data.

AMA Graphical

User Interface

AMA Command-

Line Interface

AMA

Server 2

AMA Machine 2AMA

Machine 1

Authentication Realm

Database

AMA

Server 1

AMA Cluster

Management

Daemon

AM Machine 1

AM Node

Management

Daemon

AM Machine 2

AM Node

Legend

AM TIBCO ActiveMatrix

AMA TIBCO ActiveMatrix Administrator


Authentication Realm Manages user authentication data. The authenticationrealm can be provided either by TIBCO Administrator or by another server ora file.


57/62


ActiveMatrix Administrator Graphical UI Displays the ActiveMatrixAdministrator user interface. Figure 17shows the ActiveMatrixAdministrator graphical UI welcome page. In ActiveMatrix Administrator,functionality is divided into perspectives. Aperspectiveis a set of controls usedto carry out a category of administration tasks.

ActiveMatrix Administrator Command-Line Interface Provides a script-basedinterface for ActiveMatrix Administrator functions.

Management Daemon Gathers installation information and exposesActiveMatrix node life cycle operations.

Figure 17 TIBCO ActiveMatrix Administrator

Enterprise and Environment Administration

ActiveMatrix Administrator graphical and command-line interfaces permit youto administer ActiveMatrix enterprises and environments, shared resourceconfigurations, nodes, containers, and managed resources.

In the graphical interface, enterprise configuration and environmentadministration are carried out in the Configure Enterprise Assets and Configurean Environment perspectives respectively.


Service Administration

ActiveMatrix Administrator graphical and command-line interfaces permit youto administer ActiveMatrix services. Service administration consists of


58/62


deployment tasks and monitoring and management tasks. In the graphicalinterface, these tasks are carried out in the Deploy to an Environment andMonitor & Manage perspectives.

Service Deployment

The first phase of service administration is deployment. During deployment, theservice units within a service assembly are mapped and then deployed into theirrespective containers. The services provided by the service units are registeredwith the ActiveMatrix container and the service endpoints are activated.

The choice of how to distribute services across nodes is determined by the desiredlevel of service performance and availability. Service performance and availabilitycan be enhanced if you deploy a service unit across multiple nodes, which allowsMessaging Bus to distribute requests between the service instances.

Load Balanced Services

The Mediation Bus enables load balancing at the container level by defining acontainer group. A container groupis defined as a group containing one or morecontainer instances of the same container type. When a service unit is deployed toa container group, a copy of the service unit is deployed into each container in thegroup.

Highly Available ServicesServices deployed on multiple containers are highly available; if one container fails,service requests will be handled by one of the remaining containers. Noconfiguration is required to make services highly available. Messaging Busautomatically routes to any available service instance identified in the messageexchange.

Load Balanced ServicesRequests to services deployed on multiple containers are load balancedbetweenthe available providers. No configuration is required to load balance betweenservices. Messaging Bus uses a round robin algorithm for routing requests toservice instances.


Service Monitoring and Management

TIBCO ActiveMatrix Administrator not only allows you to configure and deployservices, but also lets you monitor and manage the deployed services. Monitoring


59/62


the system performance is not a one time activity but needs to be performed on a

day-to-day basis. The Monitor & Manage perspective of TIBCO ActiveMatrixAdministrator keeps track of system health without much overhead.

In the Monitor & Manage perspective, you can monitor the overall health andperformance of the grid infrastructure, applications, and services. You canmonitor performance at various levels such as environment, machine, node,container, service assembly, and service unit.

The monitoring subsystem uses content-based metrics to measure the serviceperformance, availability of services, service usage, and the ratio of successful tofaulty service responses. These metrics provide real-time values by fetching dataevery minute and updating the values of the metrics. The real-time data is thendisplayed in a web-based dashboard provided with pre-defined views and visualalerts.



60/62


| 45

Index


61/62


A

ActiveMatrix Administrator cluster 40

ActiveMatrix Administrator server 40

ActiveMatrix Database 40

ActiveMatrix resource wizard 35

Adapterservice engine 3

standalone 3

Adapter Components 3, 3

Adapter Infrastructure Tools

TIBCO ActiveMatrix Administrator 39

TIBCO ActiveMatrix BusinessWorks Service

Engine 31

TIBCO Administrator 28TIBCO Business Studio 34

TIBCO Designer 27

TIBCO Hawk 32

TIBCO Runtime Agent 26

Adapter Microagents 32

Adapter Services 5, 19

Publication Service 5

Request-Response Invocation Service 6Request-Response Service 5

Subscription Service 5

Adapter Terms

.ear file 4

adapter

Tib Adsbl Concepts

Documents

Transcript of Tib Adsbl Concepts