TIBCO ActiveMatrix BusinessWorks Migration · TIBCO ActiveMatrix BusinessWorks 6.x architecture is...

TIBCO ActiveMatrix BusinessWorks™ MigrationSoftware Release 6.2.1March 2015

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Enterprise Message Service,TIBCO Business Studio, TIBCO Enterprise Administrator, TIBCO ActiveSpaces, TIBCO Runtime Agent,TIBCO Designer, and Two-Second Advantage are either registered trademarks or trademarks of TIBCOSoftware Inc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform EnterpriseEdition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks ofOracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE 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 ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2001-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

2

TIBCO ActiveMatrix BusinessWorks™ Migration

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

BusinessWorks 5 and BusinessWorks 6 Type Columns Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Standard Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

ActiveMatrix BusinessWorks Core Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Mapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

ActiveMatrix BusinessWorks Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

General Activities Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

General Activities Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

ActiveEnterprise Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Adapter Resources Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

BPEL Extension Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

File Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

FTP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

HTTP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

JAVA Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

JDBC Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

JMS Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Mail Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Parse Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Policy Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Process Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Rendezvous Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

REST and JSON Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

RMI Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Service Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

SOAP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

TCP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Transaction Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

XML Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Migration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Migrating 5.x Projects to 6.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Migrating Projects Using TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Migrating Projects Using Command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Post-Migration Manual Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3


HTTP Persistent Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

HTTP Basic Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

JMS Message Selector Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

JAVA Method Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Mail With Simple Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Custom XPath Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Migration Process Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4


Figures

TIBCO ActiveMatrix BusinessWorks Project Migration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

ActiveMatrix BusinessWorks 5.x Migrated Project - Before and After . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5


TIBCO Documentation and Support Services

All TIBCO documentation is available on the TIBCO Documentation site, which can be found here:

https://docs.tibco.com

Product-Specific Documentation

Documentation for TIBCO products is not bundled with the software. Instead, it is available on theTIBCO Documentation site. To directly access documentation for this product, double-click thefollowing file:

TIBCO_HOME/release_notes/TIB_BW_version_docinfo.html

The following documents for this product can be found on the TIBCO Documentation site:

● Concepts● Installation● Getting Started● Application Development● Administration● Bindings and Palettes Reference● Samples● Error Codes● API Reference● Migration

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support asfollows:

● For an overview of TIBCO Support, and information about getting started with TIBCO Support,visit this site:

http://www.tibco.com/services/support

● If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you canrequest one.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCOmmunity offersforums, blogs, and access to a variety of resources. To register, go to:

https://www.tibcommunity.com

6


https://docs.tibco.com

http://www.tibco.com/services/support

https://support.tibco.com

https://www.tibcommunity.com

Introduction

TIBCO ActiveMatrix BusinessWorks 6.x architecture is designed to have migration path for TIBCOActiveMatrix BusinessWorks 5.x projects with a few exceptions. This document explains how tomigrate from TIBCO ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks 6.x, andlists differences between the two. There are many new features in TIBCO ActiveMatrix BusinessWorks6.x that advance integration, but are not covered in this document.

Migration Queries Resolution

ActiveMatrix BusinessWorks 5.x constructsmigrating to equivalent ActiveMatrixBusinessWorks 6.x constructs

The value Supported is mentioned in the"Migration Support" for this category.

Supported does not mean defect free.

ActiveMatrix BusinessWorks 5.x constructsare not migrating to ActiveMatrixBusinessWorks 6.x because correspondingActiveMatrix BusinessWorks 6.x construct isavailable with corresponding migrationsupport, but contains corner case limitations

The value Supported with Limitations ismentioned in the "Migration Support" for thiscategory.

The corresponding ActiveMatrixBusinessWorks 6.x construct are notavailable, but are under consideration forfuture releases

1. This means feature parity gap for ActiveMatrixBusinessWorks 6.x compared with ActiveMatrixBusinessWorks 5.x

2. The value BW6 Construct Under Considerationis mentioned in the "Migration Support" for thiscategory

The corresponding ActiveMatrixBusinessWorks 6.x construct is available, butActiveMatrix BusinessWorks 5.x toActiveMatrix BusinessWorks 6.x migrationextension is not available and is underconsideration for future releases

1. This means a user can create such constructusing ActiveMatrix BusinessWorks 6.x DesignStudio, but automated migration fromActiveMatrix BusinessWorks 5.x is not yetsupported.

2. After migration, re-factor and re-create theconstruct using ActiveMatrix BusinessWorks 6.xDesign Studio.

3. The value BW6 Migration Not Supported ismentioned in the "Migration Support" for thiscategory.

7


Migration Queries Resolution

Do fundamental design improvements inActiveMatrix BusinessWorks 6.x rendersautomated migration

1. You can achieve better results in ActiveMatrixBusinessWorks 6.x compared to ActiveMatrixBusinessWorks 5.x, but only when the constructis created in ActiveMatrix BusinessWorks 6.xDesign Studio.

2. After migration, re-factor and re-create theconstruct using ActiveMatrix BusinessWorks 6.xDesign Studio.

3. The value Refactor and Recreate is mentioned inthe "Migration Support" for this category.

8


BusinessWorks 5 and BusinessWorks 6 Type ColumnsLegend

The following values are used in the "Type" columns.

Values used in Type columns Description

.<resource extension> The file extension used to describe its type. Forexample, .xml, .xsd, and .wsdl resources.

Adapter Specific Resource Special resources used only for configuration of Adapters.

Shared Configuration Resource configuration that has associated a transport statethat you can lifecycle.

Shared Resource Re-usable configuration that does not have a transport statethat you can lifecycle.

Process Starter Activity1. One of the three activity types supported by ActiveMatrix

BusinessWorks 5.x and ActiveMatrix BusinessWorks 6.x.

2. This type of activity starts a new job from external messagesor internal events.

Regular Activity1. One of the three activity types supported by ActiveMatrix


2. This type of activity processes its input in-memory.

Signal-in Activity1. One of the three activity types supported by ActiveMatrix


2. This type of activity suspends the job and waits for anexternal event. When BusinessWorks runtime receives anexternal event, it correlates the event base on a prescribedkey. The BusinessWorks runtime joins the external event tothe waiting job only when the prescribed key matches.

Built-in1. An intrinsic built-in feature of ActiveMatrix BusinessWorks

process editor.

2. A built-in feature can be from an eclipse or part of theeditor feature (for example, ActiveMatrix BusinessWorks 6Process Design Editor).

Palette1. In ActiveMatrix BusinessWorks 5, a palette is a TIBCO

Designer concept for the grouping of resources or activities.

2. For the purpose of this documentation, a palette is fordescribing a group of activities that are offered as part ofcore ActiveMatrix BusinessWorks.

9


Values used in Type columns Description

Plug-in1. In ActiveMatrix BusinessWorks 5, a BusinessWorks Plug-in

is an add-on extension that contains both design-time andruntime extensions of ActiveMatrix BusinessWorksactivities.

2. In ActiveMatrix BusinessWorks 5, a BusinessWorks Plug-inis offered as an add-on product to ActiveMatrixBusinessWorks.

3. For the purpose of this documentation, a plug-in is fordescribing a ActiveMatrix BusinessWorks add-on product.

