migration tibco activematrix businessworks software

TIBCO ActiveMatrix BusinessWorks™

MigrationSoftware Release 6.6.1May 2020

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (ORPROVIDE 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.

ANY SOFTWARE ITEM IDENTIFIED AS THIRD PARTY LIBRARY IS AVAILABLE UNDERSEPARATE SOFTWARE LICENSE TERMS AND IS NOT PART OF A TIBCO PRODUCT. AS SUCH,THESE SOFTWARE ITEMS ARE NOT COVERED BY THE TERMS OF YOUR AGREEMENT WITHTIBCO, INCLUDING ANY TERMS CONCERNING SUPPORT, MAINTENANCE, WARRANTIES,AND INDEMNITIES. DOWNLOAD AND USE OF THESE ITEMS IS SOLELY AT YOUR OWNDISCRETION AND SUBJECT TO THE LICENSE TERMS APPLICABLE TO THEM. BY PROCEEDINGTO DOWNLOAD, INSTALL OR USE ANY OF THESE ITEMS, YOU ACKNOWLEDGE THEFOREGOING DISTINCTIONS BETWEEN THESE ITEMS AND TIBCO PRODUCTS.

This document is subject to U.S. and international copyright laws and treaties. No part of thisdocument may be reproduced in any form without the written authorization of TIBCO Software Inc.

TIBCO, the TIBCO logo, the TIBCO O logo, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous,TIBCO Enterprise Message Service, TIBCO Business Studio for BusinessWorks, TIBCO EnterpriseAdministrator, TIBCO ActiveSpaces, TIBCO Runtime Agent, and TIBCO Designer are either registeredtrademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

Java and all Java based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

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, not all operating systemplatforms for a specific software version are released at the same time. Please see the readme.txt file forthe availability of this software version on a specific operating system platform.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSOR 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.

This and other products of TIBCO Software Inc. may be covered by registered patents. Please refer toTIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.

2

TIBCO ActiveMatrix BusinessWorks™ Migration

https://www.tibco.com/patents

Copyright © 2001-2020. TIBCO Software Inc. All Rights Reserved.

3


Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Type Column Legends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Standard Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

TIBCO ActiveMatrix BusinessWorks™ Core Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

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

Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Mapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

TIBCO ActiveMatrix BusinessWorks™ Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

General Activities Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

General Activities Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

ActiveEnterprise Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Adapter Resources Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

BPEL Extension Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

File Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

FTP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

HTTP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

JAVA Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

JDBC Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

JMS Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Mail Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Parse Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Policy Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Process Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Rendezvous Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

REST and JSON Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

RMI Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Service Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

SOAP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

TCP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Transaction Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

XML Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Migration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Migrating TIBCO ActiveMatrix BusinessWorks™ 5.x Projects to ActiveMatrix BusinessWorks™ 6.x . . . . . . . . . . . . . . . . . . . . . 59

4


Migrating Projects Using TIBCO Business Studio™ for BusinessWorks™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Migrating Projects Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Command line Configuration File Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Post-Migration Manual Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

HTTP Basic Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Custom XPath Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Migrating Design Time Libraries ( DTL) as Shared Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Using the Quick Fix Option to Resolve XSLT out of Sync Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Migration Process Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5


Figures

Project Migration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Migrated Project - Before and After . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

6


TIBCO Documentation and Support Services

How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainlyin HTML and PDF formats.

The TIBCO Product Documentation website is updated frequently and is more current than any otherdocumentation included with the product. To access the latest documentation, visit 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.

Access the following TIBCO ActiveMatrix BusinessWorks™ guides on the TIBCO Documentation site:

● Concepts

● Installation

● Getting Started

● Application Development

● Administration

● Bindings and Palettes Reference

● Samples

● Error Codes

● Migration

● Performance Benchmarking and Tuning

● REST Reference Guide

● Refactoring Best Practices

How to Contact TIBCO Support

You can contact TIBCO Support in the following ways:

● For an overview of TIBCO Support, visit http://www.tibco.com/services/support.

● For accessing the Support Knowledge Base and getting personalized content about products you areinterested in, visit the TIBCO Support portal at https://support.tibco.com.

● For creating a Support case, you must have a valid maintenance or support contract with TIBCO.You also need a user name and password to log in to https://support.tibco.com. If you do not have auser name, you can request one by clicking Register on the website.

How to Join TIBCO Community

TIBCO Community is the official channel for TIBCO customers, partners, and employee subject matterexperts to share and access their collective experience. TIBCO Community offers access to Q&A forums,product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, andtools that extend and enable customers to gain full value from TIBCO products. In addition, users cansubmit and vote on feature requests from within the TIBCO Ideas Portal. For a free registration, go to https://community.tibco.com.

7


https://docs.tibco.com

https://docs.tibco.com

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

https://support.tibco.com

https://support.tibco.com

https://ideas.tibco.com/

https://community.tibco.com

Introduction

TIBCO ActiveMatrix BusinessWorks™ 6.x architecture provides a migration path for ActiveMatrixBusinessWorks™ 5.x projects with a few exceptions. This document explains how to migrate fromActiveMatrix BusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x, and lists differences between thetwo. There are many new features in ActiveMatrix BusinessWorks 6.x that advance integration, but arenot 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, with corner case limitations.

The value Supported with limitations is mentionedin the "Migration Support" for this category.

The corresponding ActiveMatrixBusinessWorks 6.x constructs are notcurrently available.

1. This implies a feature parity gap forActiveMatrix BusinessWorks 6.x compared withActiveMatrix BusinessWorks 5.x.

2. The value Currently not supported is mentionedin the "Migration Support" for this category.

Contact Product Management for detailson features that are currently notsupported.

The corresponding ActiveMatrixBusinessWorks 6.x construct is available, butActiveMatrix BusinessWorks 5.x toActiveMatrix BusinessWorks 6.x migrationextension is currently not available.

1. This means a user can create such a constructusing TIBCO Business Studio™ forBusinessWorks™, but automated migration fromActiveMatrix BusinessWorks 5.x is not yetsupported.

2. After migration, re-factor and re-create theconstruct using TIBCO Business Studio forBusinessWorks.

3. The value BW6 migration not supported ismentioned in the "Migration Support" for thiscategory.

8


Migration Queries Resolution

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 TIBCO Business Studio forBusinessWorks.

2. After migration, re-factor and re-create theconstruct using TIBCO Business Studio forBusinessWorks.

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

9


Type Column Legends

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 with an associated a transport state thatcan be lifecycled.

Shared Resource Re-usable configuration without a transport state that can belifecycled.

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 ActiveMatrix BusinessWorks runtime joins theexternal event to the waiting job only when the prescribedkey 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 BusinessWorks6.x Process Design Editor).

10


Values used in Type columns Description

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

Designer™ concept for the grouping of resources oractivities.

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

Plug-in1. In ActiveMatrix BusinessWorks™ 5.x, a ActiveMatrix

BusinessWorks Plug-in is an add-on extension that containsboth design-time and runtime extensions of ActiveMatrixBusinessWorks activities.

