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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

TIBCO Business Studio .Process Developer’s Guide . and click Next.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. Right-click the Server on which you want to deploy and select Deploy Module. The following dialog is displayed: 2.

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

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

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

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

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

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

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

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

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

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

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

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

the web service information is ignored upon deployment. TIBCO Business Studio . content assist and error markers are supported. note the following: • • Send Tasks cannot be deployed. but optionally. 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. you can specify for documentation purposes that a Send or Receive Task send a message or receive a message using a web service. 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. If a Receive Task specifies a web service implementation. The usual text editing assistance such as color syntax highlighting. the following properties are available: Tab General Property Service Type Description By default this is Unspecified. However.Process Developer’s Guide . Send and Receive Tasks When you have selected a Send or Receive Task in the Process Editor.

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

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

). • TIBCO Business Studio .Process Developer’s Guide . allowing you to correct the problem. To correct the problem do one of the following: • Right-click the problem and select Quick Fix (if enabled for the current problem). Right-click the problem and select Go To. This displays the Process in the Process Editor. 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 Validation 87 | Array Fields You can access the elements of an array by specifying the index (for example. MyStringArray[2]. The gives you the option of having TIBCO Business Studio correct the problem for you.

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

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

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

Sign up to vote on this title
UsefulNot useful