Binding1. In ActiveMatrix BusinessWorks 6, binding type is offered as

a first class concept as part of activities.

2. SOAP binding and REST binding are offered as a part ofActiveMatrix BusinessWorks 6 core features.

10


Standard Constructs

The supported standard ActiveMatrix BusinessWorks constructs are listed here.

BW 5.xBW 5.xType BW 6.x

BW 6.xType

MigrationSupport Comments

DTD .dtd XSD .xsd Supported● ActiveMatrix BusinessWorks

6.x currently does notsupport DTD natively.

● ActiveMatrix BusinessWorks6.x Migration tool convertsDTD resource to XSD.

Instance .xml Instance .xml Supported Migrates as is.

Schema .xsd Schema .xsd Supported Migrates as is.

XSLT .xslt XSLT .xslt Supported Migrates as is.

WSDL .wsdl WSDL .wsdl Supported Migrates as is.

11


ActiveMatrix BusinessWorks Core Constructs

The following table displays the supported Core ActiveMatrix BusinessWorks constructs.


BW 6.xType


Design-timeLibrary

ApplicationModule

ApplicationModule

Supported In this version ofActiveMatrixBusinessWorks 6 MigrationFramework, BusinessWorks5 Design-time Libraries aremigrated inline, as part ofregular resources inApplication Module.

If ActiveMatrixBusinessWorks 6 developerwants to reuse the contentsof the DT Library, themigrated resource can bemanually re-factored intoShared Module.

12



BW 6.xType


Start ProcessStarterActivity

ServiceBindingwith WSDLInterface/Operation +Receive

ServiceBinding +ProcessStarterActivity

Supported In ActiveMatrixBusinessWorks 5, Start andEnd activities of the processplay the following roles:

● Describing the input andoutput schema of aprocess whichimplements a singlemethod.

● Starting and ending aprocess flow logically.

An ActiveMatrixBusinessWorks 5 process assuch, has the limitation ofbeing able to implementonly one operation.

In ActiveMatrixBusinessWorks 6, a processis now able to supportimplementation of multipleinterfaces and each interfacecan support multipleoperations. This leads tomore flexibleimplementation of processlogic.

An ActiveMatrixBusinessWorks 5 process ismigrated to anActiveMatrixBusinessWorks 6 processwith a single serviceinterface in one singleoperation.

The Start activity ismigrated as a Receiveactivity where its input andoutput schema is describedin the operation input andoutput, respectively. Anyexceptions thrown inActiveMatrixBusinessWorks 5 processare described as theoperation's faults.

The End activity is migratedas a Reply activity.

13



BW 6.xType


End RegularActivity

ServiceBindingwith WSDLInterface/Operation +Reply

ServiceBinding +RegularActivity

Supported This is same as Startactivity.

GlobalVariable

.substvar ProcessProperty

ModuleProperty

ApplicationProperty

.substvar

SharedResource

Supported Since ActiveMatrixBusinessWorks 6 Runtimenow supports multipleapplications, it isrecommended not to useGlobal Variable to describeapplication configurableproperties.

Instead, there are followingthree levels of properties:

● Process Properties● Module Properties● Application Properties

These three levels ofproperties are hierarchical:Application Properties arein the outer most scope,followed by ModuleProperties, followed byProcess Properties.

You can define and sourcevalue from its parent scope.For example:

1. Process Property valuescan be defined by LiteralValues or source itsvalue from its parentscope Module Property.

2. By the same token,Module Property valuecan be defined by LiteralValues or source fromits parent scopeApplication Property.

14


Groups

BW 5.x BW 5.x Type BW 6.x BW 6.x Type Migration Support

Group Built-In Scope Built-In Supported

Group : If Built-In Group : If Built-In ActiveMatrixBusinessWorks 6construct underconsideration

Group : Iterate Built-In Group : Iterate Built-In Supported

Group : RepeatUntil True

Built-In Group : Repeat Built-In Supported

Group : RepeatOn Error UntilTrue

Built-In Group : RepeatOn Error

Built-In Supported

Group :Transaction

Built-In Group : LocalTransaction

Built-In Supported

Group : CriticalSection

Built-In Group : CriticalSection

Built-In Supported

Group : PickFirst

Built-In Group : PickFirst

Built-In ActiveMatrixBusinessWorks 6construct underconsideration

Group : WhileTrue

Built-In Group : WhileTrue

Built-In Supported

15


Transitions


BW 6.xType


ProcessDefinition

.process Process .bwp Supported ActiveMatrixBusinessWorks5 .process files aremigrated as .bwp files.

Project DesignerProject

ApplicationModule

ApplicationModule

Supported

Transition:

ConditionType :

Success

Built-In Transition :ConditionType :Success

Built-In Supported

Transition:

ConditionType :

Successwithcondition

Built-In Transition :ConditionType :Success withcondition

Built-In Supported

Transition:

ConditionType :

Successwith nomatchingcondition

Built-In Transition :ConditionType :Success withno matchingcondition

Built-In Supported

16



BW 6.xType


Transition:

ConditionType :

Error

Built-In Transition :ConditionType : Error

or

Scope withCatch Block

Built-In SupportedActiveMatrixBusinessWorks 6ConstructUnderConsideration

The following listdescribes in detail whythe migration feature iscategorized as bothSupported andActiveMatrixBusinessWorks 6Construct UnderConsideration.

Supported: ErrorTransition is supportedout of all Regularactivities and Signal-Inactivities except theactivities, that do nothave the Fault tab.

ActiveMatrixBusinessWorks6Construct To BeSupported: ProcessStarter activities, Invokeactivity, and Groupcurrently do not supportError Transition. ErrorTransition for theseconstructs are on theroadmap of futurereleases.

However, a new built-infeature called Scope cannow be configured witha Catch Block to handleactivities that do notsupport ErrorTransition.

What to do aftermigration?

1. For Process Starteractivities, use Catchblock at the processlevel scope to handleerror.

2. For Invoke activity,create a Scopearound the Invokeactivity andconfigure a Catchblock to handle error.

17



BW 6.xType


3. For Group construct,use the Group'sCatch block tohandle error.

18


Mapper


BW 6.xType


XPATH XPATHinDesignerMapper

XPATH XPATH inEclipseMapper

Supported XPATH support inActiveMatrix BusinessWorks5.x is limited to XPATH 1.0.

ActiveMatrix BusinessWorks6.x supports XPATH 2.0. Forexample, all literal valuesused in XPATH 2.0 must havea corresponding constructorfunction around the literalvalue.

XSLT XSLT inDesignerMapper

XSLT XSLT inEclipseMapper

Supported XSLT support in ActiveMatrixBusinessWorks 5.x is limitedto XSLT 1.0.

ActiveMatrix BusinessWorks6.x supports XSLT 2.0.

19


ActiveMatrix BusinessWorks Palettes

General Palette


BW 6.xType


AliasLibrary

SharedConfiguration

ApplicationModulewith JavaNature orEclipseJava Plug-In Project

EclipsePlug-inProject

Supported In ActiveMatrixBusinessWorks 5.x, theAlias Library construct isused for describing orconfiguring the externalJARs used by anActiveMatrixBusinessWorks 5.xapplication Java activities.