2. In ActiveMatrix BusinessWorks™ 5.x, a ActiveMatrixBusinessWorks Plug-in is offered as an add-on product toActiveMatrix BusinessWorks.

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

Binding1. In ActiveMatrix BusinessWorks 6.x, 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.x core features.

11


Standard Constructs

The following table lists supported standard constructs.

BW 5.xBW 5.xType BW 6.x

BW 6.xType

MigrationSupport Comments

DTD .dtd XSD .xsd Supported● ActiveMatrix

BusinessWorks™ 6.xcurrently does not supportDTD 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.

12


TIBCO ActiveMatrix BusinessWorks™ Core Constructs

The following table displays supported core constructs.


BW 6.xType


Design-timeLibrary

ApplicationModule

ApplicationModule

Supported

Start Start Start Supported Applies to a Sub Process. Ifthe Sub Process refers to aninline schema it isexternalized.

ProcessStarter

ProcessStarterActivity orService

ProcessStarterActivity orService

Supported If the ActiveMatrixBusinessWorks 5.x activityis a SOAP Event Source or aService Binding then theService is created. For allother Process Starters, itcreates the Process Startersonly.

End End End Supported Applies to a Sub Process. Ifthe Sub Process refers to aninline schema it isexternalized.

13



BW 6.xType


GlobalVariable

.substvar ProcessProperty

ModuleProperty

ApplicationProperty

.substvar Supported As ActiveMatrixBusinessWorks 6.x Runtimesupports multipleapplications, it isrecommended that GlobalVariable is not used todescribe applicationconfigurable properties.

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 - - Currently notsupported

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 - - Currently notsupported

Group : WhileTrue

Built-In Group : While Built-In Supported

15


Transitions


BW 6.xType


ProcessDefinition

.process Process .bwp Supported TIBCO ActiveMatrixBusinessWorks™5.x .process filesare migrated as .bwpfiles.

Project DesignerProject

ApplicationModule

ApplicationModule

Supported

Transition :

ConditionType :

Success

Built-In Transition :ConditionType :Success

Built-In Supported

Transition :

ConditionType :

Success withcondition

Built-In Transition :ConditionType :Successwithcondition

Built-In Supported

Transition :

ConditionType :

Success withno matchingcondition

Built-In Transition :ConditionType :Successwith nomatchingcondition

Built-In Supported

Transition :

ConditionType :

Error

Built-In Transition :ConditionType : Error

Built-In Supported

16


Timer

Timer is a process starter activity that starts the process at a specific time. You can also specify theprocesses to be started periodically.

General

The General tab has the following fields.

Field

Literal Value/ModuleProperty/ProcessProperty Description

Name None The name to be displayed as the label for the activity in theprocess.

Start Time Yes The day and time to start the process. To run the processperiodically, the start time indicates the first time to run theprocess.

The local machine’s time zone is used to determine the processstart. If the project is running on machines in different time zones,the time zone of the machine where the project was saved, isused. Use a process property in this field to provide start timesrelative to the time zone where the project is deployed. If youprovide a process property for this field, the format of thespecified time must be: yyyy MMM dd HH:mm:ss z

Run Once None Indicates this process should be run only once on the day andtime indicated by the Start Time field.

If you do not select this check box, the Time Interval and IntervalUnit fields are displayed that you can use to specify the frequencyof the process.

TimeInterval

Yes The integer indicating the number of units specified in theInterval Unit field. For example, if a value of 1 is specified andthe Interval Unit field is specified as Hour, a new process isstarted every hour beginning at the time specified in the StartTime field.

● If a value of 2 is specified and the Interval Unit field isspecified as Month, a process is started every other month,beginning at the time specified in the Start Time field.

● If the value specified is less than one second (1000milliseconds), the timer ignores the specified interval and istriggered once every second.

Using Literal Value, Module Property, and ProcessProperty in this field, specifies the time interval inmilliseconds and the Interval Unit field is notdisplayed.

17


Field

Literal Value/ModuleProperty/ProcessProperty Description

Interval Unit None The unit of time to use with the Time Interval field to determinehow often to start a new process. The units can be: Millisecond,Second, Minute, Hour, Day, Week, Month, and Year.

End After None Specify the number of occurrences or the end time here. Selectfrom the following available options:

● Never: Click the Never radio button if you want tocontinuously execute the process instance. For example, if theTime Interval value specified is 5 and the Interval Unitspecified is Second, the process instance executes every 5seconds.

● Occurrences: Clicking the Occurrences radio button displaysthe Occurrences field. Specify the number of occurrences ofthe process instance execution. This field can be configuredwith Literal Value, Module Property, and Process Property.

● End Time: Clicking the End Time radio button displays theEnd Time field. Specify the end time and date when you wantthe process to end. This field can be configured with LiteralValue, Module Property, and Process Property.

Description

Provide a short description of the activity.

Advanced

The Advanced tab has the following fields.

Field Description

Sequencing Key This field contains an XPath expression that specifies which processes shouldrun in sequence. Process instances with sequencing keys evaluating to the samevalue, are executed sequentially in the sequence the process instance wascreated.

Custom Job Id This field contains an XPath expression that specifies a custom job ID for everyjob in the process instance.

Conversations

You can initiate the conversation here. Click the Add New Conversation button to initiate multipleconversations.For more information about conversations, see the TIBCO ActiveMatrix BusinessWorks™ ApplicationDevelopment guide.

18


Output

The following is the output of the activity.

Output Item Description

TimerOutputSchema The time the process instance started.

The time is represented by several items in the output schema indicating:

● Now

● Hour

● Minute

● Second

● Week

● Month

● Year

● Date

● Time

● DayOfMonth

Each of these items uses the appropriate datatype.

Threading Policy Details

The following are the details about the Timer activity threading policy.

Activity TypeMulti-Threaded?

Default ThreadCount Thread Count Configuration

ProcessStarter No 1 Not applicable.

The Timer process starter does not generatemultiple events concurrently. You cannot alterthe default thread count for this activity.

19


Mapper

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


XPATH XPATH inDesignerMapper

XPATH XPATH inEclipseMapper

Supported XPATH support in TIBCOActiveMatrixBusinessWorks™ 5.x is limitedto XPATH 1.0.

ActiveMatrixBusinessWorks™ 6.x supportsXPATH 1.0. For example, allliteral values used in XPATH1.0 must have acorresponding constructorfunction around the literalvalue.

XSLT XSLT inDesignerMapper

XSLT XSLT inEclipseMapper

Supported XSLT support in TIBCOActiveMatrixBusinessWorks™ 5.x is limitedto XSLT 1.0.

ActiveMatrix BusinessWorks6.x also supports XSLT 1.0.

When a repeating element ismapped to a string using afilter, and the xsl:value-ofinstruction parameter hasno separator attribute, and thevalue of the select expressionis a sequence of more thanone item, then under XSLT 2.0all the items in the outputsequence are space separated,whereas for XSLT 1.0, allitems after the first elementare discarded.

