BusinessWorks™ TIBCO ActiveMatrix Plug-in for Siebel User

TIBCO ActiveMatrixBusinessWorks™Plug-in for Siebel

User's GuideVersion 7.1

December 2020

Copyright © 2017-2020. TIBCO Software Inc. All Rights Reserved.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Comparison between Adapter and Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Supported and Non-supported Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

TIBCO Business Studio Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Siebel Connection Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

User Interface Elements in the Siebel Connection Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Creating a Siebel Connection using the Siebel Connection Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Siebel Objects Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

User Interface Elements in the Siebel Objects Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Creating a Siebel Schema using the Siebel Objects Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Configuring a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Testing a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Deploying an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Siebel Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Invoke Business Object Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Invoke Business Service Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Invoke Integration Object Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Invoke Workflow Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Migrating Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Migrating Projects from Adapter to Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Migrating Siebel Adapter Configuration to Siebel Connection Resource in Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Migrating Projects With Invoke an Adapter Request-Response Service Activity and Request-Response Service . . . . . . . . . . . . .39

Request-Response Service Fields Not Supported for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Invoke an Adapter Request-Response Service Activity Fields Not Supported for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Migrating Projects With Publish to Adapter Activity and Subscription Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Subscription Service Fields Not Supported For Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Publish to Adapter Activity Fields Not Supported For Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Working with Preference File (JSON) For Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Working with the Sample Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Importing Sample Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Sample Projects for Invoke Business Object Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

2

TIBCO ActiveMatrix BusinessWorks™ Plug-in for Siebel User's Guide

Sample Plugin Project for Invoke Business Object Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Sample Plug-in Project to show the Parent-Child Relationship using Invoke Business Object Activity . . . . . . . . . . . . . . . . . . . 47


Sample Plugin Project for Invoke Business Object Activity with Multi-Value Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


Sample Projects for Invoke Business Service Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Sample Plugin Project for Invoke Business Service Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50


Sample Project to show the Custom Business Service Parent-Child Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52


Sample Project to Show the Custom Business Service Write XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


Sample Project to show the Invoke Parent-Child Relationship with Integration Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54


Sample Projects for Invoke Integration Object Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Sample Plugin Project for Invoke Integration Object Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55


Sample Project for Parent-Child Relationship using the Invoke Integration Object Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57


Sample Projects for Invoke Workflow Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Sample Plugin Project for Invoke Workflow Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58


Sample Project for Non-Integration Invoke Workflow Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59


Invoking a Siebel Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Management of Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Log Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Setting up Log Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Exporting Logs to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Legal and Third-Party Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

3


Figures

Siebel Connection - Client Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Siebel Objects Editor - Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Siebel Objects Editor - Siebel Objects Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Console View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Example for Invoke Business Object Activity Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Example for Parent-Child Relationship using the Invoke Business Object Activity Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Example for Establishing Parent-Child Relationship using Siebel Objects Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Example for Invoke Business Service Activity Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Example for Invoke Integration Object Activity Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Example for Invoke Workflow Activity Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4


TIBCO Documentation and Support Services

How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainly inHTML and PDF formats.

The TIBCO Product Documentation website is updated frequently and is more current than any otherdocumentation included with the product. To access the latest documentation, visit https://docs.tibco.com.

Product-Specific Documentation

Documentation for TIBCO products is not bundled with the software. Instead, it is available on the TIBCODocumentation site at https://docs.tibco.com/products/tibco-activematrix-businessworks-plug-in-for-siebel.To directly access documentation for this product, double-click the following file:

TIBCO_HOME/release_notes/TIB_bwpluginsiebel_version_docinfo.html

where TIBCO_HOME is the top-level directory in which TIBCO products are installed. On Windows, thedefault TIBCO_HOME is C:\Program Files\tibco\bw6. On UNIX systems, the default TIBCO_HOMEis /opt/tibco/bw6.

The following documents for this product can be found on the TIBCO Documentation site:

● TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel Release Notes

● TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel Installation

● TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel User's Guide

The following documents provide additional information and can be found on the TIBCO Documentationsite:

● TIBCO ActiveMatrix BusinessWorks

● TIBCO Enterprise Administrator

How to Contact TIBCO Support

You can contact TIBCO Support in the following ways:

● For an overview of TIBCO Support, visit http://www.tibco.com/services/support.

● For accessing the Support Knowledge Base and getting personalized content about products you areinterested in, visit the TIBCO Support portal at https://support.tibco.com.

● For creating a Support case, you must have a valid maintenance or support contract with TIBCO. Youalso need a user name and password to log in to https://support.tibco.com. If you do not have a username, you can request one by clicking Register on the website.

How to Join TIBCO Community

TIBCO Community is the official channel for TIBCO customers, partners, and employee subject matterexperts to share and access their collective experience. TIBCO Community offers access to Q&A forums,product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, andtools that extend and enable customers to gain full value from TIBCO products. In addition, users cansubmit and vote on feature requests from within the TIBCO Ideas Portal. For a free registration, go to https://community.tibco.com.

5


https://docs.tibco.com

https://docs.tibco.com/products/tibco-activematrix-businessworks-plug-in-for-siebel

https://docs.tibco.com/products/tibco-activematrix-businessworks

https://docs.tibco.com/products/tibco-enterprise-administrator-2-4-0

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

https://support.tibco.com

https://support.tibco.com

https://ideas.tibco.com/

https://community.tibco.com

Product Overview

TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel is a bridge between TIBCO ActiveMatrixBusinessWorks and the Siebel server.

TIBCO ActiveMatrix BusinessWorks is a leading integration platform that can integrate a wide variety oftechnologies and systems within enterprise and on cloud. TIBCO ActiveMatrix BusinessWorks includes anEclipse-based graphical user interface (GUI) provided by TIBCO Business Studio™ for design, testing, anddeployment. If you are not familiar with TIBCO ActiveMatrix BusinessWorks before using the plug-in. Seethe TIBCO ActiveMatrix BusinessWorks documentation for more details.

TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel plugs into TIBCO ActiveMatrix BusinessWorks andadds the Siebel Palette to TIBCO Business Studio. You can create a connection between the plug-in and aSiebel server, and then configure a process that performs the activities in the Siebel palette. See the topic Getting Started for more details about how to use the plug-in.

TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel provides the following activities for inboundoperations:

● InvokeBusinessObject Activity

● InvokeBusinessService Activity

● InvokeIntegrationObject Activity

● InvokeWorkflow Activity

6


Comparison between Adapter and Plug-in

This topic is useful for users, who have previously used the TIBCO ActiveMatrix® Adapter for Siebel, tohelp understand differences in the plug-in where supported features have overlap with adapter.

Comparison between Adapter for Siebel and Plug-in for Siebel

FeatureTIBCO ActiveMatrix® Adapterfor Siebel

TIBCO ActiveMatrixBusinessWorks™ Plug-in forSiebel

Service Provided Subscription service, Request-Response service.

The plug-in is a replacement ofthe Siebel Adapter and the AEPalette available in TIBCOBusinessWorks. The activitiesprovided in the plug-in aresimilar to the service typesavailable in Siebel Adapter andits corresponding AE activity.

Transport Type RV and JMS The plug-in is native to TibcoBusinessWorks and no longerrequires messaging source forinbound operations.

Logging Configured in the Logging tab. Uses TIBCO BusinessWorks 6logging.

Number of reconnect attemptsbefore suspending impactedservices

Used in adapter in thereconnection logic.

As there is no service concept inthe plug-in, this is not present.

Siebel Business and IntegrationComponent

Business Object and integrationobject configuration is from theadapter services.

Business Object and integrationobject configuration is from theSiebel Object Editor.

TRA Properties TRA properties are maintainedin TIBCO Administrator and/oradsbl.tra file.

TRA properties are notapplicable in plug-in.

UAN Schema Support Supported XML message is native to TIBCOBusinessWorks and does notrequire any configurations. Anyreply schema wouldautomatically be in XML format.

Reply Schema, Request Schema,and Custom AESchema

Custom schema supported Reply Schema and RequestSchema only supported forInvoke Business Service Activity.

Invoke Workflows Integration Object and Non-Siebel Event supported

Integration Object and Non-Siebel Event supported

7




Parent-Child Schemas Business Object and IntegrationObject supported

Business Object and IntegrationObject supported. Notsupported for Invoke Workflowactivity.

Errors from Siebel Server Reply message containsinformation on error from SiebelServer

Fault message is created

Schema Management Schemas are maintained relativeto connection object used duringdownload of schema.

Schemas are maintained relativeto the Schema Shared Resource.

Server Request andAsynchronous WorkflowRequest

Supported Supported

Connection Transport Types TCP/IP and HTTP are supported TCP/IP supported for inboundoperations.

Connection Connection Configuration isfrom the Siebel AdapterConfiguration.

Connection configuration isfrom the Siebel Connectionshared resource maintained inthe Siebel Schema sharedresource referenced by the plug-in activity.

Schema: Literal Match, AEMessage Field, Formatted,Default

Supported Only Literal Match is supportedfor child Business Object.

Business Document -ApplicationContext,ApplicationId,ApplicationInstanceId,ComponentId, ConfirmCode,DateTimeStamp, Encrypted,ErrorAddress, LotId, Name,ReferenceId, ReplyAddress,VerbCode, Version

Supported Not supported

Advisory Document - Analysis,ApplicationContext,ApplicationId,ApplicationInstanceId, Class,Data, DateTimeStamp,Description, Name, ReferenceId,Severity, SiebelHeader,TibcoAppError, Subject, Version


8




QueryPage, Execute, andSynchronised methods of EAISiebel Adapter Business Service


Timeout exception for InvokeAdapter Service activity inTIBCO BusinessWorks 5Adapter Palette


9


Supported and Non-supported Data Types

The following is the complete list of data types, some that are supported and some that are not supportedby TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel.

Data Type Description Supported?

DTYPE_BOOL Data is stored as Y or N. It is displayed as TRUE orFALSE and checked or unchecked.

Supported

DTYPE_CURRENCY Data is stored as currency. Supported

DTYPE_DATE Data is stored as date. Supported

DTYPE_DATETIME Data is stored as date and time. Supported

DTYPE_UTCDATETIME Data that includes both the date and the timecomponent is stored in the database in UTC time(UTC is GMT excluding adjustments for daylightsavings time)

Supported

DTYPE_ID Contains primary key data, which is automaticallygenerated by the application.

Supported

DTYPE_INTEGER Data is stored as whole numbers. The range spans-2147483647 to 2147483647.

Supported

DTYPE_NOTE Data is stored as a long string. The string sizecannot exceed a size of 16 KB. If the length is notexplicitly defined the default length is 16 KB.

NotSupported

DTYPE_NUMBER Data is stored as a number. Supported

DTYPE_PHONE Data is stored as a phone number. Supported

DTYPE_TEXT Data is stored as a string. The string size cannotexceed a size of 2000 bytes. The default size is 255.

Supported

DTYPE_TIME Data is stored as time. NotSupported

10


Getting Started

This tutorial is designed for the beginners who want to use TIBCO ActiveMatrix BusinessWorks Plug-in forSiebel in TIBCO Business Studio.All the operations are performed in TIBCO Business Studio. See the topic TIBCO Business Studio Overviewto familiarise yourself with TIBCO Business Studio.

Procedure

1. Creating a Project

2. Creating a Siebel Connection using the Siebel Connection Resource

