tibco adapter for siebel examples guide - tibco software · pdf fileinvoke siebel workflow...

TIBCO Adapter™ for Siebel

Examples GuideSoftware Release 5.3.2June 2011

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIB, The Power of Now, TIBCO Adapter, TIBCO ActiveEnterprise, TIBCO InConcert, TIBCO Rendezvous, TIBCO Designer, TIBCO Administrator, TIBCO IntegrationManager and TIBCO Hawk 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 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 © 1997-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xTIBCO Adapter for Siebel Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Terminology and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xivHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xivHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xivHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv

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

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Using TIBCO BusinessWorks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Using TIBCO IntegrationManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2 TIBCO BusinessWorks: Working with the Customer Business Object. . . . . . . . . . .11

Example Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Set up the Customer Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Deploy and Run the Customer Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Expected Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 TIBCO BusinessWorks: Working with the SalesOrder Business Object . . . . . . . . .19


Set up the SalesOrder Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Test the SalesOrder Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Expected Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 4 TIBCO BusinessWorks: Working with the PurchaseOrder Business Object . . . . . .27


Set up the PurchaseOrder Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Test the PurchaseOrder Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

TIBCO Adapter for Siebel Examples Guide

iv | Contents

Expected Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5 TIBCO BusinessWorks: Working with the Employee Business Object . . . . . . . . . . 33


Set up the Employee Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Test the Employee Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37


Chapter 6 TIBCO BusinessWorks: Working with the Material Business Object . . . . . . . . . . . 39


Set up the Material Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Test the Material Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43


Chapter 7 Invoking a Business Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45


Set up the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Deploy and Run the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48


Chapter 8 TIBCO IntegrationManager: Working with the Customer Business Object . . . . . . 51

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Integration Scenario Between the Adapter and TIBCO IntegrationManager . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configure the Customer Business Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Task A Configure an Adapter Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Task B Configure Design-time Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Task C Configure an Adapter Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configure the Get_Customer Process in TIBCO IntegrationManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Task A Create a Channel for JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Task B Create Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Task C Read, Map and Invoke the Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Task D Analyze the Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Configure the Update_Customer Process Using TIBCO IntegrationManager . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configure the Sync_Customer Process Using TIBCO IntegrationManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Setting .tra File Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Start the Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Test the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Monitor the Customer Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75


Contents | v

Stop the Customer Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 9 TIBCO IntegrationManager: Working with the SalesOrder Business Object . . . . . .77

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configure the SalesOrder Business Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Setting .tra File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Start the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Test the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Monitor the SalesOrder Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Stop the SalesOrder Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 10 TIBCO IntegrationManager: Working with the PurchaseOrder Business Object . .89

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configure the PurchaseOrder Business Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Setting .tra File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Start the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Test the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Monitor the PurchaseOrder Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Stop the PurchaseOrder Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 11 TIBCO IntegrationManager: Working with the Employee Business Object . . . . .101

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Configure the Employee Business Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Setting .tra File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Start the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Test the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Monitor the Employee Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Stop the Employee Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Chapter 12 TIBCO IntegrationManager: Working with the Material Business Object . . . . . . .113

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configure the Material Business Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Setting .tra File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Start the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Test the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Monitor the Material Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123


vi | Contents

Stop the Material Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Chapter 13 Using the Custom Business Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

EAI TIBCO HTTP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Using the Business Service Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Importing the Input Parameters for the GetState Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Invoking GetState Without the Publisher Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Invoking GetState With Publisher Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Invoking Send With Single Key Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Invoking Send With the Multiple Keys Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Invoking SendReceive With Schema Reply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Examples for Siebel 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Importing the Input Parameters for the GetState Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Invoking GetState Without the Publisher Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Invoking GetState With the Publisher Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Invoking Send with the Single Key Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Invoking Send With the Multiple Keys Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Invoking SendReceive with Schema Reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Integrating in a Siebel Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Publish Request in a Workflow Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Publish Request in Workflow Process with Reply and Reply Written to an XML File . . . . . . . . . . . . . . . . . 151Importing a Workflow Process for a Publish Request with Reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Examples for Siebel 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Publish Request in a Workflow Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Publish Request in a Workflow Process with Reply and Write the Reply to an XML File . . . . . . . . . . . . . . 158Importing a Workflow Process for a Publish Request with Reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Chapter 14 Simple Publisher Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Publish Account and its Business Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Invoking the Adapter using Business Service Simulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Publish Integration Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Publish Complete Integration Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Publish Non-Siebel Business Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Publish Complete Integration Object as XML Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Chapter 15 Simple Subscription Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Invoke Siebel Workflow Process (Synchronous Request) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Invoke Siebel Workflow Process (Asynchronous Request) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177


Contents | vii

Invoke Business Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Insert Account Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Insert Integration Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Chapter 16 Simple Request Response Service Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Invoke Workflow process using TIBCO BusinessWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Send Receive Integration Objects as an XML Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Invoke Business Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Query Account Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Insert or Update Account Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Query Integration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Insert or Update Integration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Chapter 17 Invoking a Siebel Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Using a Sample Workflow to Generate an XML File from Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Using Sample Workflow to Generate an XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Using a Sample Workflow to Generate an XML File from Request Response Server . . . . . . . . . . . . . . . . . . . . 206Using Sample Workflow to Generate an XML File from Request-Response Server . . . . . . . . . . . . . . . . . . 206

Using Sample Workflow to Invoke EAI Siebel Adapter Business Service From Subscriber . . . . . . . . . . . . . . . . 214

Using Sample Workflow to Invoke EAI Siebel Adapter Business Service From Request Response Server . . . . 218

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219


viii | Contents


| ix

Preface

This guide includes examples that demonstrate how the adapter interacts with TIBCO BusinessWorks™ and TIBCO IntegrationManager™.

Topics

• Related Documentation, page x

• Terminology and Acronyms, page xiii

• How to Contact TIBCO Customer Support, page xiv


x | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Adapter for Siebel DocumentationThe following documents form the TIBCO Adapter for Siebel documentation set:

• TIBCO Adapter Concepts Read this document for an introduction to TIBCO adapters, adapter components, capabilities, lifecycle and types of adapters available.

• TIBCO Adapter for Siebel User’s Guide Read this manual for instructions on installing and using the adapter.

• TIBCO Adapter for Siebel Examples Guide Read this manual for examples of using the adapter.

• TIBCO Adapter for Siebel Release Notes Read this for a summary of features, changes since the last release, and a description of any issues that may affect installing or using the adapter.

• TIBCO Adapter for Siebel readme.txt: Read this document to check the current release number, supported platforms and required software.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products. Note that only books that relate to adapters are listed. Each of the books is available from the doc directory in the product’s installation area.

• TIBCO Designer™ software:

— TIBCO Designer User’s Guide

— TIBCO Designer Palette Reference

— TIBCO Designer Release Notes

• TIBCO Administrator™ software:

— TIBCO Administrator User’s Guide

— TIBCO Administrator Server Configuration Guide

— TIBCO Administrator Release Notes


Preface | xi

• TIBCO BusinessWorks™ software:

— TIBCO BusinessWorks Concepts

— TIBCO BusinessWorks QuickStart

— TIBCO BusinessWorks Process Design Guide

— TIBCO BusinessWorks Palette Reference

— TIBCO BusinessWorks Installation

— TIBCO BusinessWorks Release Notes

• TIBCO IntegrationManager™ software:

— TIBCO IntegrationManager Concepts

— TIBCO IntegrationManager Administrator’s Guide

— TIBCO IntegrationManager Process Design Guide

— TIBCO IntegrationManager Reference

— TIBCO IntegrationManager Release Notes

• TIBCO Rendezvous™ software:

— TIBCO Rendezvous Concepts

— TIBCO Rendezvous Administration

— TIBCO Rendezvous Configuration Tools

• TIBCO Enterprise Message Service™ software:

— TIBCO Enterprise Message Service User’s Guide

— TIBCO Enterprise Message Service Installation

— TIBCO Enterprise Message Service Application Integration

— TIBCO Enterprise Message Service Release Notes

• TIBCO Hawk® software:

— TIBCO Hawk Installation and Configuration

— TIBCO Hawk Administrator’s Guide

• TIBCO Adapter™ SDK

— TIBCO Adapter SDK Concepts


xii | Related Documentation

• TIBCO Runtime Agent™ software

— TIBCO Runtime Agent Release Notes

— TIBCO Runtime Agent Installation

— TIBCO Runtime Agent Domain Utility User’s Guide

— TIBCO Runtime Agent Upgrading to Release 5.3

Third Party Documentation

You may also find it useful to read the following documentation:

• The Siebel eBusiness Bookshelf, available from Siebel Systems Inc.


Preface | xiii

Terminology and Acronyms

Acronym Meaning

TIBCO_HOME The folder where all TIBCO products are installed on the host. For example, C:\Tibco.

<Adapter_Home> The location where the adapter has been installed on the host.

Inbound Events coming into the adapter. It refers to the inflow of data into the Siebel application. It is applicable to Subscription and Request-response services.

Outbound Events going out from the adapter. It refers to data being captured from the Siebel application and being sent out. It is applicable to the Publication Service.

JMS Java Messaging Service.

DTD Document Type Definition

XML eXtensible Markup Language

EAR File Enterprise Archive File


xiv | How to Contact TIBCO Customer Support

How to Contact TIBCO Customer Support

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

How to Access All TIBCO DocumentationAfter you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com/TibcoDoc

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

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

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

https://support.tibco.com

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


http://www.tibcommunity.com

http://docs.tibco.com/TibcoDoc

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

https://support.tibco.com

| 1

Chapter 1 Introduction

This chapter includes procedures and prerequisites that have to be carried out before you start running the examples provided with your adapter installation. Detailed information for the examples is provided in subsequent chapters of this guide.

Topics

• Overview, page 2

• Prerequisites, page 5

These examples have been configured against Siebel version 7.5.2 eBusiness Applications.


2 | Chapter 1 Introduction

Overview

The examples discussed in this guide demonstrate:

• The integration between the adapter and two TIBCO products, TIBCO BusinessWorks and TIBCO IntegrationManager.

• Invoking a Business Service

• The various adapter services

• The use of the Custom Business Service

• Invoking a Siebel Workflow

The Business Objects used in the examples are:

• Customer

• SalesOrder

• PurchaseOrder

• Employee

• Material

The examples provide different operations on each of these Business Objects. A brief of these operations is given below:

Get

In this operation, TIBCO BusinessWorks requests data to be fetched from the Siebel application. The Request-Response service is used to simulate this. The request in the example is read from an XML file. The corresponding Request-Response service is executed on the adapter and the result is returned to TIBCO BusinessWorks. TIBCO BusinessWorks maps the results according to business requirements and the data is written to an XML file.

Update

Another important requirement in an integration scenario is to update data in an existing record. This scenario is simulated in two ways.

• The first one uses a Publish-Subscribe scenario. Data is published by the adapter’s Publication Service, the values that need to be updated are modified using the TIBCO BusinessWorks process. The updated message is sent to the adapter’s Subscription Service and the Subscription Service updates the values in the target database. This scenario is used in the Customer, Employee and Material examples.


Overview | 3

Figure 1 Update Operation using Publish-Subscribe

• The second is a Request-Response scenario. The values are modified in the mapper class in TIBCO BusinessWorks and the request is sent to the adapter. The Request-Response service of the adapter receives the request and updates the values in the Siebel database. This scenario is used in the SalesOrder and PurchaseOrder examples.

Figure 2 Update Operation using Request-Response



Sync

In this operation, the adapter publishes a message. If there are any changes in the Siebel target application, TIBCO BusinessWorks picks up the message, performs the necessary mapping of the fields and writes them to an XML file.

For publishing an event from Siebel, please refer to TIBCO Adapter for Siebel User’s Guide.


Prerequisites | 5

Prerequisites

Using TIBCO BusinessWorksIf you are using the adapter with TIBCO BusinessWorks, the following software must be installed to run the examples:

• TIBCO Runtime Agent

• TIBCO BusinessWorks

• TIBCO Administrator

• TIBCO Integration Manager

• TIBCO HAWK

• TIBCO Enterprise Message Service

• TIBCO Adapter for Siebel

For the latest versions of the listed products, refer to TIBCO Adapter for Siebel readme.txt.

The examples use TIBCO Designer to create an Enterprise Archive File (EAR) and TIBCO Administrator to deploy the EAR file.

In TIBCO Administrator, make sure all software components needed by the adapter instance are installed on one or more machines that are part of a TIBCO administration domain and that the software is registered in the domain.

• Use the TIBCO Domain Utility to add a machine to a TIBCO Administration Domain.

These topics are explained in the TIBCO Administrator documentation set.

Using TIBCO IntegrationManagerIf you are using the adapter with TIBCO IntegrationManager, the following software must be installed to run the examples:

TIBCO Enterprise Message Service (EMS) must be installed to run examples that use JMS as the transport. The JMS server must be running and accessible to the machine on which the adapter is installed. Siebel Server must be installed and running. The ObjectManager on the Siebel application server being used must be active. The Custom Business Service EAI TIBCO HTTP Agent, must be imported into the Siebel repository. For more information on importing the Custom Business Service, refer to TIBCO Adapter for Siebel User’s Guide.



• TIBCO Runtime Agent

• TIBCO BusinessWorks

• TIBCO IntegrationManager

• TIBCO Administrator

• TIBCO HAWK

• TIBCO Enterprise Message Service

• TIBCO Adapter for Siebel

For the latest versions of the listed products, refer to TIBCO Adapter for Siebel readme.txt.

Working with dat Files

The dat files included in the adapter installation are used by all examples except the TIBCO BusinessWorks examples.

You cannot directly open a dat file in TIBCO Designer and make modifications to the configurations. To do this, carry out the following steps:

1. Convert the dat file to a multi-file project.

a. Open TIBCO Designer. In the first screen that is displayed, click Administration. The screen is shown next.

TIBCO Enterprise Message Service (EMS) must be installed to run examples that use JMS as the transport. The JMS server must be running and accessible to the machine on which the adapter is installed. Siebel Server must be installed and running. The ObjectManager on the Siebel application server being used must be active. The Custom Business Service EAI TIBCO HTTP Agent, must be imported into the Siebel repository. For more information on importing the Custom Business Service, refer to TIBCO Adapter for Siebel User’s Guide.


Prerequisites | 7

b. Then click the Convert DAT to Files icon. In the window that is displayed, browse the DAT File field and select the dat file you wish to convert to a multi-file project. Thereafter, browse the Project Directory field and select the location (other than the folder containing the dat file) where you wish to save the multi-file project and give the same name as your dat file. Click OK.

In the Convert DAT To File-Based Project dialog, you can see the CREATE.dat file in the temp folder. Do not choose temp to save your multi-file project, as TIBCO Designer does not allow you to save multi-file project with the same name as that of the .dat file in the same folder.

You can save the multi-file project in any other folder, with same name as that of the dat file.

If you use a different name for the multi-file project, the value of the global variable deployment will be changed. Therefore, it is mandatory to use the same name for the multi-file project as that of the.dat file.



2. Click the Open existing project icon from the first TIBCO Designer screen. Browse to the directory where the converted multi-file project is saved.

3. Make configuration changes as per your requirements.

4. Export the multi-file project to a dat. Select Project>Export Full Project from the menu. Browse and select the location of the directory you wish to save the dat file to. Ensure that the directory is different from the multi-file project. Enter the name of the project and click OK.

LocationThe files for the examples along with the sample messages are in the following location:

For TIBCO BusinessWorks examples:TIBCO_HOME\adapter\adsbl\<version_num>\examples\BusinessWorks\<Business Object>

For TIBCO IntegrationManager examples:

TIBCO_HOME\adapter\adsbl\<version_num>\examples\<Business Object>

All other examples are at:

TIBCO_HOME\adapter\adsbl\<version_num>\examples\<Business Scenario>

Folders

The folders present in the location TIBCO_HOME\adapter\adsbl\<version_num>\examples are as follows:

pubtest —This directory contains files required for a simple post-installation publication test.

pubIntObj — This directory contains files required for a simple post-installation publication test for Siebel Integration Object.


Prerequisites | 9

subtest — This directory contains files required for a simple post-installation Subscription test.

subIntObj — This directory contains files required for a simple post-installation Subscription test for Siebel Integration Object.

pubsamples — This directory contains sample Business Events configured using commonly used Siebel Business Object or Business Components in typical integration scenario for exporting Siebel data to external systems.

subsamples — This directory contains sample Business Events configured using commonly used Siebel Business Object or Business Components in typical integration scenario for importing external data into Siebel.

rpcsamples — This directory contains sample Business Events configured for demonstrating the request-response service feature of the adapter.

rpcIntObj — This directory contains sample Business Events configured for demonstrating the request-response service of the adapter for Siebel Integration Objects.

service — This directory contains examples on how to invoke the EAI TIBCO Agent Adapter and EAI TIBCO HTTP Agent Business Services using the Siebel Business Service Administration Simulator. These examples require TIBCO Integration Manager transforms to use of the SendReceive service method to return non-Siebel data to Siebel client by using the Request-Response Service.

workflow — This directory contains examples on how to invoke the EAI TIBCO HTTP Agent Business Service along with the Siebel native EAI Siebel Adapter Business Service in a workflow using the Siebel Workflow Administration Simulator. It contains an example to use the Subscription Service to invoke a Siebel Workflow process provided in subservices.dat.

