TIBCO ActiveMatrix® Adapter for Siebel Concepts

Software Release 6.0 April 2010

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

Contents iii

|

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Related 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Request-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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Siebel 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Subscription Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

TIBCO ActiveMatrix Adapter for Siebel Concepts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Adapter Microagents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Administration Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Administration Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Chapter 3 Adapter Infrastructure Tools . . . . . . . . . . . . . . . . . . . . . . 21 Request-Response Invocation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 TIBCO Designer . . . . . . . . . . . . TIBCO ActiveMatrix Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enterprise and Environment Administration . . . . . . . . Service Assembly Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 35 36 37 38 39 39 41 42 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 TIBCO ActiveMatrix Adapter for Siebel Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 28 29 29 TIBCO ActiveMatrix BusinessWorks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 TIBCO Domain Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Administrator GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ActiveMatrix Resource Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv | Contents Request-Response Service . . . . . . . . . . . . . . . . . . Composite Element Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Debugger . . . . . . . . . 25 TIBCO Runtime Agent . . 27 TIBCO Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Schema Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 TIBCO Hawk . . . . . . . . . . . . . . . Service Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO ActiveMatrix Administrator Architecture . . . . . . . . . . .

. . . . 10 Logical Architecture for Integration With Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 TIBCO Designer Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Component Property Sheet . . . . . . . . . . . 7 Choosing an Adapter Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Choosing an Adapter Service: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Typical Publication Service Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Typical Request-Response Service Flow. . . . . 40 TIBCO ActiveMatrix Administrator . . . . . . . . . . . . . . . . . . 41 TIBCO ActiveMatrix Adapter for Siebel Concepts . . . . . . . . . . . . . . . . . . . . 27 TIBCO Administrator GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Multi-layered Architecture . . . . . . . . . . . . . .Figures v | Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Adapters Provide a Bridge for Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Typical Request-Response Invocation Service Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 TIBCO ActiveMatrix Administration Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Service Assembly Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Typical Subscription Service Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi | Figures TIBCO ActiveMatrix Adapter for Siebel Concepts .

. . . . . . . . . . . . . . . . xii Syntax Typographical Conventions . . . . . . . . . . . . . . . . . . .Tables vii | Tables Table 1 Table 2 Table 3 General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Adapter Services Summary . . . . . . . . . . . . . . . . . . . . . . . 6 TIBCO ActiveMatrix Adapter for Siebel Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii | Tables TIBCO ActiveMatrix Adapter for Siebel Concepts .

page x Typographical Conventions. page xii How to Contact TIBCO Customer Support. including what the adapter is and how it works.| ix Preface This document introduces the fundamentals of TIBCO ActiveMatrix Adapter for Siebel. Topics • • • Related Documentation. page xv TIBCO ActiveMatrix Adapter for Siebel Concepts .

TIBCO ActiveMatrix Adapter for Siebel Configuration and Deployment — Read this manual for instructions on how to create. TIBCO ActiveMatrix Adapter Service Engine for Siebel Configuration and Deployment — Read this manual for instructions on how to create. TIBCO ActiveMatrix Adapter for Siebel Installation — Read this manual to learn how to install the adapter on your operating system. and known and closed issues. deprecated features. TIBCO ActiveMatrix Adapter Service Engine for Siebel Examples — Read this manual to work through the examples provided with the adapter. TIBCO ActiveMatrix Adapter for Siebel Examples — Read this manual to work through the examples provided with the adapter. • • • Other TIBCO Product Documentation You may find it useful to read the documentation for the following TIBCO products. TIBCO ActiveMatrix Adapter for Siebel Documentation The following documents form the TIBCO ActiveMatrix Adapter for Siebel documentation set: • • • TIBCO ActiveMatrix Adapter for Siebel Concepts — Read this manual to familiarize yourself with the product and its uses. configure. • • The following documents form the TIBCO ActiveMatrix Adapter Service Engine for Siebel documentation set: • TIBCO ActiveMatrix Adapter Service Engine for Siebel Installation — Read this manual to learn how to install TIBCO ActiveMatrix Adapter Service Engine for Siebel. and known and closed issues. deprecated features. TIBCO ActiveMatrix Adapter for Siebel Release Notes — Read this document for information about new features. TIBCO ActiveMatrix Adapter Service Engine for Siebel Release Notes — Read this document for information about new features. TIBCO ActiveMatrix Adapter for Siebel Concepts . and deploy adapter projects.x | Related Documentation Related Documentation This section lists documentation resources you may find useful. configure and deploy adapter projects.

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. TIBCO ActiveMatrix Adapter for Siebel Concepts . available from Siebel Systems Inc.

For example: Use MyCommand to start the foo process. on Windows systems. Portlets are mini-applications that run in a portal.xii | Typographical Conventions Typographical Conventions The following typographical conventions are used in this manual Table 1 General Typographical Conventions Convention TIBCO_HOME ENV_HOME Use Many TIBCO products must be installed within the same home directory. Other TIBCO products are installed into an installation environment. code font Code font identifies commands. To indicate a variable in a command or code syntax that you must replace. For example: See TIBCO BusinessWorks Concepts. The value of ENV_HOME depends on the operating system. MyCommand is enabled: MyCommand [enable | disable] italic font Italic font is used in the following ways: • • • To indicate a document title. pathnames. to indicate what a user types. Incompatible products and multiple instances of the same product are installed into different installation environments. For example. code examples. The directory into which such products are installed is referenced in documentation as ENV_HOME. For example: A portal page may contain several portlets. This directory is referenced in documentation as TIBCO_HOME. filenames. to indicate the parts of the sample that are of particular interest. For example: Type admin. The value of TIBCO_HOME depends on the operating system. to indicate the default parameter for a command. the default value is C:\tibco. For example. For example: MyCommand pathname TIBCO ActiveMatrix Adapter for Siebel Concepts . In large code samples. For example. bold code font Bold code font is used in the following ways: • • • In procedures. In command syntax. on Windows systems the default value is C:\tibco. To introduce new terms. and output displayed in a command window. if no parameter is specified.

for example. an additional action required only in certain circumstances. for example. For example. For example: Esc. a way to apply the information provided in the current section to achieve a specific result. For example: MyCommand [optional_parameter] required_parameter | A logical OR that separates multiple items of which only one may be chosen. for example.Preface xiii | Table 1 General Typographical Conventions (Cont’d) Convention Key combinations Use Key names separated by a plus sign indicate keys pressed simultaneously. you can select only one of the following parameters: MyCommand para1 | param2 | param3 TIBCO ActiveMatrix Adapter for Siebel Concepts . For example: Ctrl+C. The tip icon indicates an idea that could be useful. Key names separated by a comma and space indicate keys pressed one after the other. Ctrl+Q. The warning icon indicates the potential for a damaging situation. data loss or corruption if certain steps are taken or not taken. The note icon indicates information that is of special interest or importance. Table 2 Syntax Typographical Conventions Convention [ ] Use An optional item in a command or code syntax.

