TIBCO BusinessWorks™

Container Edition
Migration
Version 2.6.2
May 2021

Copyright © 2015-2021. TIBCO Software Inc. All Rights Reserved.

2 | Contents

Contents
Contents 2

Introduction 5

Migrating TIBCO ActiveMatrix BusinessWorks Projects to TIBCO

BusinessWorks Container Edition 7

Type Column Legends 8

Standard Constructs 10

TIBCO ActiveMatrix BusinessWorks™ Core Constructs 11

Groups 14

Transitions 15

Timer 17

Mapper 21

BusinessWorks Palettes 23
General Activities Shared Resources 25
General Activities Palette 28
ActiveEnterprise Palette 32
Adapter Resources Palette 34
BPEL Extension Palette 36
File Palette 39
FTP Palette 40
HTTP Palette 42
JAVA Palette 45
JDBC Palette 47

TIBCO BusinessWorks™ Container Edition Migration

3 | Contents

JMS Palette 48
Mail Palette 50
Parse Palette 51
Policy Palette 52
Process Palette 52
REST and JSON Plug-in 56
RMI Palette 59
Service Palette 59
SOAP Palette 61
TCP Palette 63
Transaction Palette 64
XML Palette 65

Migration Scenario 67
Migrating ActiveMatrix BusinessWorks 5.x Projects to TIBCO BusinessWorks
Container Edition 69
Migrating Projects Using TIBCO Business Studio for BusinessWorks 69
Migrating Project Using Command line 75
Post-Migration Manual Tasks 78
Fix Type-Casting Errors 79
HTTP Basic Sample 79
Custom XPath Migration 81
Migrating Design Time Libraries ( DTL) as Shared Modules 81
Limitations 82
Migrating Application Modules 83
Using the Quick Fix Option to Resolve XSLT out of Sync Errors 84

Migration Process Outline 86

Frequently Asked Questions 89

TIBCO Documentation and Support Services 93

TIBCO BusinessWorks™ Container Edition Migration

4 | Contents

Legal and Third-Party Notices 95

TIBCO BusinessWorks™ Container Edition Migration

5 | Introduction

Introduction
TIBCO BusinessWorks™ Container Edition architecture provides a migration path for
ActiveMatrix BusinessWork™ 5.x projects with a few exceptions. This document explains
how to migrate from ActiveMatrix BusinessWorks 5.x to TIBCO BusinessWorks
Container Edition , and lists differences between the two. There are many new features
in TIBCO BusinessWorks Container Edition that advance integration, but are not
covered in this document.

Migration Queries Resolution

ActiveMatrix BusinessWorks 5.x constructs The value Supported is mentioned in

migrating to equivalent TIBCO BusinessWorks the "Migration Support" for this
Container Edition constructs. category.

Note: Supported does not mean

defect free.

ActiveMatrix BusinessWorks 5.x constructs are The value Supported with limitations
not migrating to TIBCO BusinessWorks Container is mentioned in the "Migration Support"
Edition , because corresponding TIBCO for this category.
BusinessWorks Container Edition construct is
available with corresponding migration support,
with corner case limitations.

The corresponding TIBCO BusinessWorks 1. This implies a feature parity gap

Container Edition constructs are not currently for TIBCO BusinessWorks
available. Container Edition compared with
ActiveMatrix BusinessWorks 5.x.
2. The value Currently not
supported is mentioned in the
"Migration Support" for this
category.

TIBCO BusinessWorks™ Container Edition Migration

6 | Introduction

Migration Queries Resolution

Note: Contact Product

Management for details on features
that are currently not supported.

The corresponding TIBCO BusinessWorks 1. This means a user can create

Container Edition construct is available, but such a construct using TIBCO
ActiveMatrix BusinessWorks 5.x to TIBCO Business Studio for
BusinessWorks Container Edition migration BusinessWorks, but automated
extension is currently not available. migration from ActiveMatrix
BusinessWorks 5.x is not yet
supported.
2. After migration, re-factor and re-
create the construct using
TIBCO Business Studio for
BusinessWorks.
3. The value BWCE migration not
supported is mentioned in the
"Migration Support" for this
category.

Fundamental design improvements in TIBCO 1. You can achieve better results in

BusinessWorks Container Edition renders TIBCO BusinessWorks
automated migration. Container Edition compared to
ActiveMatrix BusinessWorks 5.x,
but only when the construct is
created in TIBCO Business
Studio for BusinessWorks.
2. After migration, re-factor and re-
create the construct using
TIBCO Business Studio for
BusinessWorks.
3. The value Refactor and
recreate is mentioned in the
"Migration Support" for this
category.

TIBCO BusinessWorks™ Container Edition Migration

7 | Migrating TIBCO ActiveMatrix BusinessWorks Projects to TIBCO BusinessWorks Container Edition

Migrating TIBCO ActiveMatrix BusinessWorks

Projects to TIBCO BusinessWorks Container Edition
After migration, the following should be deleted from your projects:
l Activities from the RV palette
l Signal-In activities (except Wait activity in the Genaral Activity tab)
l Checkpoint activity

TIBCO BusinessWorks™ Container Edition Migration

8 | Type Column Legends

Type Column Legends

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

Values used in Description

Type columns

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

Adapter Special resources used only for configuration of Adapters.

Specific
Resource

Shared Resource configuration with an associated a transport state that can be

Configuration lifecycled.

Shared Re-usable configuration without a transport state that can be lifecycled.

Resource

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

Activity BusinessWorks 5.x and TIBCO BusinessWorks Container Edition .
2. This type of activity starts a new job from external messages or
internal events.

Regular Activity 1. One of the three activity types supported by ActiveMatrix

BusinessWorks 5.x and TIBCO BusinessWorks Container Edition .
2. This type of activity processes its input in-memory.

Built-in 1. An intrinsic built-in feature of TIBCO BusinessWorks Container

Edition process editor.
2. A built-in feature can be from an eclipse or part of the editor
feature (for example, TIBCO BusinessWorks Container Edition
Process Design Editor).

Palette 1. In ActiveMatrix BusinessWorks 5.x, a palette is a TIBCO

Designer™ concept for the grouping of resources or activities.

TIBCO BusinessWorks™ Container Edition Migration

9 | Type Column Legends

Values used in Description

Type columns

2. For the purpose of this documentation, a palette is for describing a

group of activities that are offered as part of core TIBCO
BusinessWorks Container Edition.

Plug-in 1. In ActiveMatrix BusinessWorks 5.x, a TIBCO BusinessWorks

Container Edition Plug-in is an add-on extension that contains
both design-time and runtime extensions of TIBCO
BusinessWorks Container Edition activities.
2. In ActiveMatrix BusinessWorks 5.x, a TIBCO BusinessWorks
Container Edition Plug-in is offered as an add-on product to
TIBCO BusinessWorks Container Edition.
3. For the purpose of this documentation, a plug-in is for describing a
TIBCO BusinessWorks Container Edition add-on product.

Binding 1. In TIBCO BusinessWorks Container Edition , binding type is

offered as a first class concept as part of activities.
2. SOAP binding and REST binding are offered as a part of TIBCO
BusinessWorks Container Edition core features.

TIBCO BusinessWorks™ Container Edition Migration

10 | Standard Constructs

Standard Constructs
The following table lists supported standard constructs.

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

DTD .dtd XSD .xsd Supported l TIBCO

BusinessWorks
Container Edition
currently does not
support DTD
natively.
l TIBCO
BusinessWorks
Container Edition
Migration tool
converts DTD
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.

TIBCO BusinessWorks™ Container Edition Migration

11 | TIBCO ActiveMatrix BusinessWorks™ Core Constructs

TIBCO ActiveMatrix BusinessWorks™ Core

Constructs
The following table displays supported core constructs.

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Design- Application Application Supported

time Module Module
Library

Start Start Start Supported Applies to a Sub

Process. If the Sub
Process refers to
an inline schema it
is externalized.

Process Process Process Supported If the ActiveMatrix

Starter Starter Starter BusinessWorks 5.x
Activity or Activity or activity is a SOAP
Service Service Event Source or a
Service Binding
then the Service is
created. For all
other Process
Starters, it creates
the Process
Starters only.

End End End Supported Applies to a Sub

Process. If the Sub
Process refers to
an inline schema it
is externalized.

TIBCO BusinessWorks™ Container Edition Migration

12 | TIBCO ActiveMatrix BusinessWorks™ Core Constructs

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Global .substvar Process .substvar Supported As TIBCO

Variable Property BusinessWorks
Container Edition
Module
Runtime supports
Property
multiple
Application applications, it is
Property recommended that
Global Variable is
not used to
describe
application
configurable
properties.

Instead, there are

following three
levels of
properties:
l Process
Properties
l Module
Properties
l Application
Properties
These three levels
of properties are
hierarchical:
Application
Properties are in
the outer most
scope, followed by
Module
Properties,
followed by
Process

TIBCO BusinessWorks™ Container Edition Migration

13 | TIBCO ActiveMatrix BusinessWorks™ Core Constructs

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Properties.

You can define

and source value
from its parent
scope. For
example:

1. Process
Property
values can
be defined
by Literal
Values or
source its
value from
its parent
scope
Module
Property.
2. By the same
token,
Module
Property
value can be
defined by
Literal
Values or
source from
its parent
scope
Application
Property.

