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

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

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

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

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

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

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

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

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

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

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

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

For example.6 | Chapter 1 Getting Started BPM/SOA Implementation Overview This section provides an overview of how to augment the Process with execution details. the step is created with a standard iProcess Form. Service Tasks Service Tasks can be implemented in the following ways: • Web Service . a User Task with a Form URL specified becomes a step with a Form type of Formflow Form. User Tasks You can specify the input and output Parameters of a User Task on the Implementation tab of the Properties view for the User Task: You can also specify either a relative or absolute URL for any form pages that you want displayed when the Task is executed (see Elaborating a User Task on page 40): Upon import to iProcess Modeler. you may want to call a web service from a Service Task. TIBCO Business Studio . If no URL is specified. For more information.Calls to a web service can be implemented as well as the mapping of input/output parameters. see TIBCO iProcess Client (Browser) Configuration and Customization.Process Developer’s Guide . see Tasks on page 39. This section provides an overview of elaborating a Process. For more information about specific tasks.

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

however you cannot specify more than one output parameter mapping. For more information. Parameter Mapping • • The web service must have at least one input and output parameter mapping. Except for a WSDL obtained from a TIBCO BusinessWorks live link. the WSDL file that you use must conform to the following requirements for deployment to the iProcess Engine: Data Transport/Call Style • • The web service must use the SOAP over HTTP data transport mechanism. The web service call style must be either Document Literal or Remote Procedure Call (RPC) Encoded.Process Developer’s Guide . 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 .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. see the TIBCO iProcess BusinessWorks Connector User’s Guide. the iProcess Engine Service Agent must be running and the JMS provider transport information must be configured.

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

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. For more information. the previous dialog shows %Manager% rather than an explicit email address. 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 .Process Developer’s Guide . This means that a String property 'name' must have an accessor named getName():String and a mutator named setName(:String). Specifically they must have a default constructor (one without parameters) and the properties need to have standard get and set operations. see Sending an Email on page 50. Note that instead of explicitly entering email addresses. Script Tasks You can enter scripts in Script Tasks. Alternatively you can specify a Factory to be used for the creation of the class. and so on) must adhere to JavaBeans semantics. you can define Data Fields or Parameters for this purpose. on Conditional Sequence Flows. float. You can browse to select the Java class and select a Method from the drop-down list. Java A Service Task can be configured to call a Java code on the General tab of the Properties view for the Service Task as follows: The Java service class and any parameters that are not primitives (for example. For example. subject lines and so on. int. and to Timer Start or Intermediate Events.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Process Developer’s Guide . Create the Parameters or Data Fields as described in the TIBCO Business Studio Modeling User’s Guide. Click OK when you have finished selecting Parameters and Data Fields.40 | Chapter 3 Tasks Elaborating a User Task You can add Parameters or Data Fields to user tasks as follows: 1. 3. press the Ctrl key and click the desired Data Field or Parameter. 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. In the Properties view. TIBCO Business Studio .

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

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

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

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

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

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

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

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

Web service operations that return more than one Parameter are not supported in the iProcess Engine/iProcess Modeler Destination Environments. if you want to append a string to a Parameter.Adding a Service Call 49 | 3. you can do so as follows: When executed in the runtime environment. 4. This displays the following window. in which you can enter a limited amount of JavaScript: This is currently limited to concatenation of two fields on the left into a single on the right or splitting (substring) data from one left field to two on the right. TIBCO Business Studio . Complete the output mapping in a similar fashion using the Mapping Out tab. the string "SEBRANCH" is appended to the input Parameter Reference. Note that you can enter JavaScript that is applied to a mapping by clicking . Save the Package that contains the Process. For example. 5.Process Developer’s Guide .

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

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

Click SMTP Configuration to specify Simple Mail Transfer Protocol (SMTP) settings other than the default: — Select User Server SMTP Configuration to use the settings of the server where the Process will run.Process Developer’s Guide . — Select Use Custom SMTP Configuration settings to specify a different Host and Port.52 | Chapter 3 Tasks viewing the source of the body text and previewing how it will look to the recipient. TIBCO Business Studio . — Files: use this option to browse the file system and attach a file to the email message. 6. 5.use this option to attach the contents of a Parameter or Data Field to the email message. Click Attachments to specify a document to be attached to the message: — Field Contents: .

Click Error Handling to provide for basic error handling (for example. — Message: . if a message cannot be sent): — Code: .Process Developer’s Guide .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 .select either a Parameter or Data Field that represents an error code.

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

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

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

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

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

If you specify only one statement. it must evaluate to either a Date or a Time. For example: In this case. the event would fire at the specified time on the current date. 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. The script area cannot be empty if you want to export or deploy to the iProcess Engine. The script that you specify is limited to two statements. the event would fire at 00:00 on the Date specified. If you specify two statements. If only the Date were present. TIBCO Business Studio . the event will be fired at the Date and Time specified.Process Developer’s Guide . one must evaluate to a Date and the other to a Time.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Date="09/05/2007".86 | Chapter 4 Reference Unsupported Constructs/Operators The following JavaScript constructs and operators are not supported in the TIBCO iProcess Engine. You can however use the Date or Time properties of process data in expressions (for example. TIBCO Business Studio .). MyDateTime. and are therefore not allowed in Processes with the TIBCO iProcess Engine destination environment selected: • • • • • • • • • • • • • • • • • • • • • • • Local method definition Try Catch Finally Blocks Switch Case statement Throw statement New Expressions Continue statement Break statement Local variable definition Labelled statement Multi-dimensional arrays ! (NOT) ~ >> (Right shift operator) >>= (Right shift assign operator) >>> << (Left shift operator) <<= (Left shift assign operator) condition?option1:option2 % (Mod operator) %= (Mod assign operator) |= &= instanceof operator Datetime Process Data You cannot perform operations on Datetime process data.Process Developer’s Guide .

• TIBCO Business Studio . Note that there is no support for a length attribute to determine the number of items in an array.). allowing you to correct the problem.Process Developer’s Guide . The gives you the option of having TIBCO Business Studio correct the problem for you. Correcting Validation Errors Any problems that result from validation are shown in the Problems view. Right-click the problem and select Go To. MyStringArray[2]. This displays the Process in the Process Editor. 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.

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

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

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

Sign up to vote on this title
UsefulNot useful