the command can accept either two or three parameters. which can be either the pair param1 and param2. And the last parameter is either param3 or param4. the following command requires two parameters. MyCommand param1 [param2] {param3 | param4} TIBCO ActiveMatrix Adapter for Siebel Concepts . the command requires two parameters. You can optionally include param2 as the second parameter. For example. The first parameter must be param1. or the pair param3 and param4. Other syntax notations may appear within each logical group.xiv | Typographical Conventions Table 2 Syntax Typographical Conventions (Cont’d) Convention { } Use A logical group of items in a command. MyCommand {param1 param2} | {param3 param4} In the next example. The first parameter can be either param1 or param2 and the second can be either param3 or param4: MyCommand {param1 | param2} {param3 | param4} In the next example.

tibco. visit this site: http://www.tibco. please contact TIBCO Support as follows. TIBCO ActiveMatrix Adapter for Siebel Concepts .com/services/support • If you already have a valid maintenance or support contract.com • Entry to this site requires a user name and password.Preface xv | How to Contact TIBCO Customer Support For comments or problems with this manual or the software it addresses. and information about getting started with TIBCO Support. you can request one. visit this site: https://support. • For an overview of TIBCO Support. If you do not have a user name.

xvi | How to Contact TIBCO Customer Support TIBCO ActiveMatrix Adapter for Siebel Concepts .

page 3 Adapter Key terms. page 5 Choosing an Adapter Service. page 2 Adapter Components. Topics • • • • • What is an Adapter?. page 7 TIBCO ActiveMatrix Adapter for Siebel Concepts .|1 Chapter 1 Introduction This chapter introduces adapters by explaining their functions and services. page 4 Adapter Services.

Database adapters enable an enterprise’s database to initiate important business processes based on exception data they identify. Using a no-coding approach to integration. Mainframe adapters enable real-time two way communication between themselves and the rest of a companies’ business applications and databases. Database adapters also make data available to the enterprise. of the interfaces exposed by the vendor application. regardless of their data formats or communication protocols. and other technologies to become active participants in the enterprise information flow. databases. Adapters can also enable integration with component or object development models and other messaging technologies. Each adapter integrates with at least one. Adapters isolate the application from more complex actions. Unfortunately. Message transformation and business process automation can be handled once the data is published to the TIBCO infrastructure. • Adapters are available for off-the-shelf applications from leading vendors. TIBCO Adapters enable packaged applications. you usually have to purchase applications from several different application vendors. adapters allow data to be exchanged among different technologies. An adapter provides a bridge between an application and your TIBCO integration environment. and usually several.2 | Chapter 1 Introduction What is an Adapter? To deploy the best solution for each aspect of your business. vendors typically have their own way to format and expose data. Integration of new applications does not require programming skills and does not interfere with existing infrastructure. As is shown in the figure below. Therefore integrating the various applications across your enterprise poses significant challenges. • • • Figure 1 Adapters Provide a Bridge for Data TIBCO ActiveMatrix Adapter for Siebel Concepts .

Throughout this book. • Adapter Service Engine Using this component you can create and configure adapter projects that can be deployed as a service in the TIBCO ActiveMatrix environment. This adapter component is referred to as the adapter service engine. The adapter components are: • Standalone Using this component you can create adapter projects which run as a standalone process. Adapter service engine projects are created using TIBCO Business Studio and deployed using TIBCO ActiveMatrix Administrator. TIBCO ActiveMatrix Adapter for Siebel Concepts .Adapter Components 3 | Adapter Components The adapter can run either as a standalone process or as a service. This adapter component is referred to as the standalone adapter. Standalone adapter projects are created and configured using TIBCO Designer and deployed using TIBCO Administrator. The adapter component is wired with other composite elements in the ActiveMatrix SOA Project. the adapter participates in the Service Oriented Architecture (SOA) environment. When run as a service. Existing standalone adapter configurations can also be deployed as services. references to an adapter include both the standalone and adapter service engine components.

It contains service units and a descriptor that indicates the container into which each service unit is to be deployed. service level. A service assembly is an ActiveMatrix deployment package. • A palette is a standalone adapter component that contains the screens used to gather input at design-time when configuring an adapter with a service. or service instance level. The WSDL documents specify the messages that are required to access a service. A project is a collection of all configured adapter resources. A business object is the representation of the data model of the entities that the adapter service engine connects to.ear of an application contains global variables with values set at design-time by the standalone adapter. Service Oriented Architecture (SOA) is a software architecture in which applications and data are decomposed into discrete. The palette is accessed via TIBCO Designer. A message exchange pattern (MEP) defines the sequence and cardinality of messages sent between the provider and the consumer. A project contains configuration information for one or more adapter instances. each service will adopt one of two roles: provider or consumer. The suffix of a service assembly file is . operationally independent services.saf. For production.4 | Chapter 1 Introduction Adapter Key terms The following key terms are used when describing adapter interactions in this manual. The ActiveMatrix services are described in documents expressed in Web Services Description Language (WSDL). The global variables can be changed during deployment at the application level. a project is typically managed by an administration server provided by the TIBCO Administrator for the standalone adapter and TIBCO ActiveMatrix Administrator for the adapter service engine. The business objects are downloaded during the design phase and are used by the adapter services. A local project is typically used at design-time for testing adapter instances. which can be executed in a highly distributed manner. An . A service provider publishes a WSDL document that describes the services it offers. A container is an ActiveMatrix runtime entity that hosts component implementations and service bindings. During any service interaction. • • • • • • • • TIBCO ActiveMatrix Adapter for Siebel Concepts . A service consumer uses the WSDL document to determine the available services and the messages required to access the services.

Subscription Service An adapter subscription service asynchronously performs an action—such as updating business objects or invoking native Application Programming Interfaces (APIs)—on a vendor application. TIBCO ActiveMatrix Adapter for Siebel Concepts . Other applications that receive the event can then update their records just as the original application did. and it is useful for actions such as adding or deleting business objects. an adapter can be used for synchronously retrieving data from. Request-Response Service In addition to asynchronously publishing and subscribing to events. which trigger the appropriate action. and asynchronously sends out the event data in realtime to interested systems in the TIBCO environment. or executing transactions within. In the next example. After the action is performed in the vendor application. The adapter gets a response from the application and returns it. an adapter receives a request message from the TIBCO infrastructure and sends it to an application.Adapter Services 5 | Adapter Services Adapters are responsible for making information from different applications available to other applications across an enterprise. To do so. The adapter service listens to external business events. an adapter can publish an event each time a new customer account is added to an application. Referring to the previous example. For example. This entire process is called request-response. a vendor application. an adapter is configured to provide one or more of the following services: Publication Service An adapter publication service recognizes when business events happen in a vendor application. an adapter subscription service can listen for customer record creation events (happening in an application and published to the TIBCO infrastructure) and update another application. the adapter service sends a response back to the requester with either the results of the action or a confirmation that the action occurred.

6

| Chapter 1

Introduction