The Migration Tool addsthe user JAR files to theActiveMatrixBusinessWorksapplication module.During migration you caninput the JAR files byselecting the Add ExternalJARs check box andconfiguring the file path tothe JARs.

1. Migration frameworkgoes over the aliaslibraries and adds theJARs present at thealias library path to thelib folder. If the JARsare not present,manually select theJARs.

2. For the Append orPrepend path, the JARsneed to be consolidatedand then the top levelfolder should beprovided as the inputto the Migration tool.This brings all the JARsto the lib folder.

20



BW 6.xType


EnterpriseArchiveResource

SharedConfiguration

ActiveMatrixBusinessWorks 6Application


Supported The ActiveMatrixBusinessWorks 5.x projectis migrated as ApplicationModule and a singleActiveMatrixBusinessWorks 6.xApplication project iscreated.

Folder GenericResource

Folder EclipseFolder

Supported

GenericImageResource

GenericResource

GenericResource

Identity SharedConfiguration

Identity SharedConfiguration

Supported

LibraryBuilder

.projlib SharedModule


Supported

Task List .taskList Task List .taskLis

t

BW 6ConstructUnderConsideration

TextDocument

.txt TextDocument

.txt Supported

General Activities Shared Resources

ActiveMatrix BusinessWorks 5.x: General Activities Shared Resources

Type: Palette

ActiveMatrix BusinessWorks 6.x: Shared Resources Wizards

Type: Shared Resources


BW 6.xType


CustomActivity

SharedConfiguration

CustomActivity

SharedConfiguration


21



BW 6.xType


JNDIConfiguration

SharedConfiguration

JNDIConfiguration

SharedConfiguration

Supported

Job SharedVariable

SharedConfiguration

Module :Job SharedVariable

SharedConfiguration

Supported

Lock Object SharedConfiguration

Module :Job SharedVariable

SharedConfiguration

Supported In ActiveMatrixBusinessWorks 5.x, LockObject is used togetherwith Group with CriticalSection. This construct isalso supported for crossengines critical section.

In ActiveMatrixBusinessWorks 6.x, Groupwith Critical Section isconfigured with ModuleShared Variable. InActiveMatrixBusinessWorks 6.x DesignStudio, module sharedvariables are configuredthrough ModuleDescriptors > SharedVariables editor. Thisconstruct is alsosupported for AppSpacewith multiple AppNodesin ActiveMatrixBusinessWorks 6.x, if theAppSpace is configuredwith Engine Group active/active configuration.

Migration Tool migratesthe ActiveMatrixBusinessWorks 5.x LockObject as a ModuleShared Variable andGroup with CriticalSection.

NotifyConfiguration

SharedConfiguration

Process :WSDL/Interface/Operation

SharedConfiguration

Supported See Notify activity fordetails.

22



BW 6.xType


SharedVariable

SharedResource

Module :ModuleSharedVariableType:SharedResource

SharedResource

Yes ActiveMatrixBusinessWorks 5.x sharedvariable with multi-engine option is now aModule Shared Variablewith Persistent option.

General Activities Palette

ActiveMatrix BusinessWorks 5.x: General Activities Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: General Activities Palette

Type: Palette

BW 5.x BW 5.x Type BW 6.x BW 6.x TypeMigrationSupport Comments

Assign RegularActivity

Basic : Assign RegularActivity

Supported

Call Process RegularActivity

Basic : InvokeProcess +ReferenceBinding

RegularActivity +Binding Type

Supported

Catch RegularActivity


Built-in Supported

Checkpoint RegularActivity


Supported

Confirm RegularActivity

Confirm RegularActivity

Supported

EngineCommand

RegularActivity

EngineCommand

RegularActivity


ExternalCommand

RegularActivity

ExternalCommand

RegularActivity

Supported

GenerateError

RegularActivity

Basic : Throw RegularActivity

Supported

23



Get SharedVariable

RegularActivity

Get SharedVariable

RegularActivity

Supported

Inspector RegularActivity

Inspector RegularActivity

Supported

Label DiagramNotation

Note DiagramNotation

Supported

Mapper RegularActivity

Mapper RegularActivity

Supported

24



Notify RegularActivity

InvokeProcess

RegularActivity

ActiveMatrixBusinessWorks 6MigrationNotSupported

In ActiveMatrixBusinessWorks5.x, Notify,ReceiveNotification,and Waitactivities areused for inter-processcommunication.

In ActiveMatrixBusinessWorks6.x, a processnow supportsinterface withmultipleoperations.These operationscan be used forinter-processcommunication.

ActiveMatrixBusinessWorks6.x MigrationTool currentlydoes not migrateNotificationConfigurationshared resource,Notify, ReceiveNotification,and Waitconstructs toActiveMatrixBusinessWorks6.x. Aftermigrating theActiveMatrixBusinessWorks5.x project, youcan manuallyadd operationsto processes thatneed to receivenotification orwait fornotification. TheNotify activity isthen replaced bythe InvokeProcess.

25



When the Notifyor ReceiveNotification andWait activitiesare used formultipleprocesseswaiting toreceivenotification, youcan use a JMStransport withtopic to achievethe samepublish/subscribepattern.

Null RegularActivity

Basic : Empty RegularActivity

Supported

On Error

Type:

ProcessStarterActivity

TBD TBD BW 6ConstructUnderConsideration

On EventTimeout



OnNotificationTimeout



On Shutdown ProcessStarterActivity

ActivatorProcess

Process Supported Process with aspecialActiveMatrixBusinessWorks6.x definedservice thatsupports anoperation foronShutdownfunctionality.This process canbe configuredper application.

26



On Startup ProcessStarterActivity

ActivatorProcess

Process Supported Process with aspecialActiveMatrixBusinessWorks6.x definedservice thatsupports anoperation foronStartup an beconfigured perapplication.

ReceiveNotification


Basic : Receive ProcessStarterActivity

Supported See Notifyactivity fordetails.

Rethrow RegularActivity

Basic :Rethrow

RegularActivity

Supported

Set SharedVariable

RegularActivity

Set SharedVariable

RegularActivity

Supported

Sleep RegularActivity


Supported

Timer RegularActivity

Timer RegularActivity

Supported

Wait Signal-InActivity

Receive ProcessStarter

Supported See Notifyactivity fordetails.

Write To Log RegularActivity

Log RegularActivity

Supported

ActiveEnterprise Palette

ActiveMatrix BusinessWorks 5.x: ActiveEnterprise Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: ActiveEnterprise Plug-in

Type: Plug-in

In ActiveMatrix BusinessWorks, ActiveEnterprise palette is not bundled out-of-the-box. You mustinstall the Adapter Framework Pack as an add-on Plug-in.

27


BW 5.x BW 5.x Type BW 6.x BW 6.x typeMigrationSupport

AdapterRequest-Response Server

Process StarterActivity

Adapter Request-Response Server


Supported

AdapterSubscriber


AdapterSubscriber


Supported

Invoke anAdapter Requestresponse Service

Request/ReplyActivity

Invoke anAdapter Requestresponse Service

Request/ReplyActivity

Supported

Publish toAdapter

Regular Activity Publish toAdapter

Regular Activity Supported

Respond toAdapter Request