TIBCO BusinessWorks™ Container Edition Migration

14 | Groups

Groups

BW 5.x BW 5.x BWCE BWCE Migration

Type Type Support

Group Built-In Scope Built-In Supported

Group : If Built-In - - Currently not

supported

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

Group : Repeat Until Built-In Group : Repeat Built-In Supported

True

Group : Repeat On Error Built-In Group : Repeat Built-In Supported

Until True On Error

Group : Transaction Built-In Group : Local Built-In Supported

Transaction

Group : Critical Section Built-In Group : Critical Built-In Supported

Section

Group : Pick First Built-In - - Currently not

supported

Group : While True Built-In Group : While Built-In Supported

TIBCO BusinessWorks™ Container Edition Migration

15 | Transitions

Transitions

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Process .process Process .bwp Supported ActiveMatrix

Definition BusinessWorks
5.x .process files
are migrated as
.bwp files.

Project Designer Application Application Supported

Project Module Module

Transition : Built-In Transition : Built-In Supported

Condition
Condition
Type :
Type :
Success
Success

Transition : Built-In Transition : Built-In Supported

Condition
Condition
Type :
Type :
Success
Success with
with condition
condition

Transition : Built-In Transition : Built-In Supported

Condition
Condition
Type :
Type :
Success
Success with no
with no matching
matching condition
condition

TIBCO BusinessWorks™ Container Edition Migration

16 | Transitions

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Transition : Built-In Transition : Built-In Supported

Condition
Condition
Type : Error
Type :

Error

TIBCO BusinessWorks™ Container Edition Migration

17 | Timer

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

General
The General tab has the following fields.

Field Literal Description

Value/Module
Property/Process
Property

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

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

The local machine’s time zone is used to determine the

process start. If the project is running on machines in
different time zones, the time zone of the machine
where the project was saved, is used. Use a process
property in this field to provide start times relative to
the time zone where the project is deployed. If you
provide a process property for this field, the format of
the specified time must be: yyyy MMM dd HH:mm:ss z

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

If you do not select this check box, the Time Interval

and Interval Unit fields are displayed that you can use
to specify the frequency of the process.

Time Yes The integer indicating the number of units specified in

Interval the Interval Unit field. For example, if a value of 1 is

TIBCO BusinessWorks™ Container Edition Migration

18 | Timer

Field Literal Description

Value/Module
Property/Process
Property

specified and the Interval Unit field is specified as

Hour, a new process is started every hour beginning at
the time specified in the Start Time field.
l If a value of 2 is specified and the Interval Unit
field is specified as Month, a process is started
every other month, beginning at the time
specified in the Start Time field.
l If the value specified is less than one second
(1000 milliseconds), the timer ignores the
specified interval and is triggered once every
second.

Note: Using Literal Value, Module Property, and

Process Property in this field, specifies the time
interval in milliseconds and the Interval Unit field is
not displayed.

Interval None The unit of time to use with the Time Interval field to
Unit determine how 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. Select from the following available options:
l Never: Click the Never radio button if you want
to continuously execute the process instance.
For example, if the Time Interval value specified
is 5 and the Interval Unit specified is Second, the
process instance executes every 5 seconds.
l Occurrences: Clicking the Occurrences radio
button displays the Occurrences field. Specify
the number of occurrences of the process

TIBCO BusinessWorks™ Container Edition Migration

19 | Timer

Field Literal Description

Value/Module
Property/Process
Property

instance execution. This field can be configured

with Literal Value, Module Property, and
Process Property.
l End Time: Clicking the End Time radio button
displays the End Time field. Specify the end time
and date when you want the process to end. This
field can be configured with Literal Value,
Module Property, and Process Property.

Description
Provide a short description of the activity.

Advanced
The Advanced tab has the following fields.

Field Description

Sequencing This field contains an XPath expression that specifies which processes
Key should run in sequence. Process instances with sequencing keys
evaluating to the same value, are executed sequentially in the sequence
the process instance was created.

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

For more information about conversations, see TIBCO BusinessWorks™ Container

Edition Application Development.

Output
The following is the output of the activity.

TIBCO BusinessWorks™ Container Edition Migration

20 | Timer

Output Item Description

TimerOutputSchema The time the process instance started.

The time is represented by several items in the output schema

indicating:
l Now
l Hour
l Minute
l Second
l Week
l Month
l Year
l Date
l Time
l DayOfMonth

Each of these items uses the appropriate datatype.

TIBCO BusinessWorks™ Container Edition Migration

21 | Mapper

Mapper

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

XPATH XPATH in XPATH XPATH in Supported XPATH support in

Designer Eclipse ActiveMatrix
Mapper Mapper BusinessWorks 5.x is
limited to XPATH 1.0.

TIBCO
BusinessWorks
Container Edition
supports XPATH 1.0.
For example, all
literal values used in
XPATH 1.0 must
have a corresponding
constructor function
around the literal
value.

XSLT XSLT in XSLT XSLT in Supported XSLT support in

Designer Eclipse ActiveMatrix
Mapper Mapper BusinessWorks 5.x is
limited to XSLT 1.0.

TIBCO
BusinessWorks
Container Edition
also supports XSLT
1.0.

When a repeating
element is mapped to
a string using a filter,

TIBCO BusinessWorks™ Container Edition Migration

22 | Mapper

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

and the xsl:value-of

instruction parameter
has no separator
attribute, and the
value of the select
expression is a
sequence of more
than one item, then
under XSLT 2.0 all
the items in the
output sequence are
space separated,
whereas for XSLT
1.0, all items after the
first element are
discarded.

TIBCO BusinessWorks™ Container Edition Migration

23 | BusinessWorks Palettes

BusinessWorks Palettes

General Palette

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Alias Shared Application Eclipse Plug- Not

Library Configuratio Module with in Project Supported
n Java Nature or
Eclipse Java
Plug-In Project

Enterprise Shared ActiveMatrix Eclipse Plug- Not Only

Archive Configuratio BusinessWork in Project Supported ActiveMatrix
Resource n s 6.x BusinessWork
Application s 5.x source
project
migration is
supported.

Folder Generic Folder Eclipse Supported

Resource Folder

Generic Generic Generic

Image Resource Resource
Resource

Identity Shared Identity Shared Supported

Configuratio Configuratio
n n

Library .projlib Shared Eclipse Plug- Supported BusinessWork

Builder Module in Project s Container
Edition

TIBCO BusinessWorks™ Container Edition Migration

24 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Migration
Framework,
ActiveMatrix
BusinessWork
s 5.x Design-
time Libraries
are migrated
inline, as part
of regular
resources in
Application
Module.

If the
BusinessWork
s Container
Edition
developer
wants to reuse
the contents of
the DT Library,
the migrated
resource can
be manually
re-factored
into Shared
Module.

Task List .taskList Task List .taskList Currently

not
supported

Text .txt Text .txt Supported

Document Document

TIBCO BusinessWorks™ Container Edition Migration

25 | BusinessWorks Palettes

General Activities Shared Resources

ActiveMatrix BusinessWorks 5.x: General Activities Shared Resources

Type: Palette
TIBCO BusinessWorks Container Edition : Shared Resources Wizards
Type: Shared Resources

BW 5.x BW 5.x BWCE BWCE Migratio Comments

Type Type n
Support

Custom Shared Custom Activity Shared Currently

Activity Configurati Configurati not
on on supporte
d

JNDI Shared JNDI Configuration Shared Support

Configurati Configurati Configurati ed
on on on

Job Shared Module : Job Shared Shared Support

Shared Configurati Variable Configurati ed
Variable on on

Lock Shared Module : Job Shared Shared Support In

Object Configurati Variable Configurati ed ActiveMatrix
on on BusinessWo
rks 5.x, Lock
Object is
used with
the Critical
Section
group. This
construct is
also
supported

TIBCO BusinessWorks™ Container Edition Migration

26 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migratio Comments

Type Type n
Support

for cross
engines
critical
section.

In TIBCO
BusinessWo
rks
Container
Edition , the
Critical
Section
group is
configured
with Module
Shared
Variable.

In TIBCO
Business
Studio for
BusinessWo
rks, module
shared
variables are
configured
through
Module
Descriptors
> Shared
Variables
editor. This
construct is
also
supported

TIBCO BusinessWorks™ Container Edition Migration

27 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migratio Comments

Type Type n
Support

for
AppSpaces
with multiple
AppNodes in
TIBCO
BusinessWo
rks
Container
Edition , if
the
AppSpace is
configured
with Engine
Group
active/active
configuratio
n.

Migration
Tool
migrates
ActiveMatrix
BusinessWo
rks 5.x Lock
Object as a
Module
Shared
Variable and
the Critical
Section
group.

Notify Shared Process : Shared Support

Configurati Configurati WSDL/Interface/Ope Configurati ed
on on ration on

TIBCO BusinessWorks™ Container Edition Migration

28 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migratio Comments

Type Type n
Support

Shared Shared Module : Module Shared Support ActiveMatrix

Variable Resource Shared Variable Resource ed BusinessWo
Type: Shared rks 5.x
Resource shared
variable with
multi-engine
option is
now a
Module
Shared
Variable with
Persistent
option.