Request-Response Invocation Service
An adapter request-response invocation service is similar to the request-response service, 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. The adapter service acts as a proxy, giving the vendor application the ability to invoke synchronously functionality on an external system. For example, if the adapter sends a request message from application Y to application X, after it processes the message, application X returns the message to the 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 Publishing service (sends to target) Subscribing service (gets from initiator) Request-response service (gets from initiator, waits for response then sends response to target) Request-response invocation service (sends to target, waits for response, then sends response to initiator) Initiator Vendor application TIBCO infrastructure TIBCO infrastructure Target TIBCO infrastructure Vendor application Vendor application Event Mode Asynchronous

Asynchronous

Synchronous

Vendor application

TIBCO infrastructure

Synchronous

TIBCO ActiveMatrix Adapter for Siebel Concepts

Choosing an Adapter Service 7

|

Choosing an Adapter Service
A business integration scenario drives the choice of one adapter service or another. This section provides a simple flow chart that helps you to choose the service to use. Not all adapters provide all services and some adapters may provide additional services not listed here. Consider the following environment that involves application X, an adapter, and another application: Figure 2 Choosing an Adapter Service: Example
Subnet Machine A Application X TIBCO Adapter for Application X Machine B Other Application

In this scenario, data must be exchanged between the application X and another application. The other application could be a customer management system, such as PeopleSoft, or another TIBCO application, such as TIBCO ActiveMatrix BusinessWorks. To decide which adapter service to configure in the adapter, start by finding out where the scenario begins—what triggers it. Is the scenario triggered by an event inside application X, or inside the other application? For example, when a new customer account is created in application X, must the account information also be propagated via the adapter to the other application? Or does a batch business process in TIBCO ActiveMatrix BusinessWorks need information from application X to generate some report? This question is the starting point of the decision chart provided below:

TIBCO ActiveMatrix Adapter for Siebel Concepts

8

| Chapter 1

Introduction

Figure 3 Choosing an Adapter Service
business process starts

application X

where is process initiated?

another application

update another application

application X must

response required?

update one or many

only one

obtain information from another application

No

Yes

many

acknowledgem ent required?

no

Yes request-response invocation service subscription service request-response service

publication service

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

TIBCO ActiveMatrix Adapter for Siebel Concepts

page 10 Adapter Overview. page 13 Adapter Services. page 19 Schema Support. Topics • • • • Siebel eBusiness Applications Overview. page 24 TIBCO ActiveMatrix Adapter for Siebel Concepts .TIBCO ActiveMatrix Adapter for Siebel 9 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel This chapter provides an overview of Siebel eBusiness Applications and explains TIBCO ActiveMatrix Adapter for Siebel in more detail.

Siebel Multi-layered Architecture Siebel eBusiness Application uses a multi-layered architecture as the foundation for building Siebel applications. The Siebel application architecture consists of the following 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 the software. call centers. retail. TIBCO ActiveMatrix Adapter for Siebel Concepts . independent of the underlying database platform.10 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel Siebel eBusiness Applications Overview Siebel Systems provide the most comprehensive family of multi-channel eBusiness applications and services. Siebel eBusiness Applications enable organizations to create a single source of customer information. marketing. resellers. or a direct database representation construct. An object definition consists of properties which characterize the software construct that the object definition implements. and servicing customers across multiple channels. field. This section describes the Siebel core architecture. The Siebel architecture allows TIBCO ActiveMatrix Adapter for Siebel to operate on all Siebel core and industry applications. either a user interface. an abstract representation. This facilitates selling. and dealer networks. including the web.

Contact. For example. the Opportunity Business Object consists of Opportunities and related Contacts. you can extend the Siebel database schema without impacting the Siebel application. and are insulated from other layers in the architecture. Integration Objects TIBCO ActiveMatrix Adapter for Siebel Concepts . 3. and Issues. Similarly. Business Object — Represents a major functional area in the enterprise. For example. For example. which enables you to customize Siebel applications by modifying and creating object definitions. A standard Siebel application provides a core set of object definitions. Business Address. or Activity. User Interface Objects Layer The User Interface Objects Layer defines the visual elements with which users interact. Business Component — Represents a fundamental business entity in the enterprise.Siebel eBusiness Applications Overview 11 | Object definitions in a given layer depend on definitions in the next lower layer. which consists of multiple fields that characterize it. 2. which you can use as the basis for your own tailored application. Products. Business Objects Layer The following are the major object types in the Business Objects Layer: 1. which consists of a collection of one or more related business components. Activities. The Business Objects Layer insulates it from the Data Objects layer and the underlying database. you can make changes to a Siebel application without changing the underlying database structure. Siebel Enterprise provides an application configuration tool called Siebel Tools.

12 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel Siebel integration objects allow integration metadata to be represented in Siebel Business Objects as common structures that the EAI infrastructure can understand. Relational Database Management System This is a third party system. and are independent of the installed RDBMS. and pass data to and from external applications using Siebel eBusiness Application Integration (EAI). and Oracle databases. 'column'. Data Objects Layer Object definitions in the Data Objects Layer provide a logical representation of the underlying physical database (constructs like 'table'. Siebel supports IBM DB2. refer to the Supported Platforms section of the Siebel Bookshelf accompanying your Siebel Application. Siebel Workflow This is a process that allows an organization to identify the flow of data throughout the enterprise. and 'index'). MS SQL Server. For details on versions and platforms. TIBCO ActiveMatrix Adapter for Siebel Concepts . These are logical objects representing multiple Business Objects in a single entity.

The Business Service waits for the HTTP reply from the adapter for a specified duration before timing out. The adapter returns the Request Id of the asynchronous workflow request. UPDATE. Support for Return of Status Keys for Integration Objects The adapter now supports the return of Status Keys for an INSERT. During Request-Response invocation. • Support for Asynchronous Workflow Invocation The adapter now supports invocation of workflow asynchronously. Support for Dynamic Substitution of Parameters in HTTP Business Service The adapter now supports the dynamic substitution of EAI TIBCO HTTP Agent Business Service parameters during invocation. The Status Keys need to be configured for every Integration Object in Siebel (Refer Siebel Bookshelf for more information on Status Keys). overrides the parameter specified in the Business Service user properties. UPSERT or DELETE operation on Integration Objects. This parameter. • • TIBCO ActiveMatrix Adapter for Siebel Concepts . The parameters. the HTTP Timeout parameter can be set within the request. The HTTP Agent Server parameter can be set within the user properties.Adapter Overview 13 | Adapter Overview TIBCO ActiveMatrix Adapter for Siebel enables exchange of data between a Siebel system and other external systems through the TIBCO environment in real-time. The Business Event Specification is configured according to the Siebel Business Object model. The adapter defines a Business Event Specification to describe how data is sent into and sent out of the Siebel system. if specified in the request. The Business Service invokes the adapter server using this parameter. The salient features are listed below: • Support for Integration Object Schema Using XML Tags The adapter supports the downloading of Integration Object Schema either with XML tags or with field names for Publication and Subscription Services. overrides the parameter specified in the Business Service user properties. which offer maximum flexibility for configuration and deployment in real-life usage scenarios. This parameter. if specified in the request. are HTTP Timeout and HTTP Agent Server. which are supported for dynamic substitution. This is applicable for Subscription and Request-Response Services. Adapter Features The adapter provides a rich set of features.