3. Configure the Siebel Object Editor and Fetch Schema

4. Configuring a Process

5. Testing a Process

6. Deploying an Application

TIBCO Business Studio Overview

TIBCO Business Studio provides a workbench in which you can create, manage, and navigate resources inyour workspace. A workspace is the central location on your machine where all data files are stored.

The workbench consists of:

1. Menu: contains menu items such as File, Edit, Diagram, Navigate, Search, Project, Run, Window, andHelp.

2. Toolbar: contains buttons for frequently used commands such as New , Save , Enable/Disable

Business Studio Capabilities , Create a new BusinessWorks Application Module , Create a new

BusinessWorks Shared Module , Debug , Run , and so on.

3. Perspective: contains an initial set and layout of views that are required to perform a certain task.TIBCO Business Studio launches the Modeling perspective by default. You can change the perspectivefrom the menu Window > Open Perspective > Perspective_Name.

11


4. View: displays resources. For example, the Project Explorer view displays the ActiveMatrixBusinessWorks applications, modules, and other resources in your workspace, and the Properties viewdisplays the properties for the selected resource. You can open a view from the menu Window > ShowView > View_Name.

5. Editor: provides a canvas to configure, edit, or browse a resource. Double-click a resource in a view toopen the appropriate editor for the selected resource. For example, double-click an ActiveMatrixBusinessWorks process businessobject.bwp in the Project Explorer view to open the process in theeditor.

6. Palette: contains a set of widgets and a palette library. A palette groups activities that perform similartasks, and provides quick access to activities when configuring a process.

Creating a ProjectThe first task using the plug-in is creating a project. After creating a project, you can add resources andprocesses.

An Eclipse project is an application module configured for TIBCO ActiveMatrix BusinessWorks. Anapplication module is the smallest unit of resources that is named, versioned, and packaged as part of anapplication.

Procedure

1. Start TIBCO Business Studio using one of the following ways:

● On Microsoft Windows, click Start > All Programs > TIBCO > Studio for Designers● On Mac OS and Linux, run the TIBCO Business Studio executable file located in the TIBCO_HOME/

studio/version_number/eclipse directory.

2. From the menu, click File > New > BusinessWorks Resources to open the BusinessWorks Resourcewizard.

3. In the Select a wizard dialog, click BusinessWorks Application Module and click Next to open the NewBusinessWorks Application Module wizard.

4. In the Project dialog, configure the project that you want to create:a) In the Project name field, enter a project name.b) By default, the created project is located in the workspace current in use. If you do not want to use

the default location for the project, clear the Use default location check box and click Browse toselect a new location.

c) Use the default version of the application module, or enter a new version in the Version field.d) Keep the Create empty process and Create Application check boxes selected to automatically create

an empty process and an application when creating the project.e) Select the Use Java configuration check box if you want to create a Java module.

A Java module provides the Java tooling capabilities.f) Click Finish to create the project.

12


Result

Siebel Connection ResourceThe Siebel Connection is a shared resource that you should use to establish a connection from theActiveMatrix BusinessWorks Plug-in to the Siebel Repository or Siebel Server.

● User Interface Elements in the Siebel Connection Resource

● Creating a Siebel Connection using the Siebel Connection Resource

13


User Interface Elements in the Siebel Connection ResourceThe user interface elements, and their description, in the Siebel Connection resource are as follows:

Client Tab

Siebel Connection - Client Tab

Siebel Connection - General Fields

Field Description

Package When you create a new Siebel Connection usingthe Siebel Connection Wizard, the value enteredfor the Package field will be displayed for thisfield. For details see the topic Create a SiebelConnection using the Siebel Connection Resource.

The hyperlink that shows the count ofSiebel Connection references, does notconsider the reference that exists in theSiebel Objects Editor.

14


Field Description

Name When you create a new Siebel Connection usingthe Siebel Connection Wizard, the value enteredfor the Resource Name field will be displayed forthis field. For details see the topic Create a SiebelConnection using the Siebel Connection Resource.

If the name of the Siebel Connectionshared resource is changed, it does notget automatically updated in the SiebelObjects Editor.

Description Provide a description for the connection that isestablished.

Siebel Connection - Configuration Fields

Field Description

Host The name, or the IP address, of the machine onwhich the Siebel server is installed. The format ofthe host name should be <HostName or IPAddress:Port Number>. For example,MySiebelServerHost:7666.

Enterprise Server The Siebel Enterprise under which the SiebelServer is installed.

Object Manager The name of the Application Object Manager thatyou want to access. This can be a user-definedcomponent or one of the following predefinedcomponents: SCCObjMgr_enu, SSEObjMgr,ISSObjMgr, SSVObjMgr. For additionalinformation, see the "Administration Guide of theSiebel Server".

Language Select the language to be used while connecting tothe Siebel application from the drop-down list.Some of the possible values are enu, chs, cht, csy,and dan. You should provide the same value givenat the time of the Siebel applications installation.

Currently only enu-English(American) is supported.

Transport The method of transport. Currently only TCP/IP issupported.

15


Field Description

Encryption Select whether encryption has to be performed ornot. Encryption, if performed, will be done in theRSA method. The default value is None. To getconnected in the RSA mode, you have to make thecorresponding change in the Siebel Server setup.Additionally, your Siebel Setup should be capableof working in RSA mode.

Compression Specify the type of compression that should beused for network communication. The defaultvalue is ZLIB. When using Resonate, ifcompression is required on the client as well as theserver side, it must be specified for the client aswell as the server side. The server, and the client,will compress the communication as defined byyou. If you do not use Resonate, the server drivesthe compression and the client-side settings will beignored.

User Name Specify the username for the account to access theapplication. For example, sadmin.

Password Specify the password for the account to access theapplication.

Maximum Number of Reconnect Attempts Specify the maximum number of reconnectattempts that should be performed in case oftemporary or permanent network failure. Thedefault value is -1 and it indicates that thereconnect attempt will be indefinite.

Interval between Reconnect Attempts(ms) Specify the interval between reconnect attempts (inmilliseconds).

This time does not include the timerequired by the API.

Test Connection A button, when clicked, checks the connectionbetween the plugin and the Siebel server.

Advanced Tab

16


Siebel Connection - Trace Configuration Fields

Field Description

Enable SQL Siebel Trace Select this check box if you want to enable SQLSiebel trace.

SQL Trace File Provide the name of the Log file to store the SQLtrace. The log file will get generated at the Siebelserver.

Creating a Siebel Connection using the Siebel Connection ResourceAfter creating a project, you have to add a Siebel Connection shared resource to create a connectionbetween the plug-in and the Siebel server.

Prerequisites

The Siebel Connection shared resource is available at the Resources level. Ensure that you have created aproject, as described in the topic Creating a Project.

See the topic User Interface Elements in the Siebel Connection Resource to know more about the fields andtheir descriptions.

Procedure

1. Expand the created project in the Project Explorer view.

2. Right-click the Resources folder and click New > Siebel Connection to open the Siebel Connectionwizard.

3. The Resource Folder, Package Name, and the Resource Name fields are provided by default. If you do notwant to use the default configurations, change them accordingly. Click the Finish button to open theSiebel Connection resource.

4. Provide values for the following fields in the General section of the Configuration tab.

● Description

5. Provide values for the following fields in the Siebel Connection Configuration section of the Configurationtab.

● Host - Mandatory field

● Enterprise Server - Mandatory field

● Object Manager - Mandatory field

● Language

● Transport

● Encryption

● Compression

● User Name - Mandatory field

● Password - Mandatory field

● Maximum Number of Reconnect Attempts

● Interval between Reconnect Attempts(ms)

17


6. If you want to enable SQL Trace, perform the following steps:a) Click the Advanced tab.b) Select the Enable SQL Siebel Trace check box.c) In the SQL Trace File field enter the name of the Log file for storing the SQL trace.

7. Click the Test Connection button to check whether the connection has been successfully established ornot. If the connection is unsuccessful, make the necessary changes and test the connection again.

Siebel Objects EditorThe Siebel Objects Editor is schema editor which is used to define the schema or the object and componentsof Siebel that will be utilized by the ActiveMatrix BusinessWorks Plug-in to the Siebel system.

Only two objects are supported. They are:

● Business Object

● Integration Object

If you create a copy of Sample.sblObject and rename it to Sample1.sblObject, the renamed copy doesnot behave like an isolated copy because it continues to reference the activities of the original.

User Interface Elements in the Siebel Objects EditorThe user interface elements, and their description, in the Siebel Objects Editor are as follows:

Configuration Tab

Siebel Objects Editor - Configuration Tab

Configuration Tab Fields

Field Descritpion

Name Name of the Siebel schema object.

Description Add a description for the Siebel schema object.

18


Field Descritpion

SiebelConnection

Mandatory Field.

Select a Siebel connection from the available list. To create a Siebel connection seethe topic Create a Siebel Connection using the Siebel Connection Resource for moredetails.

Siebel Objects Tab

Siebel Objects Editor - Siebel Objects Tab

Siebel Objects Tab Fields

Field Descritpion

Business Objects Use this component to add Business objects. For more details on adding Businessobjects see the topic Creating a Siebel Schema using the Siebel Objects Editor.

IntegrationObjects

Use this component to add Integration objects. For more details on addingIntegration objects see the topic Creating a Siebel Schema using the Siebel ObjectsEditor.

Creating a Siebel Schema using the Siebel Objects EditorAfter establishing a connection with the Siebel server you need to setup a Siebel schema or Siebel objectsreference using the Siebel Objects editor.

Prerequisites

The Siebel Connection shared resource is available at the Resources level. Ensure that you have created aproject, as described in the topic Creating a Project.

See the topic User Interface Elements in the Siebel Objects Editor to know more about the fields and theirdescriptions.

Procedure

1. Expand the created project in the Project Explorer view.

19


2. Right-click the TIBCO Resource folder and click New > Other.

3. Click TIBCO Resource > Siebel Object Editor > Next.The Create Siebel Objects dialog is displayed.

4. Enter an appropriate name for the Name field and click the Finish button.The Siebel Objects Editor opens.

5. Click Select Siebel Connection Resource.The Siebel Connection dialog box is displayed.

6. Select an appropriate connection and click the OK button.The control passes back to the Siebel Objects Editor.

7. Click the Siebel Objects tab and select any one object.

8. The following objects are available:

20


Siebel ObjectName Details

Business Objects1. Right-click the Business Objects and click Add Business Object. The Select

Business Component dialog is displayed.

2. Type in the object name you want to locate and the matching object name isdisplayed in the Business Objects text area and the Business Componentstext area is populated on the basis of the selected Business Objects. Bydefault, the Business Objects field is selected first and accordingly theBusiness Components field is populated.

3. Select an appropriate value for the Business Objects field and the BusinessComponents field and click the OK button.

The Business Objects name is case-sensitive.

4. Right-click the newly added business object and you get the followingoptions:

● Add Business Component- Click this option to add a sub businesscomponent.

● Add MVL- Click this option to add the Multi Value Link (MVL).

● Remove- Click this option to delete the added business component.

5. Click Fetch Fields to fetch all the fields for the business component from theSiebel server.

6. The basic operations can be performed only if the fields have beenfetched from the previous step. For the downloaded schema, thefilter option is case-sensitive and generates different results for thesame string of different patterns. For example, Filter account*and Filter Account* generates different results.