General Activities Palette

ActiveMatrix BusinessWorks 5.x: General Activities Palette

Type: Palette
TIBCO BusinessWorks Container Edition : General Activities Palette

Type: Palette

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Assign Regular Basic : Regular Supported

Activity Assign Activity

Call Process Regular Call Process Regular Supported

Activity Activity Activity +
Binding

TIBCO BusinessWorks™ Container Edition Migration

29 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Type

Catch Regular Scope with Built-in Supported

Activity Catch Block

Checkpoint Regular Checkpoint Regular Not

Activity Activity Supported

Confirm Regular Confirm Regular Supported

Activity Activity

Engine Regular Engine Regular Supported

Command Activity Command Activity

External Regular External Regular Supported

Command Activity Command Activity

Generate Regular Basic : Regular Supported

Error Activity Throw Activity

Get Shared Regular Get Shared Regular Supported

Variable Activity Variable Activity

Inspector Regular Inspector Regular Supported

Activity Activity

Label Diagram Note Diagram Supported

Notation Notation

Mapper Regular Mapper Regular Supported

Activity Activity

Notify Regular Invoke Regular Supported In ActiveMatrix

Activity Process Activity BusinessWorks
5.x, Notify, and
Wait activities are

TIBCO BusinessWorks™ Container Edition Migration

30 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

used for inter-

process
communication.

In TIBCO
BusinessWorks
Container Edition ,
a process now
supports interface
with multiple
operations. These
operations can be
used for inter-
process
communication.

When the Notify

and Wait activities
are used for
multiple processes
waiting to receive
notification, you
can use a JMS
transport with
topic to achieve
the same
publish/subscribe
pattern.

Null Regular Basic : Regular Supported

Activity Empty Activity

On Error Process Currently

Starter not
Type:
Activity supported

On Event Process Currently

TIBCO BusinessWorks™ Container Edition Migration

31 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Timeout Starter not

Activity supported

On Process Supported
Notification Starter
Timeout Activity

On Process Activator Process Supported Process with a

Shutdown Starter Process special TIBCO
Activity BusinessWorks
Container Edition
defined service
that supports an
operation for
onShutdown
functionality. This
process can be
configured per
application.

Close, re-open,
and clean the
migrated project to
resolve
unresolved
schema
references.

On Startup Process Activator Process Supported Process with a

Starter Process special TIBCO
Activity BusinessWorks
Container Edition
defined service
that supports an
operation for
onStartup an be
configured per

TIBCO BusinessWorks™ Container Edition Migration

32 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

application.

Close, re-open,
and clean the
migrated project to
resolve
unresolved
schema
references.

Receive Process Basic : Process Supported

Notification Starter Receive Starter
Activity Activity

Rethrow Regular Basic : Regular Supported

Activity Rethrow Activity

Set Shared Regular Set Shared Regular Supported

Variable Activity Variable Activity

Sleep Regular Sleep Regular Supported

Activity Activity

Timer Regular Timer Regular Supported

Activity Activity

Wait Signal-In Receive Process Supported

Activity Starter

Write To Log Regular Log Regular Supported

Activity Activity

ActiveEnterprise Palette

ActiveMatrix BusinessWorks 5.x: ActiveEnterprise Palette

TIBCO BusinessWorks™ Container Edition Migration

33 | BusinessWorks Palettes

Type: Palette
TIBCO BusinessWorks Container Edition : ActiveEnterprise Plug-in
Type: Plug-in

Note: In TIBCO BusinessWorks Container Edition, the ActiveEnterprise

palette is not bundled out-of-the-box. You must install the Adapter Framework
Pack as an add-on Plug-in.

BW 5.x BW 5.x Type BWCE BWCE Type Migration

Support

Adapter Process Starter Adapter Process Starter Supported

Request- Activity Request- Activity
Response Response
Server Server

Adapter Process Starter Adapter Process Starter Supported

Subscriber Activity Subscriber Activity

Invoke an Request/Reply Invoke an Request/Reply Supported

Adapter Activity Adapter Activity
Request Request
response response
Service Service

Publish to Regular Activity Publish to Regular Activity Supported

Adapter Adapter

Respond to Regular Activity Respond to Regular Activity Supported

Adapter Adapter
Request Request

Send Exception Regular Activity Send Exception Regular Activity Supported

to Adapter to Adapter
Request Request

Wait for Adapter Signal-In Activity Wait for Signal-In Activity Not

TIBCO BusinessWorks™ Container Edition Migration

34 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Type Migration

Support

Message Adapter Supported

Message

Wait for Adapter Signal-In Activity Wait for Signal-In Activity Not
Request Adapter Supported
Request

Adapter Resources Palette

ActiveMatrix BusinessWorks 5.x: Adapter Resources Palette

Type: Palette
TIBCO BusinessWorks Container Edition : Adapter Resources Plug-in
Type: Plug-in

BW 5.x BW 5.x Type BWCE BWCE Type Migration Comments

Support

Generic Shared Generic Shared Supported

Adapter Configuration Adapter Configuration
Configuration Configuration

Message Adapter Message Adapter Supported

Filter Specific Filter Specific
Resource Resource

Adapter Adapter Adapter Adapter Supported

Archive Specific Archive Specific
Resource Resource

Advisory Adapter Advisory Adapter Supported

Specific Specific

TIBCO BusinessWorks™ Container Edition Migration

35 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Type Migration Comments

Support

Resource Resource

Client Adapter Client Adapter Supported

Specific Specific
Resource Resource

Generic Log Adapter Generic Log Adapter Supported

Sink Specific Sink Specific
Resource Resource

Generic Adapter Generic Adapter Supported

Transaction Specific Transaction Specific
Control Pool Resource Control Pool Resource

Generic Adapter Generic Adapter Supported

Session Specific Session Specific
Resource Resource

Load URL Adapter Load URL Adapter Supported

Specific Specific
Resource Resource

Log Sink Adapter Log Sink Adapter Supported

Role Specific Role Specific
Resource Resource

Publication Adapter Publication Adapter Supported

Service Specific Service Specific
Resource Resource

Publisher Adapter Publisher Adapter Supported

Specific Specific
Resource Resource

Request- Adapter Request- Adapter Supported

Response Specific Response Specific

TIBCO BusinessWorks™ Container Edition Migration

36 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Type Migration Comments

Support

Invocation Resource Invocation Resource

Service Service

Request- Adapter Request- Adapter Supported

Response Specific Response Specific
Service Resource Service Resource

Server Adapter Server Adapter Supported

Specific Specific
Resource Resource

Subscriber Adapter Subscriber Adapter Supported

Specific Specific
Resource Resource

Subscription Adapter Subscription Adapter Supported

Service Specific Service Specific
Resource Resource

Timer Adapter Timer Adapter Supported

Specific Specific
Resource Resource

BPEL Extension Palette

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

Orchestration .orchestration Built-In : .bwp Supported The

Process Process .orchestration
resource is
available in the
BPEL Palette.

TIBCO BusinessWorks™ Container Edition Migration

37 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

TIBCO
BusinessWorks
Container
Edition Process
is natively
based on
BPEL.

Assign Regular Basic: Regular Supported

Activity Assign Activity

Catch Regular Scope with Built-In Supported

Activity Catch Block

Checkpoint Regular General Regular Not

Activity Activities: Activity Supported
Checkpoint

Exit Regular Basic: Exit Regular Supported

Activity Activity

Invoke Regular Basic: Regular Supported

Activity Invoke Activity

Invoke Regular General Regular Supported

Process Activity Activities : Activity
Invoke
Process +
Reference
Binding

Null Regular Basic: Regular Supported

Activity Empty Activity

On Alarm Process Built-In: Built-In Currently

Starter Alarm not

TIBCO BusinessWorks™ Container Edition Migration

38 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

Activity Handler supported

On Event Process Built-In: Built-In Supported

Starter Event
Activity Handler

Receive Process Basic: Process Supported

Starter Starter Receive Starter
Activity (Create Activity
Instance =
true)

Type:
Process
Starter
Activity

Receive Signal-In Basic: Signal-In Not

Activity Receive Activity Supported
(Create
Instance =
false)

Reply with Regular Basic : Regular Supported

Fault Activity Reply with Activity
Fault
configured

Reply Regular Basic: Regular Supported

Activity Reply Activity

Rethrow Regular Basic: Regular Supported

Activity Rethrow Activity

Sleep Regular General Regular Supported

Activity Activities: Activity

TIBCO BusinessWorks™ Container Edition Migration

39 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

Sleep

Throw Regular Basic: Regular Supported

Activity Throw Activity

Write To Log Regular General Regular Supported

Activity Activities: Activity
Log

File Palette

ActiveMatrix BusinessWorks 5.x: File Palette

Type: Palette
TIBCO BusinessWorks Container Edition : File Palette
Type: Palette

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Copy File Regular Copy File Regular Supported

Activity Activity

Create File Regular Create File Regular Supported

Activity Activity

File Poller Process File Poller Process Supported

Starter Starter
Activity Activity

List Files Regular List Files Regular Supported

Activity Activity

TIBCO BusinessWorks™ Container Edition Migration

40 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Type Migration Comments

Type Support

Read File Regular Read File Regular Supported

Activity Activity