20


TIBCO ActiveMatrix BusinessWorks™ Palettes

General Palette

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

AliasLibrary

SharedConfiguration

ApplicationModule with JavaNature or EclipseJava Plug-InProject

Eclipse Plug-in Project

NotSupported

EnterpriseArchiveResource

SharedConfiguration

ActiveMatrixBusinessWorks™6.x Application

Eclipse Plug-in Project

NotSupported

OnlyActiveMatrixBusinessWorks5.x sourceprojectmigration issupported.

Folder GenericResource

Folder Eclipse Folder Supported

GenericImageResource

GenericResource

GenericResource

Identity SharedConfiguration

Identity SharedConfiguration

Supported

21



LibraryBuilder

.projlib Shared Module Eclipse Plug-in Project

Supported ActiveMatrixBusinessWorks6.x MigrationFramework,ActiveMatrixBusinessWorks5.x Design-timeLibraries aremigrated inline,as part of regularresources inApplicationModule.

If ActiveMatrixBusinessWorks6.x developerwants to reusethe contents ofthe DT Library,the migratedresource can bemanually re-factored intoShared Module.

Task List .taskList Task List .taskList Currentlynotsupported

TextDocument

.txt Text Document .txt Supported

General Activities Shared Resources

TIBCO ActiveMatrix BusinessWorks™ 5.x: General Activities Shared Resources

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: Shared Resources Wizards

Type: Shared Resources


CustomActivity

SharedConfiguration

CustomActivity

SharedConfiguration

Currentlynotsupported

JNDIConfiguration

SharedConfiguration

JNDIConfiguration

SharedConfiguration

Supported

22



Job SharedVariable

SharedConfiguration

Module : JobSharedVariable

SharedConfiguration

Supported

23



Lock Object SharedConfiguration

Module : JobSharedVariable

SharedConfiguration

Supported InActiveMatrixBusinessWorks5.x, LockObject is usedwith theCriticalSection group.This constructis alsosupported forcross enginescritical section.

InActiveMatrixBusinessWorks6.x, the CriticalSection groupis configuredwith ModuleSharedVariable.

In TIBCOBusinessStudio™ forBusinessWorks™ 6.x, modulesharedvariables areconfiguredthroughModuleDescriptors >SharedVariableseditor. Thisconstruct isalso supportedfor AppSpaceswith multipleAppNodes inActiveMatrixBusinessWorks6.x, if theAppSpace isconfiguredwith EngineGroup active/activeconfiguration.

24



Migration Toolmigrates theActiveMatrixBusinessWorks5.x Lock Objectas a ModuleSharedVariable andthe CriticalSection group.

NotifyConfiguration

SharedConfiguration

Process :WSDL/Interface/Operation

SharedConfiguration

Supported

SharedVariable

SharedResource

Module :ModuleSharedVariable Type:SharedResource

SharedResource

Supported ActiveMatrixBusinessWorks5.x sharedvariable withmulti-engineoption is now aModule SharedVariable withPersistentoption.

General Activities Palette

ActiveMatrix BusinessWorks™ 5.x: General Activities Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: General Activities Palette

Type: Palette


Assign RegularActivity

Basic : Assign RegularActivity

Supported

Call Process RegularActivity

Call ProcessActivity

RegularActivity +Binding Type

Supported

Catch RegularActivity

Scope withCatch Block

Built-in Supported

25



Checkpoint RegularActivity


Supported

Confirm RegularActivity

Confirm RegularActivity

Supported

EngineCommand

RegularActivity

EngineCommand

RegularActivity

Supported

ExternalCommand

RegularActivity

ExternalCommand

RegularActivity

Supported

GenerateError

RegularActivity

Basic : Throw RegularActivity

Supported

Get SharedVariable

RegularActivity

Get SharedVariable

RegularActivity

Supported

Inspector RegularActivity

Inspector RegularActivity

Supported

Label DiagramNotation

Note DiagramNotation

Supported

Mapper RegularActivity

Mapper RegularActivity

Supported

26



Notify RegularActivity

Invoke Process RegularActivity

Supported InActiveMatrixBusinessWorks™ 5.x, Notify,and Waitactivities areused for inter-processcommunication.

InActiveMatrixBusinessWorks6.x, a processnow supportsinterface withmultipleoperations.Theseoperations canbe used forinter-processcommunication.

When theNotify andWait activitiesare used formultipleprocesseswaiting toreceivenotification,you can use aJMS transportwith topic toachieve thesame publish/subscribepattern.

Null RegularActivity

Basic : Empty RegularActivity

Supported

On Error

Type:

ProcessStarterActivity

Currently notsupported

On EventTimeout



27



OnNotificationTimeout


Supported

OnShutdown


ActivatorProcess

Process Supported Process with aspecialActiveMatrixBusinessWorks6.x definedservice thatsupports anoperation foronShutdownfunctionality.This processcan beconfigured perapplication.

Close, re-open,and clean themigratedproject toresolveunresolvedschemareferences.

On Startup ProcessStarterActivity

ActivatorProcess

Process Supported Process with aspecialActiveMatrixBusinessWorks6.x definedservice thatsupports anoperation foronStartup anbe configuredperapplication.

Close, re-open,and clean themigratedproject toresolveunresolvedschemareferences.

ReceiveNotification


Basic : Receive ProcessStarterActivity

Supported

28



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

Write To Log RegularActivity

Log RegularActivity

Supported

ActiveEnterprise Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: ActiveEnterprise Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: ActiveEnterprise Plug-in

Type: Plug-in

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

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


29


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

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

TIBCO ActiveMatrix BusinessWorks™ 5.x: Adapter Resources Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: Adapter Resources Plug-in

Type: Plug-in


GenericAdapterConfiguration

SharedConfiguration

GenericAdapterConfiguration

SharedConfiguration

Supported

Message Filter AdapterSpecificResource

MessageFilter

AdapterSpecificResource

Supported

AdapterArchive


AdapterArchive


Supported

Advisory AdapterSpecificResource

Advisory AdapterSpecificResource

Supported

Client AdapterSpecificResource

Client AdapterSpecificResource

Supported

Generic LogSink


Generic LogSink


Supported

GenericTransactionControl Pool


GenericTransactionControl Pool


Supported

30



GenericSession


GenericSession


Supported

Load URL AdapterSpecificResource

Load URL AdapterSpecificResource

Supported

Log Sink Role AdapterSpecificResource

Log Sink Role AdapterSpecificResource

Supported

PublicationService


PublicationService


Supported

Publisher AdapterSpecificResource

Publisher AdapterSpecificResource

Supported

Request-ResponseInvocationService


Request-ResponseInvocationService


Supported

Request-ResponseService


Request-ResponseService


Supported

Server AdapterSpecificResource

Server AdapterSpecificResource

Supported

Subscriber AdapterSpecificResource

Subscriber AdapterSpecificResource

Supported

SubscriptionService


SubscriptionService


Supported

Timer AdapterSpecificResource

Timer AdapterSpecificResource

