P. 1
Business Studio Process Developer Guide

Business Studio Process Developer Guide

|Views: 2|Likes:
Published by Ravi Kumar

More info:

Published by: Ravi Kumar on Mar 19, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

05/13/2014

pdf

text

original

Sections

  • TIBCO Business Studio Documentation
  • Other TIBCO Product Documentation
  • Third Party Documentation
  • Typographical Conventions
  • How to Contact TIBCO Support
  • Chapter1 Getting Started
  • Who Should Use TIBCO Business Studio?
  • How TIBCO Business Studio Supports MDA
  • Implementation Approach
  • Hand Over from Business Analyst
  • BPM/SOA Implementation
  • Service Creation/Testing for Sub-Processes
  • Hand Off/Deployment
  • Process Testing
  • BPM/SOA Implementation Overview
  • User Tasks
  • Service Tasks
  • Database
  • Script Tasks
  • Deploying a Process
  • Tutorial Project
  • Tutorial 1: Elaborating a Process: User Tasks
  • Tutorial 2: Elaborating a Process: Service Tasks
  • Calling Web Services
  • Creating an E-Mail Task
  • Tutorial 3: Deploying a Process
  • Chapter2 Concepts and Definitions
  • Artifacts
  • Deployment
  • Module
  • Project Objects
  • Concept Model
  • Data Fields
  • Extended Attributes
  • Parameters
  • Participants
  • Standards Support
  • Business Process Modeling Notation (BPMN)
  • UML2
  • XML Process Definition Language (XPDL)
  • Chapter3 Tasks
  • Elaborating a User Task
  • Adding a Service Call
  • Working with UDDI Registries
  • Sending an Email
  • Making a Database Call
  • Creating a Script Activity
  • Associating a Script with a Conditional Flow
  • Timer Event Scripts
  • Calling Java Code
  • Complete the Parameter Mapping
  • Packaging a Process
  • Preparing a Process for Deployment
  • Creating a New Server
  • Connecting to a Server
  • Deploying a Module
  • Managing Deployed Modules
  • Changing Server Properties
  • Disconnecting from the Server
  • Chapter4 Reference
  • Properties View
  • User Task Properties
  • Service Task Properties (Web Service/BusinessWorks Service)
  • Service Task Properties (Email)
  • Service Task (Database)
  • Service Task (Java)
  • Script Task
  • Send and Receive Tasks
  • Process Validation
  • General Rules for Direct Deployment to the TIBCO iProcess Engine
  • Rules for Direct Deployment of Scripts
  • Correcting Validation Errors
  • Index

TIBCO Business Studio™ Process Developer’s Guide

Software Release 2.0 May 2007

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

Contents iii

|

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Business Studio Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Third Party Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 2 3

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Who Should Use TIBCO Business Studio? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 How TIBCO Business Studio Supports MDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Implementation Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hand Over from Business Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BPM/SOA Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Creation/Testing for Sub-Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hand Off/Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4 4 5 5 5

BPM/SOA Implementation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 User Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Service Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Script Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Deploying a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Tutorial Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Tutorial 1: Elaborating a Process: User Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Tutorial 2: Elaborating a Process: Service Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Calling Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Creating an E-Mail Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Tutorial 3: Deploying a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 2 Concepts and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Project Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

TIBCO Business Studio - Process Developer’s Guide

iv

