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

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

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

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

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

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

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

• “Implementing a Process" refers to taking the Process that the Business Analyst has generated. For example: • An insurance company wants to enable their financial advisors to sell pension plans door-to-door using portable tablets. adding detail to it. The following diagram shows how TIBCO Business Studio is intended to be used: TIBCO Business Studio . The Business Analyst has rationalized both companies’ working procedures and created a process for a standard way of working. and taking it through the packaging and deployment phases. A company has acquired a competitor. refining it.2 | Chapter 1 Getting Started Who Should Use TIBCO Business Studio? Typically a Business Analyst defines a new business procedure and the Corporate Developer must implement it. The Corporate Developer must implement a business process for doing this. The Corporate Developer must implement this across the organization.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). graft steps. and then the Process can be transformed to create a Code Model that can be used with a specific execution engine. The following section describes how the abstract implementation of a Process can be done first. transaction control steps. However.Who Should Use TIBCO Business Studio? 3 | Referring to the previous diagram. using version 2.Process Developer’s Guide . as well as a Platform Specific Model and Code Model. both of which are applied at the programming language level. 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. depending on the destination environment that you select. and dynamic sub-procedure call steps) for which you must perform part of the augmentation and deployment of the Process in TIBCO iProcess Modeler.0 of TIBCO Business Studio there are some constructs (for example. For example: TIBCO Business Studio . delayed release. It consists of a Platform Independent Model. How TIBCO Business Studio Supports MDA Model Driven Architecture (MDA) is typically used to design applications and write specifications.

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

For more information.Process Developer’s Guide . Test and debug the services created in Java using tools external to TIBCO Business Studio. see the TIBCO iProcess Modeler set of guides. for example using the Eclipse IDE. create any custom Java services that are required.Implementation Approach 5 | Service Creation/Testing for Sub-Processes Optionally. undelivered work items. 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. In some organizations. for more information on creating services see the documentation for TIBCO BusinessWorks and TIBCO ActiveMatrix. This guide focusses on the work of the person consuming services. TIBCO Business Studio . test queues. 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. • • Process Testing Ensure that the Process functions as intended including starting cases. 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. and so on. See the TIBCO Business Studio Modeling User’s Guide for more information about generating Process documentation. Package Process for Deployment to User Acceptance Testing/Production by the Operations staff.

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

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

8 | Chapter 1 Getting Started • BusinessWorks live link .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 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. see the TIBCO iProcess BusinessWorks Connector User’s Guide. 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.Process Developer’s Guide . Parameter Mapping • • The web service must have at least one input and output parameter mapping. the iProcess Engine Service Agent must be running and the JMS provider transport information must be configured. 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 appropriate DB2. you can select either Use local WSDL or Use remote WSDL: If you use a local WSDL. Although you do not need to be concerned about which database is used in conjunction with the iProcess Engine. E-mail A Service Task can be configured to send an E-mail message on the General tab of the Properties view for the Service Task as follows: TIBCO Business Studio . When the Process is deployed to the iProcess Engine. Database A Service Task can be configured to perform an action on a database using stored procedure calls. If you use a remote WSDL. Oracle or SQL database calls are made in the iProcess database. the abstract and concrete portion of the WSDL must be present locally.Process Developer’s Guide . Process to Service Binding In the Properties view for a Service Task.BPM/SOA Implementation Overview 9 | Message Exchange Patterns The only supported message exchange pattern is Synchronous Request/Response. and the concrete portion of the WSDL can be obtained dynamically at runtime. the abstract portion of the WSDL must be present locally. the stored procedure writer will need to be familiar with the particular database.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

5. — Files: use this option to browse the file system and attach a file to the email message. TIBCO Business Studio .52 | Chapter 3 Tasks viewing the source of the body text and previewing how it will look to the recipient. 6. Click Attachments to specify a document to be attached to the message: — Field Contents: .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.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.

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

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

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

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

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

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

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

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

Select from the drop-down list the Method that you want to use. Click Select Class. To do this. selecting it populates the Class and Method fields. the character s was entered.Calling Java Code 61 | 2. In the previous example. click Select Factory. For example: TIBCO Business Studio . Select the appropriate class that you want to use. If a factory is available.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. the matching classes are displayed. and all classes starting with s are displayed. If you begin typing. 3.

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. This shows a method that returns a String which is then mapped to the Name Parameter. mapping a String to an Integer).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.Process Developer’s Guide .

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

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

Process Developer’s Guide . TIBCO Business Studio . 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.Deploying a Process 65 | The following diagrams shows the steps for deploying a Process the first time: Once you have deployed a Process.

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

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

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

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

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

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

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

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

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

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

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

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

if a message cannot be sent) • Code: .select either a Parameter or Data Field that represents an error code.Process Developer’s Guide . Files: use this option to browse the file system and attach a file 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 contains the message you want displayed when the email cannot be sent. • 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. E-mail > Error Handling Return Status Fields • TIBCO Business Studio .80 | Chapter 4 Reference Tab E-mail > Attachments Property Field Contents Description Specify a document to be attached to the message: • Field Contents: .use this option to attach the contents of a Parameter or Data Field to the email message. Use this Property to provide for basic error handling (for example. Message: .

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

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

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

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

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

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

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

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

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

Process Developer’s Guide . contacting 5 V validation error correcting 87 W Web Service Definition Language (WSDL) file 45 adding 44 copyingL 45 creating 44 Task 47 Web Services calling 18 T technical support 5 TIBCO Business Studio sample Processes 6 tutorials 18 TIBCO BusinessWorks Web Service 7 X XML Process Definition Language (XPDL) 37 TIBCO Business Studio .90 | Index Q Quick fixes 87 U Unified Modeling Language (UML) 37 Uniform Description. 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. and Integration (UDDI) Registry adding 42 searching 42 User Task 6.

Sign up to vote on this title
UsefulNot useful