You can perform the following two basic operations:

● Click Select All to select all the fields

● Click Deselect All to deselect all the selected fields.

7. You can also perform the following advanced operations:

● Click Show All to display all the fields

● Click Show Used to display only the fields selected by you

● Click Show Required to display the fields with Required column set toYes.

● Click Show Readonly to display fields with Readonly column set toYes.

● Click Show Calculated to display fields with Calculated column set toYes.

● Click Show MVG to display fields where MVG has some value.

21



BusinessComponentFields

The following list of fields are the column fields for the business component. Ifyou select any of the following fields they get included in the schema forperforming the operation through the activity.

● Use- The Siebel field to be included.

● Key- Fields defined as user keys combine to uniquely define a Siebel recordfor a Business Component. Check the checkbox next to a Siebel BusinessComponent or field to define it as a user key. All fields that you select as userkeys combine to uniquely define a Siebel record for a Business Component.For example, the Account Name and Location can be selected as user keys touniquely define an Account in the Siebel system.

This mandatory Key field is igonored if you perform the Queryoperation.

● Field Name- Displays the name of the Siebel field.

● Match Field- The name of the parent Business Component field. This parentname defines the parent of the parent-child relationship for all its secondaryBusiness Components.

The name of the parent Business Component field. The parent name definesthe parent of a parent-child relationship for all its secondary BusinessComponents. The value you specify in the Match Field column, for aprimary Business Component, is used as the default search criteria to createor retrieve the parent and corresponding child component.

In the case of secondary Business Components, the match field establishesthe relationship with the parent Business Component to allow the plugin toretrieve a subset of the child records related to the particular parentcomponent.

For example, if the match field for the Account field of Contact is set tomatch the value for the Name field of the parent Account, you can retrievethe list of contacts related to the Account.

Match Field is only supported for single parent-child relationship.

— Literal Field - This Field is applicable for Child Business object in Parentchild combination. The Literal Field is used as a default value whileperforming query operation on a business object.

● Read Only- The Siebel field is designated as a Read Only in the Siebelrepository. Read Only fields cannot be subscribed.

● Required- The Siebel field is designated as a Required field in the Siebelrepository.

● Calculate- The Siebel field is computed based on other Siebel fields. Acalculated field cannot be subscribed.

● MVG- The Siebel field belongs to a Siebel Multi Value Group.

● MVL- Name of the Siebel Multi Value Link for the field in the above MultiValue Group. A Multi Value field cannot be subscribed. To subscribe to aMVL field, a child MVL Business Component is required.

● Pick List- Name of the Pick List if the field is controlled by a Siebel Pick Listcomponent.

22



● Type- Name of the Siebel data type.

● Hidden- To be selected if the Siebel field is designated as a Hidden field inthe Siebel repository. A hidden field cannot be subscribed.

● Inactive- To be selected if the Siebel field is inactive in the Siebel repository.Inactive fields are unavailable for users. You cannot change theconfiguration.

IntegrationObjects 1. Right-click the Integration Objects and click Add Integration Object. The

Select Integration Component dialog is displayed.

2. Type in the object name you want to locate and the matching object name isdisplayed in the Integration Objects text area and the IntegrationComponents text area is populated on the basis of the selected IntegrationObjects. By default, the Integration Objects field is selected first andaccordingly the Integration Components field gets populated.

The Integration Object name is case-sensitive.

3. Select an appropriate value for the Integration Objects field and theIntegration Components field and click the OK button.

4. Right-click the newly added integration object and you get the followingoptions:

● Add Integration Component- Click this option to add a sub integrationcomponent.

● Remove- Click this option to delete the integration component.

5. Click the Fetch Fields button to fetch all the fields for the integrationcomponent from the Siebel server.

6. The basic operations can be performed only if the fields have beenfetched from the previous step. For the downloaded schema, thefilter option is case-sensitive and it will generate different resultsfor the same string of different patterns. For example, Filteraccount* and Filter Account* will generate different results.

You can perform the following two basic operations:

● Click Select All to select all the fields

● Click Deselect All to deselect all the selected fields.

7. You can also perform the following advanced operations:

● Click Show All to display all the fields

● Click Show Used to display only the fields selected by you

● Click Show Required to display the fields with the Required columnset to Yes.

● Click Show Inactive to display the fields with the Inactive column set toYes.

23



IntegrationComponentFields

The following list of fields are the column fields for the integration component.If you select any of the following fields they get included in the schema forperforming the operation through the activity.

● Use- If you select this field the integration field gets included in theintegration components schema for the plug-in service.

● Name- Displays the name of the integration components field.

● XML Tag- The XML name of the integration field in the Siebel repository.This is a display field.

● Required- When displayed as selected, the Siebel integration field isdesignated as a Required field in the Siebel repository. This is a display field,the values for this field are provided from Siebel.

● Inactive- If you select this field it indicates that the integration field isinactive in the Siebel repository. Inactive fields are unavailable for users.Users cannot change the configuration.

● User Key- Displays the name of the user key field in the Siebel repository ofwhich this field is a part.

In Siebel, integration component fields are grouped together as user keys. Itassists in identifying a single record in an integration component for anintegration object. There might be multiple user keys for a single integrationcomponent. Each field can be present in the multiple user keys. The palette doesnot display all the information required for user keys. Please verify with theSiebel Tools to ensure you select the proper user key.

Configuring a ProcessAfter creating a project, an empty process is created. You can add activities to the empty process tocomplete a task.

Prerequisites

● Ensure that you have created an empty process when creating a project. For more details see the topic Creating a Project.

● Ensure that the Siebel connection is created and established. See the topic Creating a Siebel Connectionusing the Siebel Connection Resource for more details.

● Ensure that the Siebel Object schema is created using the Siebel Objects editor. See the topic Creating aSiebel Schema using the Siebel Objects Editor for more details.

Procedure

1. In the Project Explorer view, click the created project and open the empty process from the Processesfolder.

2. Select an activity from the Palette view and drop it in the Process editor.For example, select and drop the Timer activity from the General Activities palette and theInvokeBusinessObject activity from the Siebel palette.

None of the Siebel plug-in activities are starter activities for an inbound operation.

24


3. Drag the icon to create a transition between the added activities.

4. Configure the added Siebel activity, as described in the topic Siebel Palette.

A Siebel connection is required when configuring the Siebel activities. See the topic Creating aSiebel Connection using the Siebel Connection Resource for more details on how to create aSiebel connection.

5. Select the operation that you want to perform.

6. Select the Business Component schema using the picker.

7. Provide values in the Input tab.

8. Click File > Save to save the project.

Testing a ProcessAfter configuring, you have to debug or test a process.

Prerequisites

Ensure that you have configured a process, as described in Configuring a Process.

Procedure

1. Open the process you have configured in the TIBCO Business Studio.

2. On the toolbar, click Debug > Debug Configurations.

3. Click BusinessWorks Application > BWApplication in the left panel.By default, all the applications in the current workspace are selected in the Applications tab. Ensurethat only the application you want to debug is selected in the Applications tab in the right panel.

4. Click Debug to test the process in the selected application.TIBCO Business Studio changes to the Debug perspective. The debug information is displayed in theConsole view.

Console View

5. In the Debug tab, expand the debugged process and click an activity.

6. In the upper-right panel, click Job Data view, and then click the Output tab to check the activity output.

25


Result

Deploying an ApplicationAfter testing, if the configured process works as expected, you can deploy the application that contains theconfigured process into a runtime environment, and then use the bwadmin utility to manage the deployedapplication.

Before deploying an application, you must generate an application archive, which is an enterprise archive(EAR) file that is created in TIBCO Business Studio. See TIBCO Business Studio for more information.

Deploying an application involves the following tasks:

1. Uploading an application archive

2. Deploying an application archive

3. Starting an application

See TIBCO ActiveMatrix BusinessWorks Administration for more information about how to deploy anapplication.

26


Siebel Palette

The Siebel palette contains the following activities:

The Siebel palette contains the following activities for inbound operations:

● Invoke Business Object Activity

● Invoke Business Service Activity

● Invoke Integration Object Activity

● Invoke Workflow Activity

Invoke Business Object ActivityYou can use the InvokeBusinessObject Activity to select and configure the Siebel business object orcomponent to perform the insert, upsert, delete, and query operations using the Siebel fields.

General

The following table lists the configurations in the General tab of the Invoke Business Object activity:

FieldModuleProperty? Description

Name The name of the activity is displayed.

Siebel Connection Yes Specify the Siebel Connection type that should beused. See the topic Creating a Siebel Connection usingthe Siebel Connection Resource for more details.

1. Click the search icon. A dialog box is displayedlisting the connections.

2. Select an appropriate connection.

27



Operation Specify the operation that has to be performed usingthe activity. The following operations can beperformed using the activity:

● Insert- for inserting a new record

● Upsert- for inserting a record if the record does notexist or for updating a record if it exists.

● Delete- for deleting an existing record

● Query- for querying or searching a record orrecords

● The operations Insert, Upsert, andDelete is performed even if you selectand provide the values for the Hidden,Inactive, Calculated, and the Read onlyfields. There are no changes on the Siebelserver for these fields. For example, ifyou provide input as "*" and perform thedelete operation, all records are deleted.

● The Upsert operation cannot beperformed on multiple records in bothcase parent and parent-childcombinations which has multiplerecords.

● If the Delete operation finds multiplerecords, it deletes all the records withoutprompting you for a confirmation. Forexample, if you provide an input of a*and perform the delete operation, allrecords starting from the letter a isdeleted. To delete all the records, provide* as an input.

● If you execute a Query operation withoutinput values provided to the selectedfields, an error is displayed on theconsole.

● When any operation like Query is takingmore time than configured in the TIBCOBusinessWorks Studio (default is 3minutes) then you must increase thetimeout in Studio to avoid timeoutexception.

● If a parent-child relationship exists, theDelete operation is not performed.

28



Siebel Object Reference Only the Business Object is supported bythis activity.

Specify the object for reference created using the siebelobjects editor. See the topic Creating a Siebel Schemausing the Siebel Objects Editor for more details.

1. Click the search icon. The Siebel Business Objectdialog is displayed.

2. Select an appropriate object.

Description

In the Description tab, you can enter a short description for the Invoke Business Object activity.

Input

The values in the Input tab will be populated based on the object selected in the Siebel Object Referencefield.

Duplication or adding multiple Item fields in the Input tab is not allowed as Siebel supports only a singleparent.

Output

If the Query operation is successful, the data received from Siebel server gets displayed on the Output tab.

For the Invoke Business Object activity only the status and Object ID are displayed as the output. If theprocess executes without any error, it will show the ID, which is received from the Siebel server. If theprocess fails a Fault will be generated. The error or an exception will be displayed in the Fault tab.

Fault

In the Fault tab, you can find the error message and error message code of the Invoke Business Objectactivity. See the Error Codes topic for more detailed explanation of errors.

The following table lists the error schema elements in the Fault tab of the Invoke Business Object activity:

Error Schema Element Data Type Description

SiebelPluginException String Exceptions like key field validation, match fieldvalidation, etc will be displayed.

SiebelJDBException String Will display an exception related to the Siebeloperation. The exception will be generated either bythe Siebel server or due to operation failure.

29