| Contents
Concept Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standards Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Process Modeling Notation (BPMN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UML2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XML Process Definition Language (XPDL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 34 35 35 36 37 37 37 37

Chapter 3 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Elaborating a User Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Adding a Service Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Working with UDDI Registries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Sending an Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Making a Database Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Creating a Script Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Associating a Script with a Conditional Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Timer Event Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Calling Java Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Complete the Parameter Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Packaging a Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Deploying a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing a Process for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Deployed Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 66 66 67 68 72 72 74

Chapter 4 Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Properties View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Task Properties (Web Service/BusinessWorks Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Task Properties (Email) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Task (Database) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Task (Java) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send and Receive Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 76 77 78 81 82 84 84

Process Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

TIBCO Business Studio - Process Developer’s Guide

Contents v

|

General Rules for Direct Deployment to the TIBCO iProcess Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Rules for Direct Deployment of Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Correcting Validation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

TIBCO Business Studio - Process Developer’s Guide

vi

| Contents

TIBCO Business Studio - Process Developer’s Guide

|1 Preface This guide is aimed at the corporate developer who implements business processes designed by a business analyst. Topics • • • Related Documentation.Process Developer’s Guide . It describes how to elaborate a TIBCO Business Studio™ Process with execution details and how to deploy it to the runtime platform. page 4 How to Contact TIBCO Support. page 2 Typographical Conventions. page 5 TIBCO Business Studio .

or portal environment. existing HTML page. Concepts and Definitions explores the concepts and terminology related to TIBCO Business Studio.2 | Preface Related Documentation This section lists documentation resources you may find useful. TIBCO General Interface™ Builder. This documentation has the following main sections: • • • • Getting Started takes you through the basics of TIBCO Business Studio. Other TIBCO Product Documentation You may find it useful to read the documentation for the following products: • TIBCO iProcess Suite™. The object modeling features of TIBCO General Interface Builder enable developers to quickly create reusable GUI components and assemble them into full applications or application modules. including several tutorials. TIBCO Business Studio Documentation The TIBCO Business Studio documentation set consists of user’s guides for its main features such as modeling and simulation. The following documentation is also provided: • • TIBCO Business Studio Installation Guide: Read this manual for instructions on site preparation and installation. a development environment for building rich internet applications. Tasks describes common tasks that you perform using TIBCO Business Studio. TIBCO Business Studio Release Notes: Read the release notes for a list of new and changed features. a powerful process management engine designed to handle extremely high-volume. Applications can be accessed in a web browser from a URL. This document also contains lists of known issues and closed issues for this release. a comprehensive collection of process management software that includes modeling tools. Reference provides detail about the major components of TIBCO Business Studio such as the properties sheets and user interface (UI). mission critical transactions.Process Developer’s Guide . • TIBCO Business Studio . as well as tools for rules and analysis.

Related Documentation 3 | • TIBCO BusinessWorks™. Third Party Documentation The Eclipse help also contains useful information on the Workbench and the Eclipse UI. TIBCO Business Studio . and easy to use integration platform that allows you to develop integration projects. a scalable. extensible.Process Developer’s Guide . BusinessWorks™ includes a graphical user interface (GUI) for defining business processes and an engine that executes the process.

for example. a way to apply the information provided in the current section to achieve a specific result. to indicate the parts of the sample that are of particular interest. For example: A portal page may contain several portlets. to indicate what a user types. For example: Esc. if no parameter is specified. To introduce new terms. In large code samples. filenames. code examples. In command syntax. The warning icon indicates the potential for a damaging situation. TIBCO Business Studio . The tip icon indicates an idea that could be useful. For example: Use MyCommand to start the foo process. MyCommand is enabled: MyCommand [enable | disable] italic font Italic font is used in the following ways: • • • To indicate a document title. Ctrl+Q. For example: See TIBCO BusinessWorks Concepts. an additional action required only in certain circumstances. Portlets are mini-applications that run in a portal. for example.Process Developer’s Guide . For example: MyCommand pathname Key combinations Key name separated by a plus sign indicate keys pressed simultaneously. bold code font Bold code font is used in the following ways: • • • In procedures. Key names separated by a comma and space indicate keys pressed one after the other. data loss or corruption if certain steps are taken or not taken. for example. to indicate the default parameter for a command. For example. and output displayed in a command window.4 | Preface Typographical Conventions The following typographical conventions are used in this manual. The note icon indicates information that is of special interest or importance. For example: Type admin. pathnames. Table 1 General Typographical Conventions Convention code font Use Code font identifies commands. To indicate a variable in a command or code syntax that you must replace. For example: Ctrl+C.

For self-service support. visit this site: http://www.tibco. visit this site: http://support. • For an overview of TIBCO Support. and information about getting started with TIBCO Support. education. If you have purchased another TIBCO product that includes support for TIBCO Business Studio and have comments or problems with this manual or the software it addresses.tibco.html. visit http://www.How to Contact TIBCO Support 5 | How to Contact TIBCO Support The community edition of TIBCO Business Studio is unsupported. TIBCO Business Studio .tibco.com/services/support/ • If you already have a valid maintenance or support contract. please contact TIBCO Support as follows.Process Developer’s Guide . and access to the TIBCO Developer Network.com Entry to this site requires a username and password.com/devnet/index. you can request one. If you do not have a username.

6 | Preface TIBCO Business Studio .Process Developer’s Guide .

page 2 Implementation Approach. page 14 Tutorial 2: Elaborating a Process: Service Tasks.Process Developer’s Guide .|1 Chapter 1 Getting Started Topics • • • • • • • Who Should Use TIBCO Business Studio?. page 4 BPM/SOA Implementation Overview. page 6 Deploying a Process. page 25 TIBCO Business Studio . page 18 Tutorial 3: Deploying a Process. page 12 Tutorial 1: Elaborating a Process: User Tasks.

The Corporate Developer must implement a business process for doing this. The following diagram shows how TIBCO Business Studio is intended to be used: TIBCO Business Studio . A company has acquired a competitor. The Business Analyst has rationalized both companies’ working procedures and created a process for a standard way of working. and taking it through the packaging and deployment phases. • “Implementing a Process" refers to taking the Process that the Business Analyst has generated.2 | Chapter 1 Getting Started Who Should Use TIBCO Business Studio? Typically a Business Analyst defines a new business procedure and the Corporate Developer must implement it. For example: • An insurance company wants to enable their financial advisors to sell pension plans door-to-door using portable tablets.Process Developer’s Guide . refining it. adding detail to it. The Corporate Developer must implement this across the organization.

Process Developer’s Guide . usually written in Universal Modeling Language (UML). both of which are applied at the programming language level. How TIBCO Business Studio Supports MDA Model Driven Architecture (MDA) is typically used to design applications and write specifications. For example: TIBCO Business Studio . depending on the destination environment that you select. as well as a Platform Specific Model and Code Model.Who Should Use TIBCO Business Studio? 3 | Referring to the previous diagram. and dynamic sub-procedure call steps) for which you must perform part of the augmentation and deployment of the Process in TIBCO iProcess Modeler. and then the Process can be transformed to create a Code Model that can be used with a specific execution engine. transaction control steps. you can augment the process with execution details in TIBCO Business Studio and deploy it directly to the TIBCO iProcess Engine. using version 2. The following section describes how the abstract implementation of a Process can be done first. delayed release.0 of TIBCO Business Studio there are some constructs (for example. However. For example: TIBCO Business Studio supports an MDA approach to Business Process Management (BPM) and Service Oriented Architecture (SOA) at a higher level of abstraction than the programming language level by allowing you to develop Platform Independent Models of business processes and then transform them into Platform Specific Models. graft steps. It consists of a Platform Independent Model.

you must have a service that can come from one of the following sources: • Select an existing service interface and optionally an implementation (WSDL) from the Service Registry. file or URL. This is a mandatory part of implementing a service. Write new custom service implementation using . Selecting a service implementation. Specify a URL that refers to the location of a form authored outside of TIBCO Business Studio.NET. or BusinessWorks Live Link.4 | Chapter 1 Getting Started Implementation Approach Implementing a Process can be achieved in several different ways. 2. however the following general approach reflects best practices. TIBCO Business Studio . and bind its service interface to the Process. This is optional for technologies such as Web Services that support late binding. Enterprise Java Beans (EJBs). a JSP page authored with the JSP editor provided by WTP inside Eclipse. Receive Process from Business Analyst. which implies a concrete WSDL.Process Developer’s Guide . or other technologies. BPM/SOA Implementation For Service Tasks There are two parts to implementing services: • • Selecting the service contract. For example. which implies an abstract WSDL. Hand Over from Business Analyst 1. • • For User Tasks • • Specify the input and output parameters to the Task. Review Process with Business Analyst. Employ integration technology (such as BusinessWorks processes perhaps employing adapters) to create new service and bind its service interface to the Process. To implement a service call. then bind it to the Process.

Test and debug the services created in Java using tools external to TIBCO Business Studio. see the TIBCO iProcess Modeler set of guides. service implementations are created by different people or groups from those who consume the services provided by the process implementation. for more information on creating services see the documentation for TIBCO BusinessWorks and TIBCO ActiveMatrix. Package Process for Deployment to User Acceptance Testing/Production by the Operations staff. either those embedded in the Eclipse Platform Development Environment (PDE) or any other tools that are available. Hand Off/Deployment There are several options depending on the procedures in your organization: • Publish Process documentation to web site and return the enhanced Process model to Business Analyst and Business Owner for approval. test queues. • • Process Testing Ensure that the Process functions as intended including starting cases.Process Developer’s Guide . This is especially likely when the service implementation is done in a programming language such as Java rather than a declarative technology such as BusinessWorks.Implementation Approach 5 | Service Creation/Testing for Sub-Processes Optionally. for example using the Eclipse IDE. create any custom Java services that are required. TIBCO Business Studio . Deploy the Package/Process to the Repository and initialize it without handoff to Operations staff. For more information. See the TIBCO Business Studio Modeling User’s Guide for more information about generating Process documentation. and so on. In some organizations. undelivered work items. This guide focusses on the work of the person consuming services.

see Tasks on page 39. a User Task with a Form URL specified becomes a step with a Form type of Formflow Form. User Tasks You can specify the input and output Parameters of a User Task on the Implementation tab of the Properties view for the User Task: You can also specify either a relative or absolute URL for any form pages that you want displayed when the Task is executed (see Elaborating a User Task on page 40): Upon import to iProcess Modeler.Calls to a web service can be implemented as well as the mapping of input/output parameters. see TIBCO iProcess Client (Browser) Configuration and Customization. Service Tasks Service Tasks can be implemented in the following ways: • Web Service . This section provides an overview of elaborating a Process.6 | Chapter 1 Getting Started BPM/SOA Implementation Overview This section provides an overview of how to augment the Process with execution details. If no URL is specified. you may want to call a web service from a Service Task. For more information about specific tasks.Process Developer’s Guide . For more information. the step is created with a standard iProcess Form. TIBCO Business Studio . For example.

BW Service . This is done in the General tab of the Properties view for the Service Task. Currently the iProcess Engine database step only supports stored procedures. you must import the Process into TIBCO iProcess Modeler. and Integration (UDDI) Registry . Uniform Description. then use the appropriate EAI step (for example. SQL and DB2 databases. TIBCO BusinessWorks/Web Service A Service Task can be configured to call a service that has a WSDL. Database . For example: If you want to implement other types of service calls.Allows you to call Java code that you want to execute at runtime. Discovery.Native or Java Database Connectivity (JDBC) calls to Oracle. including functions that emulate standard iProcess Script commands.BPM/SOA Implementation Overview 7 | • • Java . you must import the WSDL file to the Eclipse workspace.specify a URL from which the WSDL is retrieved. • • E-mail . TIBCO Business Studio . or provide a service descriptor (WSDL) for the behavior.Calls to a BusinessWorks process exposed as a service can be implemented as well as the mapping of input/output parameters.obtain the WSDL from a UDDI registry.browse to select a local file.Process Developer’s Guide . Before you can configure a Service Task.You can either configure an email message that is sent when the Process is executed. URL . from one of the following sources: • • • File . EAI Java).

Except for a WSDL obtained from a TIBCO BusinessWorks live link. The web service call style must be either Document Literal or Remote Procedure Call (RPC) Encoded.use the TIBCO BusinessWorks Connector live link feature to dynamically create and import a WSDL from a BusinessWorks process exposed as a service: To use the TIBCO BusinessWorks live link invocation method. For more information. the iProcess Engine Service Agent must be running and the JMS provider transport information must be configured. see the TIBCO iProcess BusinessWorks Connector User’s Guide. the WSDL file that you use must conform to the following requirements for deployment to the iProcess Engine: Data Transport/Call Style • • The web service must use the SOAP over HTTP data transport mechanism. The web service can have the following types of request and response parameters: — Simple types — Arrays of simple types — Complex types (including complex types containing complex types) — Arrays of complex types TIBCO Business Studio .8 | Chapter 1 Getting Started • BusinessWorks live link .Process Developer’s Guide . Parameter Mapping • • The web service must have at least one input and output parameter mapping. however you cannot specify more than one output parameter mapping.

Process to Service Binding In the Properties view for a Service Task. If you use a remote WSDL. you can select either Use local WSDL or Use remote WSDL: If you use a local WSDL. Database A Service Task can be configured to perform an action on a database using stored procedure calls. E-mail A Service Task can be configured to send an E-mail message on the General tab of the Properties view for the Service Task as follows: TIBCO Business Studio . the abstract and concrete portion of the WSDL must be present locally. When the Process is deployed to the iProcess Engine. the appropriate DB2.Process Developer’s Guide . and the concrete portion of the WSDL can be obtained dynamically at runtime. Oracle or SQL database calls are made in the iProcess database. the stored procedure writer will need to be familiar with the particular database. Although you do not need to be concerned about which database is used in conjunction with the iProcess Engine. the abstract portion of the WSDL must be present locally.BPM/SOA Implementation Overview 9 | Message Exchange Patterns The only supported message exchange pattern is Synchronous Request/Response.

For more information. int.10 | Chapter 1 Getting Started Clicking More Details or clicking the E-Mail tab allows you to specify further parameters. and so on) must adhere to JavaBeans semantics. Note that instead of explicitly entering email addresses. the previous dialog shows %Manager% rather than an explicit email address. see Sending an Email on page 50. For example. subject lines and so on. Specifically they must have a default constructor (one without parameters) and the properties need to have standard get and set operations. This means that a String property 'name' must have an accessor named getName():String and a mutator named setName(:String). and to Timer Start or Intermediate Events. The following constructs are supported in TIBCO Business Studio for Processes that you want to export/deploy to the TIBCO iProcess Modeler/TIBCO iProcess Engine: TIBCO Business Studio . You can browse to select the Java class and select a Method from the drop-down list. The factory class must either offer a static factory method or must have a default constructor as the service class does. Script Tasks You can enter scripts in Script Tasks. Java A Service Task can be configured to call a Java code on the General tab of the Properties view for the Service Task as follows: The Java service class and any parameters that are not primitives (for example.Process Developer’s Guide . Alternatively you can specify a Factory to be used for the creation of the class. float. you can define Data Fields or Parameters for this purpose. on Conditional Sequence Flows.

elseif. then press Ctrl + Space. you can use the following template to construct an if else: iProcess Script is supported for backward compatibility via the TIBCO iProcess JavaScript class library. Content assist is available for process data that you define and also provides templates for common JavaScript constructs.Process Developer’s Guide . and else statements Do while loops and while loops For loops Assignment operators Conditional operators The result of an expression should correspond to one of the known data types listed in the TIBCO iProcess Expressions and Functions Reference Guide.BPM/SOA Implementation Overview 11 | • • • • • If. TIBCO Business Studio . For example. you can view the available list of iProcess Script functions by typing IPE and pressing Ctrl + Space. if you enter if. If you have selected the iProcess Engine or iProcess Modeler destination environment. Within the packaging/export phase this JavaScript is converted to iProcess Script for execution by the iProcess engine.

All of these. After preparing the software some transformation. some of which may be optional. Direct Deployment and Export to the TIBCO iProcess Engine are one-way operations. the next step could be to deploy it to a server (for example. physical delivery.12 | Chapter 1 Getting Started Deploying a Process Deployment is part of the software development cycle (design. There are two ways you can deploy a Process once you have finished elaborating it with the necessary execution details: • • Create a Deployment Server within TIBCO Business Studio and deploy the Process directly to the iProcess Engine (see Deploying a Process on page 64). execute). you should regard the import of an iProcess Modeler XPDL as a one-off activity to evaluate or migrate to TIBCO Business Studio. deploy. deploy again. packaging. after a Corporate Developer has elaborated a Process. For this reason. and so on. Export the Process to iProcess Modeler XPDL and then import it into the TIBCO iProcess Engine (see the TIBCO iProcess Modeling User’s Guide). To look at a concrete example of deployment.Process Developer’s Guide . TIBCO Business Studio . re-import to TIBCO Business Studio. This is because the Studio process description may contain far more than merely the execution information required for iProcess Modeler/iProcess Engine. Information can be lost if you deploy to the iProcess Engine. modify the Process. are aspects of deployment. a server in the test environment). configuration and initialization takes place.

You can either open the sample workspace and explore the Project or continue with this tutorial to implement the example yourself. TIBCO Business Studio .Tutorial Project 13 | Tutorial Project The samples workspace includes a Project (Process Developer Tutorial Solutions 2. 2. do the following: 1.0 Project and expand the Process Packages folder. The remainder of this chapter assumes you are implementing the example yourself. This starts TIBCO Business Studio and opens the sample workspace rather than your default workspace. To open the TIBCO Business Studio sample workspace.0) that has the completed solutions for the tutorials in the following sections.Sample Workspace.0 > TIBCO Business Studio .Process Developer’s Guide . Click Start > All Programs > TIBCO > TIBCO Business Studio 2. Expand the Process Developer Tutorial Solutions 2. which contains the tutorial solutions.

xpdl file and paste it into the Packages folder of your Project. accepting the default Special Folders. Open the Submit Expenses Process: TIBCO Business Studio . 2.Process Developer’s Guide . Copy the \Basic Samples 2. In the file system. Create a BPM/SOA Developer Project in your workspace. 4.14 | Chapter 1 Getting Started Tutorial 1: Elaborating a Process: User Tasks To learn how to implement User Tasks in a Process. 3.0\Process Packages\Office Procedures. C:\Program Files\TIBCO\Business Studio\sample-workspace). follow this tutorial. navigate to directory into which you installed TIBCO Business Studio and locate the sample workspace (for example. Task A Open the Sample Process 1.

2. and so on. • • In some cases. Adding Parameters to the Process means that when it is exported to the iProcess Modeler if will be a Sub-Procedure. Create the following Parameters: — EmployeeName (String) — EmployeeNumber (Integer Number) — Reference (string) — Amount (Decimal Number) — AccountNumber (Integer Number) — Confirmation (Boolean) Task C Specify Input and Output Parameters to the Tasks 1. In the Project Explorer.Process Developer’s Guide .Tutorial 1: Elaborating a Process: User Tasks 15 | Many of the Tasks in this Process require input and output. Click the Enqueue Payment Task. the performer of this action needs basic information such as the employee name. 4. Right-click Parameters and select New > Parameter. For example. before the expenses can be approved. TIBCO Business Studio . expand the Submit Expenses Process. right-click Data Fields and select New > Data Field. the Data Fields and Parameters may have already been added by the Business Analyst. cost center. In the Properties view. The information that is internal to the Process will be represented as Data Fields and information required outside the Process will be represented by Parameters. Create the following Data Fields: — Manager (String) — CostCenter (String) — Authorization (String) 3. expense amount. Task B Create Parameters/Data Fields Create the Data Fields and Parameters that will be used by the Process as follows: 1. click the Parameters tab.

Add the following outbound Parameters: Inbound and Outbound Parameters are from the perspective of the form. TIBCO Business Studio . For more information about using Fields in Forms. This means that Inbound Parameters are sent to the form by the Process.Basic Design. Upon deployment to the iProcess Engine. To select several Parameters in the Select Data Field dialog. not the user. Outbound Parameters are sent to the form by the user.16 | Chapter 1 Getting Started 2. see TIBCO iProcess Modeler . press the Ctrl key and click the desired Data Field or Parameter. Inbound and Outbound Parameters become Optional fields. not the user.Process Developer’s Guide .

Tutorial 1: Elaborating a Process: User Tasks 17 | Summary You can create Data Fields and Parameters and specify their input and output mappings on User Tasks. For example: For more information about deployment. the Data Fields become Fields and the Parameters become I/O Parameters and Fields. Upon import or deployment to the iProcess Modeler.Process Developer’s Guide . see Tutorial 3: Deploying a Process on page 25 and Deploying a Process on page 64. TIBCO Business Studio .

Task A Create the Process/Service Task For the purposes of this tutorial. Calling Web Services Many services that are described by a WSDL can be called from a Service Task (see TIBCO BusinessWorks/Web Service on page 7). then click Next. Save the Project. Click Finish to complete the import. Select File > Import and select Services > Service Import Wizard from the list. Select Import from a File and click Next. 5. TIBCO Business Studio .Process Developer’s Guide . Browse to specify the Services folder where you want to store the WSDL. This opens the Operation Picker dialog. 2. Task B Add the WSDL to the Project 1.18 | Chapter 1 Getting Started Tutorial 2: Elaborating a Process: Service Tasks To learn how to elaborate Service Tasks. follow this tutorial. 3. continue using the Submit Expenses Process from Tutorial 1. In the Properties view. 4. Browse to find BankPayment. In the Project Explorer select the Project that contains the Submit Expenses Process 2. 6. Task C Associate the WSDL with the Service Task 1. select Web Service from the Service Type drop-down list.wsdl in the samples workspace and click Next. Click the Select button. 3. Click the Make Payment Task.

Click the Mapping In tab. Expand the BankPayment service. 2.Tutorial 2: Elaborating a Process: Service Tasks 19 | 4. Highlight the EmployeeName Parameter and drag the pointer from the Employee Name Parameter to the EmployeeName Formal Parameter. Task D Map the Input/Output Parameters 1. On the left of the tab are the Parameters and Data Fields and on the right are the Formal Parameters that the BankPayment service expects. Complete the input parameter mapping as follows: TIBCO Business Studio . Expand the BankPayment service and select the MakePayment operation. This populates the rest of the web services fields such as Port Name and Operation.Process Developer’s Guide .

In this case the Confirmation parameter is Boolean and indicates whether the transaction completed. Save the Package. Using the same method as on the Mapping In tab. complete the output parameter mapping as follows. You can see that the web service returns Confirmation and Reference parameters.20 | Chapter 1 Getting Started 3. 4. Click the Mapping Out tab.Process Developer’s Guide . TIBCO Business Studio .

the Service Task becomes a Web Services EAI step: TIBCO Business Studio . mapping the input and output parameters.Process Developer’s Guide . Upon import or deployment to the iProcess Modeler.Tutorial 2: Elaborating a Process: Service Tasks 21 | Summary This tutorial showed how to add a WSDL file to a Project and then associate that WSDL file with a Service Task.

see Tutorial 3: Deploying a Process on page 25 and Deploying a Process on page 64. Creating an E-Mail Task In the previous section.22 | Chapter 1 Getting Started You can see that the parameter mappings are configured in the EAI step as well: For more information about deployment. we will add an email task to notify the person who submitted the claim when the payment is made. we added a call to a web service from the Make a Payment Activity. Insert a Gateway after the Make a Payment Activity. This included a Confirmation parameter which indicated whether the payment was successful.Process Developer’s Guide . TIBCO Business Studio . In this section. 1. We will also add a Manual Task in the event that the payment fails.

Enter an email address for the recipient in the To: field. TIBCO Business Studio . a subject and the body for the message. For further options. This is the minimum configuration necessary to send an email message.Process Developer’s Guide .Tutorial 2: Elaborating a Process: Service Tasks 23 | 2. It should look like this: 3. After the Gateway. Select the Notify Service Task. select the E-Mail option from the Service Type drop-down list: 4. add a Service Task called Notify and a Manual Task called Ring Bank. then on the General tab of the Properties view for the Service Task. click More Details or the E-Mail tab and continue to specify further parameters.

For example: For more information about deployment. the Service Task becomes an E-mail EAI step.24 | Chapter 1 Getting Started Summary You can configure a Service Task so that it sends an e-mail at runtime. Upon import or deployment to the iProcess Modeler.Process Developer’s Guide . see Tutorial 3: Deploying a Process on page 25 and Deploying a Process on page 64. TIBCO Business Studio .

see your iProcess administrator for details.properties file. Task A Create the Process 1. This was configured during installation of the iProcess Engine and stored in the SWJMXConfig.Tutorial 3: Deploying a Process 25 | Tutorial 3: Deploying a Process This tutorial describes creating and deploying a simple Process to an iProcess Engine. If you are unsure of any of these prerequisites. By default the Port is 10025.Process Developer’s Guide .port entry in the SWDIR\etc\swjmx. 4. 2. Select New > New Project and follow the wizard to create a new BPM/SOA Developer Project with the default configuration. and click Next. The package name will be used to create the library name when the Process is deployed to iProcess. contact your iProcess Administrator. 6. Name the Process DeployTest and click Finish. 3. TIBCO Business Studio . Click Next to accept the Packages folder and file name. Prerequisites • • • • Network access to a running iProcess Engine where you can deploy the Process Username and password of an iProcess Engine user with either the PRODEF or ADMIN permission that you can use to connect to the iProcess Engine Host name (machine name or IP address) Port number that the iProcess Engine uses for the Java Management Extension (JMX) engine. Select the Create a package using one of the following templates check box. If you cannot determine the port number. Right-click the Process Packages folder and select New > Process Packages. 5. select the An empty iProcess process item. Name the Package Tutorial and click Next.

Change to the Problems view. on the Destinations tab. Accept iProcess Engine Server as the Runtime Environment. Select the Process in the Project Explorer. 3. and you should see that there are two error messages that relate to the Process: 10.Process Developer’s Guide . Task B Create the Deployment Server 1. 12. Right-click Deployment Servers and select New > Server. 4. Click Next. You should confirm that there are no errors or warnings in the Problems view. Add a User Task and an End event as follows: 9. . 11. To correct this. 8. TIBCO Business Studio . 5. In the Properties view. Name the server TestDeploy. Switch to the Process Developer Capability by clicking 2. Save the Package.26 | Chapter 1 Getting Started 7. you can see that the iProcess Engine and iProcess Modeler have been selected: The template also creates a Participant called sw_starter. associate the sw_starter Participant with the User Task (on the General tab of the Properties view for the task).

Click Finish.Process Developer’s Guide . If you cannot determine the port number. TIBCO Business Studio . — Host . This was configured during installation of the iProcess Engine and stored in the SWJMXConfig. 7. otherwise enter the machine name or IP address of the computer where the iProcess Engine is installed. — Password . 2. contact your iProcess Administrator. The username and password you entered when you created the server is authenticated on the deployment server to prevent you from deploying a Process to a server which you do not have authorization to use.Tutorial 3: Deploying a Process 27 | 6. — Repository Type: Select Workspace. IPEADMIN). The new Server is created and displayed in the Project Explorer. Right-click the server name Test Deploy and select Connect. By default the Port is 10025.Password for the user connecting to the iProcess Engine.Valid iProcess Engine user with either the PRODEF or ADMIN permission that can connect to the iProcess Engine (for example. Task C Connect to the Server You can connect to a server you have created as follows: 1. — Port .Enter localhost if the server is on your local machine. expand Deployment Servers.port entry in the SWDIR\etc\swjmx. — Username .properties file. Enter the runtime server parameters. In the Project Explorer.The port number that the iProcess Engine uses for JMX.

check the error log by selecting Help > About Eclipse Platform. Task D Deploy the Process Deploy the Process to the iProcess Engine as follows: 1. The following dialog is displayed: TIBCO Business Studio . When you have connected.Process Developer’s Guide . click Configuration Details then click View Error Log. From the resulting dialog. the Properties view for the server displays Connected as the Server State: In addition. the icon in the Project Explorer and the status bar text in the lower left of the workspace changes to indicate that you are connected. If you encounter any problems connecting to a Server.28 | Chapter 1 Getting Started 3. Right-click the TestDeploy Server and select Deploy Module.

see Deploying a Module on page 68. (For more information about Deployment Policy. Click Details to get more information about why the deployment failed. an error symbol is displayed instead of the information symbol in the previous dialog.Process Developer’s Guide . When the deployment is finished. You are prompted to select the Package that contains the Process you want to deploy. TIBCO Business Studio displays the following message: If the deployment fails. and click Next.Tutorial 3: Deploying a Process 29 | 2. You can view the newly-deployed Process in the Project Explorer: TIBCO Business Studio . Select Workspace iProcess XPDL Module. Select Test2 and click Finish. see Deploying a Module on page 68). 3. For more information about the External Module option.

it is truncated (DEPLOYTE). when it is deployed to the iProcess Engine. see Managing Deployed Modules on page 72.Process Developer’s Guide .30 | Chapter 1 Getting Started Note that because our original Process name in TIBCO Business Studio (DeployTest) has more than eight characters. The state of the procedure (Unreleased) and other details such as the version information is displayed in the Properties view: For more information about managing deployed modules. TIBCO Business Studio .

TIBCO Business Studio .Process Developer’s Guide .| 31 Chapter 2 Concepts and Definitions This section defines concepts and terminology related to TIBCO Business Studio.

Java files). TIBCO Business Studio .Process Developer’s Guide . Project management artifacts (such as a business case or project plan).32 | Chapter 2 Concepts and Definitions Artifacts A physical item created during the project life cycle. These can include the following: • • • • Code artifacts (for example. Deployment artifacts (such as XPDL1 packages for deployment to the iProcess Engine) or BAR files for TIBCO BusinessEvents. Documentation artifacts (for example HTML or PDF procedure documentation).

Using the Server Manager in TIBCO Business Studio. some of which may be optional. Unless you have extended TIBCO Business Studio. configuration and initialization takes place. For more information.Process Developer’s Guide . When you want to deploy a Project/Process. packaging. are aspects of deployment. what happens is this: • A packaging phase occurs (either automatically or explicitly triggered by the user). TIBCO Business Studio . see Deploying a Process on page 64. All of these.Deployment 33 | Deployment Part of the software development cycle (design. Specifically in TIBCO Business Studio. • Module When you deploy an artifact. a Module corresponds to a Process with the Destination Environment set to iProcess Engine. execute). physical delivery. After preparing the software some transformation. a Module is created in the Deployment Server. A deployment server is the representation in TIBCO Business Studio of a TIBCO iProcess Engine. The artifact created by the packaging phase is the transformation of the XPDL2 package into XPDL1 for deployment to the iProcess Engine. you do so by creating a Deployment Server. you can connect the server and manage certain aspects of deployed Processes. deploy.

There are several types of Data Field: • Boolean . counterparty. If you intend to execute a Process in the TIBCO iProcess Engine. be aware that Data Fields or Parameters with spaces in their names cannot be used for mapping (for example. This is because the complex data types created in the Concept Modeler are not supported in the iProcess Engine. Data Fields Data Fields are used to represent the data that is used internally in a Process as either input to or output from an Activity. Concept Model A set of business terms specific to your corporate environment (for example. you are creating a class diagram with the addition of a UML Profile specifically intended to extend the meta-data to provide additional functionality over core UML. you cannot export the resulting Process to the iProcess Engine. mapping to Parameters in a web service). suppose an Activity is to identify a list of suitable candidates for an available position. when you create a Concept Model. and so on).Process Developer’s Guide .true or false TIBCO Business Studio . You can create Data Fields to represent the pool of candidates going into the Activity and the suitable candidates that have been identified. In object-oriented terms. For example. see the TIBCO Business Studio Concept Modeler User’s Guide.34 | Chapter 2 Concepts and Definitions Project Objects This section describes Process objects that relate to Process development. TIBCO Business Studio provides an Eclipse editor called the Concept Model Editor to help you construct your Concept Model.The advantage of creating or importing a Concept Model in TIBCO Business Studio is that you can use it: • • • for analysis purposes for documentation purposes to create Data Fields in a Process that have the attributes of a Concept If you specify Concepts as Parameters or Data Fields in the TIBCO Business Studio Process Editor. broker. For more information. in a financial environment.

combination of date/time Datetime Data Fields are deployed/exported as two separate date and time fields in the iProcess Engine (suffixed "_D" and "_T"). so the previous example.34.34 has a length of five and two decimal places) In the iProcess Modeler. the number 130. the field lengths include the decimal point. • • • Integer Number .Project Objects 35 | • Date Time . when imported into the iProcess Modeler has a length of six and two decimal places. For example.integer value of the specified length (for example. during simulation Parameters are either created by TIBCO Business Studio or imported from a file.Process Developer’s Guide . • Decimal Number .alphanumeric characters of the specified length Extended Attributes Extended attributes can be used to add extra information to the schema such as: • • • XML Plain text descriptions Supply Chain Council (SCC) models for metrics and best practices They are added either on the Extended tab of the Properties view for those objects that support extended attributes. 130.is a text field that you want to use as a Participant String .decimal number of the specified length and decimal places (for example. 345) Performer .true or false TIBCO Business Studio . Parameters can be any of the following types: There are several types of Data Field: • Boolean . or on the Extended Attributes dialog in the New Process wizard. Parameters Parameters are similar to Data Field but are either input to or output from an external source.

identifies an activity that is performed by the system.36 | Chapter 2 Concepts and Definitions • Date Time . • Participants Participants are used to identify who or what performs an Activity.combination of date/time Datetime Parameters are deployed/exported as two separate date and time fields in the iProcess Engine (suffixed "_D" and "_T"). Manager. There are several types of Participant: • Role .Process Developer’s Guide .is a text field that you want to use as a Participant String . in a financial institution there may be roles such as Reconciler.identifies the department or unit within an organization that performs an Activity. For example.identifies the role responsible for performing an Activity. be aware that Data Fields or Parameters with spaces in their names cannot be used for mapping (for example.integer value of the specified length (for example. mapping to Parameters in a web service). so the previous example. 130.alphanumeric characters of the specified length If you intend to execute a Process in the TIBCO iProcess Engine. • • • TIBCO Business Studio . The creation of a Parameter means that the Process will become a sub-procedure upon export to the iProcess Modeler. the number 130. 345) Performer .34 has a length of five and two decimal places) In the iProcess Modeler.34. a person (Human Participant) interviews the candidate and an email system (System Participant) sends out an automatic follow-up reminder. For example.decimal number of the specified length and decimal places (for example. the field lengths include the decimal point. in a hiring process. Legal. • Decimal Number . System . • • • • Integer Number . and so on. Marketing and so on. For example. when imported into the iProcess Modeler has a length of six and two decimal places. Organizational Unit . Human .identifies a specific person or user that performs an Activity.

but indirectly by creating a business process using the Process Editor or by creating a Package. Business Process Modeling Notation (BPMN) BPMN is a graphical notation developed by the Business Process Management Initiative (BPMI) for representing the steps and flow of business procedures. TIBCO Business Studio . visualize. see http://www. UML2 Unified Modeling Language (UML) is an Object Management Group (OMG) specification that helps you specify. Packages are stored in XPDL format. including their structure and design.Standards Support 37 | Standards Support TIBCO Business Studio supports several industry standards. you do not use XPDL directly. For more information.org.Process Developer’s Guide .bpmn. Normally. and document models of software systems or business systems. XML Process Definition Language (XPDL) XPDL is used to represent the underlying structure of a business process to TIBCO Business Studio. namely Business Process Modeling Notation (BPMN) and XML Process Definition Language (XPDL). This version of the TIBCO Business Studio provides support for XPDL2 and uses XPDL1 for deployment to the iProcess Engine. You can use the Concept Modeler to import UML class diagrams (for more information see the TIBCO Business Studio Concept Modeler User’s Guide. The TIBCO Business Studio Process Editor supports the core set of this notation and the Properties View supports the complete set.

Process Developer’s Guide .38 | Chapter 2 Concepts and Definitions TIBCO Business Studio .

page 64 TIBCO Business Studio . package and deploy it. page 40 Adding a Service Call.Process Developer’s Guide .| 39 Chapter 3 Tasks This section of the help describes some of the common tasks that you perform using TIBCO Business Studio to elaborate a process with execution details. page 50 Making a Database Call. page 56 Associating a Script with a Conditional Flow. page 58 Calling Java Code. page 63 Deploying a Process. Topics • • • • • • • • • Elaborating a User Task. page 42 Sending an Email. page 60 Packaging a Process. page 54 Creating a Script Activity.

40 | Chapter 3 Tasks Elaborating a User Task You can add Parameters or Data Fields to user tasks as follows: 1. Click the User Task that you want to add Parameters to. Create the Parameters or Data Fields as described in the TIBCO Business Studio Modeling User’s Guide. 2.Process Developer’s Guide . TIBCO Business Studio . 3. press the Ctrl key and click the desired Data Field or Parameter. In the Properties view. Click OK when you have finished selecting Parameters and Data Fields. click the Add button to select inbound and outbound Parameters: To select several Parameters in the Select Data Field dialog.

jsp. application and protocol. The benefit of using this type of URL is that when moving from development to user acceptance testing and then to production. Specifying a relative URL assumes that the browser client configuration has specified the host and protocol (for example. JSPFormExample/JSPForm. 5.for example. Absolute URLs allow each step of each process to specify a separate host. — Leave the Form URL field empty. http or https). http://www.Elaborating a User Task 41 | 4. the step is created with a standard iProcess Form.com/mywebapp/myjsp. For more information. Click the Implementation tab. If you specify a URL.jsp. — Absolute .for example. a User Task with a Form URL specified becomes a step with a Form type of Formflow Form. Save the Package that contains the Process.acme. Upon import to iProcess Modeler. You can do either of the following: — Specify a URL for any form pages that you want displayed when the Task is executed: Upon import to iProcess Modeler. the base URL (including the host name) needs to be changed in just one central place. see TIBCO iProcess Client (Browser) Configuration and Customization. This has the effect that all JSPs in all processes on all nodes accessed using this client must be in the same web application.Process Developer’s Guide . you can use either of the following types: — Relative (the default) . TIBCO Business Studio .

— Query Manager (Inquiry) URL . Working with UDDI Registries If you plan to add a WSDL file from your Project.xmethods. select Service Registry from the list of wizards and click Next. Select Show View > Other.net/publish). You can also use the TIBCO BusinessWorks Connector live link feature to dynamically create and import a WSDL from a BusinessWorks process. The Registries view opens and you should see any UDDI Registries that you have added.net/inquire). — Lifecycle Manager (Publish) URL . http://uddi. 3. TIBCO Business Studio . Select New > Other. Viewing a Registry 1. https://uddi.42 | Chapter 3 Tasks Adding a Service Call A Service Task can be configured to call any service that has a WSDL. 2.xmethods.the URL used to retrieve information about the services and businesses of the registry (for example. Creating a Registry Search 1. including BusinessWorks process that are exposed as services. 2. Expand Web Service Registries and select Registries.Process Developer’s Guide .for example XMethods. Adding a UDDI Registry 1. you can create a new registry either before importing the WSDL file. Enter the details of the Web Service registry: — Registry Name . Click the Add Search button ( ). 4.the URL used for publishing services and businesses to the registry (for example. Expand Services. 3. This section describes how to add a UDDI registry before importing the WSDL. Click Finish. or as part of the import process.

Process Developer’s Guide .You can use a percent sign (%) as a wildcard to specify search criteria. Click Finish. Select the type of search you want to perform (either for a business or for a service) and click Next. For example. When you expand the search in the Registries view. specifying c% would return all businesses or services that start with the character c. For example. — Search Criteria .Adding a Service Call 43 | 2. Enter the service search criteria: — Search Name . Not all registries support this wildcard syntax. however the TIBCO ActiveMatrix Service Registry does. 4. the results are displayed. the following search shows the results of a search on the XMethods registry: Search results are preserved for subsequent browsing. 3.This is the name you want displayed in the Registries view for your search. but may be refreshed. TIBCO Business Studio .

44 | Chapter 3 Tasks Adding a WSDL to the Project There are several options for getting a WSDL file into your Project. If you have chosen to create a WSDL skeleton. This section describes: • • • Creating a New WSDL If you do not already have a WSDL file for the service you want to call. either SOAP or HTTP.company. and so on) for detailed advice.NET.Process Developer’s Guide . 2.example. expand Web Services and select WSDL and click Next. 1. Specify the Parent folder and File name for the WSDL file and click Next. http://www. select the binding options you want to use in the WSDL document. — Prefix is the prefix associated with the target namespace. Creating a New WSDL Copying a WSDL Importing the WSDL TIBCO Business Studio . If you select SOAP you can then select the encoding style you want to use. you can create a new WSDL file using the tools provided by Eclipse: A full explanation of all the necessary settings and advice on creating WSDLs is outside of the scope of this document. If you select HTTP you can select whether to create an HTTP getter or setter. 3. This will generate the WSDL elements required for your service.com/service/). . including bindings. You can then modify these to meet the requirements of your Web service. ActiveMatrix. Enter the following options: — Target namespace is the namespace for the WSDL file or accept the default (http://www. You must specify a valid URI (for example. This section should be considered only a summary and you should consult the documentation associated with your web service creation tools (for example.org/MyWSDLFile/). ports and messages. — Select Create WSDL Skeleton if you want the wizard to create the skeleton of the WSDL file. binding and service defined in the WSDL file. The target namespace is used for the names of messages and the port type. Select File > New > Other.