svb — This directory contains an example on how to invoke the EAI TIBCO HTTP Agent Adapter Business Service from the Siebel event script written in Siebel VBScript.

escript — This directory contains an example on how to invoke the EAI TIBCO HTTP Agent Business Service from the Siebel event script written in Siebel eScript.

Repository Files

Following are the repository files used by the examples:

pubservices.dat — This is a local Repository instance binary file that contains all the definitions used in the following examples for configuration:

siebel/pubsamples



siebel/pubtest

siebel/pubIntObj

subservices.dat — This is a local Repository instance binary file that contains all the definitions used in the following examples for configuration:

siebel/subsamples

siebel/subtest

siebel/subIntObj

rpcservices.dat — This is a local Repository instance binary file that contains all the definitions used in the following examples for configuration:

siebel/rpcsamples

siebel/rpcIntObj


| 11

Chapter 2 TIBCO BusinessWorks: Working with the Customer Business Object

This chapter demonstrates the Get, Update and Sync operations on a Customer Business Object, using TIBCO BusinessWorks.

Topics

• Example Description, page 12

• Set up the Customer Example, page 13

• Deploy and Run the Customer Example, page 14

• Expected Results, page 17


12 | Chapter 2 TIBCO BusinessWorks: Working with the Customer Business Object

Example Description

This example demonstrates three different operations on a Customer Business Object.

• Get_Customer fetches Customer details from Siebel and writes them back in an XML file. The Customer Name is read from an XML file containing query details.

• Update_Customer updates the Customer details in Siebel. The details to update a record are read from an XML file.

• Sync_Customer publishes a message out of Siebel whenever Customer details are modified or updated in the target Siebel application, TIBCO BusinessWorks receives details of this Customer, and logs it in an XML file.


Set up the Customer Example | 13

Set up the Customer Example

Before starting the example you must import the sample project zip file and save it in a new project.

Task A Get_Customer, Update_Customer and Sync_Customer Setup

In TIBCO Designer:

1. In the initial dialog box click Open New Project and specify a name for the project.

2. Click Project>Import Full Project.

3. Click the Zip Archive tab and browse to locate the Customer.zip file. The file is located in the <install-path>/tibco/adapter/adsbl/<version_num>/examples/BusinessWorks/Customer folder.

4. Save the project as Customer.

5. Drag and drop the Enterprise Archive in the project panel.

6. Drag and drop an Adapter Archive into the Enterprise Archive.

7. Associate the Customer_RV adapter configuration with the adapter archive.

8. Select the Enterprise Archive in the project panel.

9. Click Build Archive in the Configuration tab. This creates an archive file.

10. Exit TIBCO Designer.

Make sure that the path provided for XML files to be used in File Poller, Read File and Write File is correct in TIBCO BusinessWorks.



Deploy and Run the Customer Example

Perform the following tasks to deploy and run the example.

Task B Deploy the Example

In TIBCO Administrator:

1. Click on the Installed Software link on the left panel. Check if TIBCO Adapter for Siebel 5.3.0 is registered. If the software is not registered, register by selecting the Add Custom Software button. Please refer to the TIBCO Administrator documentation for more details on adding custom software.

2. Go to Application Management. Click New Application. Upload the EAR file created in the previous section and click OK. On the following screen, clear the Quick Configure check box and then click Save.

3. Click Configuration in the newly created application. Click on the top level application name in the configuration view.

a. Go to the Advanced tab and provide the values for App Name, User Name, Password.

b. Provide appropriate values for the following global variables:SiebelEnterpriseServer

SiebelHost

SiebelServer

SiebelObjectManager

SiebelLoginName

SiebelLoginPassword

c. Click Save. The configuration screen appears.

d. Expand the Enterprise archive link, so that the adapter instance, Customer_RV.aar is visible.

e. Click Customer_RV.aar and then click the Add to Additional Machines button.

f. Select the machine and click OK. In the following screen, click Save.

4. Once the deployment is complete, click Service Instances under the application. The adapter is displayed. Select the adapter and click Start Selected. The adapter instance is started.

Make sure that the TIBCO Administrator domain and the adapter configuration domain are the same.


Deploy and Run the Customer Example | 15

Task C Run the Example

To run each example:

• To trigger Get_Customer, you must enter the key values in the Get_Customer_Request.xml file located in the <install-path>/tibco/adapter/adsbl/<version_num>/examples/BusinessWorks/Customer folder. For example a key value for the following parameter can be entered:

CustomerName

This fetches the customer details from Siebel based on the details as given in the XML file. After the customer details are fetched from Siebel, the Get_Customer_Reply.xml file is written to the locationC:/Output folder.

• To trigger Update_Customer, you must enter the data in the Update_Customer_Request.xml file located in the <install-path>/tibco/adapter/adsbl/<version_num>/examples/BusinessWorks/Customer folder. For example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<CustomerInformation>

<Customer>

<CustomerName>TIBCO Software</CustomerName>

<CustomerLocation>Palo Alto</CustomerLocation>

<CustomerPhoneNumber>123456789</CustomerPhoneNumber>

<CustomerHomePage>www.tibco.com</CustomerHomePage>

</Customer>

</CustomerInformation>

This updates a customer record in Siebel.

• To trigger Sync_Customer, complete the following steps:

1. Make sure that the custom Business Service EAI TIBCO HTTP Agent is imported into Siebel Server. For information on how to import the custom Business Service, refer to TIBCO Adapter for Siebel User’s Guide.

2. Start the Siebel Client.

3. Go to the Business Service Simulator Screen using View> SiteMap> Business Service Administration>Business Service Simulator.

In Siebel 6.2.x or higher, use Screens>Business Service Simulator.

4. On the Service Methods applet, click Load From File... to import a sample invocation file, 7HTTPAgentSimulateMethodInvokeSend.xml, provided in the folder <Adapter Home>/examples/Service for the service method Send. The Load XML File window displays.



In Siebel 6.2.x or higher load the file, HTTPAgentSimulateMethodInvokeSend.txt

5. In the Input Property Set applet, click Load from File... to load the sample property set file InvokeSync_Customer.xml from the folder <Adapter Home>/examples/Customer.

6. Change the parameter, AgentHTTPServer, to the name of the machine on which the adapter is running. For eg: <myMachine>:<myPort>

7. Click Run in the Service Methods applet.

8. Check the Output Property Set applet for the result.

9. Verify the file Sync_Customer.xml created by the TIBCO BusinessWorks process, Sync_Customer.


Expected Results | 17

Expected Results

The example results can be viewed in the respective XML files written to:

C:/Output

• Get_Customer data is fetched based on the CustomerName parameter specified in the Get_Customer_Request.xml file and is written into the Get_Customer_Reply.xml file. The Get_Customer_Reply.xml file will be similar to the XML file shown below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><CustomerInformation> <Customer> <CustomerName>Atest</CustomerName> </Customer> </CustomerInformation>

• Update_Customer data is updated in Siebel based on the CustomerName parameter specified in the Update_Customer_Request.xml file.

• Sync_Customer output is stored in the Sync_Customer.xml file.


| 19

Chapter 3 TIBCO BusinessWorks: Working with the SalesOrder Business Object

This chapter demonstrates the Get, Update and Sync operations on a SalesOrder Business Object, using TIBCO BusinessWorks.

Topics


• Set up the SalesOrder Example, page 21

• Test the SalesOrder Example, page 23



20 | Chapter 3 TIBCO BusinessWorks: Working with the SalesOrder Business Object

Example Description

This example demonstrates three different operations on a SalesOrder Business Object.

• Get_SalesOrder fetches SalesOrder details from Siebel and writes them in an XML file. The SalesOrder Number is read from an XML file containing query details.

• Update_SalesOrder updates the SalesOrder details in Siebel. The details to update a record are read from an XML file.

• Sync_SalesOrder publishes a message out of Siebel whenever SalesOrder details are modified or updated in the Siebel application. TIBCO BusinessWorks receives details of the SalesOrder, and logs it in an XML file. Sync_SalesOrder uses HTTPS to communicate between Siebel and the adapter.


Set up the SalesOrder Example | 21

Set up the SalesOrder Example


Task A> Get_SalesOrder, Sync_SalesOrder, and Update_SalesOrder Setup

In TIBCO Designer:



3. Click the Zip Archive tab and browse to locate the SalesOrder.zip file. The file is located in the <install-path>/tibco/adapter/adsbl/<version_num>2/examples/BusinessWorks/SalesOrder folder.

4. Select the adapter instance SalesOrder_JMS.

5. Click the Run-time Connection tab in the configuration panel. Provide appropriate values for the following global variables:

tibco.clientVar.SiebelEnterpriseServer <siebel>

tibco.clientVar.SiebelHost <blrkec09624>

tibco.clientVar.SiebelServer <blrkec09624>

tibco.clientVar.SiebelObjectManager < SCCObjMgr_enu>

tibco.clientVar.SiebelLoginPassword <sadmin>

tibco.clientVar.SiebelLoginName <sadmin>

Or you can specify these values in the examples.tra. In this case the values given in project file will be overridden.

6. Click the Adapter Services tab in the Configuration panel. Provide appropriate values for the following fields:

Select Use SSL

HTTPS Port to Listen to Siebel Events: <siebel_HTTPS_Port>

HTTPS Encoding: UTF8

Certificate Path: <Certificate_path_of_Keystore>

When you start your client, if you have generated the Certificate Path using the Keytool utility, you can install the Certificate on the client by accessing https://<host_name>:<HTTPS_Port_Number>.



Key Password: < Key_Password>

Keystore Password: < KeyStore_Password>

7. Save as a multi-file project named SalesOrder.


Task B>Start the EMS Server

This example uses JMS as the transport type. Ensure that the TIBCO EMS Server is running and accessible to the machine on which the adapter is installed before running any of the processes.

Task C>Run the Adapter

1. Convert the multi-file format file to a dat file.

2. Modify the repourl and configurl parameters in examples.tra to point to the dat file. (For eg: /tibco/private/adapter/SalesOrder_JMS).

3. Run the adapter from the command line:adsbl --propFile <adapter_home>/examples/examples.tra

A Certificate can be generated using the Keytool utility. Following command is used to create a certificate:keytool -genkey -keystore <KeyStore_Name> -keyalg rsa -alias <Alias_Name> -storepass <KeyStore_Password> -keypass <Key_Password>

Where:

KeyStore_Name: The name of the keystore where the Certificate will be generated.

Alias_Name: The alias name given to a public/private key pair in the Keystore.

KeyStore_Password: The password to access the Keystore.

Key_Password: The password to access the alias.

While generating a Certificate, ensure that the first name and the last name should be the IP address of the machine on which the Siebel adapter is running.



Test the SalesOrder Example | 23

Test the SalesOrder Example

In TIBCO Designer:

1. From the project panel, select the process you want to test. For example, Get_SalesOrder.

2. Click the Set Breakpoints icon in the TIBCO Designer toolbar.

3. In the window that appears, choose Select All, then click OK.

4. Click the Tester tab to the left of the project panel.

5. Click the File Poller icon. In the configuration panel, click the Browse button against the File Name field and select the input XML file. Click Apply. Any change to the input XML file starts the process.

6. Click the Start testing viewed process button.

7. In the process selection window that appears, the Get_SalesOrder process is selected by default. Click Start Selected. The process is now in Test mode.

8. Once the process starter is highlighted (indicating a process has started), click the Step to next activity icon to step through the process.

9. Step through the process once more.

10. Click the Stop Testing icon to return to design mode.

The above steps describe the testing for the Get_SalesOrder process. Follow the steps to run the Update_SalesOrder. To trigger Sync_SalesOrder, complete the following steps:



3. Go to the Business Service Simulator Screen using View> SiteMap> Business Service Administration>Business Service Simulator.


4. On the Service Methods applet, click Load From File... to import a sample invocation file, 7HTTPAgentSimulateMethodInvokeSend.xml, provided in the folder <Adapter Home>/examples/Service for the service method Send. The Load XML File window displays.



In Siebel 6.2.x or higher systems, load the file, HTTPAgentSimulateMethodInvokeSend.txt

5. In the Input Property Set applet, click Load from File... to load the sample property set file invoke Sync_SalesOrder.xml from the folder <Adapter Home>/examples/BusinessWorks/SalesOrder.

Change the parameter, AgentHTTPSServer, to the name of the machine on which the adapter is running. For example, <myMachine>:<HTTPS_Port_Number>. Change the parameter, IsSecureConn to ’Y’.



Verify the file Sync_SalesOrder.xml created by the TIBCO BusinessWorks process, Sync_SalesOrder. The Sync_SalesOrder does not have an input XML file. Any change to the data in Siebel invokes the Sync_SalesOrder process.

Ensure that the value entered in the <myMachine> field is the same as that entered while generating the certificate. For example, if you have entered the IP address of the machine as your First Name and Last Name while generating the certificate, enter the same in <myMachine> field.


Expected Results | 25

Expected Results


C:/Output

• Get_SalesOrder data is fetched based on the OrderNumber parameter specified in the Get_SalesOrder_Request.xml file and is written into the Get_SalesOrder_Reply.xml file. The Get_SalesOrder_Reply.xml file will be similar to the XML file shown below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><OrderInformation> <Order> <Id>1-A9V</Id> <OrderNumber>tr98790</OrderNumber> <OrderType>Sales Order</OrderType> <Account>3Com</Account> <Location>NNN</Location> <ContactFirstName></ContactFirstName> <ContactLastName></ContactLastName> </Order> </OrderInformation>

• Update_SalesOrder data is updated in Siebel based on the OrderNumber parameter specified in the Update_SalesOrder_Request.xml file.

• Sync_SalesOrder output is stored in the Sync_SalesOrder.xml file.


| 27

Chapter 4 TIBCO BusinessWorks: Working with the PurchaseOrder Business Object

This chapter demonstrates the Get, Update and Sync operations on a Purchaseorder Business Object, using TIBCO BusinessWorks.

Topics


• Set up the PurchaseOrder Example, page 29

• Test the PurchaseOrder Example, page 31



28 | Chapter 4 TIBCO BusinessWorks: Working with the PurchaseOrder Business Object

Example Description

This example demonstrates three different operations on a PurchaseOrder Business Object.

• Get_PurchaseOrder fetches PurchaseOrder details from Siebel and writes them back in an XML file. The PurchaseOrder Number is read from an XML file containing query details.

• Update_PurchaseOrder updates details in Siebel. The details to update a record are read from an XML file.

• Sync_PurchaseOrder publishes a message, out of Siebel whenever PurchaseOrder details are modified or updated in the target Siebel application, TIBCO BusinessWorks receives details of this PurchaseOrder, and logs it in an XML file.


Set up the PurchaseOrder Example | 29

Set up the PurchaseOrder Example


Task A>Get_PurchaseOrder, Sync_PurchaseOrder, and Update_PurchaseOrder Setup

In TIBCO Designer:



3. Click the Zip Archive tab and browse to locate the PurchaseOrder.zip file. The file is located in the <install-path>/tibco/adapter/adsbl/<version_num>/examples/BusinessWorks/PurchaseOrder folder.

4. Select the adapter instance PurchaseOrder_JMS.

5. Click the Run-time Connection tab. Provide appropriate values for the following global variables:







Or you can specify these values in the examples.tra. In this case the values given in project file are overridden.

6. Save as a multi-file project named PurchaseOrder.





Task B>Start the EMS Server

This example uses JMS as the transport type. Ensure that the TIBCO EMS Server is running and accessible to the machine on which the adapter is installed before running any of the processes.

Task C>Run the Adapter


2. Modify the repourl and configurl parameters in examples.tra to point to the dat file. (For eg: /tibco/private/adapter/PurchaseOrder_JMS).



Test the PurchaseOrder Example | 31

Test the PurchaseOrder Example

In TIBCO Designer:

1. From the project panel, select the process you want to test. For example, Get_PurchaseOrder.

2. Click the Set Breakpoints icon.





7. In the process selection window that appears, the Get_PurchaseOrder process is selected by default. Click Start Selected. The process is now in Test mode.




The above steps describe the testing for the Get_PurchaseOrder process. Follow the steps to run the Update_PurchaseOrder and Sync_PurchasesOrder processes. The Sync_PurchaseOrder does not have an input XML file. Any change to the data in Siebel invokes the Sync_PurchaseOrder process.



Expected Results


C:/Output

• Get_PurchaseOrder data is fetched based on the OrderNumber parameter specified in the Get_PurchaseOrder_Request.xml file and is written into the Get_PurchaseOrder_reply.xml file. The Get_PurchaseOrder_reply.xml file will be similar to the XML file shown below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><OrderInformation> <Order> <Id>1-A9V</Id> <OrderNumber>tr98790</OrderNumber> <OrderType>Purchase Order</OrderType> <Account>3Com</Account> <Location>NNN</Location> <ContactFirstName></ContactFirstName> <ContactLastName></ContactLastName> </Order> </OrderInformation>

• Update_PurchaseOrder data is updated in Siebel based on the OrderNumber parameter specified in the Update_PurchaseOrder_Request.xml file.

• Sync_PurchaseOrder output is stored in the Sync_PurchaseOrder.xml file.


| 33

Chapter 5 TIBCO BusinessWorks: Working with the Employee Business Object

This chapter demonstrates the Get, Update and Sync operations on a Employee Business Object, using TIBCO BusinessWorks.