Invoke Business Service ActivityYou can use the InvokeBusinessService Activity to select and configure the Siebel business services and theSiebel fields.

General

The following table lists the configurations in the General tab of the Invoke Business Service activity:




Business Service1. Click the Fetch button. The Business Services

dialog is displayed.

2. Select the value EAI Siebel Adapter.

3. Click the OK button.

30



Business Service Method The following operations can be performed using theactivity For EAI Siebel Adapter Business Service:




● Update- for updating an existing record.


● The Update operation cannot beperformed on a user-key field. Forexample, if you want to update theLocation field from City1 to City 2, andif the Location field is a user-key, theupdate operation will generate a Fault.

● The Upsert operation cannot beperformed on multiple records. Anexception is displayed if Upsert isperformed on multiple records.



● If you perform Delete operation on arecord, the output data for the recordwill not have any values.

To view all the Business Service methodsyou must re-fetch the Business Service.

31



Siebel Object Reference Only the Integration Object is supported bythis activity.

Specify the object for reference created using theeditor. See the topic Creating a Siebel Schema using theSiebel Objects Editor for more details.

1. Click the search icon. The Siebel Integration Objectdialog is displayed.


Integration Object Name The name of the integration object.

Request Schema Reference The selected schema for this field is rendered as inputschema in the Input tab.

Either Request schema reference or SiebelObject Reference is applicable for the Inputtab. Refer the sample checked in project forcustom schema.

To request a schema reference perform the followingsteps:

1. Click Load Request Schema. The Load Request(Input) Schema dialog is displayed.

2. Enter the appropriate values and click OK.

Reply Schema Reference The selected schema for this field is rendered as outputschema in the Output tab.

If request schema reference field ispopulated and Reply Schema Reference fieldis not, then there is default output schema.

To reply to a schema reference perform the followingsteps:

1. Click Load Reply Schema. The Load Reply(Output) Schema dialog is displayed.

2. Enter the appropriate values and click OK.

Description

In the Description tab, you can enter a short description for the Invoke Business Service activity.

Input

The values in the Input tab is populated based on the object selected in the Siebel Object Reference field orthe Request Schema Reference field.

Duplication or adding multiple Item fields in the Input tab is not allowed as Siebel only supports a singleparent node or a parent-children relationship in the nodes.

32


Output

The values in the Output tab is populated based on the values passed to the fields of the objects in theInput tab. If the values are appropriate, the output is appropriate. If the values are not appropriate, an erroror an exception is displayed in the Fault tab.

Fault

In the Fault tab, you can find the error message and error message code of the Invoke Business Serviceactivity. See the Error Codes topic for more detailed explanation of errors.

The following table lists the error schema elements in the Fault tab of the Invoke Business Object activity:


SiebelPluginException String Displays an exception at runtime if the user hasselected the attributes, has not assigned any valuesto the attributes, and is trying to perform the Insert,Upsert, Query, or Delete operation.

SiebelJDBException String Displays an exception related to the Siebeloperation. The exception is generated either by theSiebel server or due to operation failure.

Invoke Integration Object ActivityYou can use the InvokeIntegrationObject Activity to perform the insert, upsert, update, delete, or queryoperation using the integration object or component.

General

The following table lists the configurations in the General tab of the Invoke Integration Object activity:


Name The name of the activity will be displayed.

Siebel Connection Yes Specify the Siebel Connection type that should be used.See the topic Creating a Siebel Connection using theSiebel Connection Resource for more details.

33



Operation Specify the operation that has to be performed usingthe activity. The following operations can be performedusing the activity:



● Update- for updating an existing record.



● The Update operation cannot beperformed on a user-key field. Forexample, if you want to update theLocation field from City1 to City 2, andif the Location field is a user-key, theupdate operation will generate an error.

● The Upsert operation cannot beperformed on multiple records. Anexception is displayed if Upsert isperformed on multiple records.

● If you perform the Delete operation on arecord, the output data for the record willhave no values.



Siebel Object Reference Only the Integration Object is supported bythis activity.

Specify the object for reference created using the editor.See the topic Creating a Siebel Schema using the SiebelObjects Editor for more details.



34


Description

In the Description tab, you can enter a short description for the Invoke Integration Object activity.

Input


Duplication or adding multiple Item fields in the Input tab is not allowed as Siebel only supports a singleparent node or a parent-children relationship in the nodes.

Output

The values in the Output tab will be populated based on the values passed to the fields of the objects in theInput tab. If the process execution completes successfuly, you can see the output, otherwise a Fault will bedisplayed.

Fault

In the Fault tab, you can find the error message and error message code of the Invoke Integration Objectactivity. See the Error Codes topic for more detailed explanation of errors.

The following table lists the error schema elements in the Fault tab of the Invoke Integration Object activity:


SiebelPluginException String Will display an exception at runtime if the user hasselected the attributes, has not assigned any valuesto the attributes, and is trying to perform the Insert,Upsert, Query, or Delete operation.


Invoke Workflow ActivityYou can use the InvokeWorkflow Activity to perform operations on the Integeration object or Non-Integration object through the workflow process which exists on the Siebel server.

General

The following table lists the configurations in the General tab of the Invoke Workflow activity:




35



Workflow Process The following workflow processes are supported:

● TIBCO Sample Workflow Invocation from

Subscriber for Integration Object

● TIBCO Sample Workflow Invocation from

Subscriber

1. Type TIBCO* in the Workflow Process field.

2. Click Fetch. The Workflow Process dialog isdisplayed.

3. Select the value TIBCO Sample Workflow Invocationfrom Subscriber for Integration Object.

4. Click OK.

Server Request When checked, the workflow process runs in theSiebel Server process space. If it is unselected, it runswithin the Object Manager process space. By defaultthis option is unchecked.

Async Workflow Request Check this checkbox if you want to invoke theworkflow asynchronously. If you check this checkbox,the Siebel plugin does not wait for the reply from theSiebel workflow. The Siebel plugin replies with theAsynchronous Workflow Request ID.

Integration Object Select the Yes item from this drop-down list if theSiebel workflow is using an Integration object. Thedefault value is Yes.

Integration Object Name Specify the object for reference created using theeditor. See the topic Creating a Siebel Schema usingthe Siebel Objects Editor for more details.



Description

In the Description tab, you can enter a short description for the Invoke Workflow activity.

Input


Duplication or adding multiple Item fields in the Input tab is not allowed as Siebel only supports a singleparent node. The parent child schema is not supported for the Workflow activity.

36


Output

The values in the Output tab will be populated based on the values passed to the fields of the objects in theInput tab. If the process execution completes successfuly, you can see the output, otherwise a Fault will bedisplayed.

Fault

In the Fault tab, you can find the error message and error message code of the Invoke Workfow activity. Seethe Error Codes topic for more detailed explanation of errors.

The following table lists the error schema elements in the Fault tab of the Invoke Workflow activity:


SiebelPluginException String Will display an exception at runtime if the user hasexecuted the activity by selecting the workflowprocesses and has not given values to any of theattributes in the Input tab.


37


Migrating Projects

You can migrate a Siebel Adapter and TIBCO ActiveMatrix BusinessWorks 5.x project created in TIBCODesigner™ to TIBCO ActiveMatrix BusinessWorks 6.x or TIBCO BusinessWorks™ Container Edition studioby using the migration tool in TIBCO Business Studio. You can migrate a TIBCO ActiveMatrixBusinessWorks 5.x project to a TIBCO ActiveMatrix BusinessWorks 6.x project but migration in the otherdirection is not supported.

● In addition to the notes mentioned, it is a good practice to review the TIBCO ActiveMatrix BusinessWorks6.x Migration guide for additional information such as naming conventions, and more.

● Migration is based on the information received from the AE activities. The Invoke an Adapter Request-Response Service and Publish to Adapter AE activities are supported for migration.

Below notes should be considered before migrating from TIBCO ActiveMatrix BusinessWorks 5.x projectsto TIBCO ActiveMatrix BusinessWorks 6.x projects.

● Due to TIBCO ActiveMatrix BusinessWorks 5.x project structure and the migration process, there aresome files in the TIBCO ActiveMatrix BusinessWorks 5.x project migrated to TIBCO ActiveMatrixBusinessWorks 6.x, but are not used and must be ignored. For example, - ae folder and ae2xsd.xsdunder Schemas folder, AESchemas folder, etc.

● An EMF validation error occurs in the migrated TIBCO ActiveMatrix BusinessWorks™ 6.x project whenone TIBCO ActiveMatrix BusinessWorks™ 5.x project is saved with another name and these two projectsare migrated to the plug-in. To resolve this issue, delete the Namespaces/Imports from Process >Dependencies.

● After migration, in TIBCO ActiveMatrix BusinessWorks™ 6.x project the shared resource created is atthe root level even if it is at a resource folder level in TIBCO ActiveMatrix BusinessWorks™ 5.x project

● For migration the command line data option must be used and the user workspace directory andTIBCOActiveMatrix BusinessWorks™ 6.x target directory should be the same. For example, bwmigrator.exe -data <user workspace> -projectDir <BusinessWorks 6.x target directory> <BusinessWorks

5.x project location>

The CLI migration is not supported for Invoke Request Response AE Activity migration.

● Migration supports online schema migration, which means it retrieves the schema from the Siebel serverduring migration for the respective activity. Before migrating a project, ensure that the connectionparameters provided are correct in the project or in JSON reference file, otherwise errors might occurpost migration.

● Module property is migrated to TIBCO ActiveMatrix BusinessWorks 6.x project only if it is created inTIBCO ActiveMatrix BusinessWorks 5.x project and is referred in one of the TIBCO ActiveMatrixBusinessWorks 5.x projects or it must be referred in JSON file.

Migrating Projects from Adapter to Plug-inYou can migrate TIBCO ActiveMatrix® Adapter for Siebel projects created in TIBCO Designer™ to TIBCOActiveMatrix BusinessWorks™ Plug-in for Siebel Solutions in the following manner. Before migration,backup the original TIBCO ActiveMatrix BusinessWorks™ 5.x projects.

Procedure

1. Start TIBCO Business Studio.

2. Click Project tab and select Migrate BW Projects.

3. In the Project Migration Wizard, click Browse in the Select Project(s) to be Migrated field and select theproject you want to migrate. The default selection is Migrate Single BusinessWorks 5.x Project.

38


4. Click Migrate Multiple BusinessWorks 5.x Projects to migrate multiple 5.x projects. During migration ifthe Migrate as Shared Module check box is selected it can be migrate project as a shared module.

5. Click Migrate Project. After the migration is complete, click Finish.

Adapter services contain the components like Integration Component or Business Componentand it is migrated only when you map the respective adapter service in the AE activity on theprocess.

Migrating Siebel Adapter Configuration to Siebel Connection Resource inPlug-in

You can migrate Siebel adapter configuration from TIBCO ActiveMatrix® Adapter for Siebel projectscreated in TIBCO Designer™ to Siebel connection resource in TIBCO ActiveMatrix BusinessWorks™ Plug-infor Siebel in the following manner:

Procedure


2. Click on the Project tab and select Migrate BW Projects.

3. In the Migration Project Type section, the default selection is Migrate Single BusinessWorks 5.x Project.Select the Migrate as Shared Module check box to migrate the 5.x projects as a shared resource.