Regular Activity Respond toAdapter Request


Send Exceptionto AdapterRequest

Regular Activity Send Exception toAdapter Request


Wait for AdapterMessage

Signal-In Activity Wait for AdapterMessage

Signal-In Activity Supported

Wait for AdapterRequest

Signal-In Activity Wait for AdapterRequest

Signal-In Activity Supported

Adapter Resources Palette

ActiveMatrix BusinessWorks 5.x: Adapter Resources Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: Adapter Resources Plug-in

Type: Plug-in

BW 5.x BW 5.x Type BW 6.x BW 6.x TypeMigrationSupport

GenericAdapterConfiguration

SharedConfiguration

GenericAdapterConfiguration

SharedConfiguration

Supported

MessageFilter

AdapterSpecificResource

Message Filter AdapterSpecificResource

Supported

28



AdapterArchive


AdapterArchive


Supported

Advisory AdapterSpecificResource

Advisory AdapterSpecificResource

Supported

Client AdapterSpecificResource

Client AdapterSpecificResource

Supported

Generic LogSink


Generic LogSink


Supported

GenericTransactionControl Pool


GenericTransactionControl Pool


Supported

GenericSession


GenericSession


Supported

Load URL AdapterSpecificResource

Load URL AdapterSpecificResource

Supported

Log SinkRole


Log Sink Role AdapterSpecificResource

Supported

PublicationService


PublicationService


Supported

Publisher AdapterSpecificResource

Publisher AdapterSpecificResource

Supported

Request-ResponseInvocationService


Request-ResponseInvocationService


Supported

Request-ResponseService


Request-ResponseService


Supported

29



Server AdapterSpecificResource

Server AdapterSpecificResource

Supported

Subscriber AdapterSpecificResource

Subscriber AdapterSpecificResource

Supported

SubscriptionService


SubscriptionService


Supported

Timer AdapterSpecificResource

Timer AdapterSpecificResource

Supported

BPEL Extension Palette


BW 6.xType


OrchestrationProcess

.orchestration

Built-In :Process

.bwp Supported The .orchestrationresource is availablefrom BPEL Palette.

ActiveMatrixBusinessWorksProcess is nativelybased on BPEL.

Assign RegularActivity

Basic: Assign RegularActivity

Supported

Catch RegularActivity


Built-In Supported


GeneralActivities:Checkpoint

RegularActivity

Supported

Exit RegularActivity

Basic: Exit RegularActivity

Supported

Invoke RegularActivity

Basic: Invoke RegularActivity

Supported

30



BW 6.xType


InvokeProcess

RegularActivity

GeneralActivities :InvokeProcess +ReferenceBinding

RegularActivity

Supported

Null RegularActivity

Basic: Empty RegularActivity

Supported

On Alarm ProcessStarterActivity

Built-In:AlarmHandler

Built-In BW6ConstructUnderConsideration

On Event ProcessStarterActivity

Built-In:EventHandler

Built-In Supported

ReceiveStarter


Basic:Receive(CreateInstance =true)

Type:ProcessStarterActivity


Supported

Receive Signal-InActivity

Basic:Receive(CreateInstance =false)

Signal-InActivity

Supported

Reply withFault

RegularActivity

Basic : Replywith Faultconfigured

RegularActivity

Supported

Reply RegularActivity

Basic: Reply RegularActivity

Supported

Rethrow RegularActivity

Basic:Rethrow

RegularActivity

Supported


GeneralActivities:Sleep

RegularActivity

Supported

31



BW 6.xType


Throw RegularActivity

Basic: Throw RegularActivity

Supported

Write To Log RegularActivity

GeneralActivities:Log

RegularActivity

Supported

File Palette

ActiveMatrix BusinessWorks 5.x: File Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: File Palette

Type: Palette


Copy File RegularActivity

Copy File RegularActivity

Supported

Create File RegularActivity

Create File RegularActivity

Supported

File Poller ProcessStarterActivity

File Poller Process StarterActivity

Supported

List Files RegularActivity

List Files RegularActivity

Supported

Read File RegularActivity

Read File RegularActivity

Supported

Remove File RegularActivity

Remove File RegularActivity

Supported

Rename File RegularActivity

Rename File RegularActivity

Supported

Wait for FileChange

Signal-InActivity

Wait for FileChange

Signal-InActivity

Supported

Write File RegularActivity

Write File RegularActivity

Supported

32


FTP Palette

ActiveMatrix BusinessWorks 5.x: FTP

Type: Palette

ActiveMatrix BusinessWorks 6.x: FTP Palette

Type: Palette

BW 5.xBW 5.xType BW 6.x BW 6.x Type


FTPConnection

SharedResource

FTP ConnectionType: SharedResource

SharedResource

Supported

FTP ChangeDefaultDirectory

RegularActivity

FTP ChangeDefaultDirectory

RegularActivity

Supported

FTP DeleteFile

RegularActivity

FTP Delete FileType: RegularActivity

RegularActivity

Supported

FTP Dir RegularActivity

FTP Dir RegularActivity

Supported

FTP GetDefaultDirectory

RegularActivity

FTP Get DefaultDirectory

RegularActivity

Supported

FTP Get RegularActivity

FTP Get RegularActivity

Supported

FTP MakeRemoteDirectory

RegularActivity

FTP MakeRemoteDirectory

RegularActivity

Supported

FTP Put RegularActivity

FTP Put RegularActivity

Supported

FTP Quote RegularActivity

FTP Quote RegularActivity

Supported

FTP RemoveRemoteDirectory

RegularActivity

FTP RemoveRemoteDirectory

RegularActivity

Supported

FTP RenameFile

RegularActivity

FTP RenameFile

RegularActivity

Supported

FTP SysType

RegularActivity

FTP Sys Type RegularActivity

Supported

33


HTTP Palette

ActiveMatrix BusinessWorks 5.x: HTTP

Type: Palette

ActiveMatrix BusinessWorks 6.x: HTTP Palette

Type: Palette

BW 5.xBW 5.xType BW 6.x BW 6.x


HTTPConnection

SharedResource

HTTPConnector

SharedResource

Supported HTTP Connectionshared resource ismigrated toActiveMatrixBusinessWorks 6.x as anHTTP Connectorshared resource. This isfor the HTTP Serviceside.

ActiveMatrixBusinessWorks usesJetty Server and doesnot support Tomcat andHttpComponentimplementation fromActiveMatrixBusinessWorks 5.x.

ProxyConfiguration

SharedResource

ProxyConfiguration

SharedResource

Supported

HTTPReceiver

ProcessStarter

HTTPReceiver

ProcessStarter

Supported

34


BW 5.xBW 5.xType BW 6.x BW 6.x


Send HTTPRequest

RegularActivity

Send HTTPRequest

RegularActivity

Supported ActiveMatrixBusinessWorks 6.x hasalso introduced a newshared resource for thisclient side invoke,HTTP Client sharedresource. You can usethis shared resource toconfigure and tune anumber of optimizationparameters such asMaximum TotalConnection andMaximum TotalConnection Per Host.

This new HTTP Clientshared resource alsoallows the users toconfigure a Thread Poolshared resource ( new inActiveMatrixBusinessWorks 6.x).Using the Thread Poolshared resource you canconfigure MinimumPool Size, MaximumPool Size and a numberof other tuningparameters.

