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 2 Typographical Conventions. 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 .|1 Preface This guide is aimed at the corporate developer who implements business processes designed by a business analyst. page 5 TIBCO Business Studio . Topics • • • Related Documentation.

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

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

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

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

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

page 4 BPM/SOA Implementation Overview. page 18 Tutorial 3: Deploying a Process.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.|1 Chapter 1 Getting Started Topics • • • • • • • Who Should Use TIBCO Business Studio?. page 2 Implementation Approach. page 6 Deploying a Process.

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

It consists of a Platform Independent Model. graft steps. For example: TIBCO Business Studio . transaction control steps.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. delayed release. How TIBCO Business Studio Supports MDA Model Driven Architecture (MDA) is typically used to design applications and write specifications. usually written in Universal Modeling Language (UML). 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. However. and dynamic sub-procedure call steps) for which you must perform part of the augmentation and deployment of the Process in TIBCO iProcess Modeler. as well as a Platform Specific Model and Code Model. depending on the destination environment that you select. using version 2.Process Developer’s Guide . you can augment the process with execution details in TIBCO Business Studio and deploy it directly to the TIBCO iProcess Engine. both of which are applied at the programming language level. 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.

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

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

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

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

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

Process Developer’s Guide . Oracle or SQL database calls are made in the iProcess database. 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. Database A Service Task can be configured to perform an action on a database using stored procedure calls. When the Process is deployed to the iProcess Engine. 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 . If you use a remote WSDL. you can select either Use local WSDL or Use remote WSDL: If you use a local WSDL. Process to Service Binding In the Properties view for a Service Task. and the concrete portion of the WSDL can be obtained dynamically at runtime. the abstract portion of the WSDL must be present locally. the stored procedure writer will need to be familiar with the particular database. the appropriate DB2. the abstract and concrete portion of the WSDL must be present locally.

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

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

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

2. do the following: 1. which contains the tutorial solutions. To open the TIBCO Business Studio sample workspace. This starts TIBCO Business Studio and opens the sample workspace rather than your default workspace.0 Project and expand the Process Packages folder. Click Start > All Programs > TIBCO > TIBCO Business Studio 2. 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.Process Developer’s Guide .Sample Workspace.Tutorial Project 13 | Tutorial Project The samples workspace includes a Project (Process Developer Tutorial Solutions 2. TIBCO Business Studio .0) that has the completed solutions for the tutorials in the following sections.0 > TIBCO Business Studio . Expand the Process Developer Tutorial Solutions 2.

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

Right-click Parameters and select New > Parameter. cost center. Create the following Data Fields: — Manager (String) — CostCenter (String) — Authorization (String) 3. before the expenses can be approved.Process Developer’s Guide . In the Properties view. and so on. the performer of this action needs basic information such as the employee name. the Data Fields and Parameters may have already been added by the Business Analyst. For example. Task B Create Parameters/Data Fields Create the Data Fields and Parameters that will be used by the Process as follows: 1. In the Project Explorer. TIBCO Business Studio . 4. 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 some cases. 2. Click the Enqueue Payment Task. right-click Data Fields and select New > Data Field. expense amount. click the Parameters tab. expand the Submit Expenses Process.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. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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. Task D Deploy the Process Deploy the Process to the iProcess Engine as follows: 1. click Configuration Details then click View Error Log. 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. When you have connected. Right-click the TestDeploy Server and select Deploy Module. The following dialog is displayed: TIBCO Business Studio . If you encounter any problems connecting to a Server.Process Developer’s Guide . From the resulting dialog.

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

Process Developer’s Guide . TIBCO Business Studio . see Managing Deployed Modules on page 72.30 | Chapter 1 Getting Started Note that because our original Process name in TIBCO Business Studio (DeployTest) has more than eight characters. it is truncated (DEPLOYTE). when it is deployed to the iProcess Engine. 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 .| 31 Chapter 2 Concepts and Definitions This section defines concepts and terminology related to TIBCO Business Studio. TIBCO Business Studio .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

if you want to append a string to a Parameter. the string "SEBRANCH" is appended to the input Parameter Reference. you can do so as follows: When executed in the runtime environment. 4.Process Developer’s Guide . 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. 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. TIBCO Business Studio . Note that you can enter JavaScript that is applied to a mapping by clicking .Adding a Service Call 49 | 3. For example. Complete the output mapping in a similar fashion using the Mapping Out tab. Save the Package that contains the Process. 5.

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

use this parameter to specify a different email address to which recipients of a message can reply. — To: . Their email address is visible to other recipients of the email.Sending an Email 51 | — From: . — Cc: . — Reply to: . — Headers: .select a priority from the drop-down list (Normal.select the Subject line for the email message or select a Data Field or Parameter. — Bcc: .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.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. High or Low) or select a Data Field or Parameter. 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. select a Data Field or Parameter. Alternatively.specify the recipient of the email either as an explicit email address or by selecting a Data Field or Parameter. src and preview which allow you to alternate between TIBCO Business Studio . — Priority: .Process Developer’s Guide . Click Body to specify the main text of the message. — Subject: . At the bottom of the text area are two buttons. 4.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 Use Custom SMTP Configuration settings to specify a different Host and Port. 6. Click Attachments to specify a document to be attached to the message: — Field Contents: . TIBCO Business Studio . 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. 5. — Files: use this option to browse the file system and attach a file to the email message.Process Developer’s Guide .52 | Chapter 3 Tasks viewing the source of the body text and previewing how it will look to the recipient.use this option to attach the contents of a Parameter or Data Field to the email message.

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

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

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

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

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

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.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 . On the General tab. on the Implementation tab. Only one statement that evaluates to a Boolean value is allowed if you are exporting/deploying to the iProcess Engine. At runtime. You can comment these when implementing the condition. there may be text comments describing the condition that needs to be set. content assist and error markers (see Creating a Script Activity on page 56 for more information). TIBCO Business Studio .

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

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

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

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

a version of it is also saved to XPDL1 ready for deployment to the iProcess Engine. Project > Build Automatically is selected. This means that when you save your Package (XPDL2). because of resource or memory considerations). 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. By default. de-select Project > Build Automatically. and it has no errors.Process Developer’s Guide . 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. TIBCO Business Studio . When you want to package your project.

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

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

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

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

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

Right-click the Server on which you want to deploy and select Deploy Module. and click Next.Process Developer’s Guide .Deploying a Process 69 | 1. TIBCO Business Studio . 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. To correct the problem do one of the following: • Right-click the problem and select Quick Fix (if enabled for the current problem). • TIBCO Business Studio . Note that there is no support for a length attribute to determine the number of items in an array. Right-click the problem and select Go To.Process Validation 87 | Array Fields You can access the elements of an array by specifying the index (for example. Correcting Validation Errors Any problems that result from validation are shown in the Problems view.

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

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.

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

Sign up to vote on this title
UsefulNot useful