Topics


• Set up the Employee Example, page 35

• Test the Employee Example, page 37



34 | Chapter 5 TIBCO BusinessWorks: Working with the Employee Business Object

Example Description

This example demonstrates three different operations on a Employee Business Object.

1. Get_Employee fetches Employee details from Siebel and writes them back in an XML file. The Employee Login Name is read from an XML file containing query details.

2. Update_Employee updates Employee details in Siebel. The details to update a record are read from an XML file.

3. Sync_Employee publishes a message out of Siebel whenever Employee details are modified or updated in the target Siebel application. TIBCO BusinessWorks receives details of this Employee, and logs it in an XML file. To simulate this example we use Siebel's Business Service Simulator to send a publication request to the adapter.


Set up the Employee Example | 35

Set up the Employee Example


Task A> Get_Employee, Update_Employee, and Sync_Employee Setup

In TIBCO Designer:



3. Click the Zip Archive tab and browse to locate the Employee.zip file. The file is located in the <install-path>/tibco/adapter/adsbl/<version_num>/examples/BusinessWorks/Employee folder.

4. Select the adapter instance Employee_RV.









6. Save as a multi-file project named Employee.

7. Click Apply.


Task B> Run the Adapter





2. Modify the repourl and configurl parameters in examples.tra to point to the dat file. (For eg: /tibco/private/adapter/Employee_RV).



Test the Employee Example | 37

Test the Employee Example

In TIBCO Designer:

1. From the project panel, select the process you want to test. For example, Get_Employee.






7. In the process selection window that appears, the Get_Employee process is selected by default. Click Start Selected. The process is now in Test mode.




11. The above steps describe the testing for the Get_Employee process. Follow the steps to run the Update_Employee and Sync_Employee processes. The Sync_Employee does not have an input XML file. Any change to the data in Siebel invokes the Sync_Employee process.



Expected Results


C:/Output

• Get_Employee data is fetched based on the EmployeeNumber parameter specified in the Get_Employee_Request.xml file and is written into the Get_Employee_Reply.xml file. The Get_Employee_Reply.xml file will be similar to the XML file shown below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><OrderInformation> <Order> <Id>1-A9V</Id> <EmployeeNumber>tr98790</EmployeeNumber> <OrderType>Employee</OrderType> <Account>3Com</Account> <Location>NNN</Location> <ContactFirstName></ContactFirstName> <ContactLastName></ContactLastName> </Order> </OrderInformation>

• Update_Employee data is updated in Siebel based on the EmployeeNumber parameter specified in the Update_Employee_Request.xml file.

• Sync_Employee output is stored in the Sync_Employee.xml file.


| 39

Chapter 6 TIBCO BusinessWorks: Working with the Material Business Object

This chapter demonstrates the Get, Update and Sync operations on a Material Business Object, using TIBCO BusinessWorks.

Topics


• Set up the Material Example, page 41

• Test the Material Example, page 43



40 | Chapter 6 TIBCO BusinessWorks: Working with the Material Business Object

Example Description

This example demonstrates three different operations on a Material Business Object.

1. Get_Material fetches Material details from Siebel and writes them back in an XML file. The Material Name is read from an XML file containing query details.

2. Update_Material updates the Material details in Siebel. The details to update a record are read from an XML file.

3. Sync_Material publishes a message out of Siebel whenever Material details are modified or updated in the target Siebel application, TIBCO BusinessWorks receives details of this Material, and logs it in an XML file.


Set up the Material Example | 41

Set up the Material Example


Task A> Get_Material, Update_Material, and Sync_Material Setup

In TIBCO Designer:



3. Click the Zip Archive tab and browse to locate the Material.zip file. The file is located in the <install-path>/tibco/adapter/adsbl/<version_num>/examples/BusinessWorks/Material folder.

4. Select the adapter instance Material_RV.









6. Save as a multi-file project named Material.


Task B> Run the Adapter


2. Modify the repourl and configurl parameters in examples.tra to point to the dat file. (For eg: /tibco/private/adapter/Material_RV).



Test the Material Example | 43

Test the Material Example

In TIBCO Designer:

1. From the project panel, select the process you want to test. For example, Get_Material.






7. In the process selection window that appears, the Get_Material process is selected by default. Click Start Selected. The process is now in Test mode.




The above steps describe the testing for the Get_Material process. Follow the steps to run the Update_Material and Sync_Material processes. The Sync_Material does not have an input XML file. Any change to the data in Siebel invokes the Sync_Material process.



Expected Results


C:/Output

• Get_Material data is fetched based on the MaterialNumber parameter specified in the Get_Material_Request.xml file and is written into the Get_Material_Reply.xml file. The Get_Material_Reply.xml file will be similar to the XML file shown below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><OrderInformation> <Order> <Id>1-A9V</Id> <MaterialNumber>tr98790</MaterialNumber> <OrderType>Material</OrderType> <Account>3Com</Account> <Location>NNN</Location> <ContactFirstName></ContactFirstName> <ContactLastName></ContactLastName> </Order> </OrderInformation>

• Update_Material data is updated in Siebel based on the MaterialNumber parameters specified in the Update_Material_Request.xml file.

• Sync_Material output is stored in the Sync_Material.xml file.


| 45

Chapter 7 Invoking a Business Service

This example demonstrates how to invoke a business service using the Request-Response service.

Topics


• Set up the Example, page 47

• Deploy and Run the Example, page 48



46 | Chapter 7 Invoking a Business Service

Example Description

This example describes how to invoke the Query method of the EAI Siebel Adapter Business service.

The Invoke_BS_Process polls the file, Invoke_BS.xml in <Adapter_Home>\examples\BusinessWorks\BusinessService folder, and when the file is modified, Invoke_BS_Process reads the data from the XML file and invokes the adapter. The adapter’s Request-Response service invokes the Business Service and the reply is sent back to TIBCO BusinessWorks. TIBCO BusinessWorks writes the reply to another XML file.


Set up the Example | 47

Set up the Example


Task A Set up RPCServer_BS

In TIBCO Designer:



3. Click the Zip Archive tab and browse to locate the BusinessService.zip file. The file is located in the <install-path>/tibco/adapter/adsbl/<version_num>/examples/BusinessWorks/BusinessService folder.

4. Select the adapter instance SiebelAdapter_BS.









6. Save as a multi-file project named BusinessService.

7. Drag and drop the Enterprise Archive in the project panel.

8. Drag and drop an Adapter Archive into the Enterprise Archive.

9. Associate the SiebelAdapter_BS adapter configuration with the adapter archive.

10. Select the Enterprise Archive in the project panel.

11. Click Build Archive in the Configuration tab. This creates an archive file.




Deploy and Run the Example

Perform the following tasks to deploy and run the example.

Task A Deploy the Example

In TIBCO Administrator:

1. Go to Resource Management >Machine, and select the machine on which you wish to deploy the adapter.

2. Login to TIBCO Administrator. Click on the Installed Software link on the left panel. Check if TIBCO Adapter for Siebel 5.3.0 is registered. If the software is not registered, register by selecting the Add Custom Software button. Please refer to the TIBCO Administrator documentation for more details on adding custom software.

3. Go to Application Management. Click New Application. Upload the EAR file and click OK (Refer Chapter 7 Deploying and Starting an Adapter Using TIBCO Administrator in TIBCO Adapter for Siebel User’s Guide). On the following screen, clear the Quick Configure check box and then click Save.

4. Click Configuration in the newly created application. Click on the top level application name in the configuration view.

a. Go to the Advanced tab and provide the values for App Name, User Name, Password.

b. Provide appropriate values for the following global variables:— SiebelEnterpriseServer

— SiebelHost

— SiebelServer

— SiebelObjectManager

— SiebelLoginPassword

— SiebelLoginName

c. Click Save. The configuration screen appears.

d. Click the adapter archive and click Add To Additional Machines.

e. Select the machine and click OK. In the following screen, click Save. In the configuration screen click Deploy. Click OK. The .tra files are created in <Adapter_Home>/bin/domain/<DomainName>.

5. Once the deployment is complete, click New Application under the application. The adapter is listed. Select the adapter and click Start Selected.


Deploy and Run the Example | 49

Both the customer creation and customer fetch processes are started. The adapter instance is also started.

Task B Run the Example

To run the example:

To trigger Invoke_BS_Process, you must enter the key values in the Invoke_BS.xml file located in the <install-path>/tibco/adapter/adsbl/<version_num>/examples/BusinessWorks/BusinessService folder. For example a key value for the following parameter can be entered:

CustomerInformation

This fetches the customer details from Siebel based on the details as given in the XML file. After the customer details are fetched from Siebel, the BusinessService_Reply.xml file is written to the location c:/Output/BusinessService_Reply.xml.



Expected Results


c:/Output/BusinessService_Reply.xml

• Invoke_BS_Process data is fetched based on the CustomerInformation parameter specified in the Invoke_BS.xml file and is written to the BusinessService_Reply.xml file. The BusinessService_Reply.xml file will be similar to the XML file shown below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><CustomerInformation> <Customer> <Name>1Test</Name> </Customer></CustomerInformation>


. | 51

.Chapter 8 TIBCO IntegrationManager: Working with

the Customer Business Object

This chapter demonstrates the Get, Update and Sync operations on a Customer Business Object, using TIBCO IntegrationManager.

Topics


• Configure the Customer Business Object, page 53

• Configure the Get_Customer Process in TIBCO IntegrationManager, page 61

• Configure the Update_Customer Process Using TIBCO IntegrationManager, page 69

• Configure the Sync_Customer Process Using TIBCO IntegrationManager, page 70

• Setting .tra File Parameters, page 71

• Start the Adapter, page 72

• Test the Process, page 73

• Monitor the Customer Example, page 75

• Stop the Customer Example, page 76


52 | Chapter 8 TIBCO IntegrationManager: Working with the Customer Business Object

Overview

This example demonstrates three different operations on a Customer Business Object.

1. Get_Customer fetches Customer details from Siebel and writes them back in an XML file. The Customer Name is read from an XML file containing query details.

2. Update_Customer updates the Customer details in Siebel. The details to update a record are read from an XML file.

3. Sync_Customer publishes a message out of Siebel whenever Customer details are modified or updated in the target Siebel application, TIBCO IntegrationManager receives details of this Customer, and logs it in an XML file.

Integration Scenario Between the Adapter and TIBCO IntegrationManager An end-to end integration scenario between the adapter and TIBCO IntegrationManager involves the following steps. The steps are detailed for one example (Customer Business Object):

1. Create an adapter instance using TIBCO Designer and configure the Business Object.

2. Configure the processes using TIBCO IntegrationManager.

3. Deploy the example.

4. Start the example.

5. Monitor the example using TIBCO Hawk.

6. Stop the example.


Configure the Customer Business Object | 53

Configure the Customer Business Object

The Customer.dat file has been provided with a Customer Instance, which contains an adapter instance Customer_JMS configured with four adapter services:

— Sync_Customer

— Update_Customer

— Get_Customer

— Delete_Customer

The transport type for all the services is JMS with the connection factory type set as TOPIC.

Though the Customer.dat is pre-configured with the above services, here is a brief of how you can arrive at this configuration:

Task A Configure an Adapter Instance1. Open TIBCO Designer.

2. Drag and drop Siebel Adapter Configuration icon from the palette panel to the design panel.

To use the dat file and make configuration changes, you have to convert it to a multi-file format first. See Working with dat Files on page 6 for details.



3. In the Configuration tab rename the instance to Customer_JMS and click Apply.



Task B Configure Design-time Connection Settings1. Enter the connection parameters.

a. Specify a valid User Name and Password.

b. Specify the Host, Enterprise Server, Siebel Server and the ObjectManager.

c. Leave other fields unchanged.

2. Click Apply. A pop-up window is displayed if the connection is successful.

3. Click OK.



Task C Configure an Adapter Service1. Click Customer_JMS>Adapter Services, you can now see all the services in

the left bottom panel.

2. Drag and drop the adapter service you want (In this example, RequestResponseService).

3. Select the Transport Type as JMS.

4. Leave the Wire Format and Quality of Service fields with default values.



5. Select the RequestResponse Server Type. For this example, select Query Siebel Business Components.

6. Click Apply

7. Navigate to Customer_JMS>Get_Customer>PrimaryBusinessComponent

8. In the Configuration tab, click the Fetch button against the Business Object to get the list of Business Objects available in Siebel.

9. Select the Account Business Object, Account.



10. Click Fetch to get the list of the Business Components available under the Business Object, Account.

11. Select Account.

12. Click Apply



13. Select the required fields to make the schema from the list of the fields available for the Business Component. Click Apply.

14. Add the Child Business Component.

15. Select required fields.



16. Provide a Match Field for the Child Business Component and select it as Key.

17. Save the configuration as a multi file project. You have now successfully created a Request-Response service configuration.

18. Using the steps described above, the publication, subscription and Request-Response invocation services can be configured.

19. Select Project>Save As>Multi File Project to save the project to a folder of your choice.

20. Close the project. Go to the Administration tab of TIBCO Designer, select Convert files to DAT.

21. Choose the multi file project you just created and convert it into a .dat file.

Use this dat file to define the processes in TIBCO IntegrationManager.


Configure the Get_Customer Process in TIBCO IntegrationManager | 61

Configure the Get_Customer Process in TIBCO IntegrationManager

Get_Customer fetches customer details from the Siebel application and writes in an XML file. The Customer Name is read from an XML file where query details can be specified. The screen shot of the process is given next.

Before you start creating the Get_Customer process, you need to do the following:

1. Open the Customer.dat file in TIBCO IntegrationManager with the adapter services configured as described in the previous section. See , Task C Configure an Adapter Service, on page 56 for details.



2. Click Create New Process Diagram and name this process Get_Customer.

3. The following tasks need to be completed before creating the process.

a. Task A Create a Channel for JMS

b. Task B Create Schemas

c. Task C Read, Map and Invoke the Task

d. Task D Analyze the Response

Task A Create a Channel for JMS1. First you need to create a Channel for JMS, which triggers the process

whenever the XML file (the file from which the parameters are read to fetch Customer details) is created or modified.

2. Create a JMS Shared Parameter Object.

3. Set Topic as the connection type. The screen is given next.



4. Create a Channel for the file named getCustomer_ReadRequest

5. Use the following settings to periodically poll the XML file. Note that the transport type for this channel is FILE.

Task B Create SchemasCreate the schema, GetCustomer_Request under the Schema Files.

Ensure that the XML file is present in the specified location.

Here GetCustomer_Request file is the dtd file for the input XML that you mentioned in the FileName column in the above picture.



Task C Read, Map and Invoke the Task1. In the TIBCO IntegrationManager process, drag and drop an XML parser task

from the Tools panel to the design panel, name it as Parser and use the settings in the screen shot shown below. This class parses the XML contents that have been read from the XML file and included in the FileInput slot. The parser uses the schema defined in the previous section and the output is dumped into a slot named requestData. The screen is shown next.



2. Map this XML to the format in which we can call the Siebel target application. Drag a Mapper Task. Map the XML to the AE format of the task. The screen is shown next.

3. Drag the Invoke Task and name it as Invoke. This task invokes the adapter to fetch the customer details. Note, that the task has to be associated with jobs, to get the response in the respective slots.

4. Specify the Input and Output schemas for the task.



Task D Analyze the ResponseAt this point you can check whether the response contains an error. This can be done by using a script task that looks at the returned content. The script decides whether a successful record has been fetched or an error has occurred. Refer to the script task in the TIBCO IntegrationManager process.

1. For the successful fetch of customer details we branch out to the Success trigger else we branch out to the Error trigger.

2. From the success branch drag and drop a mapper task to the TIBCO IntegrationManager process.

3. In the mapper select the Request-Response reply schema as the input schema and specify the slot name as adapterReplyData.

4. In the mapper select the schema GetCustomer_Request as output schema, which has been created in Task B Create Schemas.

5. Specify the output slot name as replyData.



6. Drag and drop the File Writer instance to the TIBCO IntegrationManager process.

7. Configure the File Writer as shown above. This File Writer writes the Get_Customer_Reply.xml file into the location mentioned in the destination column.

8. If there has been an error we branch out to the Error trigger. Log the error message in Get_Customer_Reply.xml at C:\temp\Get_Customer_Reply.xml. Please refer to the Error task in the TIBCO IntegrationManager process.


Configure the Update_Customer Process Using TIBCO IntegrationManager | 69

Configure the Update_Customer Process Using TIBCO

IntegrationManager

Update_Customer updates records in the Siebel application. The details to update a record are read from an XML file.

The procedure to create the Update_Customer TIBCO IntegrationManager process is similar to that of creating the Get_Customer process. See Configure the Get_Customer Process in TIBCO IntegrationManager on page 61 for details. The screenshot of the process is given next.



Configure the Sync_Customer Process Using TIBCO

IntegrationManager

Sync_Customer publishes a message, out of Siebel whenever a new customer is created. TIBCO IntegrationManager receives details of this customer andwrites in an XML file.

The procedure to create the Sync_Customer TIBCO IntegrationManager process is similar to that of creating the Get_Customer process. See Configure the Get_Customer Process in TIBCO IntegrationManager on page 61 for details. The screenshot of the process is given next.


Setting .tra File Parameters | 71