which you can use to configure adapters and services to control your enterprise’s data. Ability to Publish using Non-Siebel Business Component Functionality You can use the Non-Siebel Business Component function. The multiple levels of Siebel business components can only be used in a hierarchical structure. The adapter can invoke a process through the Siebel Workflow Process Manager after receiving a message from the TIBCO environment. provided by Siebel. the Siebel Business Rules are preserved regardless of the underlying database platform. Ability to use Multiple Levels of Siebel Business Components The adapter can be configured to use multiple levels of Siebel business components from Siebel Business Objects. The services are described in detail in section Adapter Services on page 5. Support for Universal Application Network The adapter meets Universal Application Network (UAN) standards for the following adapter services: — Subscription Service — Request-Response Service — Request-Response Invocation Service • • • • TIBCO ActiveMatrix Adapter for Siebel Concepts . Request-Response. Ability to Invoke Siebel Workflow Processes The adapter can invoke Siebel Workflow processes in real time. The adapter can invoke any method in a Siebel Business Service after receiving a message from the TIBCO environment.14 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel • Supports for return of Output Parameters for Workflow Invocation The adapter now returns all the parameters of the workflow output after the workflow invocation. and Request-Response Invocation services. to send data before committing it to the Siebel Database. Support for Siebel Integration Objects Siebel Integration Objects are supported on both the inbound and the outbound side. Adapter Services The adapter provides Publication. Support for Siebel Database on Microsoft Windows and UNIX As Siebel data is accessed via the Siebel Object Interface. • • • • Ability to Invoke Siebel Business Service The adapter can invoke Siebel Business Service. Subscription. This is applicable for Subscription and Request-Response Services. You can create schema for integration objects using TIBCO Designer. Basic configuration templates are provided in TIBCO Designer.

TIBCO Enterprise Message Service supports the following connection types: — Queue . The receiver receives the message whether or not the receiver is active at the time the message is sent. Support for TIBCO Rendezvous and JMS (Java Message Service) Support for multiple message transports. It has incorporated the features of both Certified Messaging and Fault Tolerance. — Topic . — Certified-delivery (RVCM) .Queue messaging has one sender and one receiver per message. and receive messages on those topics. the adapter processes multiple messages concurrently. — Distributed Queue (RVCMQ) . • • • TIBCO ActiveMatrix Adapter for Siebel Concepts .Adapter Overview 15 | • Detection of Lost Siebel Data Connection Detection of Siebel Data Connectivity failure is provided along with the ability to re-establish the connection and prevention of message loss. TIBCO Rendezvous supports the following quality of services: — Reliable (RV) . senders address messages to a topic. Many senders can publish on a single topic.This is designed to deliver a message to one-of-many Subscription services. Multithreading The adapter supports a static number of threads. Easy-to-use GUI TIBCO Designer GUI is available for configuring and maintaining the adapter. The number of connections to the application server equals the number of threads. and a single sender can publish to many receivers.In a Topic message system. Receivers subscribe to topics.Ensures that a message will be delivered at least once. This guarantees that every certified message reaches its intended recipient in the order sent.This ensures that each multicast or broadcast message is received as long as the physical network and packet recipients are working. The number of threads is specified at the time of configuration. and the loss of a message is detected. With multiple threads. TIBCO Rendezvous or TIBCO Enterprise Message Service can be used to transport messages to and from the adapter.

Siebel Business Service — Siebel provides Business Services for moving and converting the data formats between Siebel and other external applications. The threads created for outbound services are responsible for receiving the TIBCO ActiveMatrix Adapter for Siebel Concepts . The adapter uses Java Data Bean as one of the modes of communicating with the Siebel application. Java Data Bean Interface — Java Data Bean Interface provided by Siebel is used to get and set data into the Siebel application. The adapter uses custom made Business Services to invoke the outbound requests from Siebel. It also uses a Siebel provided Business Service. EAI Siebel Adapter to get and set integration objects into the Siebel application. • Multithreading The adapter provides the flexibility to run concurrent events by running multiple threads for both inbound (Request-Response Service and Subscription Service) and outbound services (Publication and Request-Response Invocation Service).16 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel How the Adapter Interfaces with the Siebel Application The adapter is a bidirectional gateway between a Siebel application and the TIBCO environment. The distributed architecture of the adapter facilitates seamless integration into Siebel enterprise. • • Siebel VB and Siebel eScript — The VB and eScripts are used in the adapter to add validation logic while giving input to the Business Services. The following figure is a high level view of how the adapter is integrated with Siebel in the TIBCO environment. Figure 5 Logical Architecture for Integration With Siebel Siebel Application TIBCO ActiveMatrix Adapter for Siebel Message TIBCO Environment The following Siebel application interfaces are used by the adapter.

During connection pooling. The adapter creates the connections based on the following calculation: 2 (HTTP Thread Count) + 2 (DefaultRVCMQSession) + 3 (default Inbound thread count for DefaultRVCMSession) + 3 (default Inbound thread count for DefaultRVSession) + 1 backup connection object (which is not shown in the connection pool size displayed on the adapter console) = 11. If there are no Subscription Services in a session. This means that the number of connections to Siebel is the same as the number of threads. as shown in the above calculation. TIBCO ActiveMatrix Adapter for Siebel Concepts . The thread uses the same connection with Siebel till it is terminated. For example. The threads to process inbound events are configured at the session level and not at the service level. threads used for inbound services cannot be used for outbound service event execution. DefaultRVCMQSession and DefaultRVSession. The following default sessions are created in the adapter: DefaultRVCMSession. Otherwise. the adapter creates inbound connections for that session. In a typical configuration.Adapter Overview 17 | HTTP/HTTPS requests from Siebel and cannot be used for processing inbound sessions. one session could be used by a Subscription Service as well as Request-Response service. In that case. Assume that: • • You have specified HTTP threadCount (outbound) as 2. there is a one-to-one mapping between the threads and the Siebel connection. you should explicitly set the dispatcherCount for that session to 0 so that the adapter does not create connections (inbound) for that session. if you configure two threads for a RVCMSession. Both HTTP and HTTPS share the same threadpool. Similarly. two Subscription Service instances using RVCMQ and two Subscription Service instances configured using TIBCO Rendezvous messaging format. inbound thread count as 3 and threadCount for DefaultRVCMQSession as 2. Consider a scenario where there are two Publication Service instances using RVCM. a total of two threads are created for processing the events which are using this session. the same thread can process both types of events. DefaultRVSession You have not specified any threadCount value for DefaultRVCMSession and in the Multithreading tab. Connection Pooling The adapter has the capability of connection pooling.