In the Project Explorer select the folder in the Project where you want to copy the WSDL file. Locate the WSDL file. either in the file system or received via e-mail. The WSDL file is pasted into the correct location. You can also designate a special folder to hold the WSDL (this allows you to expand the WSDL file in the Project Explorer to see the operations available).Adding a Service Call 45 | 4. The WSDL file opens in the WSDL editor.Process Developer’s Guide . c. select it and press Ctrl + C to copy it. then click Finish. you can copy and paste it into the Project. For example: Importing a WSDL There are several ways to import a WSDL into a project: • • from a file from a URL TIBCO Business Studio . the press CRL + V. Click Finish. right-click and select Special Folders > Use as Services Folder. Right-click where you want to create the folder and select New > Folder. b. Select the newly-created folder. 1. you can do so as follows: a. For example: Copying a WSDL If you already have a WSDL file. 2. If you have not yet created a folder. Enter the parent directory and folder name. This enables you to expand the WSDL in the Project Explorer.

Select one of the following import methods: — Import from a File . then click Next.use this method to select a WSDL from a UDDI registry that you previously created. Click Next.46 | Chapter 3 Tasks • • from a UDDI registry from TIBCO BusinessWorks To import a WSDL file. To use the TIBCO BusinessWorks live link invocation method. the iProcess Engine Service Agent must be running and the JMS provider transport information must be configured. — Import from a Registry . do the following: 1.3+ . 2.use this method to specify a URL that resolves to the location of the WSDL file. Select File > Import and select Services > Service Import Wizard from the list. For more information.Process Developer’s Guide .use this method to import a WSDL using the BusinessWorks live link feature. TIBCO Business Studio . — Import from BusinessWorks 5. see the TIBCO iProcess BusinessWorks Connector User’s Guide. — Import from a URL .use this method to browse the file system for the WSDL file.