Setting .tra File Parameters

1. Edit the Examples.tra provided in the folder, <Adapter Home>/examples and set the following parameters:

repourl as <Adapter Home>/examples/Customer/Customer.dat

configurl as Customer_JMS

2. Also, set the following Siebel Connection parameters according to your Siebel installation:

SiebelEnterpriseServer

SiebelHost

SiebelServer

SiebelObjectManager

SiebelLoginName

SiebelLoginPassword

Make sure that the file paths specified in the channel getCustomer_ReadRequest, Update_Customer_ReadRequest and the File Writer task File Writer match your configuration.



Start the Adapter

1. Start the JMS Service by running the tibjmsd.exe file from your ..\JMS\bin directory.

2. Start the command prompt and go to <Adapter Home>\bin. Run the command, adsbl --propFile <Adapter Home>\examples\examples.tra.

3. Start the TIBCO IntegrationManager engine. You can do this from the command line or open the Customer.dat file using TIBCO IntegrationManager and start the debug process. For more details, refer to the TIBCO IntegrationManager Administration Guide.


Test the Process | 73

Test the Process

Get_Customer

To query the customer information from Siebel, copy the Get_Customer_Request.xml file provided in the folder <Adapter Home>\examples\Customer to the directory C:\temp or modify the TIBCO IntegrationManager Transform to make the channel, getCustomer_ReadRequest to point to the correct location of the file mentioned. Restart the TIBCO IntegrationManager Engine. The process sends a request to the adapter and the reply sent by the adapter is saved to the local machine at the location C:\temp\Get_Customer_Reply.xml.

Update_Customer

To update the customer information in Siebel using the Request-Response service, copy the Update_Customer_Request.xml file provided in the folder <Adapter Home>\examples\Customer to the directory C:\temp or modify the TIBCO IntegrationManager Transform to make the channel, Update_Customer_ReadRequest, point to the correct location of the file mentioned. Restart the TIBCO IntegrationManager Engine. The process reads from the file and sends a request to the adapter. Check the adapter console to see if the update is successful and verify with the Siebel database if the data has been updated.

Sync_Customer

Use the following steps to publish data from Siebel to an external application:



3. Navigate to the Business Service Simulator Screen using View> SiteMap> Business Service Administration>Business Service Simulator.


4. On the Service Methods applet, click Load From File... to import a sample invocation file, 7HTTPAgentSimulateMethodInvokeSend.xml, provided in

Make sure that the record in the XML file matches with one in the database.



the folder <Adapter Home>/examples/Service for the service method Send. The Load XML File window displays.


5. In the Input Property Set applet, click Load from File... to load the sample property set file InvokeSync_Customer.xml from the folder <Adapter Home>/examples/Customer.




9. Verify the file C:\temp\Sync_Customer.xml created by the TIBCO IntegrationManager process Sync_customer.


Monitor the Customer Example | 75

Monitor the Customer Example

1. You can monitor JMS Services by using the provided tibjmsmonitor.exe with the JMS Installation. For more details, refer to the TIBCO Enterprise Message Service documentation.

2. TIBCO Adapter for Siebel can be monitored using TIBCO Hawk. For more details refer to TIBCO Hawk documentation.

3. You can monitor and manage TIBCO IntegrationManager engines and jobs using the engine or job monitor (immon). For details on how to start this tool, see details on immon in TIBCO IntegrationManager Reference. The TIBCO IntegrationManager engine can also be monitored and managed using TIBCO Hawk software. For details on how to install and run TIBCO Hawk software, see your TIBCO Hawk documentation.

4. You can check the results of a successful fetch of a Customer in Get_Customer_Reply.xml file from the location C:\temp\Get_Customer_Reply.xml.

5. The updated results for the Update_Customer service are displayed in the adapter window.

6. The results for the Sync_Customer service are put in the Sync_Customer.xml file from the location C:\temp\Sync_Customer.xml.

7. Errors if any, are put in the TIBCO IntegrationManager console.



Stop the Customer Example

1. You can stop TIBCO IntegrationManager using the following command: imadmin -e my-nb Shutdown -mode safe.

2. Broadcast a stop message using the tibrvsend command-line tool available from TIBCO_HOME\TIBRV\bin. The Terminate Subject to stop an adapter can be configured during the design stage. This subject can be set in the General tab of the adapter instance. See TIBCO Adapter For Siebel User’s Guide for more information.

3. If you have TIBCO Hawk installed on your machine, you can stop the adapter using the StopAdapterInstance method of the TIBCO Hawk microagent.


| 77

Chapter 9 TIBCO IntegrationManager: Working with the SalesOrder Business Object

This chapter demonstrates the Get, Update and Sync operations on a SalesOrder Business Object, using TIBCO IntegrationManager.

Topics


• Configure the SalesOrder Business Object, page 79




• Monitor the SalesOrder Example, page 87

• Stop the SalesOrder Example, page 88


78 | Chapter 9 TIBCO IntegrationManager: Working with the SalesOrder Business Object

Overview

This example demonstrates three different operations on a SalesOrder Business Object.

1. Get_SalesOrder fetches SalesOrder details from Siebel and writes them back in an XML file. The SalesOrder Number is read from an XML file containing query details.

2. Update_SalesOrder updates details in Siebel. The details to update a record are read from an XML file. When a publication event (Sync_SalesOrder) is executed, the Update_SalesOrder reads the data written to the XML file by the TIBCO IntegrationManager process. TIBCO IntegrationManager modifies the data using a mapper task to send an update request to the adapter.

3. Sync_SalesOrder publishes a message out of Siebel whenever SalesOrder details are modified or updated in the target Siebel application, TIBCO IntegrationManager receives details of this SalesOrder, and logs it in an XML file.


Configure the SalesOrder Business Object | 79

Configure the SalesOrder Business Object

The SalesOrder.dat file has been provided with a SalesOrder Instance, which has four adapter services.

— Get_SalesOrder

— Update_SalesOrder

— Sync_SalesOrder

— Delete_SalesOrder


The steps to arrive at the configuration for the SalesOrder.dat are similar to that of Customer.dat. See Integration Scenario Between the Adapter and TIBCO IntegrationManager on page 52 for details.

The SalesOrder.dat file has the following processes configured using TIBCO IntegrationManager. The processes are:• Get_SalesOrder

• Update_SalesOrder

• Sync_SalesOrder

For the procedure to configure a process using TIBCO IntegrationManager, see , Configure the Get_Customer Process in TIBCO IntegrationManager, on page 61. Use this procedure to configure the three processes listed above. The screenshots of the processes are given next.




Get_SalesOrder


Configure the SalesOrder Business Object | 81

Update_SalesOrder



Sync_SalesOrder





repourl as <Adapter Home>/examples/SalesOrder/SalesOrder.dat

configurl as SalesOrder_JMS



SiebelHost

SiebelServer

SiebelObjectManager

SiebelLoginName

SiebelLoginPassword

Make sure that the file paths specified in the channel getSalesOrder_ReadRequest, Update_SalesOrder_ReadRequest and the File Writer task File Writer match your configuration.



Start the Adapter

1. Start the JMS Service by running the tibjmsd.exe file from your ../JMS/bin directory.


3. Start the TIBCO IntegrationManager engine. You can do this from the command line or open the SalesOrder.dat file using TIBCO IntegrationManager and start the debug process. For more details refer to TIBCO IntegrationManager Administration Guide.



Test the Process

Get_SalesOrder

To query the SalesOrder information from Siebel, copy the Get_SalesOrder_Request.xml file provided in the folder <Adapter Home>/examples/SalesOrder to the directory C:\temp or modify the TIBCO IntegrationManager Transform to make the channel, getSalesOrder_ReadRequest to point to the correct location of the file mentioned. Restart the TIBCO IntegrationManager Engine. The process sends a request to the adapter and the reply sent by the adapter is saved to the local machine at the location C:/temp/Get_SalesOrder_Reply.xml.

Update_SalesOrder

When the Sync operation (Sync_SalesOrder) is executed, the TIBCO IntegrationManager process Sync_SalesOrder writes the data published by the adapter to a file on the local machine under location C:\temp\Sync_SalesOrder.xml. The TIBCO IntegrationManager Process Update_SalesOrder reads the data from the file, modifies the information using a mapper task and sends the update request to the adapter.

Check the adapter console, if the event execution is successful, and verify with Siebel database if the record has been updated successfully.

Sync_SalesOrder

Use the following steps to publish the data from Siebel to external application:



3. Navigate to Business Service Simulator Screen using View> SiteMap> Business Service Administration>Business Service Simulator


4. On the Service Methods applet, click Load From File... to import a sample invocation file 7HTTPAgentSimulateMethodInvokeSend.xml provided in folder <Adapter Home>/examples/Service for the service method Send.





5. In the Input Property Set applet, click Load from File... to load the sample property set file InvokeSync_SalesOrder.xml from the folder <Adapter Home>/examples/SalesOrder




9. Verify the file C:\temp\Sync_SalesOrder.xml created by the TIBCO IntegrationManager process Sync_SalesOrder.


Monitor the SalesOrder Example | 87

Monitor the SalesOrder Example




4. You can check the results of successful fetch of a SalesOrder in the Get_SalesOrder_Reply.xml file from the location C:\Temp\Get_SalesOrder_Reply.xml.

5. The updated results for the Update service are displayed in the adapter window.

6. The results for the Sync service are put in the Sync_SalesOrder.xml file from the location C:\Temp\Sync_SalesOrder.xml.




Stop the SalesOrder Example





| 89

Chapter 10 TIBCO IntegrationManager: Working with the PurchaseOrder Business Object

This chapter demonstrates the Get, Update and Sync operations on a PurchaseOrder Business Object, using TIBCO IntegrationManager.

Topics


• Configure the PurchaseOrder Business Object, page 91




• Monitor the PurchaseOrder Example, page 99

• Stop the PurchaseOrder Example, page 100


90 | Chapter 10 TIBCO IntegrationManager: Working with the PurchaseOrder Business Object

Overview

This example demonstrates the Get operation on a PurchaseOrder Business Object.

1. Get_PurchaseOrder fetches PurchaseOrder details from Siebel and writes them back in an XML file. The PurchaseOrder Number is read from an XML file containing query details.

2. Update_PurchaseOrder updates details in Siebel. The details to update a record are read from an XML file. When a publication event (Sync_PurchaseOrder) is executed, the Update_PurchaseOrder reads the data written to the XML file by the TIBCO IntegrationManager process. TIBCO IntegrationManager modifies the data using a mapper task to send an update request to the adapter.

3. Sync_PurchaseOrder publishes a message, out of Siebel whenever PurchaseOrder details are modified or updated in the target Siebel application, TIBCO IntegrationManager receives details of this PurchaseOrder, and logs it in an XML file.


Configure the PurchaseOrder Business Object | 91

Configure the PurchaseOrder Business Object

The PurchaseOrder.dat file has been provided with a PurchaseOrder Instance, which has the following adapter services:

— Get_PurchaseOrder

— Sync_PurchaseOrder

— Update_Order

— Delete_PurchaseOrder


The steps to arrive at the configuration for the PurchaseOrder.dat are similar to that of Customer.dat. See Integration Scenario Between the Adapter and TIBCO IntegrationManager on page 52 for details.

The PurchaseOrder.dat file has the following processes configured using TIBCO IntegrationManager. The processes are:• Get_PurchaseOrder

• Update_PurchaseOrder

• Sync_PurchaseOrder

For the procedure to configure a process using TIBCO IntegrationManager, see Configure the Get_Customer Process in TIBCO IntegrationManager on page 61. Use this procedure to configure the three processes listed above. The screenshots of the processes are given next.




Get_PurchaseOrder


Configure the PurchaseOrder Business Object | 93

Update_PurchaseOrder



Sync_PurchaseOrder





repourl as <Adapter Home>/examples/PurchaseOrder/PurchaseOrder.dat

configurl as PurchaseOrder_JMS



SiebelHost

SiebelServer

SiebelObjectManager

SiebelLoginName

SiebelLoginPassword

Make sure that the file paths specified in the channels in the TIBCO IntegrationManager getPurchaseOrder_ReadRequest, Update_PurchaseOrder_ReadRequest and the File Writer task File Writer match your configuration.



Start the Adapter



3. Start the TIBCO IntegrationManager engine. You can do this from the command line or open the PurchaseOrder.dat file using TIBCO IntegrationManager and start the debug process. For more details refer to the TIBCO IntegrationManager Administration Guide.



Test the Process

Get_PurchaseOrder

To query the PurchaseOrder information from Siebel, copy the Get_PurchaseOrder_Request.xml file provided in the folder <Adapter Home>/examples/PurchaseOrder to the directory C:\temp or modify the TIBCO IntegrationManager Transform to make the channel, getPurchaseOrder_ReadRequest point to the correct location of the file mentioned. Restart the TIBCO IntegrationManager Engine. The process sends a request to the adapter and the reply sent by the adapter is saved to the local machine at the location C:/temp/Get_PurchaseOrder_Reply.xml.

Update_PurchaseOrder

When the Sync operation (Sync_PurchaseOrder) is executed, the TIBCO IntegrationManager process Sync_PurchaseOrder writes the data published by the adapter to a file on the local machine in the location, C:\temp\Sync_PurchaseOrder.xml. Edit the XML file and replace the Account field with an existing field. The TIBCO IntegrationManager Process Update_PurchaseOrder reads the data from the file, modifies the information using a mapper task and sends the update request to the adapter.

Check the adapter console, if the event execution is successful, and verify with the Siebel database if the record has been updated successfully.

Sync_PurchaseOrder

Use the following steps to publish the data from Siebel to an external application:

1. Make sure that the custom Business Service EAI TIBCO HTTP Agent is imported in to the Siebel Server. For information on how to import the custom Business Service, refer to TIBCO Adapter for Siebel User’s Guide.


3. Navigate to the Business Service Simulator Screen using View> SiteMap> Business Service Administration>Business Service Simulator





4. On the Service Methods applet, click Load From File... to import a sample invocation file 7HTTPAgentSimulateMethodInvokeSend.xml provided in the folder, <Adapter Home>/examples/Service, for the service method Send.

In Siebel 6.2.x or higher load the file, HTTPAgentSimulateMethodInvokeSend.txt.

5. In the Input Property Set applet, click Load from File... to load the sample property set file InvokeSync_PurchaseOrder.xml from the folder <Adapter Home>/examples/PurchaseOrder.

6. Change the parameter, AgentHTTPServer, with the name of the machine on which the adapter is running. For eg: <myMachine>:<myPort>



9. Verify the file C:\temp\Sync_PurchaseOrder.xml created by the TIBCO IntegrationManager process Sync_PurchaseOrder.


Monitor the PurchaseOrder Example | 99

Monitor the PurchaseOrder Example

1. You can monitor JMS Services by using the provided tibjmsmonitor.exe with the JMS Installation. For more details, refer to TIBCO Enterprise Message Service documentation.



4. You can check the results of a successful fetch of a PurchaseOrder in the Get_PurchaseOrder_Reply.xml file from the location C:\Temp\Get_PurchaseOrder_Reply.xml.


6. The results for the Sync service are put in the Sync_PurchaseOrder.xml file from the location C:\Temp\Sync_PurchaseOrder.xml.




Stop the PurchaseOrder Example





| 101

Chapter 11 TIBCO IntegrationManager: Working with the Employee Business Object

This chapter demonstrates the Get, Update and Sync operations on a Employee Business Object, using TIBCO IntegrationManager.

Topics


• Configure the Employee Business Object, page 103




• Monitor the Employee Example, page 111

• Stop the Employee Example, page 112


102 | Chapter 11 TIBCO IntegrationManager: Working with the Employee Business Object

Overview

This example demonstrates the Get operation on a Employee Business Object.

1. Get_Employee fetches Employee details from Siebel and writes them back in an XML file. The Employee Login Name is read from an XML file containing query details.

2. Update_Employee updates details in Siebel. The details to update a record are read from an XML file.

3. Sync_Employee publishes a message out of Siebel whenever Employee details are modified or updated in the target Siebel application. TIBCO IntegrationManager receives details of this Employee, and logs it in an XML file. To simulate this example we use Siebel's Business Service Simulator to send a publication request to the adapter.


Configure the Employee Business Object | 103

Configure the Employee Business Object

The Employee.dat file has been provided with a Employee instance, which has the following adapter services:

— Get_Employee

— Sync_Employee

— Update_Employee

— Delete_Employee


The steps to arrive at the configuration for the Employee.dat are similar to that of Customer.dat. See , Integration Scenario Between the Adapter and TIBCO IntegrationManager, on page 52 for details.

The Employee.dat file has the following processes configured using TIBCO IntegrationManager. The processes are:• Get_Employee

• Update_Employee

• Sync_Employee





Get_Employee


Configure the Employee Business Object | 105

Update_Employee



Sync_Employee





repourl as <Adapter Home>/examples/Employee/Employee.dat

configurl as Employee_JMS

2. Also, set the following Siebel Connection parameters according to your Siebel installation:SiebelEnterpriseServerSiebelHostSiebelServerSiebelObjectManagerSiebelLoginNameSiebelLoginPassword

Make sure that the file paths specified in the channels in the TIBCO IntegrationManager, getEmployee_ReadRequest, Update_Employee_ReadRequest and the File Writer task File Writer match your configuration.