4. Click Migrate Project. After the migration is complete, click Finish. The migration of adapterconfigurations of TIBCO ActiveMatrix BusinessWorks 5.x projects to a shared resource in TIBCOActiveMatrix BusinessWorks 6.x projects.

Migrating Projects With Invoke an Adapter Request-Response Service Activityand Request-Response Service

You can migrate your projects that use the Invoke an Adapter Request-Response Service activity of fromActiveEnterprise Adapter palette and Request-Response Service of TIBCO ActiveMatrix® Adapter forSiebel to one of the four Siebel Activities in TIBCO ActiveMatrix BusinessWorks™ Plug-in for Siebel. TheSiebel plugin Activity type is based on the type that you have selected in Request-Response adapter Servicein BW5.x.

● If you select Business Component then Invoke Business Object Activity is generated by BW6.

● If you select Integration Component then Invoke Integration Object Activity is generated by BW6.

● If you select Invoke Workflow then Invoke Workflow Activity is generated by BW6.

● If you select Business Service then Invoke Business Service Activity is generated by BW6.

An additional mapper activity is created after the BW6 Siebel plugin activity. This activity is configuredwith schema from the ActiveEnterprise Adapter palette. The mapper activity acts as a wrapper and helpsretain input mappings in the following activities. You must provide inputs for the mapper activitymanually.

After migration, the Update Siebel Business Component with Request-Response Service converts intoUpsert operation for Invoke Business Object Activity.

Procedure


2. Click the Project tab and select Migrate BW Projects.

39


3. In the Project Migration Wizard, the default selection is Migrate Single BusinessWorks 5.x Project in theMigration Project Type section. Click Migrate Multiple BusinessWorks 5.x Projects to migrate mutliple5.x projects.

4. In the Select Project Location section, click Browse in the Select Project(s) to be Migrated field andselect the project to be migrated.

5. Click Migrate Project. After the migration is complete, click Finish. All the migrated projects aredisplayed in the Project Explorer view at the parent level.All the schemas defined under AESchemas folder of the TIBCO ActiveMatrix BusinessWorks 5.x projectare not migrated. In the Configuration tab of the Invoke Adapter Request Response Service activity inTIBCO ActiveMatrix® Adapter for Siebel, an Adapter Service should be mentioned for migration.Only the schema that is referenced by the Invoke Adapter Request Response Service activity is fetchedduring migration. All the configurations of the Invoke an Adapter Request Response Service activityand Request Response Adapter Service is migrated to respective fields of BW6 Siebel plugin activityunder the General tab.In the General tab of the migrated Siebel plugin activity, the migrated shared resource is mapped to theshared resource field. The schema selected in the Invoke an Adapter Request Response Service activityis mapped to Siebel Object Reference of the migrated Siebel activity. While migrating the projectschema is fetched from server and stored in Siebel Object Editor.If schema selected in the Invoke an Adapter Request Response Service activity is from Request SchemaReference of type Invoke Business Service in Request-Response Adapter service, then the same ismigrated.

6. To run the migrated project, click Run > Debug Configurations from the menu bar.

7. In the Debug Configurations windows, click Debug.

Request-Response Service Fields Not Supported for Migration

When migrating projects from TIBCO ActiveMatrix® Adapter for Siebel to TIBCO ActiveMatrixBusinessWorks™ Plug-in for Siebel there are some fields in the adapter services (Request-Response Service)of the Siebel Adapter configuration that may default or are not supported during migration. The followingfields are not supported on the Configuration tab of the Request-Response Service in TIBCO ActiveMatrix®Adapter for Siebel during migration:

● Business Event● Transport Type● Quality of Service● Wire Format● UAN Schema Support● Integration Object Name (in case of Invoke Siebel Workflow)● Reply Schema Reference (in case of Siebel Invoke Business Service)

The fields in the Business Event Schema tab of the Request-Response Service in TIBCO ActiveMatrix®Adapter for Siebel is supported through Siebel Object Editor of the Siebel Plugin. While migrating theproject, Schema is fetched from Siebel Server and saved in the Siebel Object Editor of the Siebel Plugin.

The following fields are not supported on the Advanced tab of the Request-Response Service in TIBCOActiveMatrix® Adapter for Siebel during migration:

● Message Subject● Endpoint Reference● Class Reference

40


Invoke an Adapter Request-Response Service Activity Fields Not Supported for MigrationWhile migrating projects from TIBCO ActiveMatrix® Adapter for Siebel to TIBCO ActiveMatrixBusinessWorks™ Plug-in for Siebel there are some fields in the Invoke an Adapter Request- ResponseService activity of the Siebel Adapter Configuration that may default or are not supported during migrationare listed below. The following fields are not supported on the Configuration tab of the Invoke an AdapterRequest-Response Service Activity in TIBCO ActiveMatrix® Adapter for Siebel during migration:

● Adapter Service

● Operation

● On Way

The following tabs of the Invoke an Adapter Request-Response Service activity are not supported formigration:

● Transport tab

● Input tab

● Output tab

● Error Output tab

Migrating Projects With Publish to Adapter Activity and Subscription ServiceYou can migrate your projects that use the Publish to Adapter from ActiveEnterprise Adapter palette andSubscription Service in TIBCO ActiveMatrix® Adapter for Siebel to one of the four Siebel Activities inTIBCO ActiveMatrix BusinessWorks™ Plug-in for Siebel. The Siebel plugin Activity type is based on thetype that selected in Request-Response adapter Service in BW5.x.

● If you select Business Component then Invoke Business Object Activity is generated by BW6.

● If you select Integration Component then Invoke Integration Object Activity is generated by BW6.

● If you select Invoke Workflow then Invoke Workflow Activity is generated by BW6.

● If you select Business Service then Invoke Business Service Activity is generated by BW6.

After migration, the Update Siebel Business Component with Subscription Service converts into Upsertoperation for Invoke Business Object Activity.

Procedure


2. Click the Project tab and select Migrate BW Projects.

3. In the Project Migration Wizard, the default selection is Migrate Single BusinessWorks 5.x Project in theMigration Project Type section. Click Migrate Multiple BusinessWorks 5.x Projects to migrate mutliple5.x projects.

4. In the Select Project Location section, click Browse in the Select Project(s) to be Migrated field andselect the project to be migrated.

5. Click Migrate Project. After the migration is complete, click Finish. All the migrated projects aredisplayed in the Project Explorer view at the parent level.All the schemas defined under AESchemas folder of the TIBCO ActiveMatrix BusinessWorks 5.x projectare not migrated. In the Configuration tab of the Publish to Adapter activity in TIBCO ActiveMatrix®Adapter for Siebel, an Adapter Service must be mentioned for migration. Only the schema that isreferenced by the Publish to Adapter activity is refetched during migration.

41


All the configurations of the Publish to Adapter activity and Subscription service are migrated torespective fields of BW6 Siebel plugin activity under General tab. In the General tab of the migratedSiebel plugin activity, the migrated shared resource is mapped to the shared resource field.

The schema selected in the Publish to Adapter activity is mapped to Siebel Object Reference of themigrated Siebel activity. While migrating the project schema is fetched from server and stored in SiebelObject Editor in Siebel Plug-in.

If the schema selected in the Publish to Adapter activity is from Request Schema Reference oftype Invoke Business Service in the Subscription Adapter service, then same is migrated toplugin and mapped to Request Schema Reference in Invoke Business Service.

6. To run the migrated project, click Run > Debug Configurations from the menu bar.

7. In the Debug Configurations windows, click Debug.

Subscription Service Fields Not Supported For Migration

When migrating projects from TIBCO ActiveMatrix® Adapter for Siebel to TIBCO ActiveMatrixBusinessWorks™ Plug-in for Siebel there are some fields in the adapter services (Subscription Service) of theSiebel Adapter configuration that may default or are not supported during migration. The following fieldsare not supported on the Configuration tab of the Subscription Service in TIBCO ActiveMatrix® Adapterfor Siebel during migration:

● Business Event

● Transport Type

● Quality of Service

● Wire Format

● UAN Schema Support

● Integration Object Name (in case of Invoke Siebel Workflow)

The fields in the Business Event Schema tab of the Subscription Service in TIBCO ActiveMatrix® Adapterfor Siebel is supported through Siebel Object Editor of the Siebel Plugin. While migrating the project,Schema is fetched from Siebel Server and saved in the Siebel Object Editor of the Siebel Plugin.

The following fields are not supported on the Advanced tab of the Request-Response Service in TIBCOActiveMatrix® Adapter for Siebel during migration:

● Message Subject

● Endpoint Reference

● Class Reference

Publish to Adapter Activity Fields Not Supported For MigrationWhile migrating projects from TIBCO ActiveMatrix® Adapter for Siebel to TIBCO ActiveMatrixBusinessWorks™ Plug-in for Siebel there are some fields in the Publish to Adapter Activity of the SiebelAdapter Configuration that may default or are not supported during migration. The following fields are notsupported on the Configuration tab of the Publish to Adapter Activity in TIBCO ActiveMatrix® Adapterfor Siebel during migration:

● Adapter Service

● Custom AESchema

● Custom AESchema Reference

● RequestReply

42


The following tabs of the Publish to Adapter activity in TIBCO ActiveMatrix® Adapter for Siebel are notsupported for migration:

● Transport tab● Input tab● Output tab● Error Output tab

Working with Preference File (JSON) For MigrationWhen a user wants to migrate a TIBCO ActiveMatrix BusinessWorks 5.x project to a TIBCO ActiveMatrixBusinessWorks 6.x project or TIBCO BusinessWorks™ Container Edition project and if they want to use thefeature of preferences, then a adapter2plugin.json file would need to be created in the root folder of TIBCOActiveMatrix BusinessWorks 5.x project. A template of the preference file would be installed in the toolsfolder of the plug-in in the following location:

$TIBCO_HOME/bw/palettes/siebel/version/tools/adapter2plugin.json_template

A preference file (JSON format) can be used in the following manner:

● To override configuration defined in the TIBCO ActiveMatrix BusinessWorks 5.x project and the adapterservices carried over to the plug-in.

● To provide the configuration available in the plug-in but not available in TIBCO ActiveMatrixBusinessWorks 5.x project.

● The JSON preference file template must be used for reference only and should not be modified or usedas it is. The preference file should be edited with the necessary properties and their correspondingvalues.

● The file created under the root folder of the TIBCO ActiveMatrix BusinessWorks™ 5.x projects does notjust contain Siebel but also other plug-ins that supports adapter migration. In terms of values, the valuescan either be literals or references to module properties, which would pertain to global variables fromTIBCO ActiveMatrix BusinessWorks 5.x project.

To configure as a Literal Value:

To set the value of host of client object of SiebelConnection or SiebelConnectionResource tosiebel17:2321 in JSON file, set the values as:

"host": "siebel17:2321"

To configure as a Module Property:

To use a global variable in JSON file, you must have the same global variable declared with a value in thecorresponding TIBCO ActiveMatrix BusinessWorks™ 5.x project. Then you can add the global variable inJSON file. To set the value of host of client object of SiebelConnection orSiebelConnectionResource to siebel17:2321 using JSON file as a global variable, add a global variable inTIBCO ActiveMatrix BusinessWorks™ 5.x project as Host and set the value as siebel17:2321. Now in theJSON file, set the value as:

"host" : "%%Host%%"