Remove Regular Remove Regular Supported

File Activity File Activity

Rename Regular Rename Regular Supported

File Activity File Activity

Wait for File Signal-In Wait for File Signal-In Not

Change Activity Change Activity supported

Write File Regular Write File Regular Supported

Activity Activity

FTP Palette

ActiveMatrix BusinessWorks 5.x: FTP

Type: Palette
TIBCO BusinessWorks Container Edition : FTP Palette

Type: Palette

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

FTP Shared FTP Shared Supported

Connection Resource Connection Resource
Type: Shared
Resource

FTP Change Regular FTP Change Regular Supported

TIBCO BusinessWorks™ Container Edition Migration

41 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Default Activity Default Activity

Directory Directory

FTP Delete Regular FTP Delete Regular Supported

File Activity File Type: Activity
Regular
Activity

FTP Dir Regular FTP Dir Regular Supported

Activity Activity

FTP Get Regular FTP Get Regular Supported

Default Activity Default Activity
Directory Directory

FTP Get Regular FTP Get Regular Supported

Activity Activity

FTP Make Regular FTP Make Regular Supported

Remote Activity Remote Activity
Directory Directory

FTP Put Regular FTP Put Regular Supported

Activity Activity

FTP Quote Regular FTP Quote Regular Supported

Activity Activity

FTP Remove Regular FTP Remove Regular Supported

Remote Activity Remote Activity
Directory Directory

FTP Rename Regular FTP Rename Regular Supported

File Activity File Activity

FTP Sys Regular FTP Sys Regular Supported

Type Activity Type Activity

TIBCO BusinessWorks™ Container Edition Migration

42 | BusinessWorks Palettes

HTTP Palette

ActiveMatrix BusinessWorks 5.x: HTTP

Type: Palette
TIBCO BusinessWorks Container Edition : HTTP Palette
Type: Palette

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

HTTP Shared HTTP Shared Supported HTTP Connection

Connection Resource Connector Resource shared resource
is migrated to
TIBCO
BusinessWorks
Container Edition
as an HTTP
Connector
shared resource.
This is for the
HTTP Service.

TIBCO
BusinessWorks
Container Edition
uses Jetty Server
and does not
support Tomcat
and
HttpComponent
implementation
from ActiveMatrix
BusinessWorks
5.x.

Proxy Shared Proxy Shared Supported

Configuration Resource Configuration Resource

TIBCO BusinessWorks™ Container Edition Migration

43 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

HTTP Process HTTP Process Supported

Receiver Starter Receiver Starter

Send HTTP Regular Send HTTP Regular Supported TIBCO

Request Activity Request Activity BusinessWorks
Container Edition
has also
introduced a new
shared resource
for this client side
invoke, HTTP
Client shared
resource. You can
use this shared
resource to
configure and
tune a number of
optimization
parameters such
as Maximum
Total Connection
and Maximum
Total Connection
Per Host.

This new HTTP

Client shared
resource also
allows the users
to configure a
Thread Pool
shared resource (
new in TIBCO
BusinessWorks
Container Edition
). Using the

TIBCO BusinessWorks™ Container Edition Migration

44 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Thread Pool
shared resource
you can configure
Minimum Pool
Size, Maximum
Pool Size and a
number of other
tuning
parameters.

Note: After
Axis2 upgrade,
Apache
Commons
client library is
no longer used
in HTTP. The
projects
migrated from
ActiveMatrix
BusinessWork
s 5.x shall now
show Apache
Components
as the client
library instead
of Apache
Commons.

Send HTTP Regular Send HTTP Regular Supported

Response Activity Response Activity

Wait For Signal-In Wait For Signal-In Not

HTTP Activity HTTP Activity supported
Request Request

TIBCO BusinessWorks™ Container Edition Migration

45 | BusinessWorks Palettes

JAVA Palette

ActiveMatrix BusinessWorks 5.x: JAVA

Type: Palette
TIBCO BusinessWorks Container Edition : JAVA Palette
Type: Palette

Note: If the ActiveMatrix BusinessWorks 5.x project has an activity from the
Java palette, the TIBCO BusinessWorks Container Edition application module
gets converted to a Java project. The additional src and lib folders are seen in
the project. The src folder contains the Java source files. The lib folder
contains the Java libraries (JAR Files). Java Nature is also added to the
project.

BW BW 5.x BWCE BWCE Migratio Comments

5.x Type Type n
Support

Java Shared Shared Support

Custo Configurat Custo Configurat ed
m ion m ion
Functi XPAT
on H
Functi
on

Java Shared Java Shared Support

Global Resource Global Resource ed
Instanc Instanc
e e

Java Shared XSD .xsd Support In TIBCO BusinessWorks

Schem Configurat Schem ed Container Edition the Java To
a ion a XML and XML To Java
activities do not use Java

TIBCO BusinessWorks™ Container Edition Migration

46 | BusinessWorks Palettes

BW BW 5.x BWCE BWCE Migratio Comments

5.x Type Type n
Support

Schema. After migration the

corresponding Schema
equivalent to the Java Schema
is generated and associated
with the activity.

Java Regular Java Regular Support The source code for the Java
Code Activity Invoke Activity ed Code activity which was in-lined
in the ActiveMatrix
BusinessWorks 5.x now gets
created externally in the src
folder of the AppModule and
then it is referred by the Java
Invoke activity with MultiOutput
check box selected.

Java Process Java Process Support The Source code for Java
Event Starter Proces Starter ed Event Source activity which
Source Activity s Activity was in-lined in the ActiveMatrix
Starter BusinessWorks 5.x now gets
created externally in the src
folder of the AppModule and
then Java Process Starter
activity refers to it.

The Java class implementing

the Java Event Source now
extends
[Link]
ProcessStarter class instead of
[Link]
er.

Java Event Source in

ActiveMatrix BusinessWorks 5.x
referring to an external class

TIBCO BusinessWorks™ Container Edition Migration

47 | BusinessWorks Palettes

BW BW 5.x BWCE BWCE Migratio Comments

5.x Type Type n
Support

needs to change this.

Java Regular Java Regular Support

Metho Activity Invoke Activity ed
d

Java Regular Java Regular Support

To Activity To Activity ed
XML XML

XML Regular XML Regular Support

To Activity To Activity ed
Java Java

JDBC Palette

ActiveMatrix BusinessWorks 5.x: JDBC

Type: Palette
TIBCO BusinessWorks Container Edition : JDBC Palette

Type: Palette

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

JDBC Shared JDBC Shared Supported

Connection Resource Connection Resource

JDBC Call Regular JDBC Call Regular Supported

Procedure Activity Procedure Activity

TIBCO BusinessWorks™ Container Edition Migration

48 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

JDBC Get Regular JDBC Get Regular Currently

Connection Activity Connection Activity not
supported

JDBC Query Regular JDBC Query Regular Supported

Activity Activity

JDBC Update Regular JDBC Update Regular Supported

Activity Activity

SQL Direct Regular SQL Direct Regular Supported

Activity Activity

JMS Palette

ActiveMatrix BusinessWorks 5.x: JMS Palette

Type: Palette
TIBCO BusinessWorks Container Edition : JMS Palette
Type: Palette

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

JMS Shared XSD .xsd Supported JMS

Application Configuration Schema Application
Properties Properties is
migrated as
XML Schema
(XSD File) in
TIBCO
BusinessWorks

TIBCO BusinessWorks™ Container Edition Migration

49 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

Container
Edition .

JMS Shared JMS Shared Supported

Connection Resource Connection Resource

Get JMS Regular Get JMS Regular Supported

Queue Activity Queue Activity
Message Message

JMS Queue Process JMS Process Supported

Receiver Starter Receive Starter
Activity Message Activity

JMS Queue Regular JMS Regular Supported

Requester Activity Request Activity
Reply

JMS Queue Regular JMS Send Regular Supported

Sender Activity Message Activity

JMS Topic Regular JMS Send Regular Supported

Publisher Activity Message Activity

Type: Type:
Regular Regular
Activity Activity

JMS Topic Regular JMS Regular Supported

Requestor Activity Request Activity
Reply
Type:
Regular Type:
Activity Regular
Activity

JMS Topic Process JMS Process Supported

TIBCO BusinessWorks™ Container Edition Migration

50 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

Subscriber Starter Receive Starter

Activity Message Activity

Reply to Regular Reply to Regular Supported

JMS Activity JMS Activity
Message Message

Type: Type:
Regular Regular
Activity Activity

Wait for Signal-In Wait for Signal-In Not

JMS Queue Activity JMS Activity supported
Message Message

Wait for Signal-In Wait for Signal-In Not

JMS Topic Activity JMS Activity supported
Message Message

Mail Palette

ActiveMatrix BusinessWorks 5.x: Mail Palette

Type: Palette
TIBCO BusinessWorks Container Edition : Mail Palette
Type: Palette

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Receive Process Receive Process Supported

Mail Starter Mail Starter
Activity Activity

TIBCO BusinessWorks™ Container Edition Migration

51 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Send Mail Regular Send Mail Regular Supported TIBCO

Activity Activity BusinessWorks
Container Edition
introduces a new
SMTP shared
resource.
ActiveMatrix
BusinessWorks 5.x
Send Mail activity
configuration
migrates to both
Send Mail activity
and SMTP shared
resource.

