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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

BPM/SOA Implementation Overview 11 | • • • • • 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.Process Developer’s Guide . elseif. For example. 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. 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. TIBCO Business Studio . if you enter if. then press Ctrl + Space. Content assist is available for process data that you define and also provides templates for common JavaScript constructs. If you have selected the iProcess Engine or iProcess Modeler destination environment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

TIBCO Business Studio . 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. when it is deployed to the iProcess Engine.30 | Chapter 1 Getting Started Note that because our original Process name in TIBCO Business Studio (DeployTest) has more than eight characters. see Managing Deployed Modules on page 72.Process Developer’s Guide . it is truncated (DEPLOYTE).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

— Select Use Custom SMTP Configuration settings to specify a different Host and Port. Click Attachments to specify a document to be attached to the message: — Field Contents: . 5. TIBCO Business Studio .Process Developer’s Guide . 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. 6. — Files: use this option to browse the file system and attach a file to the email message.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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Process Developer’s Guide . Files: use this option to browse the file system and attach a file to the email message. Message: .select either a Parameter or Data Field that represents an error code.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.80 | Chapter 4 Reference Tab E-mail > Attachments Property Field Contents Description Specify a document to be attached to the message: • Field Contents: .use this option to attach the contents of a Parameter or Data Field to the email message. • E-mail > SMTP Configuration Use Server SMTP Configuration User Custom SMTP Configuration Select User Server SMTP Configuration to use the settings of the server where the Process will run. Select Use Custom SMTP Configuration settings to specify a different Host and Port from the server where the Process will run. if a message cannot be sent) • Code: .

]stored_procedure_name Database Operation SQL Database Operation SQL See previous description on the General tab. See previous description on the General tab.Process Developer’s Guide . Specify the name of the stored procedure in the following format: [owner.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. Stored Procedure is the only option available. The default instance is the one that your TIBCO iProcess Engine is currently using. TIBCO Business Studio . See description of Server. you need to provide either the server name or database name or both.

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

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

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

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

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

). 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 . Right-click the problem and select Go To. Correcting Validation Errors Any problems that result from validation are shown in the Problems view. Note that there is no support for a length attribute to determine the number of items in an array.Process Developer’s Guide . allowing you to correct the problem. MyStringArray[2]. This displays the Process in the Process Editor.Process Validation 87 | Array Fields You can access the elements of an array by specifying the index (for example.

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

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.

and Integration (UDDI) Registry adding 42 searching 42 User Task 6. 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 . Discovery.90 | Index Q Quick fixes 87 U Unified Modeling Language (UML) 37 Uniform Description. 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