The following notes must be considered prior to using the JSON preference files for a TIBCOActiveMatrix™ 5.x project.

● The location and filename of the adapter2plugin.json preference file is not configurable.● The usage of the preference file does not support the creation of new module properties in migrated

projects. For example, you must not specify a module property %%test%% in the preferences if it doesnot exist in the TIBCO ActiveMatrix BusinessWorks 5.x project.

● The usage of preference file is applicable to all adapter configurations in the TIBCO ActiveMatrixBusinessWorks 5.x project during migration.

43


● Since the module properties in TIBCO ActiveMatrix BusinessWorks 6.x project are case sensitive, themodule properties in the preference file should have the same case as the TIBCO ActiveMatrixBusinessWorks 5.x project.

● When any value is applied from the preference file, the MigrationReport.log contains logs with key inuppercase and value as is, this is a recommendation but not mandatory.

● The password used in the JSON file must be obfuscated. The bwobfuscator utility in the<TIBCO_HOME>/bw/version/bin folder must be used to obfuscate the password. Any other passwordobfuscators do not work. For more information about how to use the bwobfuscator, see TIBCOActiveMatrix™ BusinessWorks Application Developement guide.

44


Working with the Sample Projects

This section describes about the Siebel sample projects.

Importing Sample ProjectsBefore running a sample project, you have to import it to TIBCO Business Studio™.

Procedure


2. From the menu bar, click File > Import.

3. In the Import dialog, expand the General folder, and then click Existing Studio Projects intoWorkspace. Click Next.

4. In the Import Projects dialog, click Select archive file, and then click Browse next to it to locate a sampleproject. For example, select the siebel_plugin_examples.zip file, and then click Open.

The sample projects are located in the TIBCO_HOME/bw/palettes/siebel/version_number/samples directory.

5. Click Finish.

After importing the examples, if you create a copy of Sample.sblObject and rename it toSample1.sblObject, the renamed copy does not behave like an isolated copy because itcontinues to reference the activities of the original.

Result

The siebel_plugin_examples project is imported to TIBCO Business Studio.

45


Setting Up the ProjectBefore running the project, you have to set it up.

Prerequisites

You have to import the sample_plugin_examples project before setting it up. For more information, see the Importing Sample Projects topic.

Procedure

1. Expand the imported project in the Project Explorer view.

2. Expand the Module Descriptors resource, and then double-click Module Properties.

3. The values are stored here. You can modify the values if needed.

4. From the menu bar, click File > Save to save the project.

Sample Projects for Invoke Business Object ActivityThis section describes the sample projects for Invoke Business Object Activity.

The following sample projects are described in this section:

● Sample Plug-in Project for Invoke Business Object Activity

● Sample Plug-in Project to show the Parent-Child Relationship using Invoke Business

● Sample Plug-in Project for Invoke Business Object Activity with Multi-Value Link

Sample Plugin Project for Invoke Business Object ActivityYou can use the example businessobject.bwp to understand how the Invoke Business Object activitybehaves. The example shows the Insert, Upsert, Query, and Delete operation on the business object.

The following figure describes the Invoke Business Object activity process:

Example for Invoke Business Object Activity Process

The Invoke Business Object Activity process performs the following operations:

● The Insert operation inserts the value for the field or fields that are defined in the schema.

46


● The Upsert operation upserts the value for the field or fields that are defined in the schema. The Upsertoperation inserts the value for the fields that are defined in the schema if the record does not exist, andupdates the value for the fields if the record exists.

● The Query operation queries or searches the field or pattern that is defined in the schema.

● The Delete operation deletes the value for the field, or fields that are defined in the schema.

Running the Project

To run the project for the Invoke Business Object activity process, perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > sample_plugin_project resource, and then double-click businessobject.bwp.

2. Click Run > Debug Configurations...The Debug Configurations dialog opens.

3. Expand the BusinessWorks Application option and select BWApplication.

4. In the Applications tab, all processes will be selected. Click the Deselect All button and select thesample_plugin_object.businessobject option.

5. Click the Apply button and click the Debug button.

6. Click Debug to run the process.

7. Click the icon to stop the process.

Sample Plug-in Project to show the Parent-Child Relationship using Invoke BusinessObject Activity

You can use the example parentChild_businessObject.bwp to understand how the parent-childrelationship works using the Invoke Business Object activity. The example shows the Insert, Upsert, andQuery operation on the business object.

The following figure describes the parent-child relationship using the Invoke Business Object activityprocess:

Example for Parent-Child Relationship using the Invoke Business Object Activity Process

The following figure shows the parent-child relationship established using the Siebel Objects Editor:

47


Example for Establishing Parent-Child Relationship using Siebel Objects Editor





● The Log stores the logs of the operations performed.

Running the Project

To run the project for the Parent-Child Business Object process, perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > sample_plugin_project resource, and then double-click parentChild_businessObject.bwp.



4. In the Applications tab, all processes will be selected. Click the Deselect All button and select thesample_plugin_object.parentChild_businessObject option.




48


Sample Plugin Project for Invoke Business Object Activity with Multi-Value LinkYou can use the example InvokeBO_MVL.bwp to understand how the Invoke Business Object activitybehaves. The example shows the Insert, Upsert, Query, and Delete operation on the business object.






● The Delete operation deletes the value for the field, or fields that are defined in the schema.

49


Running the Project

To run the project for the Invoke Business Object activity with a multi-value link, perform the followingsteps:

Procedure

1. In the Project Explorer view, expand the Processes > invoke_business_object resource, and thendouble-click InvokeBO_MVL.bwp.



4. In the Applications tab, all processes will be selected. Click Deselect All and select theinvoke_business_object.InvokeBO_MVL option.

5. Click Apply and click Debug.



Sample Projects for Invoke Business Service ActivityThis section describes the sample projects for Invoke Business Service Activity.


● Sample Plug-in Project for Invoke Business Service Activity

● Sample Plug-in Project for Custom Business Service Parent-Child Relationship

● Sample Plug-in Project for Custom Business Service Write XML

● Sample Plug-in Project for Invoke Parent-Child Relationship with Integration Object

Sample Plugin Project for Invoke Business Service ActivityYou can use the example businessservice.bwp to understand how the Invoke Business Service activitybehaves. The example shows the Insert, Upsert, Update, Query, and Delete operation on the workflow.


The following figure describes the Invoke Business Service activity process:

50


Example for Invoke Business Service Activity Process

The Invoke Business Service Activity process performs the following operations:



● The Update operation updates the value for the field or fields that are defined in the schema.


● The Delete operation deletes the value for the field or fields that are defined in the schema.

Running the Project

To run the project for the Invoke Business Service activity process, perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > sample_plugin_project resource, and then double-click businessservice.bwp.



4. In the Applications tab, all processes will be selected. Click the Deselect All button and select thesample_plugin_object.businessservice option.




51


Sample Project to show the Custom Business Service Parent-Child RelationshipYou can use the example CustomBS_ParentChild.bwp to understand how the parent-child relationshipworks using the Invoke Business Service activity. The example shows the sample project to show theCustom Business Service Parent-Child Relationship.








Running the Project

To run the project for the Custom schema for Integration Component of Invoke Business Service activity,perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > invoke_business_service resource, and thendouble-click CustomBS_ParentChild.bwp.



4. In the Applications tab, all processes will be selected. Click the Deselect All button and select theinvoke_business_service.CustomBS_ParentChild.bwp option.



52



Sample Project to Show the Custom Business Service Write XMLYou can use the example CustomBS_WriteXML.bwp to understand how the XML Write to File Businessservice invoked using the Business Service activity.

The following figure shows the Custom Business Service Write XML using the Siebel Objects Editor:

This is application invokes the WriteEAIMsg Business Service Method of EAI XML Write to FileBusiness Service and create the file in Siebel Server with input parameters populated in the Input tab of theInvoke Business Service Activity.

Running the Project

To run the project for the Invoke Business Service activity Write XML process, perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > invoke_business_service resource, and thendouble-click CustomBS_WriteXML.bwp.



53


4. In the Applications tab, all processes will be selected. Click the Deselect All button and select theinvoke_business_service.CustomBS_WriteXML.bwp option.




Sample Project to show the Invoke Parent-Child Relationship with Integration ObjectYou can use the example Invoke_BS_ParentChild.bwp to understand how the parent-child relationshipwith multi-value link works using the Invoke Business Service activity. The example shows the Insert,Upsert, Update, Query and Delete operation on Sample Account and child Contact Integration Component.





54






Running the Project

To run the project for the Parent child Integration component of the Invoke Business Service activityprocess, perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > invoke_business_service resource, and thendouble-click Invoke_BS_ParentChild.bwp.



4. In the Applications tab, all processes will be selected. Click the Deselect All button and select theinvoke_business_service.Invoke_BS_ParentChild.bwp option.




Sample Projects for Invoke Integration Object ActivityThis section describes the sample projects for Invoke Integration Object Activity.


● Sample Plug-in Project for Invoke Integration Object Activity

● Sample Plug-in Project for Parent-Child Relationship using the Invoke Integration Object Activity

Sample Plugin Project for Invoke Integration Object ActivityYou can use the example integrationobject.bwp to understand how the Invoke Integration Objectactivity behaves. The example shows the Insert, Upsert, Update, Query, and Delete operation on theintegration object.

The following figure describes the Invoke Integration Object activity process:

55


Example for Invoke Integration Object Activity Process

The Invoke Integration Object Activity process performs the following operations:






Running the Project

To run the project for the Invoke Integration Object activity process, perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > sample_plugin_project resource, and then double-click integrationobject.bwp.



4. In the Applications tab, all processes will be selected. Click the Deselect All button and select thesample_plugin_object.integrationobject option.




56


Sample Project for Parent-Child Relationship using the Invoke Integration Object ActivityYou can use the example InvokeIO_ParentChild.bwp to understand how the parent-child relationshipworks using the Invoke Integration Object activity. The example shows the Insert, Upsert, Update, Delete,and Query operation on the business object.


The Invoke Integration Activity process performs the following operations:


57







Running the Project

To run the project for Parent child combination of Integration component in the Invoke Integration Objectactivity process, perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > invoke_integration_object resource, and thendouble-click InvokeIO_ParentChild.bwp.



4. In the Applications tab, all processes will be selected. Click the Deselect All button and select theinvoke_integration_object.invokeIO_ParentChild option.




Sample Projects for Invoke Workflow ActivityThis section describes the sample projects for Invoke Workflow Activity.


● Sample Plug-in Project for Invoke Workflow Activity

● Sample Plug-in Project for Non-Integration Object Invoke Workflow Activity

Sample Plugin Project for Invoke Workflow ActivityYou can use the example workflow.bwp to understand how the Invoke Workflow activity behaves. Theexample shows the use of TIBCO Sample Workflow Invocation from Subscriber for IntegrationObject_Insert and TIBCO Sample Workflow Invocation from Subscriber for IntegrationObject_Delete workflows which performs the Insert and Delete operations on the Integration Objectrespectively.

The following figure describes the Invoke Workflow activity process:

58


Example for Invoke Workflow Activity Process

● The workflow process TIBCO Sample Workflow Invocation from Subscriber for IntegrationObject_Insert inserts the value for the field or fields that are defined in the input schema.