Send HTTPResponse

RegularActivity

Send HTTPResponse

RegularActivity

Supported

Wait ForHTTPRequest

Signal-InActivity

Wait ForHTTPRequest

Signal-InActivity

Supported

JAVA Palette

ActiveMatrix BusinessWorks 5.x: JAVA

Type: Palette

ActiveMatrix BusinessWorks 6.x: JAVA Palette

Type: Palette

If the ActiveMatrix BusinessWorks 5.x project has an activity from the Java palette, the BusinessWorksapplication module gets converted to a Java project. You see additional src and lib folders in theproject. The src folder contains the Java source files. The lib folder contains the Java libraries (JARFiles). The project also gets added with the Java Nature.

35


BW 5.x BW 5.x Type BW 6.x BW 6.xMigrationSupport Comments

JavaCustomFunction

SharedConfiguration

CustomXPATHFunction

SharedConfiguration

Supported

Java GlobalInstance

SharedResource

Java GlobalInstance

SharedResource

Supported

Java Schema SharedConfiguration

XSDSchema

.xsd Supported In ActiveMatrixBusinessWorks 6.xthe Java To XML andXML To Javaactivities do not useJava Schema. Aftermigration thecorrespondingSchema equivalent tothe Java Schema isgenerated andassociated with theactivity.

Java Code RegularActivity

Java Invoke RegularActivity

Supported The source code forthe Java Codeactivity which wasin-lined in theActiveMatrixBusinessWorks 5.xnow gets createdexternally in the srcfolder of theAppModule and thenit is referred by theJava Invoke activitywith MultiOutputcheck box selected.

36


BW 5.x BW 5.x Type BW 6.x BW 6.xMigrationSupport Comments

Java EventSource


JavaProcessStarter


Supported The Source code forJava Event Sourceactivity which wasin-lined in theActiveMatrixBusinessWorks 5.xnow gets createdexternally in the srcfolder of theAppModule and thenJava Process Starteractivity refers to it.

The Java classimplementing theJava Event Sourcenow extendscom.tibco.bw.pale

tte.shared.java.J

avaProcessStarter

class instead ofcom.tibco.plugin.

java.JavaProcessS

tarter.

Java Event Source inActiveMatrixBusinessWorks 5.xreferring to anexternal class needsto change this.

JavaMethod

RegularActivity

Java Invoke RegularActivity

Supported

Java ToXML

RegularActivity

Java ToXML

RegularActivity

Supported

XML ToJava

RegularActivity

XML ToJava

RegularActivity

Supported

JDBC Palette

ActiveMatrix BusinessWorks 5.x: JDBC

Type: Palette

ActiveMatrix BusinessWorks 6.x: JDBC Palette

Type: Palette

37




JDBCConnection

SharedResource

JDBCConnection

SharedResource

Supported

JDBC CallProcedure

RegularActivity

JDBC CallProcedure

RegularActivity

Supported

JDBC GetConnection

RegularActivity

JDBC GetConnection

RegularActivity

BW6ConstructUnderConsideration

JDBC Query RegularActivity

JDBC Query RegularActivity

Supported

JDBC Update RegularActivity

JDBCUpdate

RegularActivity

Supported

SQL Direct RegularActivity

SQL Direct RegularActivity

Supported

JMS Palette

ActiveMatrix BusinessWorks 5.x: JMS Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: JMS Palette

Type: Palette


BW 6.xType


JMSApplicationProperties

SharedConfiguration

XSD Schema .xsd Supported JMS ApplicationProperties is migratedas XML Schema (XSDFile) in ActiveMatrixBusinessWorks 6.x.

JMSConnection

SharedResource

JMSConnection

SharedResource

Supported

Get JMSQueueMessage

RegularActivity

Get JMSQueueMessage

RegularActivity

Supported

JMS QueueReceiver


JMS ReceiveMessage


Supported

38



BW 6.xType


JMS QueueRequester

RegularActivity

JMS RequestReply

RegularActivity

Supported

JMS QueueSender

RegularActivity

JMS SendMessage

RegularActivity

Supported

JMS TopicPublisher

Type:RegularActivity

RegularActivity

JMS SendMessage


RegularActivity

Supported

JMS TopicRequestor


RegularActivity

JMS RequestReply


RegularActivity

Supported

JMS TopicSubscriber


JMS ReceiveMessage


Supported

Reply toJMSMessage


RegularActivity

Reply to JMSMessage


RegularActivity

Supported

Wait forJMS QueueMessage

Signal-InActivity

Wait for JMSMessage

Signal-InActivity

Supported

Wait forJMS TopicMessage

Signal-InActivity

Wait for JMSMessage

Signal-InActivity

Supported

Mail Palette

ActiveMatrix BusinessWorks 5.x: Mail Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: Mail Palette

Type: Palette

39



BW 6.xType


ReceiveMail


Receive Mail ProcessStarterActivity

Supported

Send Mail RegularActivity

Send Mail RegularActivity

Supported ActiveMatrixBusinessWorks 6.xintroduces a new SMTPshared resource.ActiveMatrixBusinessWorks 5.x SendMail activityconfiguration migratesto both Send Mailactivity and SMTPshared resource.

Parse Palette

ActiveMatrix BusinessWorks 5.x: Parse Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: Parse Palette

Type: Palette

BW 5.x BW 5.x Type BW 6.xBW 6.xType


Data Format SharedConfiguration

Data Format SharedConfiguration

Supported

Parse Data RegularActivity

Parse Data RegularActivity

Supported

Render Data RegularActivity

Render Data RegularActivity

Supported

Policy Palette

ActiveMatrix BusinessWorks 5.x: Policy Palette

Type: Palette

40



SecurityPolicyAssociation

SharedConfiguration

SecurityPolicyAssociation

SharedConfiguration


SecurityPolicy

SharedConfiguration

SecurityPolicy

SharedConfiguration

BW ConstructUnderConsideration

Process Palette

ActiveMatrix BusinessWorks 5.x: Process Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: Built-In

Type: Built-In


BW 6.xType


ProcessDefinition

.process Process .bwp Supported

41



BW 6.xType


ProcessArchive

SharedConfiguration

Application Project

.applicat

ion

RefactorandRecreate

In ActiveMatrixBusinessWorks 5.x, ProcessArchive is configured withinthe Enterprise ArchiveResource. This specifies whichprocesses in the ActiveMatrixBusinessWorks 5.x project areto be packaged to form an EARfile for deployment.

In ActiveMatrixBusinessWorks 6.x, theEnterprise Archive Resourceand Process Archiveconfiguration are no longersupported and theirfunctionality are replaced byApplication and ApplicationModule, respectively. Anyproject artifacts that can be re-used by multiple Applicationsand multiple ApplicationModules are to be created inShared Modules.

In the current version ofMigration Tool, anActiveMatrix BusinessWorks5.x project is migrated as anapplication module with acorresponding applicationproject. If the content of theActiveMatrix BusinessWorks5.x project is meant for creatingmultiple applications, then dothe following:

1. Convert the ApplicationModule to Shared Module.

2. Create an ApplicationModule and acorresponding applicationproject.