Parse Palette

ActiveMatrix BusinessWorks 5.x: Parse Palette

Type: Palette
TIBCO BusinessWorks Container Edition : Parse Palette

Type: Palette

BW 5.x BW 5.x Type BWCE BWCE Type Migration Comments

Support

Data Shared Data Shared Supported

Format Configuration Format Configuration

Parse Regular Activity Parse Regular Activity Supported

Data Data

TIBCO BusinessWorks™ Container Edition Migration

52 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Type Migration Comments

Support

Render Regular Activity Render Regular Activity Supported

Data Data

Policy Palette

ActiveMatrix BusinessWorks 5.x: Policy Palette

Type: Palette

BW 5.x BW 5.x Type BWCE BWCE Type Migration Comments

Support

Security Shared Security Shared Currently

Policy Configuration Policy Configuration not
Association Association supported

Security Shared Security Shared Currently

Policy Configuration Policy Configuration not
supported

Process Palette

ActiveMatrix BusinessWorks 5.x: Process Palette

Type: Palette
TIBCO BusinessWorks Container Edition : Built-In
Type: Built-In

TIBCO BusinessWorks™ Container Edition Migration

53 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Process .process Process .bwp Supported

Definition

Process Shared Applicatio .application Refactor In ActiveMatrix

Archive Configuratio n Project and BusinessWorks 5.x,
n recreate Process Archive is
configured within the
Enterprise Archive
Resource. This specifies
which processes in the
ActiveMatrix
BusinessWorks 5.x
project are packaged to
form an .EAR file for
deployment.

In TIBCO
BusinessWorks
Container Edition , the
Enterprise Archive
Resource and Process
Archive configuration
are no longer supported
and their functionality
are replaced by
Application and
Application Module,
respectively. Any project
artifacts that can be re-
used by multiple
Applications and
multiple Application
Modules are created in
Shared Modules.

In the current version of

Migration Tool, an

TIBCO BusinessWorks™ Container Edition Migration

54 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

ActiveMatrix
BusinessWorks 5.x
project is migrated as an
application module with
a corresponding
application project. If the
content of the
ActiveMatrix
BusinessWorks 5.x
project is meant for
creating multiple
applications, then do the
following:

1. Convert the
Application
Module to Shared
Module.
2. Create an
Application
Module and a
corresponding
application
project.
a. In the
Application
Module >
Module
Descriptors
>
Component
s editor,
define the
component
to refer to
process

TIBCO BusinessWorks™ Container Edition Migration

55 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

implementat
ion in the
Shared
Module.
b. Repeat 2.a
step for
each
process that
is required
to be a part
of this
Application
Module. In
TIBCO
BusinessW
orks
Container
Edition , a
Process
(say,
Process A)
in a Shared
Module is
not
activated
unless a
Component
is defined
and is
configured
with
Process A .
3. Repeat Step 2 for
the number of
applications
required.

TIBCO BusinessWorks™ Container Edition Migration

56 | BusinessWorks Palettes

REST and JSON Plug-in

ActiveMatrix BusinessWorks 5.x: REST/JSON Plug-in
Type: Plug-in
TIBCO BusinessWorks Container Edition : REST and JSON Palette
Type: Palette
Migration: Supported

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Invoke Regular Invoke Regular Supported TIBCO

REST API Activity REST Activity with BusinessWorks
API limitations Container Edition
does not support the
following:
l WADL protocols
l Responses
returned in
binary format
l Rich output
l Authentication
OAuth1.0 and
OAuth2.0

Note: The Circuit Breaker pattern is not supported by the Invoke REST API activity. If
you want to use Circuit Breaker pattern, you need to configure the REST Reference
Binding. For more information, see Using the Wizard to Create a REST Reference in
TIBCO BusinessWorks™ Container Edition REST Reference.

Parse Regular Parse Regular Supported TIBCO

JSON Activity JSON Activity with BusinessWorks
limitations Container Edition
does not support the
schema type Java

TIBCO BusinessWorks™ Container Edition Migration

57 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Classes.

Render Regular Render Regular Supported The Remove Root

JSON Activity JSON Activity with check box is not
limitations supported in
ActiveMatrix
BusinessWorks . Root
elements in TIBCO
BusinessWorks
Container Edition are
skipped by default.
You must modify the
input JSON if it
contains root element.

The schema type Java

Classes is not
supported in TIBCO
BusinessWorks
Container Edition .

REST Regular REST Service Supported The ActiveMatrix

Dispatch Activity Service Binding with BusinessWorks 5.x
and Reply Binding limitations Dispatch and Reply
REST activity is
migrated to REST
Service Binding of
TIBCO
BusinessWorks
Container Edition .

REST Service of
TIBCO
BusinessWorks
Container Edition uses
XSD as the resource
for building REST

TIBCO BusinessWorks™ Container Edition Migration

58 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

Service. The XSD

must be external to
the WSDL. That is,
direct reference to
inline schema in
WSDL is not
supported for REST
binding.

If the Dispatch and

Reply activity is
configured to route
requests to
ActiveMatrix
BusinessWorks 5.x
processes with inline
schema for its input,
output and fault, then
the TIBCO
BusinessWorks
Container Edition
Migration Tool
currently does not
externalize the inline
schema before
configuring the REST
binding. You can
manually externalize
the inline schema and
re-create the REST
binding.

TIBCO
BusinessWorks
Container Edition also
does not support the
following:

TIBCO BusinessWorks™ Container Edition Migration

59 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

l Enable WADL
Reference
l Enable OAuth
l Parameter
styles-Template
and Header

Note: For more information about additional restrictions, see "Restrictions on

XML Schema" in TIBCO BusinessWorks™ Container Edition Bindings and
Palettes Reference.

RMI Palette

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

RMI Regular RMI Regular Currently not None

Lookup Activity Lookup Activity supported

RMI Process RMI Process Currently not None

Server Starter Server Starter supported

Service Palette

ActiveMatrix BusinessWorks 5.x: Service Palette

Type: Palette
TIBCO BusinessWorks Container Edition : Built-In

TIBCO BusinessWorks™ Container Edition Migration

60 | BusinessWorks Palettes

Type: Built-In
Migration: Supported

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

Context .contextResource Built-In Supported Migrated as

Resource Job Shared
Variable

Partner Link .sharedpartner Process : Built-In Supported

Configuration Reference

Service .serviceagent Process : Built-In Supported

Service

Get Context Regular Basic : Get Regular Supported Post migration,

Activity Context Activity two sets of Get
Context and
Set Context
activities are
displayed in a
service
process. The
sets retrieve
the context
information
and pass the
information to
the
subprocesses,
and vice versa.

Invoke Regular Basic : Regular Supported SOAP

Partner Activity Invoke Activity Request Reply
Service activity is
migrated as a
process with

TIBCO BusinessWorks™ Container Edition Migration

61 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Migration Comments

Type Support

reference and
SOAP
reference
binding is
added for the
same. The
binding is
added under
Module
Descriptors >
Components >
Binding.

Receive Process Basic : Process Supported

Partner Starter Activity Receive Starter
Notification Activity

Set Context Regular Basic : Set Regular Supported Post migration,

Activity Context Activity two sets of Get
Context and
Set Context
activities are
displayed in a
service
process. The
sets retrieve
the context
information
and pass the
information to
the
subprocesses,
and vice versa.

SOAP Palette

TIBCO BusinessWorks™ Container Edition Migration

62 | BusinessWorks Palettes

ActiveMatrix BusinessWorks 5.x: SOAP Palette

Type: Palette
TIBCO BusinessWorks Container Edition : Basic Palette + SOAP Binding
Type: Binding
Migration: Supported

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

MIME Regular Parse : Regular Currently

Parser Activity MIME Activity not
Parser supported

Retrieve Regular Generate Regular Currently The WSDL in TIBCO

Resource Activity WSDL Activity not BusinessWorks Container
s Service + SOAP supported Edition has to be generated
Binding in TIBCO Business Studio for
BusinessWorks on the
Component Binding.

SOAP Process Basic : Process Supported The SOAP Event Source is

Event Starter Receive + Starter with migrated as a Process with
Source Activity SOAP Activity limitation Service and a SOAP Service
Service + SOAP s. Binding is added for the
Binding Binding same. The Binding is added
under Module Descriptors,
Components, or Binding.

Currently only Copy-Of

binding is supported for
headers in the Binding
section. Manually, set/map
the Input tab of the Set
Context activity to use the
SOAP Event Source activity
header migration
functionality.

TIBCO BusinessWorks™ Container Edition Migration

63 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

SOAP Regular Basic : Regular Supported The SOAP Request Reply is

Request Activity Invoke Activity with migrated as a Process with
Reply Service + + SOAP limitation Reference and a SOAP
SOAP Binding s. Reference Binding is added
Referenc for the same. The Binding is
e Binding added under Module
Descriptors/Components/Bin
ding.

Currently only Copy-Of

binding is supported for
headers in the Binding
section. Manually, set/map
the Input tab of the Set
Context activity to use the
SOAP Request Reply
activity header migration
functionality.

SOAP Regular Basic : Regular Supported

Send Activity Reply Activity
Fault with Fault + SOAP
+ SOAP Binding
Referenc
e Binding

