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

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

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

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

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

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

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

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

The Corporate Developer must implement this across the organization. For example: • An insurance company wants to enable their financial advisors to sell pension plans door-to-door using portable tablets. refining it. The Corporate Developer must implement a business process for doing this. adding detail to it.Process Developer’s Guide .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. 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. The following diagram shows how TIBCO Business Studio is intended to be used: TIBCO Business Studio . A company has acquired a competitor.

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

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

See the TIBCO Business Studio Modeling User’s Guide for more information about generating Process documentation. Test and debug the services created in Java using tools external to TIBCO Business Studio. service implementations are created by different people or groups from those who consume the services provided by the process implementation. For more information. see the TIBCO iProcess Modeler set of guides. create any custom Java services that are required. for more information on creating services see the documentation for TIBCO BusinessWorks and TIBCO ActiveMatrix. 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. Deploy the Package/Process to the Repository and initialize it without handoff to Operations staff. for example using the Eclipse IDE. TIBCO Business Studio . This guide focusses on the work of the person consuming services. and so on. Package Process for Deployment to User Acceptance Testing/Production by the Operations staff.Process Developer’s Guide . test queues. 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. • • Process Testing Ensure that the Process functions as intended including starting cases. undelivered work items. In some organizations. either those embedded in the Eclipse Platform Development Environment (PDE) or any other tools that are available.Implementation Approach 5 | Service Creation/Testing for Sub-Processes Optionally.

see Tasks on page 39. Service Tasks Service Tasks can be implemented in the following ways: • Web Service . For more information about specific tasks. TIBCO Business Studio . This section provides an overview of elaborating a Process. a User Task with a Form URL specified becomes a step with a Form type of Formflow Form. see TIBCO iProcess Client (Browser) Configuration and Customization. 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. the step is created with a standard iProcess Form.Calls to a web service can be implemented as well as the mapping of input/output parameters. you may want to call a web service from a Service Task. If no URL is specified. For example.Process Developer’s Guide .6 | Chapter 1 Getting Started BPM/SOA Implementation Overview This section provides an overview of how to augment the Process with execution details. For more information.

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

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.8 | Chapter 1 Getting Started • BusinessWorks live link . 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 . however you cannot specify more than one output parameter mapping. The web service call style must be either Document Literal or Remote Procedure Call (RPC) Encoded. see the TIBCO iProcess BusinessWorks Connector User’s Guide. the iProcess Engine Service Agent must be running and the JMS provider transport information must be configured. For more information.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. Except for a WSDL obtained from a TIBCO BusinessWorks live link. Parameter Mapping • • The web service must have at least one input and output parameter mapping.Process Developer’s Guide .

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

you can define Data Fields or Parameters for this purpose. int. subject lines and so on. see Sending an Email on page 50. For example. Script Tasks You can enter scripts in Script Tasks. Alternatively you can specify a Factory to be used for the creation of the class. and so on) must adhere to JavaBeans semantics. 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 . and to Timer Start or Intermediate Events. on Conditional Sequence Flows. 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 . This means that a String property 'name' must have an accessor named getName():String and a mutator named setName(:String). The factory class must either offer a static factory method or must have a default constructor as the service class does. Specifically they must have a default constructor (one without parameters) and the properties need to have standard get and set operations. the previous dialog shows %Manager% rather than an explicit email address. float. Note that instead of explicitly entering email addresses. You can browse to select the Java class and select a Method from the drop-down list.10 | Chapter 1 Getting Started Clicking More Details or clicking the E-Mail tab allows you to specify further parameters. For more information.

Process Developer’s Guide . If you have selected the iProcess Engine or iProcess Modeler destination environment. elseif. then press Ctrl + Space.BPM/SOA Implementation Overview 11 | • • • • • If. TIBCO Business Studio . 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. 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. if you enter if. For example. Within the packaging/export phase this JavaScript is converted to iProcess Script for execution by the iProcess engine. Content assist is available for process data that you define and also provides templates for common JavaScript constructs. you can view the available list of iProcess Script functions by typing IPE and pressing Ctrl + Space.

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

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

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