2. specifically the Host. click Start > TIBCO iProcess Server (Windows) > JMS Administration Utility).3+. the JMS provider information can be found in either of the following locations: — In the JMS Administration Utility (from UNIX. Port and TargetQueueName. there may be slight delay while the WSDL file is imported. Select the Service Task. On the Properties view for the Service Task. right-click and select Add Registry. If the WSDL file is located remotely.sh command. or from Windows. Click Next. Associating the WSDL with a Task You can associate a WSDL with a Service Task. do the following: — If you chose Import from a File. 5. browse to specify the Location of the WSDL file. For more information see the TIBCO iProcess BusinessWorks Connector User’s Guide. select Web Service. To add a new registry. You can then specify that the Service Task performs a web services operation at runtime.Adding a Service Call 47 | 3. enter the URL for the WSDL file. 1. Depending on the option that you chose in the previous step. — If you chose Import from BusinessWorks 5. Browse to select the Location (the folder in your Project where you want to store the WSDL file). on the General tab. you can either select a service from an existing registry or add a new registry. 4. Click Finish. — In the iProcess Service Agent area of the BusinessWorks Step Definition dialog when defining an iProcess BusinessWorks step in an iProcess Engine procedure.Process Developer’s Guide . — If you chose Import from a Registry. When using a BusinessWorks live link. enter the JMS provider information that the iProcess Engine uses to integrate with BusinessWorks. navigate to the $SWDIR\jmsadmin directory and enter the jmsadmin. TIBCO Business Studio . — If you chose Import from a URL.

48 | Chapter 3 Tasks 3. Using the Mapper 1. Highlight a Parameter on the left and drag the pointer from the parameter to the Formal Parameter on the right to create a mapping. mapping a String to an Integer). 2. TIBCO Business Studio . an error is generated in the Problems view. For example: • • You cannot map Data Fields or Parameters with spaces in their names. If you attempt to map Data Fields or Parameters to Parameters of a different type (for example. Click Select to select an operation.Process Developer’s Guide . Click the Mapping In tab. Expand the web service. The Port Name and Operation Name are populated automatically depending on the operation you select. This opens the Operation Picker dialog. On the left of the tab are the Parameters and Data Fields and on the right are the Formal Parameters that the web service expects.

5.Adding a Service Call 49 | 3. TIBCO Business Studio . This displays the following window. you can do so as follows: When executed in the runtime environment. the string "SEBRANCH" is appended to the input Parameter Reference. For example. Save the Package that contains the Process. Note that you can enter JavaScript that is applied to a mapping by clicking . Complete the output mapping in a similar fashion using the Mapping Out tab.Process Developer’s Guide . if you want to append a string to a Parameter. in which you can enter a limited amount of JavaScript: This is currently limited to concatenation of two fields on the left into a single on the right or splitting (substring) data from one left field to two on the right. 4. Web service operations that return more than one Parameter are not supported in the iProcess Engine/iProcess Modeler Destination Environments.

On the E-Mail tab. select the E-Mail option from the Service Type drop-down list: 2. you can specify further parameters for the Definition of the message: All of the Parameters on this tab can be specified using a Data Field or Parameter. This is the minimum configuration necessary to send an email message. then on the General tab of the Properties view for the Service Task. Enter an email address for the recipient in the To: field. click More Details on the E-Mail tab and continue to specify further parameters. a subject and the body for the message.50 | Chapter 3 Tasks Sending an Email A Service Task can be configured to send an email message as follows: 1. For further options. Click the button to select the Data Field or Parameter. Select the Service Task. 3. TIBCO Business Studio .Process Developer’s Guide .

select the Subject line for the email message or select a Data Field or Parameter. Their email address is visible to other recipients of the email. — Headers: .use this parameter to specify additional information in the header of the email. 4. — Bcc: .specify the recipient of the email either as an explicit email address or by selecting a Data Field or Parameter.Process Developer’s Guide . — To: .select a priority from the drop-down list (Normal. — Subject: .specify the recipients to whom you want to send a copy of the email either as explicit email addresses or by selecting a Data Field or Parameter.Sending an Email 51 | — From: . Click Body to specify the main text of the message.specify the recipients to whom you want to send a copy of the email either as explicit email addresses or by selecting a Data Field or Parameter.either Use Server Configuration to use the address of the server from which the email is sent or Use Custom Configuration to specify a Data Field or Parameter. At the bottom of the text area are two buttons. — Cc: . — Reply to: . High or Low) or select a Data Field or Parameter. Alternatively. src and preview which allow you to alternate between TIBCO Business Studio . select a Data Field or Parameter. Their email address is not visible to other recipients of the email.use this parameter to specify a different email address to which recipients of a message can reply. — Priority: .

TIBCO Business Studio . 6. Click SMTP Configuration to specify Simple Mail Transfer Protocol (SMTP) settings other than the default: — Select User Server SMTP Configuration to use the settings of the server where the Process will run.52 | Chapter 3 Tasks viewing the source of the body text and previewing how it will look to the recipient.use this option to attach the contents of a Parameter or Data Field to the email message. 5. Click Attachments to specify a document to be attached to the message: — Field Contents: . — Files: use this option to browse the file system and attach a file to the email message.Process Developer’s Guide . — Select Use Custom SMTP Configuration settings to specify a different Host and Port.

Sending an Email 53 | 7. if a message cannot be sent): — Code: . — Message: .select either a Parameter or Data Field that contains the message you want displayed when the email cannot be sent.Process Developer’s Guide . TIBCO Business Studio .select either a Parameter or Data Field that represents an error code. Click Error Handling to provide for basic error handling (for example.

then on the General tab of the Properties view for the Service Task. select the Database option from the Service Type drop-down list: 2. 3.specify the name of the stored procedure in the format shown in the above dialog .[owner.]stored_procedure_name. or the Database tab to define the parameter mappings between parameters in the stored procedure and Case TIBCO Business Studio .Process Developer’s Guide . Select the Service Task. — SQL . Specify the following: — Server. The default instance is the one that your TIBCO iProcess Engine is currently using..54 | Chapter 3 Tasks Making a Database Call A Service Task can be configured to make a database call as follows: 1. refer to the TIBCO iProcess Database Plug-in User’s Guide. Database ..Stored Procedure is the only option available. — Operation . you need to provide either the server name or database name or both. The meanings of Server and Database differ depending on the particular database being used. Click Define procedure parameters.If the stored procedure is not in the local database instance. For specific information.

TIBCO Business Studio .Process Developer’s Guide . These Case Fields are represented in TIBCO Business Studio as Data Fields: In this example. — Click the Add button to add a Parameter. and Remove buttons. — Select the Case Fields (Data Fields) from the Select Data Field dialog. Similarly. For more information about delayed release steps and using the Return Code field. the stored procedure outputs the parameters Bal and Rcode to the Case Fields BALANCE and Return Code. the stored procedure takes the input parameters Acct and Amount and maps them the Case Fields DEBIT ACCOUNT and AMOUNT.Making a Database Call 55 | Fields in the TIBCO iProcess Engine. see the TIBCO iProcess Database Plug-in User’s Guide. Move Down. output to the iProcess Engine (OUT) or both (INOUT). — You can remove or reposition the Parameters using the Move Up. — Select from the drop-down list whether the parameter is input to the stored procedure (IN).

You can then select the desired Data Field from the list and continue entering JavaScript: TIBCO Business Studio . on the Implementation tab for a Script Activity. For example. All matching Data Fields are displayed: Although TIBCO Business Studio allows you to create Process Data (for example. enter the character "F". you can enter JavaScript that will be executed at runtime: The Script: area supports the usual text editing assistance such as color syntax highlighting. such names are not displayed in content assist. content assist and error markers are supported. a Data Field) that has spaces in its name. then press Ctrl + Space.Process Developer’s Guide . if you want to specify a Data Field called Field1.56 | Chapter 3 Tasks Creating a Script Activity In the Properties view.

For example. TIBCO Business Studio . If you have selected the iProcess Engine or iProcess Modeler destination environment.Process Developer’s Guide . When this is corrected.). you can use the following template to construct an if else: iProcess Script is supported for backward compatibility via the TIBCO iProcess JavaScript class library. Content assist also provides templates for common JavaScript constructs. Within the packaging/export phase this JavaScript is converted to iProcess Script for execution by the iProcess engine. you can view the available list of iProcess Script functions by typing IPE and pressing Ctrl + Space.Creating a Script Activity 57 | Note that in this case there is a red "x" next to the line. if you enter if. This is because validation has reported an error in the Problems view because the line is not terminated with a semi-colon (. the error and the red "x" are removed. then press Ctrl + Space.

On the General tab. this causes the Sequence Flow to be followed only if the condition is met: The Script: area supports the usual text editing assistance such as color syntax highlighting. At runtime. TIBCO Business Studio . content assist and error markers (see Creating a Script Activity on page 56 for more information). You can comment these when implementing the condition.Process Developer’s Guide .58 | Chapter 3 Tasks Associating a Script with a Conditional Flow Scripts are associated with a Conditional Sequence Flow in the Properties view. there may be text comments describing the condition that needs to be set. Only one statement that evaluates to a Boolean value is allowed if you are exporting/deploying to the iProcess Engine. on the Implementation tab.

For example: In this case.Process Developer’s Guide . the event would fire at 00:00 on the Date specified. The script area cannot be empty if you want to export or deploy to the iProcess Engine.Timer Event Scripts 59 | Timer Event Scripts Scripts can be added to Start or Intermediate events in the Properties view for the event. The script that you specify is limited to two statements. If only the Time were specified. If you specify only one statement. it must evaluate to either a Date or a Time. If only the Date were present. TIBCO Business Studio . If you specify two statements. the event would fire at the specified time on the current date. one must evaluate to a Date and the other to a Time. the event will be fired at the Date and Time specified.

select the Java option from the Service Type drop-down list: TIBCO Business Studio . Select the Service Task. then on the General tab of the Properties view for the Service Task.Process Developer’s Guide .60 | Chapter 3 Tasks Calling Java Code You can call Java code by creating a Service Task as follows: You must have created a Java Project in your workspace or imported a Java Project into your workspace so that it is available for the Service Task that you are going to create. For more information about creating or importing Java Projects. see the Java Development User Guide in the Eclipse documentation. 1.

To do this. Select from the drop-down list the Method that you want to use. Select the appropriate class that you want to use. For example: TIBCO Business Studio . click Select Factory. the character s was entered. selecting it populates the Class and Method fields. If a factory is available. Click Select Class. and all classes starting with s are displayed. 3. In the previous example. If you begin typing.Calling Java Code 61 | 2. the matching classes are displayed. The Select Class dialog is displayed: An alternative to selecting the Class is to select a factory to create the Class.Process Developer’s Guide .

If you attempt to map Data Fields or Parameters to Parameters of a different type (for example.62 | Chapter 3 Tasks Complete the Parameter Mapping Click the Mapping In and Mapping Out tabs to complete the input and output mapping between any Parameters or Data Fields in your Process and the Java code. For example: • • You cannot map Data Fields or Parameters with spaces in their names. an error is generated in the Problems view.Process Developer’s Guide . TIBCO Business Studio . This shows a method that returns a String which is then mapped to the Name Parameter. mapping a String to an Integer).

When you want to package your project. Project > Build Automatically is selected.Packaging a Process 63 | Packaging a Process Packaging happens automatically and is a prerequisite to Deployment. a version of it is also saved to XPDL1 ready for deployment to the iProcess Engine. and it has no errors. This means that when you save your Package (XPDL2). By default. TIBCO Business Studio .Process Developer’s Guide . select either Project > Build All or Project > Build Project. The Process is only available for deployment using the Deployment wizard if its Destination Environment is set to iProcess Engine. because of resource or memory considerations). If you choose to package your project manually (for example. de-select Project > Build Automatically.

Process Developer’s Guide . you can manage Modules on the Server. you cannot start and stop the Server from within TIBCO Business Studio. Withdraw. a Module corresponds to a Process with the Destination Environment set to iProcess Engine. you can Release. In the iProcess Engine. For example. and so on. and a Server represents a running TIBCO iProcess Engine where you want to deploy the Process. Once connected. However. deploy again. you can connect and disconnect from the Server. modify the Process. and Undeploy Modules. re-import to TIBCO Business Studio. TIBCO Business Studio . This is because the Studio process description may contain far more than merely the execution information required for iProcess Modeler/iProcess Engine.64 | Chapter 3 Tasks Deploying a Process TIBCO Business Studio allows you to deploy a resource (represented in TIBCO Business Studio as a Module) on a local or remote system (represented in TIBCO Business Studio as a Server). Information can be lost if you deploy to the iProcess Engine. The iProcess Engine must be running. Direct Deployment to the TIBCO iProcess Engine is a one-way operation.

if the required server has been registered and the Module created.Deploying a Process 65 | The following diagrams shows the steps for deploying a Process the first time: Once you have deployed a Process. you do not need to repeat these steps each time you deploy the Process.Process Developer’s Guide . TIBCO Business Studio .

Process Developer’s Guide . If you are planning to deploy a Process to the iProcess Engine. but the version with errors will not be displayed/deployable. However. Right-click Deployment Servers and select New > Server. If you are attempting to deploy a Process for the first time and it contains errors. do the following: 1. TIBCO Business Studio . if you have de-selected Project > Build Automatically. Creating a New Server To create a new server. a new minor version is created. As described in Packaging a Process on page 63. 4. For this reason. Enter a Server Name (to identify the server within TIBCO Business Studio). enable the Process Developer Capability by clicking . 2. 2.66 | Chapter 3 Tasks Package/Process Naming The name of a Process in TIBCO Business Studio is truncated to the first eight alphanumeric characters when it is deployed to the iProcess Engine. If the Process has already been deployed. Packaging occurs automatically. If you deploy a Process that has the same name as a Process that has already been deployed. If you cannot see the Deployment Servers branch of the Project Explorer. Preparing a Process for Deployment To deploy a Process to a TIBCO iProcess Server. make sure that you select either Project > Build All or Project > Build Project to manually package your Process. Create the Process and set the Destination Environment to iProcess Engine. you should be aware of the names of existing procedures in the target deployment environment to ensure that you do not unintentionally overwrite an existing procedure. 3. TIBCO Business Studio prevents you from deploying a Process with errors. The Package Name of the Process you are deploying becomes the Library Name upon deployment to the iProcess Engine. it will not be shown in the Deployment wizard and you cannot deploy it. Resolve all of the problems reported in the Problems view. (comma) characters. do the following: 1. you should ensure that the first eight alphanumeric characters of the Process name in TIBCO Business Studio are unique and do not contain ^ (caret) or . the version that was previously deployed will be available in the Deployment wizard.

Accept iProcess Engine Server as the Runtime Environment. where the JMX objects are stored.Enter localhost if the server is on your local machine. you must ensure that you also change Path in TIBCO Business Studio so that both settings match.The MBean Name is set in the configuration file SWDIR\etc\swjmx_config. Click Next. If you cannot determine the port number.Valid iProcess Engine user with either the PRODEF or ADMIN permission that can connect to the iProcess Engine (for example. 6.Process Developer’s Guide . In the Project Explorer. — Repository Type: Select Workspace to allow the Module to be deployed from your Eclipse workspace. — Password . If you have changed the default MBean Name setting for the iProcess Engine by editing the configuration file. — Path . — Host . By default the Port is 10025.The port number that the iProcess Engine uses for the JMX engine. Enter the runtime server parameters. contact your iProcess Administrator. Connecting to a Server You can connect to a server you have created as follows: 1. TIBCO Business Studio uses the default name TIBCO:IProcessDeployment=default.Specifies the path on the server to the JMX service.properties file. Click Finish. otherwise enter the machine name or IP address of the computer where the iProcess Engine is installed. TIBCO Business Studio . — Username . If you have changed the default location of the JMX service. The new Server is created and displayed in the Project Explorer. 5. This was configured during installation of the iProcess Engine and stored in the SWJMXConfig. IPEADMIN).port entry in the SWDIR\etc\swjmx. you must ensure that you also change MBean Name in TIBCO Business Studio so that both settings match.Password for the user connecting to the iProcess Engine. — Port . expand Deployment Servers.Deploying a Process 67 | 3. The default for Path is /server (this is the default iProcess Engine setting). — MBean Name .xml. 4.

Right-click the server name of the server you are connecting to and select Connect. check the error log by selecting Help > About Eclipse Platform. you can deploy a Process to an iProcess engine as follows: TIBCO Business Studio . Deploying a Module Once you have connected to a Server.Process Developer’s Guide .68 | Chapter 3 Tasks 2. the Properties view for the server displays Connected as the Server State: If you encounter any problems connecting to a Server. The username and password you entered when you created the server is authenticated on the deployment server to prevent you from deploying a Process to a server which you do not have authorization to use. When you have connected. click Configuration Details then click View Error Log. From the resulting dialog. 3.

Process Developer’s Guide . Right-click the Server on which you want to deploy and select Deploy Module. Select the appropriate Module Type depending on whether your Module is located in your Workspace or in a local folder. The following dialog is displayed: 2. TIBCO Business Studio . and click Next.Deploying a Process 69 | 1.

70

| Chapter 3

Tasks

3. Depending on the option you selected in the previous step, continue as follows: — If you selected Workspace iProcess XPDL Module in the previous step, you are prompted to select the Package that contains the Process you want to deploy.

You can also select the Deployment Policy for the Module - either Deploy on request which deploys the Module when you explicitly choose to do so, or

TIBCO Business Studio - Process Developer’s Guide

Deploying a Process 71

|

Deploy on save which deploys the Module whenever a new version of the Package is saved/packaged. — If you selected External iProcess XPDL Module in the previous step, you are prompted to enter a URL that points to the Module you want to deploy:

You can also click Browse to locate the Module. 4. Click Finish. When the deployment is finished, TIBCO Business Studio displays the following message:

TIBCO Business Studio - Process Developer’s Guide

72

| Chapter 3

Tasks

Managing Deployed Modules
When a Module is first deployed to the iProcess Engine, the resulting Procedure is in an Unreleased state. This is indicated in the Properties view:

Right-clicking the Procedure shows the operations that you can perform when the Procedure is in an Unreleased state:

As shown, you can Release or Undeploy the Procedure. You cannot undeploy a Procedure with active Cases.

Similarly after you have released a Procedure, you can withdraw or undeploy a Procedure.

Changing Server Properties
If you need to change a Server’s properties (for example, to change the password or to change the IP address of the server) do the following:

TIBCO Business Studio - Process Developer’s Guide

3. Make the necessary changes to the properties. You can change the configuration while connected to the Server.Deploying a Process 73 | 1. 4. When you have finished making changes. Click Auto Deployed Modules to see a list of Modules for which you specified Deploy on save when you created them. click Remove to disable automatic deployment for the selected Module. If there are Modules which you no longer wish to automatically deploy. TIBCO Business Studio . Select the Server. right-click and select Properties. The changes take effect the next time you connect to the Server. A dialog similar to the following is displayed: 2.Process Developer’s Guide . and when you next Connect your changes will be applied. click OK.

74 | Chapter 3 Tasks Disconnecting from the Server To disconnect from a Server. The Server State in the Properties view should change to Disconnected: TIBCO Business Studio . right-click the Server and select Disconnect.Process Developer’s Guide .

there are two Capabilities: • • Analyst Capability (see the TIBCO Business Studio Modeling User’s Guide) Process Developer Capability (described in this section). TIBCO Business Studio . Within the Modeling Perspective.Process Developer’s Guide .| 75 Chapter 4 Reference In Eclipse. A Capability in Eclipse is a mechanism to enable and disable specific areas of UI based on the current user's selected role. This section of the help describes the major parts of the TIBCO Business Studio user interface that are specific to the Process Developer Capability of the Modeler Perspective. a Perspective includes the views and set of editors that you commonly use for a specific type of work. TIBCO has created several TIBCO Business Studio perspectives that include the views and editors you commonly use when creating business processes.

Allows you to select the Data Fields or Parameters that the Task requires as output. the step is created with a standard iProcess Form Allows you to select the Data Fields or Parameters that the Task requires as input.Process Developer’s Guide . Upon deployment/import to the iProcess Engine. To see this view. the Task becomes a step with a Form type of Formflow Form. Parameters Inbound Parameters Outbound Parameters TIBCO Business Studio . If you do not specify a URL. select Window > Show View > Properties.76 | Chapter 4 Reference Properties View The Properties View shows you detailed information about the currently selected object and allows you to specify the characteristics of an object. the following properties are available: Tab Implementation Property Form URL Description You can specify the URL of a form that you have created. To view property information. you must have an object selected. User Task Properties When you have selected a User Task in the Process Editor.

Note: Except for a WSDL obtained from BusinessWorks.Properties View 77 | Service Task Properties (Web Service/BusinessWorks Service) When you have selected a Service Task in the Process Editor with either Web Service or BW Service as the Service Type. Port Name Operation Name See Service Name description. Select this option if the WSDL is located remotely. the WSDL you select must use the SOAP over HTTP data transport mechanism and the call style must be either Document Literal or RPC Encoded. Select this option if you have added the WSDL to the project and want the WSDL to be packaged with the Project during the Packaging phase. the following properties are available: Tab General Property Service Name Description • When you click the Select button and choose a WSDL operation. it cannot be packaged with the Project. It must also use the Synchronous Request/Response Message Exchange Pattern.Process Developer’s Guide . Use local WSDL Use remote WSDL TIBCO Business Studio . the Service Name and Port Name fields are populated from the WSDL. Click the Select button to choose a WSDL operation from a WSDL that you have added to the Project (see Adding a WSDL to the Project on page 44). If this is the case.

you must specify at least one input parameter mapping. dragging to the destination Parameter.Process Developer’s Guide . the following properties are available: Unless otherwise stated. Create a mapping by clicking a Parameter. button to select the Data TIBCO Business Studio . Note: For deployment to the iProcess Engine. you must specify at least one output parameter mapping. Click the Field or Parameter. Note: For deployment to the iProcess Engine. Create a mapping by clicking a Parameter. all of the properties listed in the following table can be specified using a Data Field or Parameter. then releasing the mouse button. Use this section to create a mapping from a formal parameter of a service to an actual parameter (Data Field or Parameter).78 | Chapter 4 Reference Tab Mapping In Property Description Use this section to create a mapping from an actual parameter (Data Field or Parameter) into the formal parameters of the selected service. dragging to the destination Parameter. Mapping Out Service Task Properties (Email) When you have selected a Service Task in the Process Editor with Email as the Service Type. however you cannot specify more than one output parameter mapping. then releasing the mouse button.

Click src and preview to alternate between viewing the source of the body text and previewing how it will look to the recipient E-mail > Definition From To Cc Bcc Reply To Headers Priority Subject E-mail > Body TIBCO Business Studio . Specify the body text that comprises the message. Use this parameter to specify additional information in the header of the email. Use this parameter to specify a different email address to which recipients of a message can reply. Specify the recipients to whom you want to send a copy of the email. Their email address is visible to other recipients of the email. Their email address is not visible to other recipients of the email. High or Low). Specify a subject line for the message. Specify the recipients to whom you want to send a copy of the email.Properties View 79 | Tab General Property To Subject Body Description Specify the recipient of the email. Specify a subject line for the message.Process Developer’s Guide . Select a priority from the drop-down list (Normal. Specify the recipient of the email. Select either Use Server Configuration to use the address of the server from which the email is sent or select Use Custom Configuration to select different configuration details. Enter the body text of the message.

80 | Chapter 4 Reference Tab E-mail > Attachments Property Field Contents Description Specify a document to be attached to the message: • Field Contents: .select either a Parameter or Data Field that contains the message you want displayed when the email cannot be sent. Select Use Custom SMTP Configuration settings to specify a different Host and Port from the server where the Process will run. • E-mail > SMTP Configuration Use Server SMTP Configuration User Custom SMTP Configuration Select User Server SMTP Configuration to use the settings of the server where the Process will run. Use this Property to provide for basic error handling (for example. E-mail > Error Handling Return Status Fields • TIBCO Business Studio . Message: . Files: use this option to browse the file system and attach a file to the email message.use this option to attach the contents of a Parameter or Data Field to the email message.select either a Parameter or Data Field that represents an error code. if a message cannot be sent) • Code: .Process Developer’s Guide .

the following properties are available: Tab General Property Server Description If the stored procedure is not in the local database instance.]stored_procedure_name Database Operation SQL Database Operation SQL See previous description on the General tab. The default instance is the one that your TIBCO iProcess Engine is currently using. See description of Server. Stored Procedure is the only option available.Properties View 81 | Service Task (Database) When you have selected a Service Task in the Process Editor with Database as the Service Type. TIBCO Business Studio . you need to provide either the server name or database name or both. See previous description on the General tab.Process Developer’s Guide . Specify the name of the stored procedure in the following format: [owner.

Process Developer’s Guide . Select the Case Fields (Data Fields) from the Select Data Field dialog.82 | Chapter 4 Reference Tab Property Parameters Description Click Define procedure parameters. You can automatically populate this field by clicking Select Class and selecting the desired class. or the Database tab to define the parameter mappings between parameters in the stored procedure and Case Fields in the TIBCO iProcess Engine.. Class TIBCO Business Studio . the following properties are available: Tab General Property Project Description Specifies the Project that contains the Java code you want to call. output to the iProcess Engine (OUT) or both (INOUT). Service Task (Java) When you have selected a Service Task in the Process Editor with Java as the Service Type.. • You can remove or reposition the Parameters using the Move Up. • • Click the Add button to add a Parameter. Move Down. Displays the Class of which you want to create an instance (selected by clicking Select Class or Select Factory). These Case Fields are represented in TIBCO Business Studio as Data Fields. Select from the drop-down list whether the parameter is input to the stored procedure (IN). and Remove buttons.

Class (factory) Method (factory) Mapping In Mapping Out TIBCO Business Studio . then releasing the mouse button. dragging to the destination Parameter. As an alternative to clicking Select Class. Method factory used to create an instance of a Class. you can click Select Factory to choose a factory class to create an instance of a Class.Properties View 83 | Tab Property Method Description After you have selected a class. Create a mapping by clicking a Parameter. Use this section to create a mapping from a parameter of a Method to an actual parameter (Data Field or Parameter).Process Developer’s Guide . This is populated when the Factory is selected. Select a Method from the drop-down list. Create a mapping by clicking a Parameter. then releasing the mouse button. dragging to the destination Parameter. this drop-down list is populated with the available methods. Use this section to create a mapping from an actual parameter (Data Field or Parameter) into the parameters of the selected Method.

84 | Chapter 4 Reference Script Task When you have selected a Script Task in the Process Editor. The usual text editing assistance such as color syntax highlighting. However. the following properties are available: Tab General Property Service Type Description By default this is Unspecified.see Service Task Properties (Web Service/BusinessWorks Service) on page 77. TIBCO Business Studio . you can specify for documentation purposes that a Send or Receive Task send a message or receive a message using a web service. note the following: • • Send Tasks cannot be deployed. the web service information is ignored upon deployment. but optionally. You select a web service operation for a Send or Receive Task in the same way you would for a Service Task (Web Service) . the following properties are available: Tab Implementation Property Script Description Enter JavaScript that will be executed at runtime. Send and Receive Tasks When you have selected a Send or Receive Task in the Process Editor. content assist and error markers are supported.Process Developer’s Guide . If a Receive Task specifies a web service implementation.

If you selected TIBCO iProcess Engine. For more information see the TIBCO Business Studio Modeling User’s Guide. • Any error messages resulting from this validation will be displayed in the Problems View and indicate which parts of your Process need to be changed. In addition.Process Developer’s Guide . General Rules for Direct Deployment to the TIBCO iProcess Engine For a Process that you intend to directly deploy to the TIBCO iProcess Engine (those with the TIBCO iProcess Engine Destination Environment selected).for more information see the TIBCO Business Studio Modeling User’s Guide. even if you have not explicitly selected that Destination Environment. TIBCO Business Studio performs validation to ensure that the Process can be imported into the TIBCO iProcess Modeler. Independent Sub-Process step must specify a Sub-Process located within the same Package. when you save your Process. TIBCO Business Studio performs validation to ensure that the Process can be directly deployed to the TIBCO iProcess Engine. when you save your Process. TIBCO Business Studio . Observe the following general rules for Processes that you intend to directly deploy to the TIBCO iProcess Engine: • Timer events must have scripts defined. • Rules for Direct Deployment of Scripts Note the rules listed in this section for Processes that you are deploying to the TIBCO iProcess Engine. TIBCO Business Studio also performs the validation for import into the TIBCO iProcess Modeler.Process Validation 85 | Process Validation When you created your Process you selected the Destination Environment: • If you selected TIBCO iProcess Modeler. it cannot contain other types of script expressions. TIBCO iProcess Engine validation (described in this section). These validation rules are described in this section. The script must contain a date expression or a time expression or both. there are three different sets of validation rules that are applied to the Process: • • TIBCO iProcess Modeler validation .

and are therefore not allowed in Processes with the TIBCO iProcess Engine destination environment selected: • • • • • • • • • • • • • • • • • • • • • • • Local method definition Try Catch Finally Blocks Switch Case statement Throw statement New Expressions Continue statement Break statement Local variable definition Labelled statement Multi-dimensional arrays ! (NOT) ~ >> (Right shift operator) >>= (Right shift assign operator) >>> << (Left shift operator) <<= (Left shift assign operator) condition?option1:option2 % (Mod operator) %= (Mod assign operator) |= &= instanceof operator Datetime Process Data You cannot perform operations on Datetime process data.86 | Chapter 4 Reference Unsupported Constructs/Operators The following JavaScript constructs and operators are not supported in the TIBCO iProcess Engine. TIBCO Business Studio . MyDateTime. You can however use the Date or Time properties of process data in expressions (for example.Date="09/05/2007".Process Developer’s Guide .).

Process Validation 87 | Array Fields You can access the elements of an array by specifying the index (for example. MyStringArray[2]. Right-click the problem and select Go To. The gives you the option of having TIBCO Business Studio correct the problem for you. • TIBCO Business Studio . This displays the Process in the Process Editor.Process Developer’s Guide . Note that there is no support for a length attribute to determine the number of items in an array.). allowing you to correct the problem. Correcting Validation Errors Any problems that result from validation are shown in the Problems view. To correct the problem do one of the following: • Right-click the problem and select Quick Fix (if enabled for the current problem).

88 | Chapter 4 Reference TIBCO Business Studio .Process Developer’s Guide .

68 definition 33 managing Modules 72 tutorial 25 Packaging 63 Parameter 35 mapping 62 Participant 36 Process 34 correcting errors 87 testing 5 validation 85 Process Component 33 Properties View 76 E E-Mail Task 22 TIBCO Business Studio .Process Developer’s Guide .Index 89 | Index A Artifact 32 error correcting 87 errors 85 Extended Attributes 35 B J Business Process Management (BPM) 4 Business Process Modeling Notation (BPMN) 37 Java code 10 calling 60 C M Concept 34 Concept Model 34 Conditional Flow script 58 customer support 5 Mapper 48 Model Driven Architecture (MDA) 3 Module 33 P D Data Field 34 database 9 database call 54 Deployment 12.

40 properties 76 tutorial 14 S sample Processes 6 script on Conditional Flow 58 Script Activity 56 Script Task 84 Sending an Email 50 Server connecting to 67 creating 66 disconnecting 74 properties 72 Service Call adding 42 Service Oriented Architecture (SOA) 4 Service Task 6 Database 81 Email 78 Java 82 tutorial 18 Web Service 77 Service Task BusinessWorks 77 support.Process Developer’s Guide . contacting 5 V validation error correcting 87 W Web Service Definition Language (WSDL) file 45 adding 44 copyingL 45 creating 44 Task 47 Web Services calling 18 T technical support 5 TIBCO Business Studio sample Processes 6 tutorials 18 TIBCO BusinessWorks Web Service 7 X XML Process Definition Language (XPDL) 37 TIBCO Business Studio . and Integration (UDDI) Registry adding 42 searching 42 User Task 6.90 | Index Q Quick fixes 87 U Unified Modeling Language (UML) 37 Uniform Description. Discovery.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->