● The workflow process TIBCO Sample Workflow Invocation from Subscriber for IntegrationObject_Delete deletes the value for the field or fields that are defined in the input schema.

Running the Project

To run the project for the Invoke Workflow activity process, perform the following steps:

Procedure

1. In the Project Explorer view, expand the Processes > sample_plugin_project resource, and then double-click workflow.bwp.



4. In the Applications tab, all processes will be selected. Click the Deselect All button and select thesample_plugin_object.workflow option.




Sample Project for Non-Integration Invoke Workflow ActivityYou can use the example invoke_workflow_NonIO.bwp to understand how the Invoke Workflow for non-input-output activity behaves.

This example shows a sample workflow using the input process property in a workflow step to generate anXML file using the following service methods: Write Property Set of the Siebel Business Service, EAI XMLWrite to File.

After the execution of this example, verify that the output XML file c:\propertySetData.xml is generatedat the Siebel server.

The following figure describes the Non-Integration Invoke Workflow Activity:

59


The example shows the use of TIBCO Sample Workflow Invocation from Subscriber workflow whichcreates the file with the content provided in the Input tab of the Invoke Workflow activity in the Siebelserver.

Running the Project

To run the project for Non-integration Object of the Invoke Workflow activity process, perform thefollowing steps:

Procedure

1. In the Project Explorer view, expand the Processes > invoke_workflow resource, and then double-clickinvoke_workflow_NonIO.bwp.



4. In the Applications tab, all processes will be selected. Click Deselect All and select theinvoke_workflow.invoke_workflow_NonIO option.

5. Click Apply and click Debug.



60


Invoking a Siebel Workflow

This chapter describes the method to import the Workflow process at Siebel server. You can invoke theWorkflow through the given sample examples.

Workflow with Integration Object

These workflows are used to Insert and Delete the data into Siebel Integration Objects on Siebel Server.

SIEBEL_HOME\samples\workflow

\7TIBCOSampleWorkflowInvocationfromSubscriberforIntegrationObjects_Insert.xml

SIEBEL_HOME\samples\workflow

\7TIBCOSampleWorkflowInvocationfromSubscriberforIntegrationObjects_Delete.xml

These workflows are used in the sample plug-in project for Invoke Workflow Activity. For moreinformation, see Sample Plugin Project for Invoke Workflow Activity

Workflow with Non Integration Object

This workflow is used to create the XML file at Siebel server by using the EAI XML Write to File BusinessService.

SIEBEL_HOME\samples\workflow\TIBSiebelAdapterWorkflowSubInvoke.xml

This workflow is used in the sample project sample project for Non-Integration Invoke Workflow Activity.For more information, see Sample Project for Non-Integration Invoke Workflow Activity

Importing the Workflow ProcessPerform the following steps to import the workflow process on the Siebel Server:

Procedure

1. Start the Siebel Tools and log in.

2. Click Workflow Process.

3. Right click in the Workflow Processes window and click Import Workflow Process in the menu.

4. Go to the SIEBEL_HOME\samples\workflow\ and select TIBSiebelAdapterWorkflowSubInvoke.xml.

5. Right click the TIBCO sample workflow Invocation from Subscriber from the list of Workflow Processesand select Edit Workflow Process in the menu.

61


6. Double click the workflow step Write Data to XML File.

62


Management of Logs

When an error occurs, you can check logs to trace and troubleshoot the plug-in exceptions.

By default, error logs are displayed in the Console view when you run a process in debug mode. You canchange the log level of the plug-in to trace different messages and export logs to a file. Different log levelscorrespond to different messages, as described in the topic Log Levels.

Log LevelsDifferent log levels include different information.

The plug-in supports the following log levels:

Log Level Description

Trace Includes all information regarding the running process.

Debug Indicates a developer-defined tracing message.

Info Indicates normal plug-in operations. No action is required. A tracing message taggedwith Info indicates that a significant processing step is reached, and logged for trackingor auditing purposes. Only info messages preceding a tracking identifier are consideredas significant steps.

Warn Indicates that an abnormal condition occurred. Processing continues, but for bestpractice, you can contact the administrator to investigate it.

Error Indicates that an unrecoverable error occurred. Depending on the severity of the error,the plug-in might continue with the next operation or might stop.

Setting up Log LevelsYou can configure a different log level for the plug-in and plug-in activities to trace different messages.

If you do not configure any log levels, the plug-in uses the default log level of TIBCO ActiveMatrixBusinessWorks. The default log level is ERROR.

Procedure

1. Navigate to the TIBCO_HOME/bw/version_number/config/design/logback directory and open thelogback.xml file.

2. Add the following node in the BusinessWorks Palette and Activity loggers area to specify a log levelfor the plug-in:<logger name="com.tibco.bw.palette.siebel.runtime"> <level value="DEBUG"/></logger>

The value of the level element can be Error, Info, or Debug.

If you set the log level to Debug, the input and output for the plug-in activities are alsodisplayed in the Console view. See the topic Log Levels for more details regarding each loglevel.

63


3. Optional: Add the following node in the BusinessWorks Palette and Activity loggers area to specify alog level for an activity:<logger name="com.tibco.bw.palette.siebel.runtime.ActivityNameActivity"> <level value="DEBUG"/></logger>

For example, you can set the log level to Debug for all the activities as follows:

● For the Invoke Business Object activity:<logger name="com.tibco.bw.palette.siebel.runtime.InvokeBOActivity"><level value="DEBUG"/></logger>

● For the Invoke Integration Object activity:<logger name="com.tibco.bw.palette.siebel.runtime.InvokeIOActivity"><level value="DEBUG"/></logger>

● For the Invoke Business Service activity:<logger name="com.tibco.bw.palette.siebel.runtime.InvokeBSActivity"><level value="DEBUG"/></logger>

● For the Invoke Workflow activity:<logger name="com.tibco.bw.palette.siebel.runtime.InvokeWFActivity"><level value="DEBUG"/></logger>

The activities that are not configured with specific log levels use the log level configured forthe plug-in.

4. Save the file.

Exporting Logs to a FileYou can update the logback.xml file to export plug-in logs to a file.

Procedure

1. Navigate to the TIBCO_HOME/bw/version_number/config/design/logback directory and open thelogback.xml file.

After deploying an application in TIBCO Enterprise Administrator, navigate to theTIBCO_HOME/bw/version_number/domains/domain_name/appnodes/space_name/

node_name directory to find the logback.xml file.

2. Add the following node to specify the file where the log is exported:<appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>c:/bw6-siebel.log</file> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36}-%msg%n</pattern> </encoder></appender>

The value of the file element is the absolute path of the file that stores the exported log.

3. Add the following node to the root node at the bottom of the logback.xml file:<root level="DEBUG"> <appender-ref ref="STDOUT" /> <appender-ref ref="FILE" /></root>

4. Save the file.

64


Error Codes

The following table lists error codes, detailed explanation of each error, and where applicable, ways to solvedifferent errors.

Error Code RoleCategory Description Solution

TIBCO-BW-PALETTE-Siebel-100015

Total execution time for Invoke

Business Object Activity :{0} ms

Trace BW-Plug-in

Displays the totalexecution timefor the InvokeBusiness ObjectActivity.

This is a tracemessage andresolution is notapplicable.



Business Object Activity :{0} ms

Trace BW-Plug-in

Displays the totalexecution timefor the InvokeIntegrationObject Activity.




Business Service Activity :{0}

ms

Trace BW-Plug-in

Displays the totalexecution timefor the InvokeBusiness ServiceActivity




WorkFlow Activity :{0} ms

Trace BW-Plug-in

Displays the totalexecution timefor the InvokeWorkFlowActivity.



{0} method, on

MatchFiledOperation failed for

BusComp={1}, Error message:{2}

Trace BW-Plug-in

Logging Buscomp details onmissing matchfield



{0} method, executeQuery breaks,

with query criteria={1} for

BusComp [{2}]

SiebelException:={3}

Trace BW-Plug-in

Logging buscomp objectdetails, querycriteria on failureof queryoperation.



{0} method, executeQuery returns

false, with query criteria={1}

for BusComp [{2}]

Trace BW-Plug-in

Returned falsevalue byExecuteQuerymethod



{0} method, Done the query with

criteria={1} for BusComp [{2}]

Trace BW-Plug-in

Logging theQuery criteriawith BusCompdetails


65




{0} method, Record not found

with query criteria, will do a

insert operation!

Trace BW-Plug-in

If record doesnot exist with aspecified querycriteria, then theInsert operationis performed.



{0} method, More than one record

found, with query criteria={1}

for BusComp [{2}], so no {3}

operation performed!

Trace BW-Plug-in

When multiplerecords arefound for theQuery criteria,the operation isaborted.



{0} method, received an existing

record with Id [{1}], will do

the update operation!

Trace BW-Plug-in

The updateoperation isperformed whena single record isfound during theupdatedoperation.



{0} method, {1} Query Result for

BusComp [{2}],RecordCount [{3}]

Trace BW-Plug-in

Number ofrecords found onSiebel serverbeforeperforminggiven operation.



{0} method, on Parent-Child

Operation failed for


Trace BW-Plug-in

Parent childdelete operationnot allowed.



{0} method, Done the query with

criteria={1}

Trace BW-Plug-in

Logging theQuery criteria.



{0} method, Done with query

criteria but no data found.


Trace BW-Plug-in

No record foundwith querycriteria provided.



Set Parent Child Search Spec for

BusComp={0},Attr={1},Value={2}

Trace BW-Plug-in

Shown when seta searchspecification forParent Childbussinesscomponent .


66




Set Search Spec for

{0}={1},Attr={2},Value={3}

Trace BW-Plug-in

Logging thesearchspecification



{0} method, input fields are

blank or null, Error message:{1}

Trace BW-Plug-in

Displayed on ablank input



{0} method, input fields are in

appropriate, so set Search Spec

is getting set to null,

{1}.getSearchExpr()={2} for {3}

[{4}]

Trace BW-Plug-in

Logging theinvalid searchspecification.



{0} method, obtain a

SiebelBusComp ={0}

Trace BW-Plug-in

Before writingthe buscompobject overserver loggingbuscomp objectdetails



{0} method, Record with Id [{1}]

of BusComp [{2}] has been

deleted!

Trace BW-Plug-in

Shown when arecord is deleted.



{0} method, field [{1}]

activated!

Trace BW-Plug-in

Fields areactivated beforeperforming anoperation.



{0} method, SetFieldValue: field

[{1}], value [{2}]

Trace BW-Plug-in

Field values areset beforeperforming anoperation



Done WriteRecord

{0}={1},Result={2}

Trace BW-Plug-in

Bus comp objectdetails afterwriting recordon server



{0} method, input Id={1}

Trace BW-Plug-in

BeforeperformingQuery operationlogging buscompID


67




{0} method, Record Result:

attrName [{1}], attrValue [{2}]

Trace BW-Plug-in

Showing theQuery result byBusComp Id



Before Save {0}={1}

Trace BW-Plug-in

Bus comp objectdetails beforeupdating recordon server



After Save {0}={1}, Result={2}

Trace BW-Plug-in

Bus comp objectdetails afterupdating recordon the serverwith resultreturned



{0} method, obtained parent

BusComp={1}

Trace BW-Plug-in

Shows businesscomponentdetails



{0} method, get parent buscomp

field name [{1}], field value