For example. • • In some cases. click the Parameters tab. expense amount. TIBCO Business Studio . Click the Enqueue Payment Task. the Data Fields and Parameters may have already been added by the Business Analyst.Process Developer’s Guide . In the Project Explorer. Task B Create Parameters/Data Fields Create the Data Fields and Parameters that will be used by the Process as follows: 1. 4. before the expenses can be approved. the performer of this action needs basic information such as the employee name. 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. and so on. right-click Data Fields and select New > Data Field. 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 Properties view.Tutorial 1: Elaborating a Process: User Tasks 15 | Many of the Tasks in this Process require input and output. Adding Parameters to the Process means that when it is exported to the iProcess Modeler if will be a Sub-Procedure. Right-click Parameters and select New > Parameter. expand the Submit Expenses Process. cost center. 2.

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

see Tutorial 3: Deploying a Process on page 25 and Deploying a Process on page 64. Upon import or deployment to the iProcess Modeler.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. TIBCO Business Studio .Process Developer’s Guide . the Data Fields become Fields and the Parameters become I/O Parameters and Fields. For example: For more information about deployment.

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

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

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

mapping the input and output parameters.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. Upon import or deployment to the iProcess Modeler.Process Developer’s Guide . the Service Task becomes a Web Services EAI step: TIBCO Business Studio .

In this section. see Tutorial 3: Deploying a Process on page 25 and Deploying a Process on page 64. we will add an email task to notify the person who submitted the claim when the payment is made.Process Developer’s Guide .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 also add a Manual Task in the event that the payment fails. 1. Insert a Gateway after the Make a Payment Activity. Creating an E-Mail Task In the previous section. we added a call to a web service from the Make a Payment Activity. TIBCO Business Studio . This included a Confirmation parameter which indicated whether the payment was successful.

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

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

5. 6.Process Developer’s Guide .port entry in the SWDIR\etc\swjmx. 3. If you are unsure of any of these prerequisites. Right-click the Process Packages folder and select New > Process Packages. contact your iProcess Administrator. If you cannot determine the port number. By default the Port is 10025. TIBCO Business Studio . 4.properties file. Name the Package Tutorial and click Next. This was configured during installation of the iProcess Engine and stored in the SWJMXConfig. 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. Name the Process DeployTest and click Finish. Select New > New Project and follow the wizard to create a new BPM/SOA Developer Project with the default configuration. and click Next. Click Next to accept the Packages folder and file name. select the An empty iProcess process item. Select the Create a package using one of the following templates check box.Tutorial 3: Deploying a Process 25 | Tutorial 3: Deploying a Process This tutorial describes creating and deploying a simple Process to an iProcess Engine. see your iProcess administrator for details. The package name will be used to create the library name when the Process is deployed to iProcess. Task A Create the Process 1. 2.

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

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

Right-click the TestDeploy Server and select Deploy Module. From the resulting dialog. check the error log by selecting Help > About Eclipse Platform.28 | Chapter 1 Getting Started 3. the Properties view for the server displays Connected as the Server State: In addition. When you have connected. 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.Process Developer’s Guide . If you encounter any problems connecting to a Server. Task D Deploy the Process Deploy the Process to the iProcess Engine as follows: 1. The following dialog is displayed: TIBCO Business Studio . click Configuration Details then click View Error Log.

see Deploying a Module on page 68. Click Details to get more information about why the deployment failed. Select Test2 and click Finish. When the deployment is finished. You can view the newly-deployed Process in the Project Explorer: TIBCO Business Studio . (For more information about Deployment Policy.Process Developer’s Guide .Tutorial 3: Deploying a Process 29 | 2. 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. an error symbol is displayed instead of the information symbol in the previous dialog. For more information about the External Module option. Select Workspace iProcess XPDL Module. see Deploying a Module on page 68). 3.

TIBCO Business Studio . when it is deployed to the iProcess Engine.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.Process Developer’s Guide . see Managing Deployed Modules on page 72. it is truncated (DEPLOYTE).

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

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

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