SOAP Regular Basic Regular Supported

Send Activity Activities: Activity
Reply Reply + + SOAP
SOAP Binding
Referenc
e Binding

TCP Palette

ActiveMatrix BusinessWorks 5.x: TCP Palette

TIBCO BusinessWorks™ Container Edition Migration

64 | BusinessWorks Palettes

Type: Palette
TIBCO BusinessWorks Container Edition : TCP Palette
Type: Palette
Migration: Supported

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

TCP Shared TCP Shared Supported

Connection Resource Connection Resource

Read TCP Regular Read TCP Regular Supported

Data Activity Data Activity

TCP Close Regular TCP Close Regular Supported

Connection Activity Connection Activity

TCP Open Regular TCP Open Regular Supported

Connection Activity Connection Activity

TCP Process TCP Process Supported

Receiver Starter Receiver Starter
Activity Activity

Wait for TCP Signal-In Wait for TCP Signal-In Not

Request Activity Request Activity Supported

Write TCP Regular Write TCP Regular Supported

Data Activity Data Activity

Transaction Palette

TIBCO BusinessWorks™ Container Edition Migration

65 | BusinessWorks Palettes

BW 5.x BW 5.x BWCE BWCE Migration Comments

Type Type Support

JTA User Shared JTA User Shared Currently

Transaction Resource Transaction Resource not
Configuration Configuration supported

XA Shared XA Shared Currently

Transaction Resource Transaction Resource not
Manager Manager supported
Configuration Configuration

Transaction Regular Transaction Regular Currently

State Activity State Activity not
supported

XML Palette

ActiveMatrix BusinessWorks 5.x: XML Palette

Type: Palette
TIBCO BusinessWorks Container Edition : XML Palette
Type: Palette
Migration: Supported

BW 5.x BW 5.x Type BWCE BWCE Type Migration Comments

Support

XSLT File Shared XSLT File Shared Supported

Configuration Configuration

Parse XML Regular Parse XML Regular Supported

Activity Activity

Render Regular Render Regular Supported

TIBCO BusinessWorks™ Container Edition Migration

66 | BusinessWorks Palettes

BW 5.x BW 5.x Type BWCE BWCE Type Migration Comments

Support

XML Activity XML Activity

Transform Regular Transform Regular Supported

XML Activity XML Activity

TIBCO BusinessWorks™ Container Edition Migration

67 | Migration Scenario

Migration Scenario
The migration scenarios show the core construct migration of ActiveMatrix
BusinessWorks 5.x projects. After migration, these projects are converted to their
equivalent in TIBCO BusinessWorks Container Edition . The TIBCO BusinessWorks
Container Edition Call Process, Start, and End activities 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
ActiveMatrix BusinessWorks 5.x to TIBCO BusinessWorks Container Edition .

ActiveMatrix BusinessWorks 5.x TIBCO BusinessWorks Container Edition

Call Process is literal. It calls a process Call Process mechanism is based on the
with process pipeline data mapped into it standard Invoke activity. It abstracts out the
and generates an output that is in essence actual Call Process configuration to the
the output of the called process. reference that the Invoke activity is calling.

After Migration: Call Process activity is

migrated as a Direct Call Process.

Start and End Activity Migration

The following table provides information about the Start and End activities migration
from ActiveMatrix BusinessWorks 5.x to TIBCO BusinessWorks Container Edition .

ActiveMatrix BusinessWorks 5.x TIBCO BusinessWorks

Container Edition

The Start activity is a receiver that starts a process on receiving The Start activity and
a message that may be empty. The End activity sends a reply. End activity are now
supported.
The Start activity is the first activity in a process definition
(process starters replace the Start activity when used in a
process definition).

The End activity is the last activity in a process definition.

TIBCO BusinessWorks™ Container Edition Migration

68 | Migration Scenario

Activator
In TIBCO BusinessWorks Container Edition , each application module has one Activator
process that has two service operations, On StartUp and On ShutDown. Any TIBCO
Designer process linked with the On Start and On ShutDown activity in ActiveMatrix
BusinessWorks 5.x after migration is simultaneously changed to a StartUp Operation
activity and On ShutDown Operation activity. The activator calls the start() and stop()
methods to start or stop the process.

Service and References

Service and References are defined at a process level.

ActiveMatrix TIBCO BusinessWorks Container Edition

BusinessWorks 5.x

SOAP services are used for Includes REST compliant services along with HTTP and
exchanging information in JMS, where the purpose of the service is to manipulate
the implementation of web XML representations of web resources using a uniform set
services relying on XML of stateless operations. When using a stateless operation,
message format sent over the state is managed by the job itself instead of by the
HTTP and JMS. engine.

TIBCO BusinessWorks™ Container Edition Migration

69 | Migration Scenario

Migrating ActiveMatrix BusinessWorks 5.x Projects

to TIBCO BusinessWorks Container Edition
Use the following options to migrate ActiveMatrix BusinessWorks 5.x projects to TIBCO
BusinessWorks Container Edition
l Project > Migrate BW Projects option in TIBCO Business Studio for
BusinessWorks
l 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 for BusinessWorks.

Before you begin

l Perform validation and ensure that ActiveMatrix BusinessWorks 5.x project does

not have errors.

l Optionally, schemas without namespaces should be refactored before migration.
l Remove spaces in the namespace.
l Remove or update any retrieve WSDL processes.
l It is recommended to add missing namespaces for the schemas.
l Ensure that there are no spaces or special characters in folder names.
l 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.
l Ensure that no two resources, such as schemas, WSDLs, and DTDs have the
same name when they have a common hierarchical structure or layout.

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

TIBCO BusinessWorks™ Container Edition Migration

70 | Migration Scenario

TIBCO BusinessWorks™ Container Edition Migration

71 | Migration Scenario

2. In the Project Migration Wizard dialog box, to migrate a single ActiveMatrix

BusinessWorks 5.x project, click Migrate Single BusinessWorks 5x Project.
To migrate multiple projects, click Migrate Multiple BusinessWorks 5.x Project.
When migrating a single ActiveMatrix BusinessWorks 5.x project, you can also

TIBCO BusinessWorks™ Container Edition Migration

72 | Migration Scenario

migrate selective processes or subprocesses. Select the Select Processes for

Migration check box, and provide the required information as explained in Step 7,
below.
After the required information is provided, the Select Processes button is
displayed.

Note: The Select Processes for Migration check box is disabled when
you select the Migrate Multiple BusinessWorks 5.x Projects option.
Use this check box only to migrate single projects.

The list of processes in the selected TIBCO ActiveMatrix BusinessWorks™ 5.x

project are displayed in the Project Migration Wizard dialog box. The processes
can be viewed in the Flat Hierarchy or in the Tree Hierarchy structures.
3. To select all the subprocesses under the main process, click Select Linked
Processes. Clear the check box for the process you do not want to migrate.
To view the static and dynamic processes that are selected for migration, click
Show Linked Process Hierarchy.
4. While migrating selective processes, to select or clear the already migrated
existing processes, on the Select Processes page of the Project Migration Wizard
dialog box, select the Re-Select Process check box.

Note: 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.

Note: 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 workspace where the project is migrated. To provide a different
workspace, click Browse.

TIBCO BusinessWorks™ Container Edition Migration

73 | Migration Scenario

c. While migrating any project from version 2.5.3 of ActiveMatrix

BusinessWorks onwards, the default XPATH language for transitions is pre-
set to XPATH 1.0. Select XPATH 2.0 to set the XPATH language for
transitions to XPATH 2.0. The transitions are migrated by default to XPATH
2.0 for versions prior to ActiveMatrix BusinessWorks.

Note: The XPATH language for transition is introduced to get rid of

invalid comparison or conversion issues on transitions or groups
while migrating ActiveMatrix BusinessWorks 5.x projects.

d. To browse for third party jars required for your project, click the Select Third
Party JAR's folder field.
e. The Single XPath Function Group Project check box is selected by default,
to create all custom XPaths as a single plugin project and under a single
custom XPath.
After migration, the custom XPath function group plugin project is included in
the application project. The classes folder is located in the
[Link] file, and is no longer available 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 libraries to be used for the project.
g. In the Select Java Libraries used by Project field, click Browse and provide
the location of the JAR files on disk if the ActiveMatrix BusinessWorks 5.x
project is using external JAR files in context with Java activities.
Important: TIBCO recommends that you place the external JAR files in a
single location.
These JAR files can then be in-lined in the migrated TIBCO BusinessWorks
Container Edition project.
7. Click Migrate Project.
l The process count displayed on the Migrate page of the Project Migration
Wizard is inclusive of migration service agents.
l The tooltip available for the Migration progress bar displays the general
information about migration process.

TIBCO BusinessWorks™ Container Edition Migration

74 | Migration Scenario

l 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 process respectively.
l To cancel the migration process anytime, in the Project Migration Wizard,
click Cancel.
8. Click Finish after the migration is complete.

Project with Subprocess after Migration

Subprocesses in TIBCO BusinessWorks Container Edition use a standardized concept
of receiving messages and replying to messages through a service.

Before Migration

After Migration

The Call Process is migrated as a Direct Call Process.

TIBCO BusinessWorks™ Container Edition Migration

75 | Migration Scenario