a. In the ApplicationModule > ModuleDescriptors >Components editor,define the componentto refer to processimplementation in theShared Module.

42



BW 6.xType


b. Repeat 2.a step for eachprocess that is neededto be a part of thisApplication Module.Note: In ActiveMatrixBusinessWorks 6.x, aProcess (such asProcess A) in a SharedModule is not activatedunless a Component isdefined and isconfigured withProcess A .

3. Repeat Step 2 for thenumber of applicationsrequired.

Rendezvous Palette

ActiveMatrix BusinessWorks 5.x: Rendezvous Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: Rendezvous Palette

Type: Palette


RendezvousTransport

SharedResource

RendezvousTransport

SharedResource

Supported

PublishRendezvousMessage

RegularActivity

RendezvousPublisher

RegularActivity

Supported

RendezvousSubscriber


RendezvousSubscriber


Supported

Reply ToRendezvousRequest

RegularActivity

RendezvousReply ToRequest

RegularActivity

Supported

SendRendezvousRequest

RegularActivity

RendezvousRequestReply

RegularActivity

Supported

43



Wait forRendezvousMessage

Signal-InActivity

Wait forRendezvousMessage

Signal-InActivity

Supported

REST and JSON Plug-in

ActiveMatrix BusinessWorks 5.x: REST/JSON Plug-in

Type: Plug-in

ActiveMatrix BusinessWorks 6.x: REST and JSON Palette

Type: Palette

Migration: Supported



Invoke RESTAPI

RegularActivity

Invoke RESTAPI

RegularActivity

Supported

Parse JSON RegularActivity

Parse JSON RegularActivity

Supported

Render JSON RegularActivity

Render JSON RegularActivity

Supported

44




RESTDispatch andReply

RegularActivity

REST ServiceBinding

ServiceBinding

SupportedwithLimitations

ThisActiveMatrixBusinessWorks5 Dispatch andReply RESTactivity ismigrated toREST ServiceBinding ofActiveMatrixBusinessWorks6.

REST Service ofActiveMatrixBusinessWorks6 uses XSD asthe resource forbuilding RESTService. TheXSD must beexternal to theWSDL. That is,direct referenceto inline schemain WSDL is notsupported forREST binding.

If the Dispatchand Replyactivity isconfigured toroute requests toActiveMatrixBusinessWorks5 processes withinline schemafor its input,output andfault, then theActiveMatrixBusinessWorks6 Migration Toolcurrently doesnot externalizethe inlineschema beforeconfiguring theREST binding.You canmanuallyexternalize the

45




inline schemaand re-create theREST binding.

RMI Palette


RMI Lookup RegularActivity

RMI Lookup RegularActivity

BW6 ConstructUnderConsideration

Low PriorityRoadmap Item

RMI Server ProcessStarter

RMI Server ProcessStarter


Low PriorityRoadmap Item

Service Palette

ActiveMatrix BusinessWorks 5.x: Service Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: Built-In

Type: Built-In




ContextResource

.contextRe

source

XSD File .xsd Supported ActiveMatrixBusinessWorks 6uses regular XSDfor definingContext SharedResource, which isequivalent toActiveMatrixBusinessWorks5 .contextResource.

Partner LinkConfiguration

.sharedpar

tner

Process :Reference

Built-In Supported

46




Service .serviceag

ent

Process :Service

Built-In Supported The ServiceResource ismigrated as aprocess withservice and aSOAP servicebinding is addedfor the same. Thebinding is addedunder ModuleDescriptors >Components >Binding.

Get Context RegularActivity

Basic : GetContext

RegularActivity

BW 6Migration NotSupported

InvokePartner

RegularActivity

Basic :InvokeService

RegularActivity

Supported SOAP RequestReply activity ismigrated as aprocess withreference andSOAP referencebinding is addedfor the same. Thebinding is addedunder ModuleDescriptors >Components >Binding.

ReceivePartnerNotification


Basic :Receive


Supported

Set Context RegularActivity

Basic : SetContext

RegularActivity

BW 6Migration NotSupported

47




ContextSupport

SOAPHeaders(Bound ,Unbound,Undescribed)

SOAPAttachments(SwA andMTOM)

SOAPSecurity

Refactor andRecreate

SOAP Palette

ActiveMatrix BusinessWorks 5.x: SOAP Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: Basic Palette + SOAP Binding

Type: Binding



MIME Parser RegularActivity

Parse : MIMEParser

RegularActivity


RetrieveResources

RegularActivity

GenerateWSDLService

RegularActivity +SOAP Binding


The WSDL inBW6 has to begenerated intheBusinessWorks DesignStudio on theComponentBinding.

48



SOAP EventSource


Basic :Receive +SOAP ServiceBinding

Process StarterActivity +SOAP Binding

Supported The SOAPEvent Sourceis migrated asa Process withService and aSOAP ServiceBinding isadded for thesame. TheBinding isadded underModuleDescriptors/Components/Binding.

SOAPRequestReply

RegularActivity

Basic : InvokeService +SOAPReferenceBinding


Supported The SOAPRequest Replyis migrated asa Process withReference anda SOAPReferenceBinding isadded for thesame. TheBinding isadded underModuleDescriptors/Components/Binding.

SOAP SendFault

RegularActivity

Basic : Replywith Fault +SOAPReferenceBinding


Supported

SOAP SendReply

RegularActivity

BasicActivities:Reply + SOAPReferenceBinding


Supported

SOAP SendReply

49



ContextSupport

SOAPHeaders(Bound ,Unbound,Undescribed)

SOAPAttachments(SwA andMTOM)

SOAPSecurity

Refactor andRecreate

TCP Palette

ActiveMatrix BusinessWorks 5.x: TCP Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: TCP Palette

Type: Palette



TCPConnection

SharedResource

TCPConnection

SharedResource

Supported

Read TCPData

RegularActivity

Read TCPData

RegularActivity

Supported

TCP CloseConnection

RegularActivity

TCP CloseConnection

RegularActivity

Supported

TCP OpenConnection

RegularActivity

TCP OpenConnection

RegularActivity

Supported

TCP Receiver ProcessStarterActivity

TCP Receiver ProcessStarterActivity

Supported

Wait for TCPRequest

Signal-InActivity

Wait for TCPRequest

Signal-InActivity

Supported

Write TCPData

RegularActivity

Write TCPData

RegularActivity

Supported

50


Transaction Palette


JTA UserTransactionConfiguration

SharedResource

JTA UserTransactionConfiguration

SharedResource


XATransactionManagerConfiguration

SharedResource

XATransactionManagerConfiguration

SharedResource


TransactionState

RegularActivity

TransactionState

RegularActivity


XML Palette

ActiveMatrix BusinessWorks 5.x: XML Palette

Type: Palette

ActiveMatrix BusinessWorks 6.x: XML Palette

Type: Palette



XSLT File SharedConfiguration

XSLT File SharedConfiguration

Supported

Parse XML RegularActivity

Parse XML RegularActivity

Supported

Render XML RegularActivity

Render XML RegularActivity

Supported

TransformXML

RegularActivity

TransformXML

RegularActivity

Supported

51


Migration Scenario