Start the Adapter



3. Start the TIBCO IntegrationManager engine. You can do this from the command line or open the Employee.dat file using TIBCO IntegrationManager and start the debug process. For more details refer to TIBCO IntegrationManager Administration Guide.



Test the Process

Get_Employee

To query the employee information from Siebel, copy the Get_Employee_Request.xml file provided in the folder <Adapter Home>/examples/Employee to the directory C:\temp or modify the TIBCO IntegrationManager Transform to make the channel, getEmployee_ReadRequest to point to the correct location of the file mentioned. Restart the TIBCO IntegrationManager Engine. The process sends a request to the adapter and the reply sent by the adapter is saved to the local machine at the location C:/temp/Get_Employee_Reply.xml.

Update_Employee

To update the employee information in Siebel using the Request-Response service, copy the Update_Employee_Request.xml file provided in the folder <Adapter Home>/examples/Employee to the directory C:\temp or modify the TIBCO IntegrationManager Transform to make the channel, Update_Employee_ReadRequest point to the correct location of the file mentioned. Restart the TIBCO IntegrationManager Engine. The process reads from the file and sends a request to the adapter. Check the adapter console to see if the update is successful and verify with the Siebel database if the data has been updated.

Sync_Employee


1. Make sure that the custom Business Service EAI TIBCO HTTP Agent is imported into the Siebel Server. For information on how to import the custom Business Service, refer to TIBCO Adapter for Siebel User’s Guide.









5. In the Input Property Set applet, click Load from File... to load the sample property set file InvokeSync_Employee.xml from the folder <Adapter Home>/examples/Employee




9. Verify the file C:\temp\Sync_Employee.xml, created by the TIBCO IntegrationManager process Sync_Employee.


Monitor the Employee Example | 111

Monitor the Employee Example




4. You can check the results of a successful fetch of a Employee in the Get_Employee_Reply.xml file from the location C:\Temp\Get_Employee_Reply.xml.


6. The results for the Sync service are put in the Sync_Employee.xml file from the location C:\Temp\Sync_Employee.xml.




Stop the Employee Example





| 113

Chapter 12 TIBCO IntegrationManager: Working with the Material Business Object

This chapter demonstrates the Get, Update and Sync operations on a Material Business Object, using TIBCO IntegrationManager.

Topics


• Configure the Material Business Object, page 115




• Monitor the Material Example, page 123

• Stop the Material Example, page 124


114 | Chapter 12 TIBCO IntegrationManager: Working with the Material Business Object

Overview

This example demonstrates three different operations on a Material Business Object.

1. Get_Material fetches Name details from Siebel and writes them back in an XML file. The Name is read from an XML file containing query details.

2. Update_Material updates details in Siebel. The details to update a record are read from an XML file.

3. Sync_Material publishes a message out of Siebel whenever Material details are modified or updated in the target Siebel application. TIBCO IntegrationManager receives details of this Material, and logs it in an XML file. To simulate this example, we use Siebel's Business Service Simulator to send a publication request to the adapter.


Configure the Material Business Object | 115

Configure the Material Business Object

The Material.dat file has been provided with a Material Instance, which has the following adapter services:

— Get_Material

— Sync_Material

— Update_Material

— Delete_Material


The steps to arrive at the configuration for Material.dat are similar to that of Customer.dat. See , Integration Scenario Between the Adapter and TIBCO IntegrationManager, on page 52 for details.

The Material.dat file has the following processes configured using TIBCO IntegrationManager:• Get_Material

• Update_Material

• Sync_Material





Get_Material


Configure the Material Business Object | 117

Update_Material



Sync_Material





repourl as <Adapter Home>/examples/Material/Material.dat

configurl as Material_JMS



SiebelHost

SiebelServer

SiebelObjectManager

SiebelLoginName

SiebelLoginPassword

Make sure that the file paths specified in the channels in the TIBCO IntegrationManager, getMaterial_ReadRequest, Update_Material_ReadRequest and the File Writer task File Writer match your configuration.



Start the Adapter



3. Start the TIBCO IntegrationManager engine. You can do this from the command line or open the Material.dat file using TIBCO IntegrationManager and start the debug process. For more details refer to TIBCO IntegrationManager Administration Guide.



Test the Process

Get_Material

To query the material information from Siebel, copy the Get_Material_Request.xml file provided in the folder <Adapter Home>/examples/Material to the directory C:\temp or modify the TIBCO IntegrationManager Transform to make the channel, getMaterial_ReadRequest to point to the correct location of the file mentioned. Restart the TIBCO IntegrationManager Engine. The process sends a request to the adapter and the reply sent by the adapter is saved to the local machine at the location C:/temp/Get_Material_Reply.xml.

Update_Material

To update the material information in Siebel using the Request-Response service, copy the Update_Material_Request.xml file provided in the folder <Adapter Home>/examples/Material to the directory C:\temp or modify the TIBCO IntegrationManager Transform to make the channel, Update_Material_ReadRequest to point to the correct location of the file mentioned. Edit the XML file and modify the Name field. Restart the TIBCO IntegrationManager Engine. The process reads from the file and sends a request to the adapter. Check the adapter console to see if the update is successful and verify with Siebel database if the data has been updated.

Sync_Material











5. In the Input Property Set applet, click Load from File... to load the sample property set file InvokeSync_Material.xml from the folder <Adapter Home>/examples/Material




9. Verify the file C:\temp\Sync_Material.xml created by the TIBCO IntegrationManager process Sync_Material.


Monitor the Material Example | 123

Monitor the Material Example




4. You can check the results of successful fetch of a Material in the Get_Material_Reply.xml file from the location C:\Temp\Get_Material_Reply.xml.


6. The results for the Sync service are put in the Sync_Material.xml file from the location C:\Temp\Sync_Material.xml.




Stop the Material Example





| 125

Chapter 13 Using the Custom Business Service

The examples in this chapter demonstrate the process of using the EAI TIBCO HTTP Agent business service to publish the PubAccountTest event. The EAI TIBCO HTTP Agent business service is available on all supported platforms.

The examples invoke the GetState, Send and SendReceive service methods of the EAI TIBCO HTTP Agent business service.

Topics

• EAI TIBCO HTTP Agent, page 126

— Using the Business Service Simulator, page 127

— Integrating in a Siebel Workflow, page 148


126 | Chapter 13 Using the Custom Business Service

EAI TIBCO HTTP Agent

This section contains examples to invoke the Publication Service, using the EAI TIBCO HTTP Agent Business Service, through the Business Service Simulator and Workflow Policy Manager.


Using the Business Service Simulator | 127

Using the Business Service Simulator

Examples for Siebel 6.2.x

The examples files are located in <Adapter Home>\examples\service

The example files available are:

• HTTPAgentSimulateMethodInvokeGetState.txt—This file contains the definition for invoking the GetState service method.

• HTTPAgentSimulateMethodInvokeSend.txt—This file contains the definition for invoking the Send service method.

• HTTPAgentSimulateMethodInvokeSendReceive.txt—This file contains the definition for invoking the SendReceive service method.

• HTTPAgentSimulateMethodInvokeSendInput.xml—This file contains input arguments for the Send service method to send a publication request for the PubAccountTest event. It contains a single name or value key that is used by the Publication Service to retrieve appropriate records from Siebel.

• HTTPAgentSimulateMethodInvokeSendMultiKeyInput.xml—This file contains input arguments for the Send method to send a publication request for PubAccountTest event. It contains multiple name or value keys that is used by the Publication Service to retrieve appropriate records from Siebel.

• HTTPAgentSimulateMethodInvokeSendReceiveInput.xml—This file contains input arguments for the SendReceive method to send a Request-Response Invocation event. It contains a single name or value key that is used by the Request-Response Invocation Service to retrieve appropriate records from Siebel.

• HTTPAgentSimulateMethodInvokeGetStateInput.xml --- This file contains the input argument for invoking the GetState method of the Business Service.

• HTTPAgentSimulateMethodInvokeSendNonSiebelBusCompInput.xml — This file contains the input argument for the Send service method to send a publication request for invoking the Non-Siebel Business Component.

• HTTPAgentSimulateMethodInvokeSendCompleteIntObjInput.xml — This file contains the input argument for the Send service method and Send Receive service method to send a publication request for invoking the Complete Integration Object and Complete Integration Object as XML files.

TIBCO Repository Instances<Adapter Home>\examples\pubservices.dat



<Adapter Home>\examples\rpcservices.dat

Usage

Before starting the examples:

1. Start the Siebel client and login to the database.

2. Select Screens>Business Service Administration>Business Service Simulator.

Importing the Input Parameters for the GetState Method1. Click Load From File on the Input Property Set applet.

2. Go to the <Adapter Home>\examples\service directory and select HTTPAgentSimulateMethodInvokeGetStateInput.xml. The file is loaded into the Input PropertySet applet.

3. In the Input PropertySet applet, click on the name in the Property Name column and click on the adjacent icon. The Property Set Properties window displays the input properties. Modify the value of the parameter AgentHTTPServer as per the machine where the adapter is running.

Invoking GetState Without the Publisher RunningThis process comprises two procedures:

1. Import the GetState method definition.

2. Invoke the method.

See the next sections for steps to invoke the GetState, Send and SendReceive service methods.



Importing the GetState Service Method Definition

1. Click Load From File… on the Service Methods applet.

2. Go to the <Adapter Home>\examples\service directory and select HTTPAgentSimulateMethodInvokeGetState.txt.

Invoking the GetState Service Method

1. Click Run in the Service Methods applet in the Business Service Simulator screen in the Siebel client.

2. Update the Output Arguments applet to display the following error message "Exception occurred :No Running Adapter Instance found. Adapter

not running or listening on a different port."

Invoking GetState With Publisher RunningThis process comprises of three procedures.

1. Run the publisher procedure.





Running the Publisher Procedure

1. Go to <Adapter Home>\examples\pubtest.

2. On Microsoft Windows, run runadapter.bat.


See Importing the GetState Service Method Definition on page 129.


1. Click Run in the Service Methods applet in Business Service Simulator screen in the Siebel client.

2. Update the Output Arguments applet to display the error code of 0, implying successful connection with the Publisher.

Invoking Send With Single Key ProcessThis process comprises of three procedures. You must import the Send service method definition and input parameters then invoke the method.

Importing the Send Service Method Definition

1. Make sure the Publisher is running as described in Invoking GetState With Publisher Running on page 129.

2. Click Load From File… on the Service Methods applet.



3. Go to the <Adapter Home>\examples\service directory and select HTTPAgentSimulateMethodInvokeSend.txt.

Importing the Input Parameters for the Send Service Method

1. Click Load From File… on the Input PropertySet applet.

2. Go to the <Adapter Home>\examples\service directory and select HTTPAgentSimulateMethodInvokeSendInput.xml.

3. Update the Input Arguments applet with event parameters for the PubAccountTest event.



4. Modify the value of the parameter AgentHTTPServer as per the machine where the adapter is running.

Invoking the Send Method

To invoke the Send method:

1. Go to the <Adapter Home>\examples\pubtest directory. On Microsoft Windows, run listenpub.bat in a command prompt window to listen to messages published by the Server Publisher.


If the event is processed successfully, the listener should display the published message for all accounts with names that start with 'A'.

Invoking Send With the Multiple Keys ProcessThis process comprises three procedures.

1. Import the Send service method definition.

2. Input parameters.



See Importing the Send Service Method Definition on page 130.


1. Click Load From File… on the Input PropertySet applet.



2. Go to the <Adapter Home>\examples\service directory and select HTTPAgentSimulateMethodInvokeSendMultiKeyInput.xml.

3. Update the Input Arguments applet with event parameters for the PubAccountTest event.

4. Modify the value of the parameter AgentHTTPServer as per the machine where the adapter is running.



1. Go to <Adapter Home>\examples\pubtest. On Microsoft Windows, run listenpub.bat in a command prompt window to listen to the message published by the Server Publisher.

2. Click Run in the Service Methods applet in the Business Service Simulator screen in Siebel client.

If the event is processed successfully, the listener displays the published message for all accounts with names that start with A and locations that start with HQ.



Invoking SendReceive With Schema ReplyThis section explains how to invoke the SendReceive method with TIBCO IntegrationManager and get a schema-based reply.

1. Start TIBCO IntegrationManager to serve as the TIBCO ActiveEnterprise Operation server that processes the reply.

2. Select the rpcservices.dat repository in the ActiveEnterprise Logon dialog. The rpcservices.dat repository can be found in the <Adapter Home>\examples directory.

TIBCO IntegrationManager Transform siebelRpcServerSchemaClassReply Process

• The TIBCO ActiveEnterprise Operation Server listens for requests.

• The TIBCO IntegrationManager Mapper maps the processEvent AE Operation for the event class from the incoming message, to the Data section of the advisoryDoc attribute of the processEvent AE Operation in the reply.

• The TIBCO ActiveEnterprise Operation Server returns the schema-based reply.



Navigate to the Debug tab and start the debug engine.

Invoking the SendReceive Service Method

1. Click Run in the Service Methods applet in the Business Service Simulator screen in Siebel client.

2. The reply is displayed in the Output Property Set applet.

Viewing the Reply from the SendReceive Service Method

1. Click … in the Child Type column in the Output Property Set applet.



2. Click … in the Property Key column in the Property Set window.

The pop-up window contains the reply that was received.

3. Click … in the Child Type column in the Property Set pop-up window (shown in the previous step). Navigate the subsequent pop-up windows to view the complete reply.

Examples for Siebel 7The examples files are located in <Adapter Home>\examples\service directory.

The following example files are available:

• 7HTTPAgentSimulateMethodInvokeGetState.xml—This file contains the definition for invoking the GetState service method.

• 7HTTPAgentSimulateMethodInvokeSend.xml—This file contains the definition for invoking the Send service method.

• 7HTTPAgentSimulateMethodInvokeSendReceive.xml—This file contains the definition for invoking the SendReceive service method.



• HTTPAgentSimulateMethodInvokeSendInput.xml—This file contains input arguments for Send service method to send a publication request for the PubAccountTest event. It contains a single name or value key that is used by the Publication Service to retrieve appropriate records from Siebel.

• HTTPAgentSimulateMethodInvokeSendMultiKeyInput.xml—This file contains input arguments for Send method to send a publication request for the PubAccountTest event. It contains multiple names or value keys that is used by the Publication Service to retrieve appropriate records from Siebel.

• HTTPAgentSimulateMethodInvokeSendReceiveInput.xml—This file contains input arguments for the SendReceive method to send a Request-Response Invocation event. It contains a single name or value key that is used by the Request-Response Invocation Service to retrieve appropriate records from Siebel.

• HTTPAgentSimulateMethodInvokeGetStateInput.xml --- This file contains the input argument for invoking the GetState method of the Business Service.

• HTTPAgentSimulateMethodInvokeSendNonSiebelBusCompInput.xml — This file contains the input argument for the Send service method to send a publication request for invoking the Non-Siebel Business Component.

• HTTPAgentSimulateMethodInvokeSendCompleteIntObjInput.xml — This file contains the input argument for the Send service method and Send Receive service method to send a request for invoking the Complete Integration Object and Complete Integration Object as XML files.

TIBCO Repository Instances<Adapter Home>\examples\pubservices.dat<Adapter Home>\examples\rpcservices.dat

Usage

Before starting the examples:

1. Start Siebel 7 and login to the database.

2. Click View in the top menu and select Sitemap from the drop-down menu. In the Sitemap screen, click Business Service Administration>Business Service Simulator.



See the next sections for steps to invoke the GetState, Send and SendReceive service methods.



Importing the Input Parameters for the GetState Method1. Click Load From File on the Input Property Set applet.

2. Go to the <Adapter Home>\examples\service directory and select HTTPAgentSimulateMethodInvokeGetStateInput.xml. The file is loaded into the Input PropertySet applet.

3. In the Input PropertySet applet, click on the name in the Property Name column and click on the adjacent icon. The Property Set Properties window displays the input properties. Modify the value of the parameter AgentHTTPServer as per the machine where the adapter is running.



Invoking GetState Without the Publisher RunningThis process comprises two procedures.



Importing the GetState Service Method Definition - Siebel 7

Before starting this procedure, make sure that the Business Service is imported using Siebel Tools.

1. Click Load From File… on the Service Methods applet. The Load XML File window displays.

2. Click Browse. Go to the <Adapter Home>\examples\service directory and select 7HTTPAgentSimulateMethodInvokeGetState.xml.

Figure 3 Select File Screen

3. Click Open. The file is selected in the Load XML File window. Click Load to load the file.


1. Click Run in the Service Methods applet in the Business Service Simulator screen in the Siebel client. The Output Property Set applet is populated with data.

2. In the Output Property Set applet, in the Property Name column, click on the name and click the lookup icon. The Property Set Properties window displays.



Figure 4 Get State Service Method Property Set - Screen 1

3. Select Error Message to update the Output Property Set applet to display following error message "Exception occurred: No Running Adapter Instance found. Adapter not running or listening on a different

port." Close the Property Set Properties window.

Invoking GetState With the Publisher RunningThis process comprises three procedures.

1. Run the publisher procedure.



Running the Publisher Procedure


2. On Microsoft Windows, run runadapter.bat.