the adapter exits if it fails to establish the first connection. But. it stops. If this connection check is successful. the adapter will continue with the reconnection attempts till it crosses the parameter configured for Number of attempts before stopping the adapter. The adapter tries to reconnect to the Siebel server as many times as you have configured it to retry. It should be configured in such a way that it is always greater than the threadCount (inbound + outbound) specified for the adapter. If the adapter is still not able to reconnect. While recreating the connection pool. Reconnection Mechanism The adapter uses a reconnection mechanism to handle the network glitches or Siebel server timeout related issues. If the adapter is able to reconnect. it does not exit. TIBCO ActiveMatrix Adapter for Siebel Concepts . it drops all the existing connections from the pool and recreates the complete connection pool. The reconnection mechanism starts whenever the adapter faces a Siebel application error while processing an event. if the adapter is able to create one or more connections. You can configure the numbers of times the adapter will attempt to connect to the Siebel server. It performs a dummy operation with the existing connection to check whether the connection is valid or not. If the operation is unsuccessful. the adapter displays an error for that event with the proper error message. Thereafter. the adapter suspends the Subscription Services.18 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel Relation between Max Jobs and Adapter Threads The Max Jobs at the Siebel server level refers to the Maximum number of tasks available in the Siebel Object Manager. The adapter does not attempt to recreate the connection pool. If it exceeds the parameter No of attempts before suspending services. the adapter activates the reconnection mechanism. but waits for the events.

and sends the message to the TIBCO environment. TIBCO ActiveMatrix Adapter for Siebel provides the following adapter services: • • • • Publication Service Subscription Service Request-Response Service Request-Response Invocation Service Communication parameters. Siebel connectivity parameters. Publication Service The adapter receives data from a Siebel application. and other parameters can be configured for these adapter services using TIBCO’s configuration tool.Adapter Services 19 | Adapter Services In TIBCO terminology. an adapter offers services to the host application and to the TIBCO environment. TIBCO Designer. converts the data to a TIBCO message. Figure 6 Typical Publication Service Flow Siebel Application TIBCO ActiveMatrix Adapter for Siebel Publish a Siebel Business Event Message Publication Service TIBCO Environment TIBCO ActiveMatrix Adapter for Siebel Concepts . A service broadly encapsulates routing rules for messages handled by the service and also custom configuration information. The following sections describe how these adapter services interact with a Siebel environment to provide message connectivity.

updated and updated by fields. created by. which will then publish it in the TIBCO environment. Publishes Siebel fields in Siebel formatted output forms. Queries Siebel Business Components and publishes them. Publishes non-Siebel business components. Publishes using TIBCO Rendezvous or JMS as the mode of transport. Publishes Siebel System fields including created. the Siebel system can be configured to send out records when an account is created in Siebel. when an account is created. Enables the adapter to directly interact with the Siebel application using the built in HTTP(S) Listener. For example. Allows user defined message field names representing native Siebel field names. Enables the adapter to read message from JMS queue added by the adapter’s Siebel JMS Business Service for publication. Siebel can be configured to send (via HTTP(S)) a notification to the adapter. For instance. Publishes Integration Objects Subscription Service The adapter gets a message from the TIBCO environment and sends the message to the Siebel application. TIBCO ActiveMatrix Adapter for Siebel Concepts .20 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel Publication Service Features The basic features of the Publication Service are as follows: • • • • • • • • • Example Scenario The Publication Service can publish business components received from the Siebel system.

When a response is returned to the adapter from the Siebel application.Adapter Services 21 | Figure 7 Typical Subscription Service Flow Siebel Application TIBCO ActiveMatrix Adapter for Siebel Subscribe to a Siebel Business Event Message Subscription Service TIBCO Environment Subscription Service Features The basic features of the Subscription Service are as follows: • • • • Example Scenario An external system publishes a message with Order Invoice information. the adapter sends the response to the TIBCO environment. Request-Response Service The adapter gets a request from the TIBCO environment and sends the request to the Siebel application. The transformation step involves conversion of the message so that it adheres to a schema recognized by the adapter. TIBCO ActiveMatrix Adapter for Siebel Concepts . 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 mode of transport Supports interfacing with Siebel Workflow and Integration Objects. The adapter subscribes to this message and updates the Order Invoice information into the Siebel system. This message is then transformed to a TIBCO message by an intermediate application and then published to the adapter.

converts it into formatted Siebel schema. fetches customer information from the Customer Business Component and sends a reply to the external system. 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. it takes the raw requested data.22 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel Figure 8 Typical Request-Response Service Flow Siebel Application PRC Client such as TIBCO BusinessWorks TIBCO ActiveMatrix Adapter for Siebel Reply Message Operating as an RPC Server Request Message TIBCO Environment The adapter supports Request-Response scenarios by acting like an RPC (Remote Procedural Call) server. When the adapter receives a request. and sends it to Siebel using a designated Siebel interface. The adapter passes on the request to the Siebel system. high throughput and load balanced message processing via the TIBCO Rendezvous Distributed Queues (RVCMQ) Protocol Example Scenario An external system querying for customer information invokes an operation in the Siebel adapter configuration. TIBCO ActiveMatrix Adapter for Siebel Concepts .

which sends out a request and receives a reply from the external system. Supports sending and receiving complete integration objects. TIBCO ActiveMatrix Adapter for Siebel Concepts . Can be invoked through the SendReceive method of the provided custom Siebel Business Service. The Siebel system invokes the adapter. EAI TIBCO HTTP Agent Business Service. When a response is returned from the TIBCO environment. the adapter sends the response back to the application. The adapter then sends the reply to the Siebel system.Adapter Services 23 | Request-Response Invocation Service The adapter gets a request from the Siebel application and sends the request through the TIBCO environment. Figure 9 Typical Request-Response Invocation Service Flow Siebel application Third-party application TIBCO ActiveMatrix Adapter for Siebel Response message Request message TIBCO environment 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 TIBCO Request-Response Services. Example Scenario The Siebel system may be configured to query for the Customer Business Component from an external system. Supports querying integration objects and returning integration objects from external systems.

developers do not have to redesign the business process. a specification document normally defines the data model for several related adapter applications. The adapter configuration is built using this definition. TIBCO Designer connects to the Siebel Business Layer using the design-time connection and fetches the Siebel Schema definition. Inside the TIBCO framework. When the data model of the Siebel application changes. for example: • When several developers collaborate on an adapter application. Using Schemas in conjunction with the various mapping tools available in the TIBCO environment. TIBCO ActiveMatrix Adapter for Siebel Concepts . you can instead define a schema to serve as the data model and update it as needed. • • Schemas for the Siebel Application are configured based on the Siebel Business Layer Definition. you can transfer data across applications with incompatible data formats.24 | Chapter 2 TIBCO ActiveMatrix Adapter for Siebel Schema Support The adapter uses schema to describe data received from or sent to the TIBCO environment. Schemas are useful in various situations.

page 34 TIBCO ActiveMatrix Administrator.Adapter Infrastructure Tools 25 | Chapter 3 Adapter Infrastructure Tools This chapter introduces the required and optional TIBCO infrastructure tools that work with an adapter. page 39 TIBCO ActiveMatrix Adapter for Siebel Concepts . page 27 TIBCO Administrator. page 28 TIBCO ActiveMatrix BusinessWorks. page 26 TIBCO Designer. page 32 TIBCO Business Studio. page 31 TIBCO Hawk. Topics • • • • • • • TIBCO Runtime Agent.