The migration scenarios show the core construct migration of TIBCO ActiveMatrix BusinessWorks 5.xprojects. After migration, these projects are converted to their equivalent in TIBCO ActiveMatrixBusinessWorks 6.x. The TIBCO ActiveMatrix BusinessWorks 6.x Call Process, Signal-in, Start, and Endactivities are notably different from the activities in TIBCO ActiveMatrix BusinessWorks 5.x.

Call Process Activity Migration

The following table provides information about the Call Process activity migration from ActiveMatrixBusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x.

TIBCO ActiveMatrix BusinessWorks 5.x TIBCO ActiveMatrix BusinessWorks 6.x

Call Process is literal. It calls a process withprocess pipeline data mapped into it andgenerates an output that is in essence theoutput of the called process.

Call Process mechanism is based on the standardInvoke activity. It abstracts out the actual CallProcess configuration to the reference that theInvoke activity is calling.

After Migration: Call Process activity converts to anInvoke activity which calls a reference that holdsthe Call Process activity configuration.

Signal-in Activity Migration

The following table provides information about the Signal-in activity migration from ActiveMatrixBusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x.

52



Signal-In activities join an existing job bycomparing the key generated by mappingprocess pipeline data to the key field of thesignal-in activity. The value is matched withthe value generated for the candidate eventkey field of the signal-in activity by mappingthe signal-in output data.

Conversations, a new mechanism, is introduced tojoin an existing process instance, which is based on acorrelation mechanism. It applies to all the activitiesreceiving a message after the process instance iscreated.

A process instance can initialize a conversationusing an activity by initializing a conversation keywith the values mapped from the process pipelinedata. If the join activity generates a conversation keyvalue by evaluating the expression against themessage data, which matches the value of theinitialized conversation key, a message can join theconversation.

● Input key mapping migrates as ConversationInitiate

● Candidate Event Key migrates as ConversationJoin.

After Migration: Signal-in activity is migrated to anActiveMatrix BusinessWorks 6.x equivalent Signal-in activity with a dummy conversation with Initiateand Join as "true". This mechanism initiates theconversation based on the process data mapped to akey and matches it with a value that is generated bymapping the activity output data.

Start and End Activity Migration

The following table provides information about the Start and End activities migration fromActiveMatrix BusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x.

53



The Start activity is a receiver that starts aprocess on receiving a message that may beempty. The End activity sends a reply.

The Start activity is the first activity in aprocess definition (process starters replacethe Start activity when used in a processdefinition).

The End activity is the last activity in aprocess definition.

The Start activity is changed to a Receive activityand the End activity is changed to Reply activity.

After Migration:

● The Start activity converts to a Receive activity.The input is wrapped inside a WSDL messagethat listens on a generated port type that acts asthe interface for the process.

● The End activity converts to a Reply activity.The output is wrapped inside a WSDL messagethat listens on a generated port type that acts asthe interface for the process.

If the ActiveMatrix BusinessWorks 5.xprocess has an Event Source activityinstead of a Start activity, then the Endactivity gets migrated to an Emptyactivity.

Activator

In TIBCO ActiveMatrix BusinessWorks 6.x, each application module has one Activator process that hastwo service operations, On StartUp and On ShutDown. Any TIBCO Designer process linked with theOn Start and On ShutDown activity in TIBCO ActiveMatrix BusinessWorks 5.x after migration issimultaneously changed to a StartUp Operation activity and On ShutDown Operation activity. Theactivator calls the start() and stop() methods to start or stop the process.

Service and References

Service and References are defined at a process level.

54



SOAP services are used for exchanginginformation in the implementation of webservices relying on XML message format sentover HTTP and JMS.

Includes REST compliant services along with HTTPand JMS, where the purpose of the service is tomanipulate XML representations of web resourcesusing a uniform set of stateless operations. Whenusing a stateless operation, the state is managed bythe job itself instead of by the engine.

Migrating 5.x Projects to 6.x

You can migrate ActiveMatrix BusinessWorks 5.x projects to ActiveMatrix BusinessWorks 6.x using thefollowing options:

● Project > Migrate BW Projects option in TIBCO Business Studio● The command-line option

Migrating Projects Using TIBCO Business StudioTIBCO ActiveMatrix BusinessWorks 6.x provides an easy way to migrate TIBCO ActiveMatrixBusinessWorks 5.x projects by using the Migrate BW Projects menu option in TIBCO Business Studio™.You can also use the Eclipse import mechanism to migrate the projects.

Procedure

1. In TIBCO Business Studio, go to Project > Migrate BW Projects....

2. In the BusinessWorks Migration Tool wizard, specify the relevant information in the following

fields.a) Click Browse in the BusinessWorks 5 Project Folder field and provide the location of the

ActiveMatrix BusinessWorks 5.x project that you want to migrate. The tool scans theActiveMatrix BusinessWorks 5.x projects in the specified folder location and displays the list ofprojects.

b) In the Migrated Project Folder field, click Browse and provide the location where you want tomigrate the project.

55


c) Select the Add External JARs check box if the ActiveMatrix BusinessWorks 5.x project is usingexternal JAR files in context with Java activities.It is recommended you place the external JAR files in a single location. These JAR files can thenbe in-lined in the migrated ActiveMatrix BusinessWorks 6.x project.

d) Click Browse in the Jar Location field and provide the location of the JAR files on disk.

3. In the BusinessWorks 5 Projects area, select the projects you want to migrate, and click Migrate.The migrated projects are visible in the Migration Output area.

4. Click Close after the migration is complete.

You can alternatively migrate the projects using the File > Import menu option. SelectMigrate BW Projects > Next in the Import dialog.

56


Project with Subprocess after Migration

Subprocess in ActiveMatrix BusinessWorks 6.x uses a standardized concept of receiving andreplying messages through a service.

Before Migration

After Migration

The Subprocess moves to a green chevron.

Migrating Projects Using Command lineAnother option for a speedy migration is migrating the projects using the command line.

Usage: bwmigrator [-options] BW5Project...

57


where options include the following:

-projectDir Location where ActiveMatrix BusinessWorks 6.x projects are to be generated.

BW5Project... Location\locations of ActiveMatrix BusinessWorks 5.x projects.

Examples

● bwmigrator -projectDir <BW6_PROJECTS_HOME>\projects <TIBCO_HOME>\5.9\examples

\activities\file\File (Migrates single ActiveMatrix BusinessWorks 5.x project.)


\activities\file\File <TIBCO_HOME>\5.9\examples\activities\ftp\ftp (Migrates File andFTP ActiveMatrix BusinessWorks 5.x projects.)


\activities (Migrates all ActiveMatrix BusinessWorks 5.x projects in activities directory.)


\file <TIBCO_HOME>\5.9\examples\ftp (Migrates all ActiveMatrix BusinessWorks 5.x Projectsin File and FTP directories.)

Procedure

● In the command prompt, type the following command:bwmigrator.exe -projectDir c:/temp <BW 5.x Project Path>

For Java migration type the following command: bwmigrator.exe -projectDir c:/temp -classpath <Jar Location Path> <BW 5.x Project Path>

Post-Migration Manual TasksIf you encounter problem markers that are related to activity input mapping, resolve these constraintsby using the Show Check and Repair and the Fix Type-Casting Errors functions.