Supported

31


BPEL Extension Palette

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


OrchestrationProcess

.orchestration Built-In :Process

.bwp Supported The .orchestrationresource is availablein the BPEL Palette.

TIBCO ActiveMatrixBusinessWorks™Process is nativelybased on BPEL.

Assign RegularActivity

Basic:Assign

RegularActivity

Supported

Catch RegularActivity

Scope withCatch Block

Built-In Supported


GeneralActivities:Checkpoint

RegularActivity

Supported

Exit RegularActivity

Basic: Exit RegularActivity

Supported

Invoke RegularActivity

Basic:Invoke

RegularActivity

Supported

InvokeProcess

RegularActivity

GeneralActivities :InvokeProcess +ReferenceBinding

RegularActivity

Supported

Null RegularActivity

Basic:Empty

RegularActivity

Supported

On Alarm ProcessStarterActivity

Built-In:AlarmHandler

Built-In Currentlynotsupported

On Event ProcessStarterActivity

Built-In:EventHandler

Built-In Supported

32




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

Throw RegularActivity

Basic:Throw

RegularActivity

Supported

Write To Log RegularActivity

GeneralActivities:Log

RegularActivity

Supported

File Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: File Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: File Palette

Type: Palette

33



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

FTP Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: FTP

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: FTP Palette

Type: Palette



FTPConnection

SharedResource

FTP ConnectionType: SharedResource

SharedResource

Supported

FTP ChangeDefaultDirectory

RegularActivity

FTP ChangeDefaultDirectory

RegularActivity

Supported

34




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

HTTP Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: HTTP

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: HTTP Palette

Type: Palette

35



BW 6.xType


HTTPConnection

SharedResource

HTTPConnector

SharedResource

Supported HTTP Connectionshared resource ismigrated toActiveMatrixBusinessWorks 6.x asan HTTP Connectorshared resource. Thisis for the HTTPService.

ActiveMatrixBusinessWorks usesJetty Server and doesnot support Tomcatand HttpComponentimplementation fromActiveMatrixBusinessWorks 5.x.

ProxyConfiguration

SharedResource

ProxyConfiguration

SharedResource

Supported

HTTPReceiver

ProcessStarter

HTTPReceiver

ProcessStarter

Supported

36



BW 6.xType


Send HTTPRequest

RegularActivity

Send HTTPRequest

RegularActivity

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

This new HTTP Clientshared resource alsoallows the users toconfigure a ThreadPool shared resource( new in ActiveMatrixBusinessWorks 6.x).Using the Thread Poolshared resource youcan configureMinimum Pool Size,Maximum Pool Sizeand a number of othertuning parameters.

After Axis2upgrade,ApacheCommonsclient library isno longer usedin HTTP. Theprojectsmigrated fromActiveMatrixBusinessWorks5.x shall nowshow ApacheComponentsas the clientlibrary insteadof ApacheCommons.

Send HTTPResponse

RegularActivity

Send HTTPResponse

RegularActivity

Supported

37



BW 6.xType


Wait ForHTTPRequest

Signal-InActivity

Wait ForHTTP Request

Signal-InActivity

Supported

JAVA Palette

TIBCO 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 ActiveMatrixBusinessWorks application module gets converted to a Java project. The additional src and lib foldersare seen in the project. The src folder contains the Java source files. The lib folder contains the Javalibraries (JAR Files). Java Nature is also added to the project.


JavaCustomFunction

SharedConfiguration

CustomXPATHFunction

SharedConfiguration

Supported

Java GlobalInstance

SharedResource

Java GlobalInstance

SharedResource

Supported

JavaSchema

SharedConfiguration

XSDSchema

.xsd Supported In ActiveMatrixBusinessWorks 6.xthe Java To XMLand XML To Javaactivities do not useJava Schema. Aftermigration thecorrespondingSchema equivalentto the Java Schemais generated andassociated with theactivity.

38



Java Code RegularActivity

JavaInvoke

RegularActivity

Supported The source code forthe Java Codeactivity which wasin-lined in theActiveMatrixBusinessWorks 5.xnow gets createdexternally in the srcfolder of theAppModule andthen it is referred bythe Java Invokeactivity withMultiOutput checkbox selected.

Java EventSource


JavaProcessStarter


Supported The Source code forJava Event Sourceactivity which wasin-lined in theActiveMatrixBusinessWorks 5.xnow gets createdexternally in the srcfolder of theAppModule andthen Java ProcessStarter activityrefers 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 Sourcein ActiveMatrixBusinessWorks 5.xreferring to anexternal class needsto change this.

JavaMethod

RegularActivity

JavaInvoke

RegularActivity

Supported

39



Java ToXML

RegularActivity

Java ToXML

RegularActivity

Supported

XML ToJava

RegularActivity

XML ToJava

RegularActivity

Supported

JDBC Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: JDBC

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: JDBC Palette

Type: Palette



JDBCConnection

SharedResource

JDBCConnection

SharedResource

Supported

JDBC CallProcedure

RegularActivity

JDBC CallProcedure

RegularActivity

Supported

JDBC GetConnection

RegularActivity

JDBC GetConnection

RegularActivity

Currentlynotsupported

JDBC Query RegularActivity

JDBC Query RegularActivity

Supported

JDBC Update RegularActivity

JDBCUpdate

RegularActivity

Supported

SQL Direct RegularActivity

SQL Direct RegularActivity

Supported

JMS Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: JMS Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: JMS Palette

Type: Palette

40




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

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 toJMSMessage


RegularActivity

Supported

Wait forJMS QueueMessage

Signal-InActivity

Wait for JMSMessage

Signal-InActivity

Supported

41




Wait forJMS TopicMessage

Signal-InActivity

Wait for JMSMessage

Signal-InActivity

Supported

Mail Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: Mail Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: Mail Palette

Type: Palette


BW 6.xType


ReceiveMail


Receive Mail ProcessStarterActivity

Supported

Send Mail RegularActivity

Send Mail RegularActivity

Supported ActiveMatrixBusinessWorks 6.xintroduces a new SMTPshared resource. TIBCOActiveMatrixBusinessWorks™ 5.xSend Mail activityconfiguration migratesto both Send Mailactivity and SMTPshared resource.

Parse Palette

TIBCO ActiveMatrix BusinessWorks™ TIBCO ActiveMatrix BusinessWorks™ 5.x: Parse Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: Parse Palette

Type: Palette


Data Format SharedConfiguration

Data Format SharedConfiguration

Supported

Parse Data RegularActivity

Parse Data RegularActivity

Supported

42



Render Data RegularActivity

Render Data RegularActivity

Supported

Policy Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: Policy Palette

Type: Palette


SecurityPolicyAssociation

SharedConfiguration

SecurityPolicyAssociation

SharedConfiguration


SecurityPolicy

SharedConfiguration

SecurityPolicy

SharedConfiguration


Process Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: Process Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: Built-In

Type: Built-In


ProcessDefinition

.process Process .bwp Supported

43



ProcessArchive

SharedConfiguration