Migrate previous TIBCO Administrator installations. — The agent monitors the machine. and performs recovery as specified. Changing domain credentials is an advanced option. that is. Changing TIBCO Rendezvous parameters is an advanced option performed only by users familiar with TIBCO Rendezvous. That information is then visible via the TIBCO Administrator GUI.26 | Chapter 3 Adapter Infrastructure Tools TIBCO Runtime Agent The TIBCO Run-time Agent (TRA) provides basic connectivity between the adapter and other TIBCO infrastructure tools. all shared libraries including third-party libraries required by the adapter. • • • • TIBCO ActiveMatrix Adapter for Siebel Concepts . which is used to manage the components available on a TIBCO administration domain. The TRA has two main functions: • Supplies an agent that runs in the background on each machine. You must perform it on the machine where the TIBCO Administration Server is installed. • Supplies the run-time environment. Change TIBCO Rendezvous parameters. If you perform this task. TIBCO Domain Utility The TRA contains the TIBCO Domain Utility. The TRA is required on any machine on which an adapter is installed. then restart the TIBCO Administration Server. Add or remove the TIBCO Enterprise Message Service server plug-in to a TIBCO administration domain. The utility allows you to: • • • Add or remove a machine to a TIBCO administration domain. The TRA runs on each machine on which an adapter runs and executes scripts. sends alerts. Change TIBCO administration domain credentials. Remove a secondary TIBCO Administration Server. — The agent is responsible for starting and stopping processes that run on a machine according to the deployment information. you must perform it on each machine in the TIBCO administration domain. Enable TIBCO administration domain and security management on a machine where TIBCO Administrator has been installed.

The standalone adapter adds a palette to the TIBCO Designer environment which provides the adapter-specific resources Figure 10 TIBCO Designer Main Window TIBCO ActiveMatrix Adapter for Siebel Concepts . add adapter services to it with a simple drag-and-drop interface. you create a project. The next diagram shows the TIBCO Designer interface. Before using TIBCO Designer. The documentation can be accessed from the menu bar via TIBCO Designer Help > Designer Help. and specify the configuration information for each adapter service. Using Designer. make sure you read the TIBCO Designer help documentation.TIBCO Designer 27 | TIBCO Designer TIBCO Designer provides the design-time environment for configuring a standalone adapter project.

This includes security for server-based projects at design-time and for deployed applications at runtime. • Failure recovery. configure. while the secondary server supports read operations. machines. This console is also used to start and stop adapters. Alerts can be created. To get the load balancing benefit with HTTP. You can use a load-balanced TIBCO Administration Server for failure recovery. you can instead use a database back-end for your server and use checkpoints in the database for failure recovery. • User Management. Components within an administration domain can communicate with systems outside of the domain. users and groups. for example. • • • TIBCO Administration Domain A TIBCO administration domain is installed only if you have also installed the User Management module. In a completely trusted environment.28 | Chapter 3 Adapter Infrastructure Tools TIBCO Administrator TIBCO Administrator provides user. and components that an administration server manages. Load balancing. to notify an administrator if the number of processes or disk usage exceed a certain level. Application Management. TIBCO ActiveMatrix Adapter for Siebel Concepts . The primary server allows read and write operations. A TIBCO administration domain is a collection of users. you must either use an IP redirector or explicitly point to a backup server to be used when a server fails. This module allows you to upload Enterprise Archive (EAR) files. This module allows you to monitor machines and all running applications in a TIBCO administration domain. An adapter can be served by a primary and secondary TIBCO Administration Server. and deploy adapters. You define authentication. This module allows you to set permissions for adapter users. Load balancing is implemented through the use of the TIBCO Rendezvous distributed queue protocol (RVDQ) and therefore is not available for HTTP. See your IP Redirector or HTTP Server documentation for information on how to do this. Resource Management. resource. and application management modules for adapters. but the domain is the administrative boundary of your enterprise integration project. and create. There is only one Administration Server for each administration domain. and assign access control lists to users.

This is similar to a Microsoft Windows network domain where your machine can also belong to only one network domain. The server is included in both Administrator editions. Each machine can belong to only one TIBCO administration domain.TIBCO Administrator 29 | Each TIBCO administration domain contains one or more machines. TIBCO ActiveMatrix Adapter for Siebel Concepts . You can. TIBCO Administration Server The TIBCO Administrator Server provides a central storage and distribution point for configuration and schema data needed by an adapter. The GUI allows you to create user profiles and assign access to projects managed by the Administration Server. The TIBCO Administration Server is the machine process that handles the stored projects and user requests to manage the TIBCO administration domain. however. set up your system to use TIBCO Rendezvous rvrd and can then use the components across subnets. Each administration domain has one and only one TIBCO Administration Server. See the TIBCO Administrator Server Configuration Guide for details. By default. Using the TIBCO Administrator GUI. The TIBCO Administration Server supports centralized authentication and authorization. The next diagram shows the GUI. TIBCO Administrator GUI You can access the TIBCO Administration Server using the web-based TIBCO Administrator GUI. users with full administrative privileges can define who has access to projects that are managed by the repository server. The TIBCO Administrator Server contains its own web server (Apache Tomcat) that can be accessed via the TIBCO Administrator GUI for configuration and monitoring information. all machines within an administration domain are expected to be in the same network subnet. You can invoke the GUI from any machine in a TIBCO administration domain.

30 | Chapter 3 Adapter Infrastructure Tools Figure 11 TIBCO Administrator GUI TIBCO ActiveMatrix Adapter for Siebel Concepts .

TIBCO ActiveMatrix Adapter for Siebel Concepts . and easy to use integration platform that allows you to develop integration projects. and partner bindings. The business process receives data from an adapter service and routes data to an adapter service. Adapter Subscriber—Subscribes to incoming data published by the adapter.TIBCO ActiveMatrix BusinessWorks 31 | TIBCO ActiveMatrix BusinessWorks TIBCO ActiveMatrix BusinessWorks is a scalable. TIBCO ActiveMatrix BusinessWorks provides the following activities for use with adapters: • Publish to Adapter—Publishes data from the process to an adapter. Wait for Adapter Message—Waits for the receipt of a message from the publication service of the specified adapter. See the TIBCO ActiveMatrix BusinessWorks Service Engine documentation for more information. extensible. In TIBCO ActiveMatrix BusinessWorks. Invoke an Adapter Request-Response Service—Communicates (as a client) with an adapter request-response service. partners. TIBCO ActiveMatrix BusinessWorks includes a graphical user interface for defining business processes and an engine that executes the processes. which subscribes to data coming from the process and passes the data to the target application. adapter services are responsible for publishing or subscribing to business data in a decoupled yet reliable manner. Adapter Request-Response Server—Starts a process based on the receipt of a request from an adapter. Respond to Adapter Request—Sends a response to an adapter for a previously received request. Wait for Adapter Request—Waits for the receipt of a request from a request-response invocation service. TIBCO ActiveMatrix BusinessWorks supports service oriented processing with the use of service resources. • • • • • • See the TIBCO ActiveMatrix BusinessWorks documentation for more information. TIBCO ActiveMatrix BusinessWorks Service Engine The product provides an ActiveMatrix container to deploy ActiveMatrix BusinessWorks projects using TIBCO ActiveMatrix Administrator.