TIBCO Business Studio provides an Eclipse editor called the Concept Model Editor to help you construct your Concept Model.34 | Chapter 2 Concepts and Definitions Project Objects This section describes Process objects that relate to Process development. In object-oriented terms. broker. For example. 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. you cannot export the resulting Process to the iProcess Engine. when you create a Concept Model. There are several types of Data Field: • Boolean .Process Developer’s Guide . 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. This is because the complex data types created in the Concept Modeler are not supported in the iProcess Engine. If you intend to execute a Process in the TIBCO iProcess Engine. in a financial environment. You can create Data Fields to represent the pool of candidates going into the Activity and the suitable candidates that have been identified. be aware that Data Fields or Parameters with spaces in their names cannot be used for mapping (for example.true or false TIBCO Business Studio . mapping to Parameters in a web service). For more information. suppose an Activity is to identify a list of suitable candidates for an available position. and so on).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. counterparty. Concept Model A set of business terms specific to your corporate environment (for example. see the TIBCO Business Studio Concept Modeler User’s Guide.

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. the field lengths include the decimal point. or on the Extended Attributes dialog in the New Process wizard. For example.is a text field that you want to use as a Participant String .34 has a length of five and two decimal places) In the iProcess Modeler.Process Developer’s Guide .decimal number of the specified length and decimal places (for example. • Decimal Number . 345) Performer .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").integer value of the specified length (for example. Parameters Parameters are similar to Data Field but are either input to or output from an external source. • • • Integer Number .true or false TIBCO Business Studio . when imported into the iProcess Modeler has a length of six and two decimal places.34. so the previous example. the number 130.Project Objects 35 | • Date Time . 130. Parameters can be any of the following types: There are several types of Data Field: • Boolean . during simulation Parameters are either created by TIBCO Business Studio or imported from a file.

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

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

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

page 63 Deploying a Process. page 42 Sending an Email. page 56 Associating a Script with a Conditional Flow. Topics • • • • • • • • • Elaborating a User Task. page 64 TIBCO Business Studio . page 60 Packaging a Process. page 50 Making a Database Call. page 40 Adding a Service Call.| 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 58 Calling Java Code. page 54 Creating a Script Activity. package and deploy it.Process Developer’s Guide .

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

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

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

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

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

The WSDL file opens in the WSDL editor. Select the newly-created folder. Click Finish. b. either in the file system or received via e-mail. you can do so as follows: a.Process Developer’s Guide . For example: Copying a WSDL If you already have a WSDL file. Locate the WSDL file. Enter the parent directory and folder name. then click Finish. the press CRL + V. If you have not yet created a folder. 1. select it and press Ctrl + C to copy it. 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). Right-click where you want to create the folder and select New > Folder. right-click and select Special Folders > Use as Services Folder. In the Project Explorer select the folder in the Project where you want to copy the WSDL file. This enables you to expand the WSDL in the Project Explorer. you can copy and paste it into the Project. c. 2. 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 .Adding a Service Call 45 | 4.

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

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

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

5. Note that you can enter JavaScript that is applied to a mapping by clicking . if you want to append a string to a Parameter. This displays the following window. Web service operations that return more than one Parameter are not supported in the iProcess Engine/iProcess Modeler Destination Environments.Process Developer’s Guide . TIBCO Business Studio . 4.Adding a Service Call 49 | 3. Complete the output mapping in a similar fashion using the Mapping Out tab. Save the Package that contains the Process. 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. For example. the string "SEBRANCH" is appended to the input Parameter Reference. you can do so as follows: When executed in the runtime environment.

TIBCO Business Studio .Process Developer’s Guide . On the E-Mail tab. This is the minimum configuration necessary to send an email message. Select the Service Task. a subject and the body for the message. click More Details on the E-Mail tab and continue to specify further parameters. 3. select the E-Mail option from the Service Type drop-down list: 2. For further options.50 | Chapter 3 Tasks Sending an Email A Service Task can be configured to send an email message as follows: 1. 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. 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 the button to select the Data Field or Parameter.

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

use this option to attach the contents of a Parameter or Data Field to the email message. 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.Process Developer’s Guide . TIBCO Business Studio . — Select Use Custom SMTP Configuration settings to specify a different Host and Port. 6. — Files: use this option to browse the file system and attach a file to the email message. Click Attachments to specify a document to be attached to the message: — Field Contents: . 5.52 | Chapter 3 Tasks viewing the source of the body text and previewing how it will look to the recipient.

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

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

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

on the Implementation tab for a Script Activity. All matching Data Fields are displayed: Although TIBCO Business Studio allows you to create Process Data (for example. For example. You can then select the desired Data Field from the list and continue entering JavaScript: TIBCO Business Studio .Process Developer’s Guide . a Data Field) that has spaces in its name. enter the character "F".56 | Chapter 3 Tasks Creating a Script Activity In the Properties view. if you want to specify a Data Field called Field1. then press Ctrl + Space. 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.

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