[{2}]

Trace BW-Plug-in

Shows bussinesscomponent fielddetails



Performing association for

busComp={0}

Trace BW-Plug-in

If record isalready presentin MVL thenassociation isperformed



Record already exist for busComp

{0}, Skipping insertion

operation for busComp {1}

Trace BW-Plug-in

If record alreadyexists theninsertion ofrecord is skippedin MVL


TIBCO-BW-PALETTE-Siebel- 200000

Siebel Activity {0} received

input:\n{1}

Debug

BW-Plug-in

Activity input isdisplayed

This is a debugmessage andresolution is notapplicable.


Siebel Activity {0} generated

output:\n{1}

Debug

BW-Plug-in

Activity outputis displayed


68




[ServerRequest : {0}],

[Asynchronous Server Request :

{1}], [Process Type : {2}],

[Service Name: {3}]

Debug

BW-Plug-in

Logs are visiblefor validatingtrue false valueforServerRequestandAsynchronousServer Request.Process Type andService Name aredisplayed.



No Data Provided for MVL [{0}],

Operation : [{1}].

Debug

BW-Plug-in

Invalid dataprovided forMVL operation.



Total number of record deleted :

{0}

Info BW-Plug-in

Total number ofrecords deletedover the server.

This is aninformation messageand resolution is notapplicable.


Retry attempt : {0}

Info BW-Plug-in

It tries toreconnect to theSiebel server fora specificnumber of times(Retry Connectvalue).

This is aninformation messageand resolution is notapplicable.


Association of BusComp [{0}]

Failed. [{1}]

Warn BW-Plug-in

Warning log isshown when anerror occursduring theassociation of analready presentrecord.

This is a warningmessage andresolution is notapplicable.


Not Parent/Child Match Field or

Value found for Business

Component: [{0}]

Error BW-Plug-in

Match-field isnot specified tothe parent andthe childattribute for theBusinessComponent.

Specify the match-field to the parentand child attribute ofthe BusinessComponent.


Insert operation failed on

business component. : [{0}]

Error BW-Plug-in

Refer the errormessage or theerror trace fordescription.

As per the errormessage, take theappropriate steps orrefer the Siebeldocumentation.

69




No Match Field found or Match

Field has empty or "" value for

Business Component: [{0}]

Error BW-Plug-in

Values are notprovided to thematch-fieldattribute for theBusinessComponent.

Specify the value forthe match-fieldattribute of theBusiness Component.


Input Search Criteria is blank

or null set for Business

Component:[{0}]

Error BW-Plug-in

Input parametersare NULL orblank for theBusinessComponent.

Specify values for theinput parameters.


No Record Found, for business

component:[{0}] :- Record not

available at Siebel server.

Error BW-Plug-in

No records arepresent in theSiebel server forthe inputparametersspecified for theBusinessComponent.

Specify differentvalues for the inputparameters.


Record already exist on business

component. : [{0}]

Error BW-Plug-in

Record with thesame values arealready presentin the Siebelserver for theBusinessComponent.

Provide uniquevalues for theattributes of theBusiness Component.


Error occurs when invoking

Integration Object Activity for

Method: [{0}], Siebel Error

Message: [{1}]

Error BW-Plug-in


As per the errormessage, takeappropriate steps orrefer the Siebeldocumentation.


Record already exist when

invoking Integration Object

Activity for Method: [{0}]

Error BW-Plug-in

Record with thesame values arealready presentin the Siebelserver for theIntegrationObject.

Provide uniquevalues for theattributes of theIntegration Object.

70




No Record Found, when invoking


Method: [{0}]

Error BW-Plug-in

No records arepresent in theSiebel server forthe inputparametersspecified for theIntegrationObject.



Record already exist when

invoking Invoke Business Service

Activity for Business Service:

[{0}], Method: [{1}]

Error BW-Plug-in

Record with thesame values arealready presentin the Siebelserver for theBusiness Service.

Provide differentvalues for theattributes of theBusiness Service.



Invoke Business Service Activity

for Business Service: [{0}],

Method: [{1}]

Error BW-Plug-in





Invoke Business Service Activity

for Business Service: [{0}],

Method: [{1}], Siebel Error

Message: [{2}]

Error BW-Plug-in





or null set for Invoke Business

Service Activity

Error BW-Plug-in

Input parametersare NULL orblank for theBusiness Service.

Specify the values forthe input parameters.



or null set for Invoke

Integration Object Activity

Error BW-Plug-in

Input parametersare NULL orblank for theIntegrationObject.

Specify the values forthe input parameters.

71




Multiple Records Found for

business component:[{0}], while

performing update operation, so

no update operation performed

Error BW-Plug-in

Updateoperation cannotbe performedwhen multiplerecords arepresent for theBusinessComponent inthe Siebel server.

Provide valid valuesfor the inputparameters. Thevalue should be aunique record andshould be present inthe Siebel server forperforming theupdate operation.


Error occurs on executeQuery api

of Siebel Business component:

[{0}]

Error BW-Plug-in




Error occurs on delete api of

Siebel Business component:[{0}]

Error BW-Plug-in




Error occurs on write api of

Siebel Business component:[{0}]

Error BW-Plug-in




No Matching record Found, when



[{0}], Method: [{1}]

Error BW-Plug-in

No matchingrecord wasfound in theSiebel server forthe providedinput paramtersfor the givenBusiness Serviceand method.

Provide valid valuesfor the inputparameters


No user key provided or user key

value is blank when invoking


Method:[{0}]

Error BW-Plug-in

Value for theuser key attributeis not providedor is kept blankfor theIntegrationObject.

Specify the value forthe user key attribute.

72





invoking Integration Object

Activity for Method: [{0}]

Error BW-Plug-in

No matchingrecord wasfound in theSiebel server forthe providedinput paramters,for theIntegrationobject, when theupdate operationwas performed.

Provide valid valuesfor the inputparameters of theIntegration Object.



is blank when invoking Invoke

Business Service Activity for

Business Service: [{0}], Method:

[{1}]

Error BW-Plug-in







[{0}], Method: [{1}]

Error BW-Plug-in

No matchingrecord wasfound in theSiebel server forthe providedinput paramters,for theIntegrationobject, when theupdate operationwas performedfor the BusinessService activity.




Invoke WorkFlow Activity for

WorkFlow Process: [{0}]

Error BW-Plug-in





Invoke WorkFlow Activity for

WorkFlow Process: [{0}], Siebel

Error Message: [{1}]

Error BW-Plug-in



73





is blank when invoking Invoke

WorkFlow Activity for WorkFlow

Process: [{0}]

Error BW-Plug-in





invoking Invoke WorkFlow

Activity for WorkFlow Process:

[{0}]

Error BW-Plug-in

No matchingrecord found insiebel server forthe inputparamtersprovided forIntegration objectwhenperformingupdate operationfor InvokeWorkflowactivity.



No key provided or key is blank.

[{0}]

Error BW-Plug-in

No matchingrecord wasfound in theSiebel server forthe providedinput paramters,for theIntegrationobject, when theupdate operationwas performedfor the InvokeWorkflowactivity.

Specify at least onekey attribute, orprovide values forthe key attribute ofthe BusinessComponent.


The username or password you

have entered is not correct.:

[{0}]

Configuration

BW-Plug-in

The username orpassword isincorrect.

Specify the correctusername orpassword.


Error occurs when connecting to

Siebel with Config: [{0}],

Detail: [{1}]

Configuration

BW-Plug-in

Theconfigurationdetails providedfor the Siebelconnection areincorrect.

Specify validconfiguration details.

74




Error in enabling SQL trace:

[{0}]

Error BW-Plug-in

Error occurswhen an invalidtrace file name oror an invalidtrace file path isprovided in theadvanced sectionof the SiebelConnection.

Provide valid tracefile name or path.


No value provided for SQL Trace

File: [{0}]

Error BW-Plug-in

Error occurswhen the "EnableSQL SiebelTrace" check-boxis checked andthe "SQL tracefile" is keptblank, or if thereis no inputprovided for theadvanced sectionof the SiebelConnection.

Specify SQL TraceFile in the advancedsection of the SiebelConnection.


Error occurs when performing

delete for Business Component:

[{0}].Delete is only allowed

with primary business component

that does not have child

objects.

Error BW-Plug-in

Delete operationcannot beperformed forthe BusinessObject that haschild objects.

Do not performdelete operation forthe primary BusinessComponent that hasany child object orchild objects.



or null set for Invoke WorkFlow

Activity.

Error BW-Plug-in

Input parametersare NULL orblank for theWorkflow.

Specify values for theinput parameters.


Given Input fields are

inappropriate for Business

Component:[{0}]

Error BW-Plug-in

Error occurswheninappropriateinput fields areselected for theBusinessComponent.

Provide appropriateinput fields of theBusiness Component.


Error processing Workflow

Activity, Invalid Operation

Code : [{0}].

Error BW-Plug-in

Occurs whenOperation codeused other than1,2,3,4.

Use operation codefrom 1,2,3,4 only.

75




Record already exists for MVL :

[{0}]

Error BW-Plug-in

Occurs whenMVL record isalready exist

Provide unique valuefor MVL record.


Error occurs on executeQuery api

of Siebel Business component

MVL:[{0}]

Error BW-Plug-in

Error occurswhileperforming theexecuteQueryoperation.

Contact the SiebelAdministrator.


Multiple Records Found for MVL:

[{0}], while performing update

operation, so no update

operation performed

Error BW-Plug-in

During updateoperation ifmultiple recordsare found thenerror occurs.

Provide record whichcan be uniquelyidentified.


Insert operation failed on

MVL. : [{0}]

Error BW-Plug-in

Occurs whenInsert operationfails for MVL



Error occurs on write api of

MVL:[{0}]

Error BW-Plug-in

Occurs when theWrite API callfails for MVL



Given Input fields are

inappropriate for MVG:[{0}]

Error BW-Plug-in

This error occurswhen the searchspecification isinvalid

Provide valid searchfields/keyfields


Error Occurred : {0}

Error BW-Plug-in

Generic errormessage

As per error need tofind error cause andsolution.


Input provided in {0} is blank.

Error BW-Plug-in

Occurs whenActivity input isblank.

Provide non emptyinput field values.

76


Legal and Third-Party Notices

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (ORPROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONSOF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSEAGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USERLICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THESOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCHSOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THELICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT ISSUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTEACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document is subject to U.S. and international copyright laws and treaties. No part of this documentmay be reproduced in any form without the written authorization of TIBCO Software Inc.

TIBCO, the TIBCO logo, TIB, Information Bus, Rendezvous, TIBCO Rendezvous, and TIBCO MessagingAppliance are either registered trademarks or trademarks of TIBCO Software Inc. in the United Statesand/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition(J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of OracleCorporation in the U.S. and other countries.

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

This software may be available on multiple operating systems. However, not all operating system platformsfor a specific software version are released at the same time. Please see the readme.txt file for the availabilityof this software version on a specific operating system platform.

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

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

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

This and other products of TIBCO Software Inc. may be covered by registered patents. Please refer toTIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.

Copyright © 2017-2020. TIBCO Software Inc. All Rights Reserved.

77


https://www.tibco.com/patents

Documents

BusinessWorks™ TIBCO ActiveMatrix Plug-in for Siebel User