and slowdowns of critical business systems. and loading activities for all nodes in a local or wide-area network and take action when pre-defined conditions occur. log. Hawk Application Management Interface (AMI) routines can be embedded within custom adapters. and CPU utilization. TIBCO Hawk features include: • Extensive monitoring capabilities at the operating system and application levels including process data. Built-in routines within other TIBCO ActiveEnterprise components allow for proactive management. and system files. and microagents whose monitoring duties are defined by the rule bases. a central repository for storage of configuration objects. The microagents provide: • Business level statistics—statistics that report the progress of the adapter as it interacts with the vendor application. System administrators can monitor application parameters. Adapter Microagents Each adapter includes a standard and custom microagent. run-time failures or slowdowns can be repaired automatically within seconds of their discovery. In many cases. • • Agents monitor local conditions and take action or publish alert information that appears in the TIBCO Hawk display. disk. which continue to perform local tasks even in the event of network failure • • • • TIBCO Hawk consists of several components: a console display. in a database adapter such TIBCO ActiveMatrix Adapter for Siebel Concepts . behavior.32 | Chapter 3 Adapter Infrastructure Tools TIBCO Hawk TIBCO Hawk monitors and manages distributed applications and systems throughout the enterprise. allowing active management of those adapters by the Hawk micro-agent Distributed micro-agents support autonomous network behavior so local management and problem resolution can continue during an outage Fault-tolerance is achieved through the independent operation of Hawk agents. For example. network statistics. Problems can be found and fixed before failures can occur. reducing unscheduled outages. agents. Microagents act as an interface to the managed objects and are invoked through their supported methods.

Using these methods. one might be able to identify certain bottlenecks or gauge how successfully an adapter is scaling with respect to the current environment. internal queues. specific queries can return information about threads. or connections to the target system. This includes retrieving the current runtime parameters and setting new runtime parameters without restarting the adapter. This can be an important tool for seeing the internal of an adapter and debugging it if something appears wrong. Updates to the adapter runtime parameters. An example of this is getting and setting the polling interval. or deleted in the database.TIBCO Hawk 33 | statistics might indicate whether objects were successfully or unsuccessfully inserted. • Queries that return information about the state of the adapter. Updating a runtime parameter through the Hawk microagent only affects the setting of the instance that is running. updated. • TIBCO ActiveMatrix Adapter for Siebel Concepts . For example.

and so on. In this view you can delete the TIBCO ActiveMatrix Adapter for Siebel Concepts . For introductory information on TIBCO Business Studio. You can easily navigate from one part of a composite to another. Other editors allow you to configure shared resources and service assemblies. WSDL files. composite files. The Composite Editor contains a canvas on which you can drop elements and a palette that organizes the elements that you can add to the composite. To view the online help. • Outline Provides a overview of the Composite Editor canvas. Tool bar See Help > Help Contents > Workbench User Guide. Figure 12 TIBCO Business Studio The screen contains the following area and views: • • • Menu See Help > Help Contents > Workbench User Guide. select Help > Help Contents. Editor Displays editors for the objects currently being edited. Project Explorer Displays a tree containing all the project resources such as project folders. refer to the Workbench User Guide in the TIBCO Business Studio online help. You can switch • between editors by clicking the tabs at the top of the Editor area. The Outline view also displays a content tree structure that contains the composite element inside the composite.34 | Chapter 3 Adapter Infrastructure Tools TIBCO Business Studio The TIBCO ActiveMatrix development tools consist of TIBCO Business Studio and a set of ActiveMatrix plug-ins. service assembly files. shared resource definition files.

TIBCO Business Studio 35 | contents of the composite. — Registries Lists UDDI registries and the WSDL files returned from searching for a registry. ActiveMatrix Resource Wizard The starting point for creating all types of ActiveMatrix projects and assets is the ActiveMatrix Resource Wizard. • Views Appears under the Editor Area and contains the following views: — Properties Displays property sheets for editing composites and composite elements. — Problems Displays validation and other errors. When you select a composite or composite element in the Composite Editor canvas. The resource wizard allows you to select wizards to create: • • • • • • Adapter service engine projects ActiveMatrix sample projects ActiveMatrix SOA projects Composites Mediation flows Service assemblies TIBCO ActiveMatrix Adapter for Siebel Concepts . the corresponding artifact in the composite becomes selected. You can open a view by selecting Window > Show View > View. this view shows the properties of the selected object in a vertical tabbed notebook. When you select a composite element in the Outline tree.

Figure 13 shows the an example of the Properties view.36 | Chapter 3 Adapter Infrastructure Tools Composite Element Editors Composite elements are configured in property sheets accessed through the Properties view. Figure 13 Component Property Sheet TIBCO ActiveMatrix Adapter for Siebel Concepts .

TIBCO Business Studio 37 | Debugger The TIBCO Business Studio debugger provides a testing environment for stepping through composite elements and determining the sources of errors. In the Variables view on the top-right. Figure 14 Debugger TIBCO ActiveMatrix Adapter for Siebel Concepts . Figure 14 shows the debugger in the process of debugging a sample HelloWorld composite. and the debugger is stopped at the first breakpoint. the value of the request is being examined. Breakpoints have been set before and after the Java component executes.

Figure 15 Service Assembly Editor TIBCO ActiveMatrix Adapter for Siebel Concepts . Figure 15 shows a sample service assembly editor view. composites must be transformed into service units and service assemblies.38 | Chapter 3 Adapter Infrastructure Tools Service Assembly Editor In order to be deployed.

TIBCO ActiveMatrix Administrator Architecture Figure 16 shows ActiveMatrix Administrator components. environment.TIBCO ActiveMatrix Administrator 39 | TIBCO ActiveMatrix Administrator ActiveMatrix provides TIBCO ActiveMatrix Administrator for enterprise. other servers. To get a quick introduction to the use of the administration tools. TIBCO ActiveMatrix Adapter for Siebel Concepts . ActiveMatrix Administrator supports both graphical and command-line interfaces. The following sections provide an overview of TIBCO ActiveMatrix Administrator. see TIBCO Hawk Administrator’s Guide. and service management. see TIBCO ActiveMatrix Service Grid Getting Started. For detailed information about the administration tools. and the relationship between ActiveMatrix Administrator. and ActiveMatrix machines and nodes.