Show Check and Repair

Procedure

1. To clear the problem markers in the migrated project, click project.bwp.

2. Click the activity in your project and click the Input tab.

3. Click the Show Check and Repair icon .The Mapper Check and Repair window displays.

58


This option is applicable to the following projects:● JAVA Method Project

● Mail With Simple Attachment

● simple_attachment

4. Perform Check and Repair, click OK and run the project.

Fix Type-Casting Errors

To fix the construct functions errors, click the Fix Type-Casting Errors icon .

If the Project > Clean option does not work to resolve problem markers, close andreopen the project.

HTTP Persistent Connection

This topic describes migrating this project from TIBCO ActiveMatrix BusinessWorks 5.x to TIBCOActiveMatrix BusinessWorks 6.x.

Prerequisites

Migrate the TIBCO ActiveMatrix BusinessWorks 5.x project.

Procedure

1. In the HTTP Client shared resource, Client.ClientProcess-Send-HTTP-Request-HttpClientResource, provide the specified details in the following fields.Field Value

Maximum Total Connections 3

Maximum Total Connections Per Host 2

Connection Timeout (ms) 20000

2. Provide the same HTTP Client shared resource Client.ClientProcess-Send-HTTP-Request-HttpClientResource to the following activities in the process, ClientProcess.bwp.a) Send-HTTP-Request-1b) Send-HTTP-Request-1-1c) Send-HTTP-Request-1-2d) Send-HTTP-Request-1-3

HTTP Basic Sample


Prerequisites


Procedure

1. Click the Incoming-HTTP-request (HTTP Receiver) activity and click the General tab.2. In the Parameter table, change the Parameter Cardinality from Required to Optional.

59


3. Click the Send-Request-to-Wiki-News (Send HTTP Request) activity and specify the followingthree values on Input tab.

Input Type Values

RequestURI "/wiki/Main_Page"

Accept-Encoding "text/*, text/html, text/html;level=1"

Content-Type "text/html;charset=UTF-8"

4. Click the Send-Response-from-Wiki-News (Send HTTP Response) activity and specify the valuefor Content-Type on the Input tab as shown in the following image.

60


JMS Message Selector Project


Prerequisites


Procedure

1. Open QueueMessageSelector.bwp, click on the JMS-Queue-Sender activity and click theAdvanced tab.

2. Click Application Properties Type, open the Select Schema Type Definition wizard and selectJMSApplicationProperties.

3. Delete the Body element from the Input tab in the JMS Queue Sender activity two body elementsare generated after migration.

61


4. Provide a value in the Body element.

5. Do Check and Repair to remove all the problem markers.

6. Run the process.

JAVA Method Project


Prerequisites


Procedure

1. Go to PublishBalance.bwp and perform Check and Repair for the InvalidAcctExp andPublishException activities.

2. In the Mapper Check and Repair wizard, check for jmexample.InvalidAccountException.

3. Run the sample.

62


Mail With Simple Attachment


Prerequisites


Procedure

1. After migrating the project, select the Sender.bwp process, click on Send-Mail activity and doCheck and Repair.

2. Select the Receiver.bwp process and go to Write-binary-attachment-content activity's Input taband do Check and Repair.

Custom XPath MigrationSome manual tasks are needed to be performed after custom XPath migration. These tasks impactDesigntime and Runtime.

Design Time

The migrated custom XPath functions need to be provisioned into TIBCO Business Studio. You can dothis in the following two ways:

Procedure

1. Export the custom XPath function plug-ins into the Host repository. To do this, right-click on theXPath Function Plug-in, and select Plug-in Development/Deployable Plug-ins and fragments.

2. Select Install into .host Repository and, click Finish.You are prompted to restart Business Studio. Restart and refresh your workspace. This results in thevalidation errors related to XPath functions not visible.

63


Run Time

Make sure to include the XPath function plug-ins in your application.

Go to the Includes folder and add the XPath function plug-ins.

64


Migration Process Outline

The migration mechanism takes ActiveMatrix BusinessWorks 5.x projects and converts them to theirequivalent in ActiveMatrix BusinessWorks 6.x.

The process flow in the project is migrated as is for the following:

● The activities and their associated mappings● The transitions and their associated conditions● Groups

TIBCO ActiveMatrix BusinessWorks Project Migration

ActiveMatrix BusinessWorks 5.x Projectin TIBCO Designer

ActiveMatrix BusinessWorks 6.x Project inTIBCO Business Studio

Process ActiveMatrix BusinessWorks 6.x Process

Schema Schema

WSDL WSDL

Shared Resource ActiveMatrix BusinessWorks 6.x Shared Resource

TIBCO ActiveMatrix BusinessWorks Project Migration Diagram

The process flow in the project after the migration is shown in the following image. Activities,transitions, and their associated mappings visible in the ActiveMatrix BusinessWorks 5.x project inTIBCO Designer are displayed in ActiveMatrix BusinessWorks 6.x project in TIBCO Business Studio.

65


ActiveMatrix BusinessWorks 5.x Migrated Project - Before and After

66


Frequently Asked Questions

What to do... Resolution

When migrated process shows mappingerrors? 1. Go to Menu > Project > Clean and click Clean

All Projects.

2. Go to the Activity Input with the Mapping Error.Click Show Check and Repair and fix existingerrors. Click Fix Type Casting Errors.

3. If the error still persists, check the expressionand do the necessary corrections.

When processes have unresolved WSDLreferences? 1. Close and reopen the project.

2. If this does not fix the references, then check theWSDL Interface value on the General tab of theProcess Service.

When Java Invoke activities show InputConfiguration Error after migration? 1. Go to the General tab of the Java Invoke activity

and check whether the Class Name is availablein the workspace. If available, re-select the Javaclass.

2. If the class is not available, check whether theJAR file packaging the Java class is available.Otherwise, copy the JAR file to the "lib" folderand reselect the Java class.

When activities in the Catch block showMapping errors?

The Catch Block activities does not have thevisibility to the output of the activities from themain process.

Re-map the activity input accordingly. This issimilar to the Java try or catch constructs.

When the Iterate Group "Iteration Element"fails to resolve?

When Variable not defined error forIterate Group Index variable is used outsidethe Iterate scope?

1. In ActiveMatrix BusinessWorks 6.x the IterateGroup Index Variable does not have thevisibility outside the Iterate scope.

2. Define a Process Variable of Type integer andmap it to the Iterate Group Index variable. Nowyou can use this variable in the Process scope.

67


What to do... Resolution

When ActiveMatrix BusinessWorks 5.xactivity migrates as Empty or Rescue activityin ActiveMatrix BusinessWorks 6.x?

1. The ActiveMatrix BusinessWorks 5.x activitymigrates as Rescue activity, if the migrationframework fails to migrate.

2. Check the ActiveMatrix BusinessWorks 5.xproject and add the corresponding activity in theActiveMatrix BusinessWorks 6.x project andredo the mappings.

68


Date post:	16-Mar-2020
Category:	Documents
Upload:	others
View:	32 times
Download:	0 times

TIBCO ActiveMatrix BusinessWorks Migration · TIBCO ActiveMatrix BusinessWorks 6.x architecture is...

Documents