ApplicationProject

.application Refactorandrecreate

In ActiveMatrixBusinessWorks™ 5.x,Process Archive isconfigured within theEnterprise ArchiveResource. Thisspecifies whichprocesses in theActiveMatrixBusinessWorks™ 5.xproject are packaged toform an EAR file fordeployment.

In ActiveMatrixBusinessWorks 6.x, theEnterprise ArchiveResource and ProcessArchive configurationare no longersupported and theirfunctionality arereplaced byApplication andApplication Module,respectively. Anyproject artifacts thatcan be re-used bymultiple Applicationsand multipleApplication Modulesare created in SharedModules.

In the current versionof Migration Tool, anActiveMatrixBusinessWorks™ 5.xproject is migrated asan application modulewith a correspondingapplication project. Ifthe content of theActiveMatrixBusinessWorks™ 5.xproject is meant forcreating multipleapplications, then dothe following:

1. Convert theApplicationModule to SharedModule.

44



2. Create anApplicationModule and acorrespondingapplication project.

a. In theApplicationModule >ModuleDescriptors >Componentseditor, definethe componentto refer toprocessimplementation in the SharedModule.

b. Repeat 2.a stepfor eachprocess that isrequired to be apart of thisApplicationModule. Note:In ActiveMatrixBusinessWorks6.x, a Process(say, Process A)in a SharedModule is notactivatedunless aComponent isdefined and isconfiguredwith ProcessA .

3. Repeat Step 2 forthe number ofapplicationsrequired.

Rendezvous Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: Rendezvous Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: Rendezvous Palette

45


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

Wait forRendezvousMessage

Signal-InActivity

Wait forRendezvousMessage

Signal-InActivity

Supported

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

Type: Plug-in

ActiveMatrix BusinessWorks™ 6.x: REST and JSON Palette

Type: Palette

Migration: Supported

46




Invoke RESTAPI

RegularActivity

Invoke RESTAPI

RegularActivity

Supportedwithlimitations

ActiveMatrixBusinessWorks6.x does notsupport thefollowing:

● WADLprotocols

● Responsesreturned inbinaryformat

● Rich output

● Authentication OAuth1.0andOAuth2.0

The Circuit Breaker pattern is not supported by the Invoke REST API activity. If you wantto use Circuit Breaker pattern, you need to configure the REST Reference Binding. Formore information, see Using the Wizard to Create a REST Reference in the TIBCOActiveMatrix BusinessWorks™ REST Reference guide.

Parse JSON RegularActivity

Parse JSON RegularActivity


ActiveMatrixBusinessWorks6.x does notsupport theschema typeJava Classes.

47




Render JSON RegularActivity

Render JSON RegularActivity


The RemoveRoot check boxis not supportedin ActiveMatrixBusinessWorks6.x. Rootelements inActiveMatrixBusinessWorks6.x are skippedby default. Youmust modify theinput JSON if itcontains rootelement.

The schematype JavaClasses is notsupported inActiveMatrixBusinessWorks6.x.

48




RESTDispatch andReply

RegularActivity

REST ServiceBinding

ServiceBinding


ThisActiveMatrixBusinessWorks™5.x Dispatchand ReplyREST activity ismigrated toREST ServiceBinding ofActiveMatrixBusinessWorks6.x.

REST Service ofActiveMatrixBusinessWorks6.x 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 toActiveMatrixBusinessWorks™5.x processeswith inlineschema for itsinput, outputand fault, thentheActiveMatrixBusinessWorks6.x MigrationTool currentlydoes notexternalize theinline schemabeforeconfiguring theREST binding.You can

49




manuallyexternalize theinline schemaand re-create theREST binding.

ActiveMatrixBusinessWorks6.x also does notsupport thefollowing:

● EnableWADLReference

● EnableOAuth

● Parameterstyles-Templateand Header

For more information about additional restrictions, see "Restrictions on XML Schema" in TIBCOActiveMatrix BusinessWorks™ Bindings and Palettes Reference.

RMI Palette


RMI Lookup RegularActivity

RMI Lookup RegularActivity


None

RMI Server ProcessStarter

RMI Server ProcessStarter


None

Service Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: Service Palette

Type: Palette

ActiveMatrix BusinessWorks™ 6.x: Built-In

Type: Built-In


50




ContextResource

.contextResour

ce

Built-In Supported Migrated as JobShared Variable

Partner LinkConfiguration

.sharedpartner Process :Reference

Built-In Supported

Service .serviceagent Process :Service

Built-In Supported

Get Context Regular Activity Basic : GetContext

RegularActivity

Supported Post migration,two sets of GetContext and SetContextactivities aredisplayed in aservice process.The sets retrievethe contextinformation andpass theinformation tothesubprocesses,and vice versa.

InvokePartner

Regular Activity Basic :InvokeService

RegularActivity

Supported SOAP RequestReply activity ismigrated as aprocess withreference andSOAP referencebinding isadded for thesame. Thebinding isadded underModuleDescriptors >Components >Binding.

ReceivePartnerNotification


Basic :Receive


Supported

51




Set Context Regular Activity Basic : SetContext

RegularActivity

Supported Post migration,two sets of GetContext and SetContextactivities aredisplayed in aservice process.The sets retrievethe contextinformation andpass theinformation tothesubprocesses,and vice versa.

SOAP Palette

TIBCO 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 inActiveMatrixBusinessWorks 6.x has to begenerated inthe TIBCOBusinessStudio™ forBusinessWorks™ 6.x on theComponentBinding.

52



SOAP EventSource


Basic :Receive +SOAP ServiceBinding

Process StarterActivity +SOAP Binding

Supportedwithlimitations.

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

Currently onlyCopy-Ofbinding issupported forheaders in theBindingsection.Manually,set/map theInput tab ofthe SetContextactivity to usethe SOAPEvent Sourceactivity headermigrationfunctionality.

53



SOAPRequestReply

RegularActivity

Basic : InvokeService +SOAPReferenceBinding


Supportedwithlimitations.

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

Currently onlyCopy-Ofbinding issupported forheaders in theBindingsection.Manually,set/map theInput tab ofthe SetContextactivity to usethe SOAPRequest Replyactivity headermigrationfunctionality.

SOAP SendFault

RegularActivity

Basic : Replywith Fault +SOAPReferenceBinding


Supported

SOAP SendReply

RegularActivity

BasicActivities:Reply + SOAPReferenceBinding


Supported

TCP Palette

TIBCO ActiveMatrix BusinessWorks™ 5.x: TCP Palette

54


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

Transaction Palette


JTA UserTransactionConfiguration

SharedResource

JTA UserTransactionConfiguration

SharedResource


XATransactionManagerConfiguration

SharedResource

XATransactionManagerConfiguration

SharedResource


TransactionState

RegularActivity

TransactionState

RegularActivity


55


XML Palette

TIBCO 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

RenderXML

RegularActivity

Supported

TransformXML

RegularActivity

TransformXML

RegularActivity

Supported

56