See Importing the GetState Service Method Definition - Siebel 7 on page 140.



2. In the Output Property Set applet, click the name in the Property Name column and click the icon. The Property Set Properties window displays.



Figure 5 Get State Service Method Property Set - Screen 2

3. Select the value 0, implying successful connection with the Publisher. Close the Property Set Properties window.

Invoking Send with the Single Key ProcessThis process comprises of three procedures.

1. Import the Send service method definition.

2. Import the input parameters.


Importing the Send Service Method Definition - Siebel 7

1. Make sure the Publisher is running. Go to <Adapter Home>\examples\pubtest directory. On Microsoft Windows, run runadapter.bat.

2. Click Load From File… on the Service Methods applet. The Load XML File window displays.

3. Click Browse. Go to the <Adapter Home>\examples\service and select 7HTTPAgentSimulateMethodInvokeSend.xml. The file is loaded into the Service Methods applet.



1. Click Load From File… on the Input Property Set applet. The Load XML File window displays.

2. Click Browse. Go to the <Adapter Home>\examples\service directory and select HTTPAgentSimulateMethodInvokeSendInput.xml.



The file is loaded into the Input Property Set applet.

3. In the Input Property Set applet, click the name in the Property Name column and click the icon. The Property Set Properties window displays.

Figure 6 Send Service Method Property Set - Screen 1

4. Select Event Name to update the Input Property Set applet with event parameters for the PubAccountTest event. Modify the value of the parameter AgentHTTPServer as per the machine where the adapter is running. Close the Property Set Properties window.



1. Go to <Adapter Home>\examples\pubtest directory. On Microsoft Windows, run listenpub.bat in a command prompt window to listen to messages published by the Server Publisher.

2. Click Run in the Service Methods applet in the Business Service Simulator screen in Siebel 7.

If the event is processed successfully, the listener displays the published message for all accounts with names that starts with A.



Invoking Send With the Multiple Keys ProcessThis process comprises three procedures. You must import the Send service method definition and input parameters then invoke the method.


See Importing the Send Service Method Definition - Siebel 7 on page 142.

Importing the Input Parameters for Send Service Method

1. Click Load From File... on the Input Property Set applet. The Load XML File window displays.

2. Click Browse. Go to the <Adapter Home>\examples\service directory and select HTTPAgentSimulateMethodInvokeSendMultiKeyInput.xml.


4. In the Input Property Set applet, click on the name in the Property Name column and click the icon. The Property Set Properties window displays.

Figure 7 Send Service Method with Multiple Keys Property Set - Screen 1

5. Select Event Name to update the Input Property Set applet with event parameters for the PubAccountTest event. Modify the value of the parameter AgentHTTPServer as per the machine where the adapter is running. Close the Property Set Properties window.



1. Go to <Adapter Home>\examples\pubtest directory. On Microsoft Windows run listenpub.bat in a command prompt window to listen to the message published by the Server Publisher.



2. Click Run in the Service Methods applet in the Business Service Simulator screen in Siebel 7.

If the event is processed successfully, the listener should display the published message for all accounts with names that start with A and locations that start with HQ.

Invoking SendReceive with Schema ReplyThis section explains how to invoke the SendReceive method with TIBCO IntegrationManager and get a schema-based reply.



TIBCO IntegrationManager Transform siebelRpcServerSchemaClassReply Process

• The TIBCO ActiveEnterprise Operation Server listens for requests.

• The TIBCO IntegrationManager Mapper maps the processEvent AE Operation for the event class from the incoming message, to the Data section of advisoryDoc attribute of the processEvent AE Operation in the reply.

• The TIBCO ActiveEnterprise Operation Server returns the schema-based reply.



Navigate to the Debug tab and start the debug engine.

Invoking the SendReceive Service Method


2. The reply is displayed in the Output Property Set applet.

Viewing the Reply from the SendReceive Service Method

3. Click on the value in the Child Type column in the Output Property Set applet. Then click the adjacent icon. The PropertySet window displays.



Figure 8 SendReceive Service Method Reply Property Set

4. Click on the value in the Property Key column in PropertySet window. The pop-up window contains the reply that was received.

5. Click on the value in the Child Type column in the PropertySet pop-up window (shown in the previous step). Navigate the subsequent pop-up windows to view the complete reply.



Integrating in a Siebel Workflow

Examples for Siebel 6.2.x

The examples in this chapter are at the following location:

Location<Adapter Home>\examples\workflow

Example Files

• TIBSiebelAdapterHTTPAgentWorkflowEventPublish.xml—This file contains the definition for the sample Siebel workflow for publishing.

• TIBSiebelAdapterHTTPAgentWorkflowEventPublishWithReply.xml—This file contains the definition of the sample workflow for the SendReceive service method.

TIBCO Repository Instance<Adapter Home>\examples\pubservices.dat

Using the Workflow Simulator

1. Start Siebel client and login to the database.

2. Select the Screens>Siebel Workflow Administration>Workflow Processes>All Processes menu choice.

The next sections explain how to invoke publishing requests.

Publish Request in a Workflow ProcessThis sample Siebel workflow demonstrates how to use the EAI TIBCO HTTP Agent Business Service to forward a publication request to the adapter. It also includes workflow steps for retrying the request submission, and for sending an error description to a log file if a retry fails.


Integrating in a Siebel Workflow | 149

Importing Workflow Process for Publishing

Make sure the Publisher is running as in the examples given on page 165 and page 166 respectively.

1. Click Import on the Workflow Processes applet.

2. Go to the <Adapter Home>\examples\workflow directory and select TIBSiebelAdapterHTTPAgentWorkflowEventPublish.xml.

Running Workflow Process for Publishing

1. Select the TIBCO Send Business Event Publication Request from the list of Workflow Processes.

2. Go to Process Designer and modify the value of the input property AgentHTTPServer as per the machine where the adapter is running.



3. Click Process Simulator.

4. Go to <Adapter Home>\examples\pubtest directory. On Microsoft Windows, run listenpub.bat in a command prompt window.

5. Click Start on the Simulator applet.

6. Click Continue.

If the event is processed successfully, the listener (listenpub.bat/listenpub.sh) displays the published message.

If the event returns with an error, the workflow waits by sleeping for the number of seconds defined by the Process Property, Retry timeout.

To set the Retry timeout:

1. Select TIBCO Send Business Event Publication Request from the list of Workflow Processes.

2. Click Process Properties.



3. Change the timeout value of Retry timeout property.

Publish Request in Workflow Process with Reply and Reply Written to an XML File

This sample Siebel workflow demonstrates how to use the EAI TIBCO HTTP Agent Business Service to send Siebel data to the adapter and receive a reply with non-Siebel data to the Siebel application. The adapter extracts the requested Siebel data and packs it in an AE operation request. When a reply is received from a Request-Response service, the data in the reply is converted into Siebel property sets and returned to the Siebel application. The example in this section uses the Siebel Workflow Simulator to submit the SendReceive request.

Importing a Workflow Process for a Publish Request with Reply1. Complete the steps given in Using the Workflow Simulator on page 148.

2. Make sure the Publisher is running as described on Publish Account and its Business Address on page 165 and Invoking the Adapter using Business Service Simulator on page 166.

3. Click Import on the Workflow Processes applet.



4. Go to the <Adapter Home>\examples\workflow directory and select TIBSiebelAdapterHTTPAgentWorkflowEventPublishWithReply.xml.

Running the Workflow Process for Publishing with Reply

1. Select TIBCO Send Business Event Publication Request with Reply from the list of Workflow Processes.






5. Start the debug engine.

6. On the Process Simulator applet, click Start.

7. Click Continue.

If the event is processed successfully, Step Details displays the status.

Viewing the Reply

The reply in the XML file c:\tibReplyMsg.xml is represented by the process property file name.



View the generated file c:\tibReplyMsg.xml in your browser.

If the event returns with an error, the workflow waits by sleeping for number of seconds defined by the Process Property, Retry timeout.

Examples for Siebel 7The examples in this chapter are at the following location:

Location<Adapter Home>\examples\workflow

Example Files

• TIBSiebelAdapterHTTPAgentWorkflowEventPublish.xml—This file contains the definition for the sample Siebel workflow for publishing.

• TIBSiebelAdapterHTTPAgentWorkflowEventPublishWithReply.xml—This file contains the definition of the sample workflow for the SendReceive service method.




Using the Workflow Simulator - Siebel 7

1. Start Siebel 7 and login to the database.

2. Click View in the top menu and select Sitemap from the drop-down menu. In the Sitemap screen, click Siebel Workflow Administration>Workflow Processes.

Figure 9 Select Workflow Processes Screen

The next sections explain how to invoke publishing requests.

Publish Request in a Workflow Process This sample Siebel workflow demonstrates how to use the EAI TIBCO HTTP Agent Business Service to forward a publication request to the adapter. It also includes workflow steps for retrying the request submittal, and for sending an error description to a log file if a retry fails.

Importing Workflow Process for Publishing

Make sure the Publisher is running. Go to <Adapter Home>\examples\pubtest. On Microsoft Windows, run runadapter.bat to start the adapter.

1. In the Workflow Processes applet, click the button with the "down" arrow and select Import Workflow as shown in the next screen. The Workflow Process Import window displays.



Figure 10 Import Workflow

2. Click Browse. Go to the <Adapter Home>\examples\workflow directory and select TIBSiebelAdapterHTTPAgentWorkflowEventPublish.xml.

Figure 11 Select TIBSiebelAdapterWorkflowEventPublish.xml File

3. Click Open. The file is selected in the Workflow Process Import window. Click Import to import the file.



Running Workflow Process for Publishing

1. Click Query in the Workflow Processes applet.

2. In the Name column, enter TIBCO* and click Search. A list of names matching the search criteria is displayed.

Figure 12 Workflow Processes Applet

3. Select the TIBCO Send Business Event Publication Request from the list.

4. In the bottom applet, click Process Simulator. The following screen displays.

Figure 13 Process Simulator

5. Go to <Adapter Home>\examples\pubtest directory. On Microsoft Windows, run listenpub.bat in a command prompt window.


7. Click Continue.

If the event is processed successfully, the listener (listenpub.bat/listenpub.sh) displays the published message.



If the event returns with an error, the workflow waits by sleeping for the number of seconds defined by the Process Property, Retry timeout.

To set the Retry timeout:

1. Select TIBCO Send Business Event Publication Request from the list in the Workflow Processes applet.

2. Click Process Properties.

Change the timeout value of the Retry timeout property.

Check the Event name and the Object ID, the Event name should be PubAccountTest and Object ID should be *.

Figure 14 Retry Timeout Property

Publish Request in a Workflow Process with Reply and Write the Reply to an XML File

This sample Siebel workflow demonstrates how to use the EAI TIBCO HTTP Agent Business Service to send Siebel data to the adapter and receive a reply with non-Siebel data to the Siebel application. The adapter extracts the requested Siebel data and packs it in an ActiveEnterprise operation request. When a reply is received from a Request-Response service, the data in the reply is converted into Siebel property sets and returned to the Siebel application. The example in this section uses the Siebel Workflow Simulator to submit the SendReceive request.

Importing a Workflow Process for a Publish Request with Reply1. Complete the steps given in Using the Workflow Simulator - Siebel 7 on

page 155.

2. Go to <Adapter Home>\examples\rpcsamples directory. On Microsoft Windows, run runadapter.bat.



3. In the Workflow Processes applet, click the button with the "down" arrow and select Import Workflow. The Workflow Process Import window displays.

4. Click Browse. Go to the <Adapter Home>\examples\workflow directory and select TIBSiebelAdapterHTTPAgentWorkflowEventPublishWithReply.xml.

Figure 15 Select TIBSiebelAdapterWorkflowEventPublishWithReply.xml File

Running the Workflow Process for Publishing with Reply

1. Select TIBCO Send Business Event Publication Request with Reply from the list in the Workflow Processes applet.

2. Go to Process Designer and modify the value of the input property AgentHTTPServer as per the machine where the adapter is running.






6. Start the debug engine.


8. Click Continue.

If the event is processed successfully, Step Details displays the status.



Viewing the Reply

After the event is successfully processed a file named tibReplyMsg.xml containing the reply property set is created in C:\.

View the generated file c:\tibReplyMsg.xml in your browser.


| 163

Chapter 14 Simple Publisher Examples

The Publication Service can publish business components or integration objects received from the Siebel system. This chapter explains publication examples.

Topics


• Publish Account and its Business Address, page 165

• Invoking the Adapter using Business Service Simulator, page 166

• Publish Integration Object, page 168

• Publish Complete Integration Object, page 169

• Publish Non-Siebel Business Component, page 170

• Publish Complete Integration Object as XML Message, page 171


164 | Chapter 14 Simple Publisher Examples

Overview

These examples demonstrate how the Siebel system can be configured to send out records when an account is created in Siebel and how the adapter picks up the event and publishes it.

Location<Adapter Home>\examples\pubtest<Adapter Home>\examples\pubIntObj <Adapter Home>\examples\pubsamples



Publish Account and its Business Address | 165

Publish Account and its Business Address

This example publishes account information including the business address. A business address is added as a Multi Value Link object to an account.

Usage

To run the publisher:


2. On Microsoft Windows, run runadapter.bat to start the adapter. On UNIX, run runadapter.sh to start the adapter.

3. On Microsoft Windows, run listenpub.bat to listen on the subject for an account message published by the adapter. On UNIX, run listenpub.sh.



Invoking the Adapter using Business Service Simulator

1. Make sure that the custom Business Service EAI TIBCO HTTP Agent is imported into the Siebel Server. For information on how to import the custom Business Service, refer to TIBCO Adapter for Siebel User’s Guide.


3. Navigate to the Business Service Simulator Screen using View>SiteMap> Business Service Administration>Business Service Simulator.


4. On the Service Methods applet, click Load From File... to import a sample invocation file 7HTTPAgentSimulateMethodInvokeSend.xml for service method Send or 7HTTPAgentSimulateMethodInvokeSendReceive.xml for the service method SendReceive. The XML files are provided in folder <Adapter Home>/examples/Service. The Load XML File window displays.


5. In the Input Property Set applet, click Load from File... to load the sample property set file HTTPAgentSimulateMethodInvokeSendInput.xml for Publishing Integration Objects, HTTPAgentSimulateMethodInvokeSendCompleteIntObjInput.xml for Publishing Complete Integration Object (also for Publishing Complete Integration Object as XML Message and Send Receive Complete Integration Object as XML),


Invoking the Adapter using Business Service Simulator | 167

HTTPAgentSimulateMethodInvokeSendNonSiebelBusCompInput.xml for Publishing Non-Siebel Business Component. All the above-mentioned files are in folder <Adapter Home>/examples/service.

6. Change the parameter, AgentHTTPServer, to the name of the machine on which the adapter is running. For eg: <myMachine>:<myPort>.



9. You can verify the data published by the adapter on the console that is running listenpub.bat.



Publish Integration Object

This example publishes the account information and the associated contacts from the Integration Object, Sample Account.

Usage

To run the adapter:

1. Go to <Adapter Home>\examples\pubIntObj.



4. Invoke the adapter using the Business Service Simulator provided by Siebel. Change the Event name to pubAccountIntObj. This publishes all accounts with names starting with ’A’. Refer to Invoking the Adapter using Business Service Simulator, page 166.

5. At listenpub console, the published data will be displayed, as shown next:Account={îdx^=2 ^class^="sequence[pubAccountIntObjÂccount]" ^1^={îdx^=1 ^class^="pubAccountIntObjÂccount" Name="Amit" Location="" ListOfContact={îdx^=1 ^class^="pubAccountIntObj^ListOfContact" Contact={îdx^=2 ^class^="sequence[pubAccountIntObjÂccount^Contact]"}}} ^2^={îdx^=1 ^class^="pubAccountIntObjÂccount" Name="Accord" Location="India" ListOfContact={îdx^=1 ^class^="pubAccountIntObj^ListOfContact" Contact={îdx^=2 ^class^="sequence[pubAccountIntObjÂccount^Contact]"}}}}

The sample output shown above contains an Id field. This field is unique and depends on the database or Siebel Server being used.


Publish Complete Integration Object | 169

Publish Complete Integration Object

This example publishes the complete account information in the Siebel Data format.

Usage

To run the adapter:

1. Go to <Adapter Home>\examples\pubsamples.



4. Invoke the adapter using the Business Service Simulator provided by Siebel. Change the event name to SendIntegrationObjectEvent. This publishes the account information with Name as TIBCO and Location as PaloAlto. Refer to Invoking the Adapter using Business Service Simulator, page 166.

5. At listenpub console, the published data will be displayed as shown next:^class^="SendIntegrationObjectEvent" ListOfSample Account={îdx^=1 ^class^="SendIntegrationObjectEvent^ListOfSample Account" Account={îdx^=2 ^class^="sequence[SendIntegrationObjectEventÂccount]" ^1^={îdx^=1 ^class^="SendIntegrationObjectEventÂccount" Name="TIBCO" Location="PaloAlto"}}}



Publish Non-Siebel Business Component

This example publishes the information provided in the any format.

Usage

To run the adapter:




4. Invoke the adapter using the Business Service Simulator provided by Siebel. Change the event name to NonSiebelBusCompEvent. This publishes the namevalue with name as Name and its value. Refer to Invoking the Adapter using Business Service Simulator, page 166.