Migrating Project Using Command line

Another option for a speedy migration is migrating the projects using the command line.
Usage: bwmigrator [-options] BW5Project...

where options include the following:

Option Description

-projectDir Location where TIBCO BusinessWorks Container Edition projects are to

be generated.

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

-propFile The [Link] file. The syntax for passing the bw6migration
properties file is [Link] [-data <User_Workspace>] -projectDir

TIBCO BusinessWorks™ Container Edition Migration

76 | Migration Scenario

Option Description

<BusinessWorks 6.x Target directory> <BusinessWorks 5.x Project location> -propFile

<[Link] location>.

The template can be found at, <TIBCO_HOME>\bw\6.4\config\bw6migration_

[Link].

Examples
l bwmigrator -projectDir <BWCE_PROJECTS_HOME>\projects <TIBCO_
HOME>\5.9\examples\activities\file\File (Migrates single TIBCO ActiveMatrix
BusinessWorks™ 5.x project.)
l bwmigrator -projectDir <BWCE_PROJECTS_HOME>\projects <TIBCO_
HOME>\5.9\examples\activities\file\File <TIBCO_HOME>\5.9\examples\activities\ftp\ftp (Migrates
File and FTP TIBCO ActiveMatrix BusinessWorks™ 5.x projects.)
l bwmigrator -projectDir <BWCE_PROJECTS_HOME>\projects <TIBCO_
HOME>\5.9\examples\activities (Migrates all TIBCO ActiveMatrix BusinessWorks™ 5.x
projects in activities directory.)
l bwmigrator -projectDir <BWCE_PROJECTS_HOME>\projects <TIBCO_HOME>\5.9\examples\file
<TIBCO_HOME>\5.9\examples\ftp (Migrates all TIBCO ActiveMatrix BusinessWorks™
5.x Projects in File and FTP directories.)

Procedure
1. In the command prompt, type the following command:
[Link] -projectDir c:/temp <BW 5.x Project Path>

Note: For Java migration type the following command: [Link] -

projectDir c:/temp -classpath <Jar Location Path> <BW 5.x Project Path>

Command line Configuration File Template

The TIBCO BusinessWorks Container Edition migration configuration file, .properties file is
a template file that contains configurable properties to migrate design time libraries,
custom XPath functions, selected processes and projects using the command line.
To migrate projects using the command line migration option open the .properties file and
paste the command from the .properties file on the command prompt and execute the
command which has the following format as stated below:

TIBCO BusinessWorks™ Container Edition Migration

77 | Migration Scenario

Example: [Link] [-data <User_Workspace>] -projectDir <BusinessWorks 6.x Target directory>

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

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

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

Selective Migration
Prop Description
erty

select The default value false migrates all the processes.

Proces
s Set the property to true to migrate only the specified processes.

selectL The default value false migrate the specified main process.
inkedP
rocess For example, .process=<process1>,<process2>....

Set the property to true to migrate all the dependent processes, of the specified
main process.
For example,.process=<folder1/process1>,</process2>,. Specifying the main process
path migrate all the processes that are dependent on the main process.

.proce Provide comma separated processes with relative process paths with respect to
ss the ActiveMatrix BusinessWorks 5.x project root folder as explained in the following
example. .process=Service/ZipInfo-
[Link],TestService/[Link],Service/[Link],TestS
ervice/[Link],Service/[Link],TestService/getCity
[Link],TestService/[Link],

Design Time Library Migration (DTL)

Property Description

sharedModule The default value of this property is false, and migrates the DTL as an
application module.

Set the property to true to create an TIBCO BusinessWorks Container

Edition shared module.

TIBCO BusinessWorks™ Container Edition Migration

78 | Migration Scenario

Mapping DTLs to Shared Modules

Property Description

dtlDir Provide the project lib folder location here.

For example, C:/Users/workspace1/folder/[Link].

sharedModuleDirs Provide multiple directory locations by using comma separated values.

For example, C:/CLIWorkspace,C:/CLIWorkspace/SharedModuleProject1,....

Custom XPath Migration

Property Description

singleCXFGroupProject By default, the property is set to true, to migrate all the custom
XPath functions under a single custom XPath function group.

Set the property to false to migrate each custom XPath function

and create custom XPath function groups for each individual
XPath function.

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

Post-Migration Manual Tasks

If you encounter problem markers that are related to activity input mapping, use the
Show Check and Repair 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 [Link].
2. Click the activity in your project, then click the Input tab.

3. Click the Show Check and Repair icon .

The Mapper Check and Repair window is displayed.

TIBCO BusinessWorks™ Container Edition Migration

79 | Migration Scenario

4. Click OK and run the project.

Fix Type-Casting Errors

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

Note: If the Project > Clean option does not work to resolve problem
markers, close and reopen the project.

HTTP Basic Sample

This section describes how to migrate an HTTP Basic sample.

Before you begin

Migrate the 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.

TIBCO BusinessWorks™ Container Edition Migration

80 | Migration Scenario

4. Click the Send-Request-to-Wiki-News (Send HTTP Request) activity and

specify the following three values on the 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"

5. Click the Send-Response-from-Wiki-News (Send HTTP Response) activity and

specify the value for Content-Type on the Input tab.

TIBCO BusinessWorks™ Container Edition Migration

81 | Migration Scenario

Custom XPath Migration

Some 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
BusinessWorks Container Edition .

Procedure
1. Export the custom XPath function plug-ins into the Host repository. To do this,
right-click on the XPath 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.

Migrating Design Time Libraries ( DTL) as Shared

Modules
ActiveMatrix BusinessWorks 5.x design time library source projects are migrated as
TIBCO BusinessWorks Container Edition shared modules.

Migrating Design Time Libraries Using TIBCO Business Studio for BusinessWorks

TIBCO BusinessWorks™ Container Edition Migration

82 | Migration Scenario

Use the TIBCO BusinessWorks Container Edition framework to migrate ActiveMatrix

BusinessWorks 5.x projects where the business process uses design time libraries to
define processes, resources, and subprocesses.

You can migrate the design time libraries using the following options:
l Project > Migrate BW Projects option in TIBCO Business Studio for
BusinessWorks

Procedure
1. In the Project Migration Wizard dialog box, click Migrate Single BusinessWorks
5.x Project and select the Migrate as Shared Module check box.
2. Provide the Project Location details and the XPATH Function Group
Configuration details if a custom XPath is used in the project.
3. To browse for third party jars only if your project contains a custom XPath, click the
Select Third Party JARs folder field .
4. Click Migrate Project.

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

After migration, do not perform refactoring operations on any of the resources, such as
the schema, TIBCO BusinessWorks Container Edition shared resources, and service
definitions. The resource properties, and naming conventions must be retained as they
are. Mapping issues, if any, can be corrected, and resource specific properties of the
shared resources can be changed.

Limitations
l Shared module migration does not support ActiveMatrix BusinessWorks 5.x AE
schemas. AE Schemas are migrated as part of the application module.
l Custom XPath function project duplication should be managed manually by
deleting the duplicate source projects.
l DTL migration does not support the Process Name Dynamic Override feature of

TIBCO BusinessWorks™ Container Edition Migration

83 | Migration Scenario

the Call Process activity. Instead, add the process name manually.

Migrating Application Modules

ActiveMatrix BusinessWorks 5.x projects using design time libraries can be migrated as
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.

TIBCO BusinessWorks™ Container Edition Migration

84 | Migration Scenario

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

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

Using the Quick Fix Option to Resolve XSLT out of

Sync Errors
After migrating a project, use the Quick Fix option to resolve XSLT out of Sync errors in
the project.

Before you begin

Set the minimum JVM heap size to either 4GB, 6GB or 8GB, keeping in mind the size of
the project. For additional instructions, see Specifying JVM Heap Size in TIBCO
BusinessWorks™ Container Edition Performance Benchmarking and Tuning.
After migrating a project, follow these steps:

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

TIBCO BusinessWorks™ Container Edition Migration

85 | Migration Scenario

2. From the Problems tab, click the downward arrow icon, and select Configure
Contents.
The Configure Contents window is displayed.
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. If there are a few XSLT out of Sync errors still lingering, use the Quick Fix
option to resolve these problems. Make sure the Auto Build is turned off during this
process.

TIBCO BusinessWorks™ Container Edition Migration

86 | Migration Process Outline

Migration Process Outline

The migration mechanism takes ActiveMatrix BusinessWorks 5.x projects and converts
them to their equivalent in TIBCO BusinessWorks Container Edition .
The process flow in the project is migrated as is for the following:
l The activities and their associated mappings
l The transitions and their associated conditions
l Groups

TIBCO BusinessWorks Container Edition Project Migration

5.x Project in TIBCO 6.x Project in TIBCO Business Studio for
Designer BusinessWorks

Process TIBCO BusinessWorks Container Edition Process

Schema Schema

WSDL WSDL

Shared Resource TIBCO BusinessWorks Container Edition Shared

Resource

Note: 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 project can run into design time
issues due to incorrect namespaces and imports.

TIBCO BusinessWorks™ Container Edition Migration

87 | Migration Process Outline

Project Migration Diagram