Migration Scenario

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

ActiveMatrix BusinessWorks™ 5.x 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 is migrated asa Direct Call Process.

Signal-in Activity Migration

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

ActiveMatrix BusinessWorks 5.x ActiveMatrix BusinessWorks 6.x

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 is introduced to join an existingprocess instance, which is based on a correlationmechanism. It applies to all the activities receiving amessage after the process instance is created.

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.

57


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.


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 and End activity are nowsupported.

Activator

In ActiveMatrix BusinessWorks 6.x, each application module has one Activator process that has twoservice operations, On StartUp and On ShutDown. Any TIBCO Designer process linked with the OnStart and On ShutDown activity in ActiveMatrix BusinessWorks™ 5.x after migration is simultaneouslychanged to a StartUp Operation activity and On ShutDown Operation activity. The activator calls thestart() and stop() methods to start or stop the process.

Service and References

Service and References are defined at a process level.

58



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 TIBCO ActiveMatrix BusinessWorks™ 5.x Projects to ActiveMatrixBusinessWorks™ 6.x

Use the following options to migrate ActiveMatrix BusinessWorksTIBCO ActiveMatrixBusinessWorks™ 5.x projects to ActiveMatrix BusinessWorks 6.x

● Project > Migrate BW Projects option in TIBCO Business Studio™ for BusinessWorks™

● A command-line option

Migrating Projects Using TIBCO Business Studio™ for BusinessWorks™

This section describes how to use the Migrate BW Projects menu option in TIBCO Business Studio forBusinessWorks.

Prerequisites

● Perform validation and ensure that ActiveMatrix BusinessWorks 5.x project does not have errors.

● Optionally, schemas without namespaces should be refactored before migration.

● Remove spaces in the namespace.

● Remove or update any retrieve WSDL processes.

● It is recommended to add missing namespaces for the schemas.

● Ensure that there are no spaces or special characters in folder names.

● Global variables with integer values and a String data type must be updated to data type as Integer.Examples include timeouts, message size, and so on.

● Ensure that no two resources, such as schemas, WSDLs, and DTDs have the same name when theyhave a common hierarchical structure or layout.

Procedure

1. In TIBCO Business Studio for BusinessWorks, choose Project > Migrate BW Projects.

59


60


2. In the Project Migration Wizard dialog box, to migrate a single ActiveMatrix BusinessWorks 5.xproject, click Migrate Single BusinessWorks 5x Project

To migrate multiple projects, click Migrate Multiple BusinessWorks 5.x ProjectsWhen migrating a single ActiveMatrix BusinessWorks 5.x project, you can also migrate selectiveprocesses or subprocesses. Select the Select Processes for Migration check box, and provide therequired information as explained in Step 6, below.

After the required information is provided, the Select Processes button is displayed.

The Select Processes for Migration check box is disabled when you select the MigrateMultiple BusinessWorks 5.x Projects option. Use this check box only to migrate singleprojects.

61


The list of processes in the selected ActiveMatrix BusinessWorks 5.x project are displayed in theProject Migration Wizard dialog box. The processes can be viewed in the Flat Hierarchy or in theTree Hierarchy structures.

3. To select all the subprocesses under the main process, click Select Linked Processes. Clear the checkbox for the process you do not want to migrate.To view the static and dynamic processes that are selected for migration, click Show LinkedProcess Hierarchy.

4. While migrating selective processes, to select or clear the already migrated existing processes, onthe Select Processes page of the Project Migration Wizard dialog box, select the Re-Select Processcheck box.

During the re-migration process, the module properties are not changed.

5. Click Migrate Project.

6. Specify the relevant information in the following fields.a) Click Browse in the Select Project(s) to be migrated field and provide the location of the

ActiveMatrix BusinessWorks 5.x project to migrate.

Select CTRL+ Spacebar to retrieve the history of the last five migrated project paths.

b) The Select Migrated Project Location field displays the location of the current open workspacewhere the project is migrated. To provide a different workspace, click Browse.

c) While migrating any project from version 6.6.1 of TIBCO ActiveMatrix BusinessWorks™onwards, the default XPATH language for transitions is pre-set to XPATH 1.0. Select XPATH 2.0to set the XPATH language for transitions to XPATH 2.0. The transitions are migrated by defaultto XPATH 2.0 for versions prior to 6.6.1 of TIBCO ActiveMatrix BusinessWorks™.

The XPATH language for transition is introduced to get rid of invalid comparison orconversion issues on transitions or groups while migrating TIBCO ActiveMatrixBusinessWorks™ 5.x projects.

d) To browse for third party jars required for your project, click the Select Third Party JAR's folderfield.

e) The Single XPath Function Group Project check box is selected by default, to create all customXPaths as a single plugin project and under a single custom XPath.After migration, the custom XPath function group plugin project is included in the applicationproject. The classes folder is located in the customXPathFunction.jar file, and is no longeravailable in the plug-in project. This jar file is also added to the project class path.

f) In the Select ProjectLibs (DTLs) used by Project field, click Browse to select the project librariesto be used for the project.

g) In the Select Java Libraries used by Project field, click Browse and provide the location of theJAR files on disk if the ActiveMatrix BusinessWorks 5.x project is using external JAR files incontext with Java activities.

TIBCO recommends that you place the external JAR files in a singlelocation.

These JAR files can then be in-lined in the migrated ActiveMatrix BusinessWorks 6.x project.h) To generate the dot (.) properties file which is used for performing command-line migration,

click Export. For more information about the (.) properties file, see Command line ConfigurationFile Template.

i) To browse the (.) properties file which populates the referred 5.x project path for migration, clickImport.


● The process count displayed on the Migrate page of the Project Migration Wizard is inclusive ofmigration service agents.

62


● The tooltip available for the Migration progress bar displays the general information aboutmigration process.

● The Project Migration Wizard dialog box displays the migration status in blue and green colors,where blue and green colors indicate the start and the completion of the migration processrespectively.

● To cancel the migration process anytime, in the Project Migration Wizard, click Cancel.

8. Click Finish after the migration is complete.

63


Project with Subprocess after Migration

Subprocesses in ActiveMatrix BusinessWorks 6.x use a standardized concept of receivingmessages and replying to messages through a service.

Before Migration

After Migration

The Call Process is migrated as a Direct Call Process.

64


Migrating Projects Using the Command LineThis section describes how to migrate the projects using the command line.

Usage: bwmigrator [-options] BW5Project...

where options include the following:

Option Description

-projectDir Location where TIBCO ActiveMatrixBusinessWorks™ 6.x projects are generated.

BW5Project... Location\locations of ActiveMatrixBusinessWorks™ 5.x projects.

-propFile The bw6migration.properties file. The syntax forpassing the bw6migration properties file isbwmigrator.exe [-data <User_Workspace>]

-projectDir <BusinessWorks 6.x Target

directory> <BusinessWorks 5.x Project

location> -propFile

<bw6migration.properties location>.

The template is at, <TIBCO_HOME>\bw\6.x\config