TIBCO ActiveMatrix Adapter for Siebel Concepts . • ActiveMatrix Database Stores ActiveMatrix administration data. interacts with the authentication realm server to authenticate users.40 | Chapter 3 Adapter Infrastructure Tools Figure 16 TIBCO ActiveMatrix Administration Architecture AMA Client Machine AM Machine 1 AMA CommandLine Interface AMA Graphical User Interface AM Node Management Daemon AMA Machine 2 AMA Server 2 AMA Machine 1 AMA Server 1 AM Machine 2 Management Daemon AM Node Authentication Realm Database AMA Cluster Legend AM TIBCO ActiveMatrix AMA TIBCO ActiveMatrix Administrator The TIBCO ActiveMatrix Administrator administration architecture consists of the following components: • TIBCO ActiveMatrix Administrator Server Gathers management data from nodes. responds to requests from the ActiveMatrix Administrator graphical and command-line UIs. ActiveMatrix Administrator servers within a cluster share a database and authentication realm and are kept synchronized. and interacts withTIBCO Management Daemon to manage nodes. • TIBCO ActiveMatrix Administrator Cluster Groups one or more ActiveMatrix Administrator servers.

enterprise configuration and environment administration are carried out in the Configure Enterprise Assets and Configure an Environment perspectives respectively. In the graphical interface. • ActiveMatrix Administrator Graphical UI Displays the ActiveMatrix Administrator user interface. and managed resources. containers. Figure 17 TIBCO ActiveMatrix Administrator Enterprise and Environment Administration ActiveMatrix Administrator graphical and command-line interfaces permit you to administer ActiveMatrix enterprises and environments. shared resource configurations. Management Daemon Gathers installation information and exposes ActiveMatrix node life cycle operations. • • ActiveMatrix Administrator Command-Line Interface Provides a script-based interface for ActiveMatrix Administrator functions.TIBCO ActiveMatrix Administrator 41 | • Authentication Realm Manages user authentication data. functionality is divided into perspectives. The authentication realm can be provided either by TIBCO Administrator or by another server or a file. nodes. A perspective is a set of controls used to carry out a category of administration tasks. Figure 17 shows the ActiveMatrix Administrator graphical UI welcome page. In ActiveMatrix Administrator. TIBCO ActiveMatrix Adapter for Siebel Concepts .

TIBCO ActiveMatrix Adapter for Siebel Concepts . The choice of how to distribute services across nodes is determined by the desired level of service performance and availability. During deployment. these tasks are carried out in the Deploy to an Environment and Monitor & Manage perspectives. No configuration is required to make services highly available. A container group is defined as a group containing one or more container instances of the same container type. Service Deployment The first phase of service administration is deployment. if one container fails. the service units within a service assembly are mapped and then deployed into their respective containers. Load Balanced Services The Mediation Bus enables load balancing at the container level by defining a container group.42 | Chapter 3 Adapter Infrastructure Tools Service Administration ActiveMatrix Administrator graphical and command-line interfaces permit you to administer ActiveMatrix services. Service administration consists of deployment tasks and monitoring and management tasks. which allows Messaging Bus to distribute requests between the service instances. The services provided by the service units are registered with the ActiveMatrix container and the service endpoints are activated. a copy of the service unit is deployed into each container in the group. When a service unit is deployed to a container group. In the graphical interface. Load Balanced Services Requests to services deployed on multiple containers are load balanced between the available providers. Service performance and availability can be enhanced if you deploy a service unit across multiple nodes. service requests will be handled by one of the remaining containers. Messaging Bus automatically routes to any available service instance identified in the message exchange. Highly Available Services Services deployed on multiple containers are highly available. Messaging Bus uses a round robin algorithm for routing requests to service instances. No configuration is required to load balance between services.

TIBCO ActiveMatrix Administrator 43 | Service Monitoring and Management TIBCO ActiveMatrix Administrator not only allows you to configure and deploy services. and services. In the Monitor & Manage perspective. but also lets you monitor and manage the deployed services. and service unit. TIBCO ActiveMatrix Adapter for Siebel Concepts . availability of services. The Monitor & Manage perspective of TIBCO ActiveMatrix Administrator keeps track of system health without much overhead. you can monitor the overall health and performance of the grid infrastructure. and the ratio of successful to faulty service responses. container. node. These metrics provide real-time values by fetching data every minute and updating the values of the metrics. service usage. The monitoring subsystem uses content-based metrics to measure the service performance. Monitoring the system performance is not a one time activity but needs to be performed on a day-to-day basis. service assembly. machine. The real-time data is then displayed in a web-based dashboard provided with pre-defined views and visual alerts. applications. You can monitor performance at various levels such as environment.

44 | Chapter 3 Adapter Infrastructure Tools TIBCO ActiveMatrix Adapter for Siebel Concepts .

19 Publication Service 5 Request-Response Invocation Service 6 Request-Response Service 5 Subscription Service 5 Adapter Terms . 15. 3 Adapter Infrastructure Tools TIBCO ActiveMatrix Administrator 39 TIBCO ActiveMatrix BusinessWorks Service Engine 31 TIBCO Administrator 28 TIBCO Business Studio 34 TIBCO Designer 27 TIBCO Hawk 32 TIBCO Runtime Agent 26 Adapter Microagents 32 Adapter Services 5.ear file 4 adapter container 4 business objects 4 Message Exchange Pattern (MEP) 4 palette 4 project 4 service assembly 4 SOA 4 WSDL 4 authentication realm 41 B Business Event specification 13 C composite element editors 36 Connection Pooling 17 Customer Support xv E ENV_HOME xii H highly available services 42 L load balanced services 42 M Multithreading 15.| 45 Index A ActiveMatrix Administrator cluster 40 ActiveMatrix Administrator server 40 ActiveMatrix Database 40 ActiveMatrix resource wizard 35 Adapter service engine 3 standalone 3 Adapter Components 3. 15 TIBCO ActiveMatrix Adapter for Siebel Concepts .

12 Integration Objects 11 Relational Database Management System (RDBMS) 10. 11 Subscription Service typical flow diagram 21 support. 42 service and binding definition editor 36 service assembly deployment 42 service deployment 42 service monitoring and management 43 Service Oriented Architecture (SOA) 3 Siebel Application Interfaces Siebel Business Service 16 Siebel eScript 16 Siebel VB 16 Siebel eBusiness Applications 10 Siebel Multi-layered Architecture 10 Business Objects Layer 10. contacting xv TIBCO ActiveMatrix Adapter for Siebel Concepts .46 | Index P Publication Service typical flow diagram 19 T technical support xv Third-Party Documentation xi TIBCO ActiveMatrix Administrator 39 TIBCO ActiveMatrix Administrator architecture 39. 12 Siebel Workflow 12 User Interface Objects Layer 10. x RPC server used by the adapter 22 S schema examples of use 24 Schema Support 24 service administration 42. 11 Data Objects Layer 10. 39 TIBCO Administration Domain 28 TIBCO Administration Server 29 TIBCO Business Studio debugger 37 TIBCO Domain Utility 26 TIBCO Resource Wizard 35 TIBCO Runtime Agent 26 TIBCO_HOME xii TRA 26 Typographical Conventions xii general xii syntax xiii R Reconnection Mechanism 18 Related Documentation x.