The following image shows the project process flow after the migration. Activities,
transitions, and their associated mappings visible in ActiveMatrix BusinessWorks 5.x
project in TIBCO Designer are displayed in TIBCO BusinessWorks Container Edition
project in TIBCO Business Studio for BusinessWorks.

TIBCO BusinessWorks™ Container Edition Migration

88 | Migration Process Outline

Migrated Project - Before and After

TIBCO BusinessWorks™ Container Edition Migration

89 | Frequently Asked Questions

Frequently Asked Questions

What do I do... Answer

When migrated process shows 1. Go to Menu > Project > Clean and click Clean
mapping errors? All Projects.
2. Go to the Activity Input with the Mapping Error.
Click Show Check and Repair and fix existing
errors.
3. Click Fix Type Casting Errors.
4. If the error still persists, check the expression
and do the necessary corrections.

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

WSDL references?
2. If this does not fix the references, heck the
WSDL Interface value on the General tab of the
Process Service.

When Java Invoke activities show 1. Go to the General tab of the Java Invoke
Input Configuration Error after activity and check whether the Class Name is
migration? available in the workspace. If available, re-select
the Java class.
2. If the class is not available, check whether the
JAR file packaging the Java class is available.
Otherwise, copy the JAR file to the "lib" folder
and reselect the Java class.

When activities in the Catch block The Catch Block activities does not have the visibility
show Mapping errors? to the output of the activities from the main process.

Re-map the activity input accordingly. This is similar to

the Java try or catch constructs.

When Variable not defined error for 1. In TIBCO BusinessWorks Container Edition the
Iterate Group Index variable is Iterate Group Index Variable does not have
used outside the Iterate scope? visibility outside the Iterate scope.

TIBCO BusinessWorks™ Container Edition Migration

90 | Frequently Asked Questions

What do I do... Answer

2. Define a process variable of type integer, map it

to the Iterate Group Index variable, and use the
variable in the process scope.

When a ActiveMatrix The ActiveMatrix BusinessWorks 5.x activity migrates

BusinessWorks 5.x activity as Rescue activity, if the migration framework fails to
migrates as Empty or Rescue migrate.
activity TIBCO BusinessWorks
1. Check the ActiveMatrix BusinessWorks 5.x
Container Edition ?
project
2. Add the corresponding activity in the TIBCO
BusinessWorks Container Edition project
3. Redo the mappings.

After migrating a project using the The function tib:concat-sequence-format() does not accept
tib:concat-sequence-format(), the a string as its return value for node set.
output returns errors.
After migration, replace the tib:concat-sequence-format()
with the string-join() function.

When a group is around the 1. Verify the XPath condition and resolve the group
activities and the XPath condition issues (for example, iterator, for-each...)
over the group is not satisfied
2. Re-map the same from the group.
after migration, the Expected Non
Repeating got repeating error is
displayed.

When the Variable not defined error 1. Remove all the variables
is displayed post migration for
2. Recreate the variables
multiple variables created in the
input of any activity and each 3. Add the mappings again. In this case the back-
variable is created with the end references are also removed.
condition on another variable. 4. Delete the XPath on the variables one by one
and re-correct them. This also resolves the issue
sometimes.

When the Unresolved reference Reconfigure the broken module variables. Redo all the

TIBCO BusinessWorks™ Container Edition Migration

91 | Frequently Asked Questions

What do I do... Answer

schema error is displayed. mappings as they break due to reconfiguration.

When the Catch-All End error is not When a Catch All fault handler is used in a
configured. ActiveMatrix BusinessWorks project, on migration the
fault handler is converted as expected but an End
activity is created in place of a Catch All activity. An
End activity without any input is created. Delete the
end activity and to resolve the issue.

Schema references issues post References of schemas that are imported in another
migration schema are not found. Delete the import and add it
again. The references are updated with the correct
namespace and the namespace issues are resolved.

When you map an integer value, Create a new Mapper activity using the same naming
for example 1, to a decimal field, and mappings from the existing mapper activity.
expecting the output in the
Once all the inwards and outwards mappings are
decimal field to be 1, but, instead,
done, delete the old Mapper activity, which is already
the decimal field result is 1.0.
migrated, and point the transitions to the newly created
mapper activity.

There is no tokenize-allow-empty() After migration to TIBCO BusinessWorks Container

function in TIBCO BusinessWorks Edition , the tokenize() function can yield the same
Container Edition . results as the tib:tokenize-allow-empty() and tib:tokenize()
functionsof ActiveMatrix BusinessWorks 5.x.

When a mapper activity that has a Post migration, convert the XSLT version in the activity
tokenize function inside a for-each from 1.0 to 2.0, since in version 1.0 the for-each
expression, throws a Null Input at expression requires things to be evaluated to a node-
runtime? set.

The Tokenize function creates a sequence of string

atoms, which is not node-set.

In 2.0, the for-each expression must be evaluated to

sequence, which covers the sequence of atoms and
node scenario.

TIBCO BusinessWorks™ Container Edition Migration

92 | Frequently Asked Questions

What do I do... Answer

After migration, when a boolean 1. Navigate to Windows > Preferences > Mapper.
always evaluates to false with
2. Select the Assume all inputs untyped check
XSLT 1.0 and validation off.
box.
3. Click Apply, and then OK.
4. Clean the project. After the errors related to
untyped input are displayed, use the Quick Fix
option to resolve them.
5. Execute the project.

After migration, when there is a 1. Navigate to Windows > Preferences > Mapper.
invalid comparison, or conversion
2. Select the Enable Quick fix to change Xpath
error in a transition or a group.
version 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 the
Quick Fix option for the XPath Version 2.0.

TIBCO BusinessWorks™ Container Edition Migration

93 | TIBCO Documentation and Support Services

TIBCO Documentation and Support Services

For information about this product, you can read the documentation, contact TIBCO
Support, and join TIBCO Community.

How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation
website, mainly in HTML and PDF formats.
The TIBCO Product Documentation website is updated frequently and is more current
than any other documentation included with the product. To access the latest
documentation, visit [Link]

Product-Specific Documentation
Documentation for TIBCO BusinessWorks™ Container Edition is available on the TIBCO
BusinessWorks™ Container Edition Product Documentation page.
To directly access documentation for this product, double-click the following file:
TIBCO_HOME/release_notes/TIB_bwce_2.6.2_docinfo.html where TIBCO_HOME is the top-level
directory in which TIBCO products are installed. On Windows, the default TIBCO_HOME
is C:\tibco. On UNIX systems, the default TIBCO_HOME is /opt/tibco.
The following documents for this product can be found in the TIBCO Documentation site:
l TIBCO BusinessWorks™ Container Edition Release Notes
l TIBCO BusinessWorks™ Container Edition Installation
l TIBCO BusinessWorks™ Container Edition Application Development
l TIBCO BusinessWorks™ Container Edition Application Monitoring and
Troubleshooting
l TIBCO BusinessWorks™ Container Edition Bindings and Palettes Reference
l TIBCO BusinessWorks™ Container Edition Concepts
l TIBCO BusinessWorks™ Container Edition Error Codes
l TIBCO BusinessWorks™ Container Edition Getting Started
l TIBCO BusinessWorks™ Container Edition Migration

TIBCO BusinessWorks™ Container Edition Migration

94 | TIBCO Documentation and Support Services

l TIBCO BusinessWorks™ Container Edition Performance Benchmarking and

Tuning
l TIBCO BusinessWorks™ Container Edition REST Implementation
l TIBCO BusinessWorks™ Container Edition Refactoring Best Practices
l TIBCO BusinessWorks™ Container Edition Samples

How to Join TIBCO Community

TIBCO Community is the official channel for TIBCO customers, partners, and employee
subject matter experts 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, and tools that extend and enable
customers to gain full value from TIBCO products. In addition, users can submit and vote
on feature requests from within the TIBCO Ideas Portal. For a free registration, go to
[Link]

TIBCO BusinessWorks™ Container Edition Migration

95 | Legal and Third-Party Notices

Legal and Third-Party Notices

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

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND
CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED
SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT,
THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING
DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE
LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR
CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE
“LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE
TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE
OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

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

TIBCO, the TIBCO logo, the TIBCO O logo, TIBCO ActiveMatrix BusinessWorks, TIBCO
ActiveSpaces, TIBCO Business Studio for BusinessWorks, TIBCO Designer, TIBCO Enterprise
Message Service, TIBCO Hawk, TIBCO Rendezvous, and TIBCO Runtime Agent are either
registered trademarks 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
Corporation and/or its affiliates.

This document includes fonts that are licensed under the SIL Open Font License, Version 1.1,
which is available at: [Link]

Copyright (c) Paul D. Hunt, with Reserved Font Name Source Sans Pro and Source Code Pro.

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

This software may be available on multiple operating systems. However, not all operating system
platforms for a specific software version are released at the same time. See the readme file for the
availability of this software version on a specific operating system platform.

TIBCO BusinessWorks™ Container Edition Migration

96 | Legal and Third-Party Notices

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

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL

ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE
CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO
SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY

OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,
INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

This and other products of TIBCO Software Inc. may be covered by registered patents. Please
refer to TIBCO's Virtual Patent Marking document ([Link] for details.

Copyright © 2015-2021. TIBCO Software Inc. All Rights Reserved.

TIBCO BusinessWorks™ Container Edition Migration