\bw6migration_template.properties.

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

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

Path>

2. For non-Java migration enter the following command:bwmigrator.exe -projectDir c:/temp <BW 5.x Project Path>

3. For the Eclipse environment, run the bwmigrator tool as described in step 2, but use a temporarydirectory (not the Eclipse workspace directory) as a target.In addition, to make the project visible in the current workspace, open the Eclipse UI, select File >Import Existing Studio Project into Workspace, and specify the temporary directory as the source.

65


Command line Configuration File Template

The TIBCO ActiveMatrix BusinessWorks™ 6.x migration configuration file, .properties file is atemplate file that contains configurable properties to migrate design time libraries, custom XPathfunctions, selected processes and projects using the command line.

To migrate projects using the command line migration option, open the .properties file and paste thecommand from the .properties file into the command prompt, and execute the command using thefollowing format:

bwmigrator.exe [-data <User_Workspace>] -projectDir <BusinessWorks 6.x Target

directory> <BusinessWorks 5.x Project location> -propFile <.properties location>

Optionally, you can also modify the User_Workspace path. If the User_Workspace path has been modified,make sure that the same path is provided for the BW6 Target directory.

The properties to be configured to migrate design time libraries, custom XPath functions, and selectedprocesses are explained in the tables below.

Selective Migration

Property Description

selectProcess The default value false will migrate all theprocesses.Set the property to true to migrate only thespecified processes.

selectLinkedProcess The default value false will migrate the specifiedmain process.

Forexample, .process=<process1>,<process2>...Set the property to true to migrate all thedependent processes, of the specified mainprocess.

For example,.process=<folder1/process1>,</process2>,.

Specifying the main process path will migrate allthe processes that are dependent on the mainprocess.

.process Provide comma separated processes with relativeprocess paths with respect to the ActiveMatrixBusinessWorks 5.x project root folder as explainedin the following example.

.process=Service/ZipInfo-

service1.serviceagent,TestService/

getCityInfoTest.process,Service/

getCityInfoService.process,TestService/

getCityDistanceTestJMS.process,Service/

getCityDistanceService.process,TestServic

e/getCityInfoTestJMS.process,TestService/

getCityDistanceTest.process,

66


Design Time Library Migration (DTL)


sharedModule The default value of this property is false, andwill migrate the DTL as an application module.Set the property to true to create anActiveMatrix BusinessWorks 6.x shared module.

Mapping DTLs to Shared Modules


dtlDir Provide the project lib folder location here.

For example:

C:/Users/workspace1/folder/

BW5DTLLib.projlib.

sharedModuleDirs Provide multiple directory locations usingcomma separated values.

For example:

C:/CLIWorkspace,C:/CLIWorkspace/

SharedModuleProject1,....

Custom XPath Migration


singleCXFGroupProject By default, the property is set to true, to migrateall the custom XPath functions under a singlecustom XPath function group.Set the property to false to migrate eachcustom XPath function and create custom XPathfunction groups for each individual XPathfunction.

thirdPartyCXFJarDir Provide the location of the third party JAR filesthat are referred by the custom XPath function.

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

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, then click the Input tab.

67


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

4. 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 Basic Sample

This section describes how to migrate an HTTP Basic sample.

Prerequisites

Migrate the TIBCO ActiveMatrix BusinessWorks™ 5.x project.

Procedure

1. Click the Incoming-HTTP-request (HTTP Receiver) activity.

2. Click the General tab.

3. In the Parameter table, change the Parameter Cardinality from Required to Optional.

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

68


Input Type Values

RequestURI "/wiki/Main_Page"

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

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

5. Click the Send-Response-from-Wiki-News (Send HTTP Response) activity and specify the valuefor Content-Type on the Input tab.

Custom XPath MigrationSome manual tasks need to be performed after custom XPath migration. These tasks impact Design-time.

Design Time

This section describes how to provision migrated custom XPath functions into TIBCO ActiveMatrixBusinessWorks™ 6.x.

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.

3. Restart and refresh your workspace.This results in the validation errors related to XPath functions not visible.

69


Custom XPath Migration Using the Command Line

Set the following properties to migrate custom XPath functions using thebw6migration.properties file.


singleCXFGroupProject By default, the property is set to true, andmigrates all the custom XPath functions under asingle custom XPath function group.Set the property to false to migrate eachcustom XPath function and create custom XPathfunction groups for each individual XPathfunction.

thirdPartyCXFJarDir Provide the location of the third party JAR filesthat are referred by the custom XPath function.

Migrating Design Time Libraries ( DTL) as Shared ModulesTIBCO ActiveMatrix BusinessWorks™ 5.x design time library source projects are migrated asActiveMatrix BusinessWorks™ 6.x shared modules.

Migrating Design Time Libraries Using TIBCO Business Studio™ for BusinessWorks™

Use the ActiveMatrix BusinessWorks 6.x framework to migrate TIBCO ActiveMatrix BusinessWorks™5.x projects where the business process uses design time libraries to define processes, resources, andsubprocesses.

You can migrate the design time libraries using the following options:

● Project > Migrate BW Projects option in ActiveMatrix BusinessWorks

● The command-line option

Procedure

1. In the Project Migration Wizard dialog box, click Migrate Single BusinessWorks 5.x Project andselect the Migrate as Shared Module check box.

2. Provide the Project Location details and the XPATH Function Group Configuration details if acustom XPath is used in the project.

3. To browse for third party jars only if your project contains a custom XPath, click the Select ThirdParty JARs folder field .


Result

After migration, view the folder structure of the resources, including the resource, schema, wsdl, and soon that are available in the shared module under the Module Descriptors > Provides tab.

70


After migration, do not perform refactoring operations on any of the resources, such as theschema, ActiveMatrix BusinessWorks 6.x shared resources, and service definitions. Theresource properties, and naming conventions must be retained as they are. Mapping issues, ifany, can be corrected, and resource specific properties of the shared resources can be changed.Limitations

● Shared module migration does not support TIBCO ActiveMatrix BusinessWorks™ 5.x AEschemas. AE Schemas are migrated as part of the application module.

● Custom XPath function project duplication should be managed manually by deleting theduplicate source projects.

● DTL migration does not support the Process Name Dynamic Override feature of the CallProcess activity. Instead, add the process name manually.

71


Migrating Application Modules

TIBCO ActiveMatrix BusinessWorks™ 5.x projects using design time libraries can be migratedas application modules by linking the corresponding shared modules to the DTL libraries.

Select the Link DTL to Shared Module check box.

Select the required DTL project, and click OK.

Mapping the DTL to the <Do Not Migrate> option does not link the DTL to the shared module.

72


Multiple DTL libraries can be linked to one shared module. After migration all the DTLlibraries refer to the same shared module to resolve resource references.

Migrating Design Time Libraries Using Command line

Design time library source projects can be migrated as shared modules using the commandline.

Set the following properties to migrate DTL projects as a shared module using thebw6migration.properties file.