5. At listenpub console the published data will be displayed as shown next:^class^="NonSiebelBusCompEvent" eventKeys={^idx^=1 ^class^="sequence[namevalue]" ^1^={^idx^=2 ^class^="namevalue" name="Name" value="<?xml version="1.0" encoding="UTF-8"?><?Property set="true"?><PropertySet Property1="one" Property2="two" ></PropertySet>"}}


Publish Complete Integration Object as XML Message | 171

Publish Complete Integration Object as XML Message

This example publishes the complete account information in the XML message format.

Usage

To run the adapter:




4. Invoke the adapter using the Business Service Simulator provided by Siebel. Change the Event name to SendIntegrationObjectEvent1. This publishes the account information with Name as TIBCO and Location as PaloAlto in the XML message format. Refer to Invoking the Adapter using Business Service Simulator, page 166.

5. At listenpub console the published data will be displayed as shown next:^class^="SendIntegrationObjectEvent1" XMLMessage="<?xml version="1.0" standalone="no"?><?Siebel-Property-Set EscapeNames="true"?><SiebelMessage IntObjectName="Sample Account"><ListOfSample_spcAccount><Account Name="TIBCO" Location="PaloAlto"/></ListOfSample_spcAccount></SiebelMessage>"


| 173

Chapter 15 Simple Subscription Services

This chapter demonstrates examples for the Subscription Service provided by TIBCO Adapter for Siebel.

Topics


• Invoke Siebel Workflow Process (Synchronous Request), page 175

• Invoke Siebel Workflow Process (Asynchronous Request), page 177

• Invoke Business Service, page 179

• Insert Account Information, page 181

• Insert Integration Object, page 183


174 | Chapter 15 Simple Subscription Services

Overview

The examples provided in this chapter deal with an external system publishing a message, which is suitably mapped to a business event schema. The adapter configuration subscribes to this message and updates the information into the Siebel system.

Location<Adapter Home>\examples\subtest<Adapter Home>\examples\subIntObj<Adapter Home>\examples\subsamples

TIBCO Repository Instance

<Adapter Home>\examples\subservices.dat


Invoke Siebel Workflow Process (Synchronous Request) | 175

Invoke Siebel Workflow Process (Synchronous Request)

This example invokes the Siebel workflow process TIBCO Sample Workflow Invocation from Subscriber using TIBCO BusinessWorks. By specifying the reply address or the error address parameter in TIBCO BusinessWorks while sending the request to the adapter, the status in reply data of the workflow invocation is also captured in this example.

Prerequisite

The workflow process TIBCO Sample Workflow Invocation from Subscriber should be imported into Siebel Server and activated. For importing, refer to steps 1,2 and 3 of Process on Siebel 6.2.x on page 199 or Process On Siebel Client 7 on page 202.

For this example to run, TIBCO BusinessWorks should be installed and running.

Usage

To run the adapter:

1. Go to <Adapter Home>\examples\subsamples.


3. Import the subservices.dat from <Adapter Home>\examples in TIBCO Designer to invoke the TIBCO BusinessWorks process. Save the multi-file project with the name subservices. Otherwise, the global variable deployment would have different values in dat and multi-file project. To use the dat file and convert it to a multi-file format, see Working with dat Files on page 6. Refer to the BWProcess/subsamples/SubscribeSiebelWorkflow in subservices.dat.

4. In TIBCO BusinessWorks, click the Tester tab, choose SubscribeSiebelWorkflow and start the process.

5. Without stopping the TIBCO BusinessWorks process check for element Data in the Output tab of Wait for Adapter Message palette (in the configuration panel). The data is displayed in the format shown below, except for the field Id (Since Id is a unique field, its value is different):



The propertyset that the workflow invocation returns is available. For more information on configuring TIBCO BusinessWorks, refer TIBCO BusinessWorks Process Design Guide.


Invoke Siebel Workflow Process (Asynchronous Request) | 177

Invoke Siebel Workflow Process (Asynchronous Request)

This example invokes the Siebel workflow process TIBCO Sample Workflow Invocation from Subscriber with asynchronous reply using TIBCO BusinessWorks. By specifying the reply address or the error address parameter in TIBCO BusinessWorks while sending the request to the adapter, the status in reply data of the workflow invocation is also captured in this example.

Prerequisite

The workflow process TIBCO Sample Workflow Invocation from Subscriber should be imported into Siebel Server and activated. For importing, refer to steps 1,2 and 3 of Process on Siebel 6.2.x on page 199 or Process On Siebel Client 7 on page 202.


Usage

To run the adapter:



3. Import the subservices.dat from <Adapter Home>\examples in TIBCO Designer to invoke the TIBCO BusinessWorks process. Save the multi-file project with the name subservices. Otherwise, the global variable deployment will have different values in dat and multi-file project. To use the dat file and convert it to a multi-file format, see Working with dat Files on page 6. Refer to the BWProcess/subsamples/SubscribeAsynWorkflow in subservices.dat.

4. In TIBCO BusinessWorks, click the Tester tab, choose SubscribeAsynWorkflow and start the process.

5. Without stopping the TIBCO BusinessWorks process, check for the element Data in the Output tab of Wait for Adapter Message palette (in the configuration panel). The data is displayed in the format shown below:



The Event Keys are not available. The reqId is generated.

For more information on configuring TIBCO BusinessWorks, refer TIBCO BusinessWorks Process Design Guide.


Invoke Business Service | 179

Invoke Business Service

This example invokes the UPSERT method of EAI Siebel Adapter Business Service and returns the Status Keys of the Integration Object instance updated in Siebel on the Reply Address specified.


Prerequisites

For the EAI Siebel Adapter Business Service to return the Status Keys, the Integration Object being updated should have the Statys Keys defined in its configuration. The Status Key is one of the user key type. The fields which are to be returned as Status Keys should be specified into the definition. The keys (fields) which are part of Status keys are usually those which form the Composite key for IO. For more information about status key refer to Siebel Bookshelf.

Usage

To run the adapter:



3. Import the subservices.dat from <Adapter Home>\examples in TIBCO Designer to invoke the TIBCO BusinessWorks process. Save the multi-file project with the name subservices. Otherwise, the global variable deployment will have a different values in dat and multi-file project. To use the dat file and convert it to a multi-file format, see Working with dat Files on page 6. Refer to the BWProcess/subsamples/SubscribeBusinessServiceInvocation in subservices.dat.

4. In TIBCO BusinessWorks, click the Tester tab, choose SubscribeBusinessServiceInvocation and start the process.

5. Without stopping the TIBCO BusinessWorks process, check for element Data in the Output tab of Wait for Adapter message palette (in the configuration panel). The data is displayed in the format shown below:



The status keys are Id , operation, location and name.



Insert Account Information | 181

Insert Account Information

This example upserts (inserts or updates) an account with Name Tibco Software Inc., in Siebel.

Prerequisites for this example

TIBCO IntegrationManager is installed and running

To Run the example

1. Go to <Adapter Home>\examples\subtest


3. Start the TIBCO IntegrationManager server using subservices.dat. <im_installation>/bin> imse –f <Adapter Home>/examples/subservices.dat

4. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject ' insert.busComp ':tibrvsend “insert.busComp” “test”

5. Verify with the Siebel Client if an Account with the Name, Tibco Software Inc. has been inserted.

Refer to the TIBCO IntegrationManager workflow busComp/SubscribeAccount in subservices.dat.


Insert Integration Object | 183

Insert Integration Object

This example upserts (inserts or updates) an account with the Name, Tibco Software Inc., and Contact from the Integration Object, Sample Account.


TIBCO IntegrationManager is installed and running.

To Run the example

1. Go to <Adapter Home>\examples\subIntObj.


3. Start the TIBCO IntegrationManager server using subservices.dat. <im_installation>/bin> imse –f <Adapter Home>/examples/subservices.dat

4. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject ' insert.intObj':tibrvsend “insert.intObj” “test”

5. Verify with the Siebel Client if an Account with the Name, Tibco Software Inc. and the Contact associated with it has been inserted.

Refer to the TIBCO IntegrationManager workflow intObj/subInsertIntObj in subservices.dat.

If your Siebel Application version is 2000, invoke the TIBCO IntegrationManager workflow with subject set.intObj6 and refer to the workflow intObj/subInsertIntObj6.


| 185

Chapter 16 Simple Request Response Service Examples

This chapter demonstrates examples for the Request-Response Service and Request-Response Invocation Service provided by TIBCO Adapter for Siebel.

Topics


• Invoke Workflow process using TIBCO BusinessWorks, page 187

• Send Receive Integration Objects as an XML Message, page 188

• Invoke Business Service, page 189

• Query Account Information, page 191

• Insert or Update Account Information, page 193

• Query Integration Objects, page 194

• Insert or Update Integration Objects, page 195


186 | Chapter 16 Simple Request Response Service Examples

Overview

The examples provided in this chapter deal with an external system sending a request, which is suitably mapped to a business event schema. The adapter configuration, acting as a Request-Response server, subscribes to this message, processes the information into the Siebel system and sends a reply to the external system.

Location<Adapter Home>\examples\rpcsamples<Adapter Home>\examples\rpcIntObj

TIBCO Repository Instance

<Adapter Home>\examples\rpcservices.dat


Invoke Workflow process using TIBCO BusinessWorks | 187

Invoke Workflow process using TIBCO BusinessWorks

This example invokes the Siebel workflow process TIBCO Sample Workflow Invocation from Subscriber for Integration Object using TIBCO BusinessWorks and writes the reply in Reply.txt file.


Usage

To run the adapter:

1. Go to <Adapter Home>\examples\rpcIntObj.


3. Import the rpcservices.dat from <Adapter Home>\examples in TIBCO Designer to invoke the TIBCO BusinessWorks process. Save the multi-file project with the name rpcservices. Otherwise, the global variable deployment will have different values in dat and multi-file project. To use the dat file and convert it to a multi-file format, see Working with dat Files on page 6. Refer to the BWProcess/rpcIntObj/rpcServerInvokeWF in rpcservices.dat.

4. In TIBCO BusinessWorks, click the Tester tab, choose rpcServerInvokeWF and start the process.

5. Verify the Reply.txt file in C:.The data is displayed in the format shown below, except for the field Id (Since Id is a unique field, its value is different): <?xml version="1.0" encoding="UTF-8"?><?Siebel-Property-Set EscapeNames="true"?><PropertySet Object_spcId="" Siebel_spcOperation_spcObject_spcId="" Error_spcCode="" Error_spcMessage="" ><TibcoMessage ></TibcoMessage ><SiebelMessage ><SiebelMessage IntObjectName="Sample Account" ><ListOfSample_spcAccount ><Account Location="PaloAlto" Name="TIBCO" ></Account ></ListOfSample_spcAccount ></SiebelMessage ></SiebelMessage ></PropertySet >




Send Receive Integration Objects as an XML Message

This example demonstrates the Send Receive Integration Objects type of the Request-Response Invocation Service as XML message format.

Usage

To run the adapter:



3. On Microsoft Windows, run listenclient.bat to listen on the subject for a message published by the adapter. On UNIX, run listenclient.sh.

4. Import the rpcservices.dat from <Adapter Home>\examples in TIBCO Designer to invoke the TIBCO BusinessWorks process. Save the multi-file project with the name rpcservices. Otherwise, the global variable deployment will have different values in dat and multi-file project. To use the dat file and convert it to a multi-file format, see Working with dat Files on page 6. Refer to the BWProcess/rpcIntObj/rpcClientSendReceiveCompleteIntObjAsXML in rpcservices.dat.

5. In TIBCO BusinessWorks, click the Tester tab, choose rpcClientSendReceiveCompleteIntObjAsXML and start the process.

6. Invoke the adapter using the Business Service Simulator simulated in Siebel Client. Change the event name to NonSiebelBusCompEvent. This publishes the namevalue with name as Name and its value. Refer to Invoking the Adapter using Business Service Simulator, page 166.