On the General tab. TIBCO Business Studio . on the Implementation tab. content assist and error markers (see Creating a Script Activity on page 56 for more information). 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. Only one statement that evaluates to a Boolean value is allowed if you are exporting/deploying to the iProcess Engine. You can comment these when implementing the condition.58 | Chapter 3 Tasks Associating a Script with a Conditional Flow Scripts are associated with a Conditional Sequence Flow in the Properties view.Process Developer’s Guide . there may be text comments describing the condition that needs to be set.

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

then on the General tab of the Properties view for the Service Task. Select the Service Task. see the Java Development User Guide in the Eclipse documentation. For more information about creating or importing Java Projects.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.Process Developer’s Guide . select the Java option from the Service Type drop-down list: TIBCO Business Studio . 1.

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

If you attempt to map Data Fields or Parameters to Parameters of a different type (for example. For example: • • You cannot map Data Fields or Parameters with spaces in their names. This shows a method that returns a String which is then mapped to the Name Parameter. TIBCO Business Studio . an error is generated in the Problems view. mapping a String to an Integer).Process Developer’s Guide .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.

If you choose to package your project manually (for example.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. When you want to package your project. TIBCO Business Studio . and it has no errors. 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.Process Developer’s Guide . Project > Build Automatically is selected. This means that when you save your Package (XPDL2). because of resource or memory considerations). By default. de-select Project > Build Automatically.

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

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

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

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

From the resulting dialog. When you have connected. 3. Deploying a Module Once you have connected to a Server.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. click Configuration Details then click View Error Log. Right-click the server name of the server you are connecting to and select Connect.Process Developer’s Guide . check the error log by selecting Help > About Eclipse Platform. you can deploy a Process to an iProcess engine as follows: TIBCO Business Studio .

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

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

Process Developer’s Guide . right-click the Server and select Disconnect.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 .

Process Developer’s Guide . 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.| 75 Chapter 4 Reference In Eclipse. TIBCO Business Studio . there are two Capabilities: • • Analyst Capability (see the TIBCO Business Studio Modeling User’s Guide) Process Developer Capability (described in this section). TIBCO has created several TIBCO Business Studio perspectives that include the views and editors you commonly use when creating business processes. Within the Modeling Perspective.

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

it cannot be packaged with the Project. 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.Process Developer’s Guide . 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). Select this option if the WSDL is located remotely. If this is the case.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. Use local WSDL Use remote WSDL TIBCO Business Studio . Note: Except for a WSDL obtained from BusinessWorks. Port Name Operation Name See Service Name description. the Service Name and Port Name fields are populated from the WSDL. It must also use the Synchronous Request/Response Message Exchange Pattern. the following properties are available: Tab General Property Service Name Description • When you click the Select button and choose a WSDL operation.

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

Specify the recipients to whom you want to send a copy of the email. Specify the body text that comprises the message. Enter the body text of the message. Their email address is not visible to other recipients of the email. Use this parameter to specify additional information in the header of the email.Process Developer’s Guide . Select a priority from the drop-down list (Normal. Specify a subject line for the message. 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 . High or Low). Use this parameter to specify a different email address to which recipients of a message can reply. Their email address is visible to other recipients 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. Specify the recipients to whom you want to send a copy of the email. Specify a subject line for the message. Specify the recipient of the email.Properties View 79 | Tab General Property To Subject Body Description Specify the recipient of the email.

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

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

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

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

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

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

86 | Chapter 4 Reference Unsupported Constructs/Operators The following JavaScript constructs and operators are not supported in the TIBCO iProcess Engine. MyDateTime. You can however use the Date or Time properties of process data in expressions (for example. 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.Process Developer’s Guide .Date="09/05/2007". TIBCO Business Studio .).

• TIBCO Business Studio . Right-click the problem and select Go To. This displays the Process in the Process Editor. allowing you to correct the problem. MyStringArray[2].).Process Developer’s Guide . The gives you the option of having TIBCO Business Studio correct the problem for you. 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). Note that there is no support for a length attribute to determine the number of items in an array.Process Validation 87 | Array Fields You can access the elements of an array by specifying the index (for example.

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 .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.Process Developer’s Guide .

Discovery. 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. 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 .90 | Index Q Quick fixes 87 U Unified Modeling Language (UML) 37 Uniform Description.