sharedModule Set the property to true to create anActiveMatrix BusinessWorks 6.x shared module.

Set the property to false to migrate the DTL asan application module.

The shared module and the application module must be maintained in the sameworkspace while performing migration using the command line.

Mapping a Design Time Library to a Shared Module

Set the following properties to link a DTL library to the shared module.


dtlDir Provide the project lib folder location. Forexample, C:/Users/workspace1/folder/BW5DTLLib.projlib.

sharedModuleDirs Provide the shared module location. You canprovide multiple directory locations usingcomma separated values. For example, C:/CLIWorkspace,C:/CLIWorkspace/

SharedModuleProject1,....

Using the Quick Fix Option to Resolve XSLT out of Sync ErrorsAfter migrating a project, use the Quick Fix option to resolve XSLT out of Sync errors in the project.

Prerequisites

Set the minimum JVM heap size to either 4GB, 6GB or 8GB, keeping in mind the size of the project. Foradditional instructions, see Specifying JVM Heap Size in the TIBCO ActiveMatrix BusinessWorks™Performance Benchmarking and Tuning guide .

After migrating a project, follow these steps:

Procedure

1. Turn off the Auto Build, which is enabled by default, by selecting Project > Build Automatically.

2. From the Problems tab, click the downward arrow icon, and select Configure Contents.The Configure Contents window is displayed.

73


3. Clear the Use item limits check box and select OK.This causes all of the errors in the project to display.

4. From the Problems tab, right-click on an XSLT out of Sync error, and select Quick Fix.

5. Click Select All.

6. Click Finish.

7. Clean the project to fix broken mappings that might have occurred.

8. To fix broken mappings, select Project > Clean.

Result

The number of XSLT out of Sync errors in the migrated project are either reduced or fully resolved. Ifthere are a few XSLT out of Sync errors still lingering, use the Quick Fix option to resolve theseproblems. Make sure the Auto Build is turned off during this process.

74


Migration Process Outline

The migration mechanism takes TIBCO ActiveMatrix BusinessWorks™ 5.x projects and converts themto their equivalent 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

ActiveMatrix BusinessWorks Project Migration

5.x Project in TIBCO Designer6.x Project in TIBCO Business Studio™ forBusinessWorks™

Process ActiveMatrix BusinessWorks 6.x Process

Schema Schema

WSDL WSDL

Shared Resource ActiveMatrix BusinessWorks 6.x Shared Resource

While migrating projects, if a project rests in a multiple folder hierarchy structure and contains WSDLs,or schemas, or both, the folder names must be unique. If the folder names are not unique the projectcan run into design time issues due to incorrect namespaces and imports.

For ActiveMatrix BusinessWorks 6.x, spaces are not allowed in the namespace.

Project Migration Diagram

75


The following image shows the project process flow after the migration. Activities, transitions, and theirassociated mappings visible in the ActiveMatrix BusinessWorks 5.x project in TIBCO Designer aredisplayed in ActiveMatrix BusinessWorks 6.x project in TIBCO Business Studio for BusinessWorks.

Migrated Project - Before and After

76


Frequently Asked Questions

What do I do... Answer

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.

3. Click Fix Type Casting Errors.

4. 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, heck the WSDLInterface value on the General tab of the ProcessService.

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 Variable not defined error forIterate Group Index variable is used outsidethe Iterate scope?

1. In TIBCO ActiveMatrix BusinessWorks™ 6.x theIterate Group Index Variable does not havevisibility outside the Iterate scope.

2. Define a process variable of type integer, map itto the Iterate Group Index variable, and use thevariable in the process scope.

77



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

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

1. Check the ActiveMatrix BusinessWorks 5.xproject

2. Add the corresponding activity in theActiveMatrix BusinessWorks 6.x project

3. Redo the mappings.

After migrating a project using thetib:concat-sequence-format(), theoutput returns errors.

The function tib:concat-sequence-format()does not accept a string as its return value for nodeset.

After migration, replace the tib:concat-sequence-format() with the string-join()function.

When a group is around the activities andthe XPath condition over the group is notsatisfied after migration, the Expected NonRepeating got repeating error isdisplayed.

1. Verify the XPath condition and resolve the groupissues (for example, iterator, for-each...)

2. Re-map the same from the group.

When the Variable not defined error isdisplayed post migration for multiplevariables created in the input of any activityand each variable is created with thecondition on another variable.

1. Remove all the variables

2. Recreate the variables

3. Add the mappings again. In this case the back-end references are also removed.

4. Delete the XPath on the variables one by one andre-correct them. This also resolves the issuesometimes.

When the Unresolved reference schemaerror is displayed.

Reconfigure the broken module variables. Redo allthe mappings as they break due to reconfiguration.

When the Catch-All End error is notconfigured.

When a Catch All fault handler is used in aActiveMatrix BusinessWorks 5.x project, onmigration the fault handler is converted as expectedbut an End activity is created in place of a Catch Allactivity. An End activity without any input iscreated. Delete the end activity and to resolve theissue.

Schema references issues post migration References of schemas that are imported in anotherschema are not found. Delete the import and add itagain. The references are updated with the correctnamespace and the namespace issues are resolved.

78



When you map an integer value, for example1, to a decimal field, expecting the output inthe decimal field to be 1, but, instead, thedecimal field result is 1.0.

Create a new Mapper activity using the samenaming and mappings from the existing mapperactivity.

Once all the inwards and outwards mappings aredone, delete the old Mapper activity, which isalready migrated, and point the transitions to thenewly created mapper activity.

There is no tokenize-allow-empty()function in ActiveMatrix BusinessWorks 6.x.

After migration to ActiveMatrix BusinessWorks 6.x,the tokenize() function can yield the same resultsas the tib:tokenize-allow-empty() andtib:tokenize() functions of ActiveMatrixBusinessWorks 5.x.

When a mapper activity that has a tokenizefunction inside a for-each expression,throws a Null Input at runtime?

Post migration, convert the XSLT version in theactivity from 1.0 to 2.0, since in version 1.0 the for-each expression requires things to be evaluated to anode-set.

The Tokenize function creates a sequence of stringatoms, which is not node-set.

In 2.0, the for-each expression must be evaluatedto sequence, which covers the sequence of atomsand node scenario.

After migration, when a boolean alwaysevaluates to false with XSLT 1.0 andvalidation off.

1. Navigate to Windows > Preferences > Mapper.

2. Select the Assume all inputs untyped check box.

3. Click Apply, and then OK.

4. Clean the project. After the errors related tountyped input are displayed, use the Quick Fixoption to resolve them.

5. Execute the project.

After migration, when there is a invalidcomparison, or conversion error in atransition or a group.

1. Navigate to Windows > Preferences > Mapper.

2. Select the Enable Quick fix to change Xpathversion from 2.0 to 1.0 check box.

3. Click Apply, and then OK.

4. Clean the project.

5. On the Problems tab, right-click and select theQuick Fix option for the XPath Version 2.0.

79


migration tibco activematrix businessworks software

Documents