7. At listenclient console, the published data will be displayed as shown next:^class^="^request^BusinessServiceRPCClientEvent^processEvent" ^userClosure^="1094736114585" businessDoc={^idx^=1 ^class ^="BusinessServiceRPCClientEvent" XMLMessage="<?xml version="1.0" standalone="no"?><?Siebel-Property-Set EscapeNames="true"?><SiebelMessage IntObjectName="Sample Account"><ListOfSample_spcAccount><Account Name="TIBCO" Location="PaloAlto"/></ListOfSample_spcAccount></SiebelMessage>"


Invoke Business Service | 189

Invoke Business Service

This example invokes the UPSERT method of EAI Siebel Adapter Business Service and returns the Status Keys of the Integration Object instance updated in Siebel on the Reply Address specified.


Prerequisites

For the EAI Siebel Adapter Business Service to return the Status Keys, the Integration Object being updated should have the Statys Keys defined in its configuration. The Status Key is one of the user key type. The fields which are to be returned as Status Keys should be specified into the definition. The keys (fields) which are part of Status keys are usually those which form the Composite key for IO. For more information about status key refer to Siebel Bookshelf.

Usage

To run the adapter:



3. Import the rpcservices.dat from <Adapter Home>\examples in TIBCO Designer to invoke the TIBCO BusinessWorks process. Save the multi-file project with the name rpcservices. Otherwise, the global variable deployment will have different values in dat and multi-file project. To use the dat file and convert it to a multi-file format, see Working with dat Files on page 6. Refer to the BWProcess/rpcIntObj/rpcServerInvokeBusinessService in rpcservices.dat.

4. In TIBCO BusinessWorks, click the Tester tab, choose rpcServerInvokeBusinessService and start the process.

5. Without stopping the TIBCO BusinessWorks process, check for element Data in the Output tab of Invoke an Adapter Request-Response Service palette (in the configuration panel). The data is displayed in the format shown below:



The status keys are Id , operation, location and name.



Query Account Information | 191

Query Account Information

This example demonstrates the Query Siebel Business Components type of the Request-Response Service. When the adapter receives a request from an external application (TIBCO IntegrationManager, in this example), the adapter retrieves the Account information whose names start with A.*, all the Business Addresses of the account and associated Contact information.



To Run the example

1. Go to <Adapter Home>\examples\rpcsamples.


3. Open the TIBCO IntegrationManager application and connect to rpcservices.dat.




4. Run the TIBCO IntegrationManager Engine by clicking the Start Engine Button in the debug panel.

5. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject ' query.account’:tibrvsend “query.account” “test”

Refer to the TIBCO IntegrationManager workflow busComp/ServerGetAccountContact.

6. Check the output schema of the mapper to see all accounts.


Insert or Update Account Information | 193

Insert or Update Account Information

This example demonstrates the Insert or Update Siebel Business Components type of Request-Response Service. When the adapter receives a request from an external application (TIBCO IntegrationManager in this example), the adapter upserts (inserts or updates) the Account and associated Contact information with the data provided in the request message.



To Run the example

1. Go to <Adapter Home>\examples\rpcsamples


3. Open the TIBCO IntegrationManager application and connect to rpcservices.dat


5. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject ' insert.account’:tibrvsend “insert.account” “test”

Check the Siebel Client if an Account is inserted or updated with the data provided in the job slot insert_account in the TIBCO IntegrationManager transform. Refer to the TIBCO IntegrationManager workflow busComp/ServerSetAccountContact.




Query Integration Objects

This example demonstrates the Query Siebel Integration Components type of Request-Response Service. The adapter, when it receives a request from external application (TIBCO IntegrationManager in this example) queries Siebel to fetch Accounts whose name starts with A.* , all the Business Addresses for the Account and associated Contact information for the Integration Object, Sample Account.



To Run the example

1. Go to <Adapter Home>\examples\rpcIntObj




5. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject 'query.IntObj’:tibrvsend “query.IntObj” “test”

6. Look for the data replied by the adapter in the TIBCO IntegrationManager’s Engine Output tab. Refer to the TIBCO IntegrationManager workflow intObj/rpcServerGetIntObj in rpcservices.dat.


If your Siebel Application version is 2000, invoke the TIBCO IntegrationManager workflow with subject query.IntObj6 and refer to the workflow intObj/rpcServerGetIntObj6.


Insert or Update Integration Objects | 195

Insert or Update Integration Objects

This example demonstrates the Insert or Update Siebel Integration Components type of Request-Response Service. The adapter, when it receives a request from external application (TIBCO IntegrationManager in this example) upserts (inserts or updates) the Account and associates Contact information to the Account for the Integration Object, Sample Account.



To Run the example

1. Go to <Adapter Home>\examples\rpcIntObj




5. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject set.IntObj:tibrvsend “set.IntObj” “test”

6. Look for the data replied by Adapter in the TIBCO IntegrationManager’s Engine Output tab. Refer to the TIBCO IntegrationManager workflow intObj/rpcServerSetIntObj in rpcservices.dat.


If your Siebel Application version is 2000, invoke the TIBCO IntegrationManager workflow with subject query.IntObj6 and refer to the workflow intObj/rpcServerSetIntObj6.


| 197

Chapter 17 Invoking a Siebel Workflow

This chapter discusses examples to invoke a Siebel workflow using the Subscriber and Request-Response Server.

Topics


• Using a Sample Workflow to Generate an XML File from Subscriber, page 199

• Using Sample Workflow to Generate an XML File from Request-Response Server, page 206

• Using Sample Workflow to Invoke EAI Siebel Adapter Business Service From Subscriber, page 214

• Using Sample Workflow to Invoke EAI Siebel Adapter Business Service From Request Response Server, page 218


198 | Chapter 17 Invoking a Siebel Workflow

Overview

The adapter installation provides a sample subscriber configuration that demonstrates how the subscriber is used to invoke a Siebel Workflow Process. In this example, an ActiveEnterprise message is the input process property.

The first example in this section shows a sample workflow using the input process property in a workflow step to generate a XML file using the service method, Write Property Set of the Siebel Business Service, EAI XML Write to File.

The second example in this section shows a sample workflow using the input process property in a workflow step to invoke a Business Service called EAI Siebel Adapter to populate data into Siebel integration objects.

These examples can be run on Microsoft Windows and UNIX.

Location<Adapter Home>\examples\rpcsamples<Adapter Home>\examples\rpcIntObj<Adapter Home>\examples\subsamples<Adapter Home>\examples\subIntObj<Adapter Home>\examples\subtest

TIBCO Repository Instance<Adapter Home>\examples\rpcservices.dat <Adapter Home>\examples\subservices.dat


Using a Sample Workflow to Generate an XML File from Subscriber | 199

Using a Sample Workflow to Generate an XML File from Subscriber

The adapter installation provides an sample subscriber configuration that demonstrates how the subscriber is used to invoke a Siebel Workflow Process. In this example, an ActiveEnterprise message is the input process property.

Using Sample Workflow to Generate an XML File

Process on Siebel 6.2.x

The series of steps you must take and the system responses and actions for Siebel 6.2.x or higher are described below.

1. In the Siebel system, select Screens> Siebel Workflow Administration> Workflow Processes>All Processes.

2. Click the Import button to import the sample workflow process from the adapter installation under:<Adapter

Home>\examples\workflow\TIBSiebelAdapterWorkflowSubInvoke.xml

When the adapter is installed on UNIX, the TIBSiebelAdapterWorkflowSubInvoke.xml file is located in the directory mentioned above. Therefore, you need to transfer the file to a local directory and then import it.



Figure 16 Sample Siebel Workflow Diagram

3. Double-click the workflow step, Write Data to XML File. This step describes the details of the input and output arguments for the Siebel Business Service EAI XML Write to File.

Recall that the input workflow process property, TibcoMessage, is mapped by the subscriber component and created as data type, Hierarchy; and it is used as the input argument for the service method WritePropertySet in the Business Service Workflow step. The input argument FileName specifies the output file for the service method WritePropertySet.



Figure 17 Sample Siebel Workflow Step

4. A preconfigured Subscriber adapter instance called subservices is provided along with the adapter installation. Go to <Adapter Home>\examples\subsamples directory. On Microsoft Windows, run runadapter.bat. On UNIX, run runadapter.sh.

5. Open the example file, subservices.dat, in TIBCO Integration Manager, to generate a subscriber message for the Business Event that contains an instance invokeWorkflow in the Process Diagram\workflow directory. Recall that the ApplicationContext attribute was substituted by a class schema. See



Passing a Message into the Siebel Workflow Process in Chapter 6 of the TIBCO Adapter for Siebel User Guide.

6. Navigate to the Debug tab and start the debug engine.

7. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject’invokeWF’:tibrvsend “invokeWF” “test”Refer to the TIBCO IntegrationManager workflow/invokeWF in subservices.dat.

8. The Siebel Subscriber receives the message and identifies the Siebel Workflow Process to run through the user property SiebelWorkflowProcess. The data in the ApplicationContext attribute is converted to Siebel PropertySet and the Siebel Workflow Process TIBCO Sample Workflow Invocation from Subscriber is invoked.

9. Check on the output XML file c:\propertySetData.xml generated from the workflow step using the Siebel Business Service EAI XML Write to File.

Process On Siebel Client 7

The series of steps you must take and the system responses and actions for Siebel 7 are described below.



1. Select View>Site Map> Siebel Workflow Administration>Workflow Processes.

2. Click New and select Import Workflow to import the sample workflow process from the adapter installation under:<Adapter


Figure 18 Sample Siebel Workflow Diagram for Siebel 7

3. Double click the workflow step Write Data to XML File. This step describes the details of the input and output arguments for the Siebel Business Service EAI XML Write to File.

Recall that the input workflow process property, TibcoMessage, is mapped by the subscriber component and created as data type, Hierarchy; and it is used as the input argument for the service method WritePropertySet in the Business Service Workflow step. The input argument FileName specifies the output file for the service method WritePropertySet.



Figure 19 Sample Workflow Step for Siebel 7

4. A preconfigured Subscriber adapter instance called subservices is provided along with the adapter installation. Go to <Adapter Home>\examples\subsamples directory. On Microsoft Windows, run runadapter.bat. On UNIX, run runadapter.sh.

5. Open the example file, subservices.dat, in TIBCO IntegrationManager, to generate a subscriber message for the Business Event that contains an instance invokeWorkflow in the Process Diagram\workflow directory. Recall that the ApplicationContext attribute was substituted by a class schema. See



Passing a Message into the Siebel Workflow Process in Chapter 6 of the TIBCO Adapter for Siebel User Guide.


7. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject’invokeWF’:tibrvsend “invokeWF” “test”Refer to the TIBCO IntegrationManager workflow/invokeWF in subservices.dat.

8. The Siebel Subscriber receives the message and identifies the Siebel Workflow Process to run through the user property SiebelWorkflowProcess. The data in the ApplicationContext attribute is converted to Siebel PropertySet and the Siebel Workflow Process TIBCO Sample Workflow Invocation from Subscriber for Integration Object is invoked.




Using a Sample Workflow to Generate an XML File from Request

Response Server

The adapter installation provides an example rpcservices.dat project that demonstrates how the Request-Response Service is used to invoke a Siebel Workflow Process.

The example shows a sample workflow using the input process property in a workflow step to generate an XML file using the service method, Write Property Set of the Siebel Business Service EAI XML Write to File.

A sample Request-Response service is provided in the rpcservices.dat project. To see details of the service:

1. Start TIBCO Designer. Open the rpcservices.dat project.

2. In the project panel double-click rpcservices and then double-click Adapter Services.

3. Select RPCInvokeWorkflow. The service details are displayed in the configuration panel.

Using Sample Workflow to Generate an XML File from Request-Response Server

Process on Siebel 6.2.x

The series of steps you must take and the system responses and actions for Siebel 6.2.x or higher are described below.

1. In the Siebel system, select Screens >Siebel Workflow Administration> Workflow Processes>All Processes.

2. Click the Import button to import the sample workflow process from the adapter installation under:



Using a Sample Workflow to Generate an XML File from Request Response Server | 207

<Adapter Home>\examples\workflow\TIBSiebelAdapterWorkflowSubInvoke.xml

Figure 20 Sample Siebel Workflow Diagram

3. Double-click the workflow step Write Data to XML File. This step describes the details of the input and output arguments for the Siebel Business Service EAI XML Write to File.

Recall that the input workflow process property, TibcoMessage, is mapped by the Request-Response component and created as data type, Hierarchy; and it is used as the input argument for the service method WritePropertySet in the Business Service Workflow step. The input argument FileName specifies the output file for the service method WritePropertySet.

When the adapter is installed on UNIX, the TIBSiebelAdapterWorkflowSubInvoke.xml file is located in the directory mentioned above. Therefore, you need to transfer the file to a local directory and then import it.



Figure 21 Sample Siebel Workflow Step

4. A preconfigured Request-Response adapter instance called rpcservices is provided along with the adapter installation. Go to <Adapter Home>\examples\rpcsamples directory.

5. Make the following change to the runadapter.bat file on Microsoft Windows.Change the configurl to /tibco/private/adapter/siebel/rpcsamples.Run runadapter.bat. Make the following change to the runadapter.sh file on UNIX.Change the configurl to /tibco/private/adapter/siebel/rpcsamples.Run runadapter.sh.



6. Open the example file rpcservices.dat in TIBCO IntegrationManager. This generates a message for the Business Event that contains an instance rpcServerInvokeWF6 in the Process Diagram.


8. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject ‘invokeWF.intObj6’:tibrvsend “invokeWF.intObj” “test”Refer to the TIBCO IntegrationManager intObj/rpcServerinvokeWF6 in rpcservices.dat.



9. The Siebel Subscriber receives the message and identifies the Siebel Workflow Process to run through the user property, SiebelWorkflowProcess. The data in the input message to the adapter is converted to Siebel PropertySet and the Siebel Workflow Process TIBCO Sample Workflow Invocation from Subscriber for the Integration Object is invoked.


Process On Siebel Client 7


1. Select View - Site Map - Siebel Workflow Administration - Workflow Processes.



Figure 22 Sample Request-Response Workflow Diagram for Siebel 7



3. Double click the workflow step Write Data to XML File. This step describes the details of the input and output arguments for the Siebel Business Service EAI XML Write to File.

Recall that the input workflow process property, TibcoMessage, is mapped by the Request-Response component and created as data type, Hierarchy; and it is used as the input argument for the service method WritePropertySet in the Business Service Workflow step. The input argument FileName specifies the output file for the service method WritePropertySet.

Figure 23 Sample Workflow Step for Siebel 7

4. A preconfigured Request-Response adapter instance called rpcservices is provided along with the adapter installation. Go to <Adapter Home>\examples\rpcsamples directory.

5. Make the following change to the runadapter.bat file on Microsoft Windows.Change the configurl to /tibco/private/adapter/siebel/rpcsamples.Run runadapter.bat. Make the following change to the runadapter.sh file on UNIX.Change the configurl to /tibco/private/adapter/siebel/rpcsamples.Run runadapter.sh.




6. Open the example file rpcservices.dat in TIBCO IntegrationManager. This generates a message for the Business Event that contains an instance rpcServerInvokeWF in the Process Diagram.


8. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject ‘invokeWF.intObj’:tibrvsend “invokeWF.intObj” “test”Refer to the TIBCO IntegrationManager intObj/rpcServerinvokeWF in rpcservices.dat.



9. The Request-Response Service receives the message and identifies the Siebel Workflow Process to run through the user property, SiebelWorkflowProcess. The data in the input message to the adapter is converted to Siebel PropertySet and the Siebel Workflow Process TIBCO Sample Workflow Invocation from Subscriber is invoked.




Using Sample Workflow to Invoke EAI Siebel Adapter Business

Service From Subscriber

This section describes a sample workflow using the input process property in a workflow step to invoke a Business Service called EAI Siebel Adapter to populate data into Siebel integration objects. It uses the service method Upsert.

For details on how to configure schema for Integration Objects, refer to Siebel Integration Components Configuration in the TIBCO Adapter for Siebel User’s Guide.

Example for Siebel 6.2.x

The series of steps you must take and the system responses and actions for Siebel 6.2.x are described below.

1. In the Siebel system, select Screens>Siebel Workflow Administration> Workflow Processes> All Processes.

2. Click the Import button to import the sample workflow process from the adapter installation under:<Adapter

Home>\examples\workflow\TIBSiebelAdapterWorkflowSubInvokeIntObj.xml

3. Double-click the workflow step, Write Data to Integration Object. This step describes the details of the input and output arguments for the Siebel Business Service, EAI Siebel Adapter.


Using Sample Workflow to Invoke EAI Siebel Adapter Business Service From Subscriber | 215

Recall that the input workflow process property, SiebelMessage, is mapped by the subscriber component and created as data type, Hierarchy; and it is used as the input argument for the service method WritePropertySet in the Business Service Workflow step. The input argument Operation Code specifies the type of operation to be performed on the Integration Object.

4. A preconfigured Subscriber adapter instance called subservices is provided along with the adapter installation. Go to <Adapter Home>\examples\subIntObj directory. On Microsoft Windows, run runadapter.bat. On UNIX, run runadapter.sh.

5. Open the TIBCO IntegrationManager application and connect to subservices.dat.

6. Run the TIBCO IntegrationManager Engine by clicking on the Start Engine Button in the debug panel.

7. Trigger the TIBCO IntegrationManager workflow by sending an TIBCO Rendezvous message on the subject ‘invokeWF.intObj6’:tibrvsend “invokeWF.intObj6” “test”

Refer to the TIBCO IntegrationManager intObj/rpcServerInvokeWF6 in subservices.dat.

8. The Siebel Subscriber receives the message and identifies the Siebel Workflow Process to run through the user property SiebelWorkflowProcess. The data in the input message to the adapter is converted to Siebel PropertySet and the Siebel workflow process TIBCO Sample Workflow Invocation from Subscriber for Integration Object is invoked.




9. Check the Account screen, in which the data is updated.

Example for Siebel 7


1. Select View - Site Map - Siebel Workflow Administration - Workflow Processes.


Home>\examples\workflow\TIBSiebelAdapterWorkflowSubInvokeIntObj.xml

3. Double-click the workflow step Write Data to Integration Object. This step describes the details of the input and output arguments for the Siebel Adapter Business Service.

Recall that the input workflow process property, SiebelMessage, is mapped by the subscriber component and created as data type, Hierarchy; and it is used as the input argument for the service method WritePropertySet in the


Using Sample Workflow to Invoke EAI Siebel Adapter Business Service From Subscriber | 217

Business Service Workflow step. The input argument Operation Code specifies the type of operation to be performed on the Integration Object.

4. A preconfigured Subscriber adapter instance called subservices is provided along with the adapter installation. Go to <Adapter Home>\examples\examples\subIntObj directory. On Microsoft Windows, run runadapter.bat. On UNIX, run runadapter.sh.

5. Open the TIBCO IntegrationManager application and connect to subservices.dat

6. Run the TIBCO IntegrationManager Engine by clicking on the Start Engine Button in the debug panel.

7. Trigger the TIBCO IntegrationManager workflow by sending a TIBCO Rendezvous message on the subject ‘invokeWF.intObj’:tibrvsend “invokeWF.intObj” “test”

Refer to the TIBCO IntegrationManager intObj/rpcServerInvokeWF in subservices.dat.

8. The Siebel Subscriber receives the message and identifies the Siebel Workflow Process to run through the user property SiebelWorkflowProcess. The data in the input message to the adapter attribute is converted to Siebel PropertySet and the Siebel Workflow Process TIBCO Sample Workflow Invocation from Subscriber for Integration Object is invoked.

9. Check the Account screen, in which the data is updated.




Using Sample Workflow to Invoke EAI Siebel Adapter Business

Service From Request Response Server

This example is similar to the one demonstrated for using a sample workflow to invoke EAI Siebel Adapter Business Service from the subscriber, except that the adapter has to be started using the runadapter.bat (runadapter.sh in case of UNIX) available in the <Adapter Home>\examples\rpcIntObj directory of the adapter installation and the TIBCO IntegrationManager workflows are to be used from rpcservices.dat. Follow the steps given in the section, Using Sample Workflow to Invoke EAI Siebel Adapter Business Service From Subscriber, page 214.

Refer to the TIBCO IntegrationManager workflows intObj/rpcServerinvokeWF6 and intObj/rpcServerinvokeWF for Siebel 6.2.x or higher and Siebel 7 respectively in rpcservices.dat.


| 219

Index

A

acronyms xiii

B

Build Archive 13, 47

C

conventions used in this manual xiiiConvert DAT to Files 7Custom Business Service 5Customer 2customer support xiv, xiv

D

dat 6documents, related x

E

EAI TIBCO HTTP Agent 5EAI XML Write to File 206Employee 2EmployeeNumber 38Enterprise Archive 13, 47

G

Get 2Get_Customer 12Get_Customer_Request.xml 15Get_Employee 34Get_Employee_Request.xml 38Get_Material 40Get_PurchaseOrder 28Get_PurchaseOrder_Request.xml 32Get_SalesOrder 20

J

JMS Server 22, 30

L

Location 8

M

Material 2MaterialNumber 44

O

ObjectManager 5OrderNumber 25


220 | Index

P

PurchaseOrder 2

R

related documents x

S

SalesOrder 2Siebel 98 Enterprise xiiSiebel Workflow Administration 199, 203, 210, 214,

216SiebelEnterpriseServer 14SiebelHost 14SiebelLoginName 14SiebelLoginPassword 14SiebelObjectManager 14SiebelServer 14support, contacting xiv, xivSync 4Sync_Customer 12Sync_Customer.xml 17Sync_Employee 34, 37Sync_Material 40Sync_Material.xml 44Sync_PurchaseOrder 28Sync_PurchaseOrder.xml 32Sync_SalesOrder 20Sync_SalesOrder.xml 25

T

technical support xiv, xivTIBCO Administrator 14TIBCO Enterprise for JMS 6

U

Update 2Update_Customer 12Update_Customer_Request.xml 15Update_Employee 34, 37Update_Employee_Request.xml 38Update_Material 40Update_Material_Request.xml 44Update_PurchaseOrder 28Update_PurchaseOrder_Request.xml 32Update_SalesOrder 20Update_SalesOrder_Request.xml 25Using TIBCO BusinessWorks 5

W

workflowsample 206, 214

X

XML fileoutput from workflow 202, 205

Z

Zip Archive 21


tibco adapter for siebel examples guide - tibco software · pdf fileinvoke siebel workflow...

Documents