TIBCO BusinessWorks™ Container Edition Migration
-
Upload
khangminh22 -
Category
Documents
-
view
0 -
download
0
Transcript of TIBCO BusinessWorks™ Container Edition Migration
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, TIBCO ActiveMatrix BusinessWorks™, TIBCO Administrator™, TIBCOBusiness Studio™ for BusinessWorks™, Hawk®, Rendezvous®, TIBCO Runtime Agent™, TIBCODesigner™, TIBCO Enterprise Message Service™, and TIBCO ActiveSpaces® 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 OracleCorporation in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.
This software may be available on multiple operating systems. However, 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 BusinessWorks™ Container Edition Migration
Copyright © 2015-2019. TIBCO Software Inc. All Rights Reserved.
3
TIBCO BusinessWorks™ Container Edition Migration
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Migrating TIBCO ActiveMatrix BusinessWorks Projects to TIBCO BusinessWorks Container Edition . . . . 10
ActiveMatrix BusinessWorks 5.x and TIBCO BusinessWorks™ Container Edition Type Columns Legend . .11
Standard Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
TIBCO BusinessWorks™ Container Edition Core Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Mapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
BusinessWorks Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
General Activities Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
JDBC Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
JMS Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Mail Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Parse Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Policy Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Process Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
REST and JSON Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
RMI Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Service Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
SOAP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
TCP Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Transaction Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
XML Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Migration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4
TIBCO BusinessWorks™ Container Edition Migration
Migrating TIBCO BusinessWorks™ Container Edition 5.x projects to TIBCO BusinessWorks Container Edition . . . . . . . . . 56
Migrating Projects Using TIBCO Business Studio™ for BusinessWorks™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Migrating Project Using Command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Command line Configuration File Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Post-Migration Manual Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
HTTP Basic Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Custom XPath Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Migrating Design Time Libraries ( DTL) as Shared Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Using the Quick Fix Option to Resolve XSLT out of Sync Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Migration Process Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5
TIBCO BusinessWorks™ Container Edition Migration
Figures
TIBCO BusinessWorks Container Edition Project Migration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
TIBCO BusinessWorks Container Edition 5.x Migrated Project - Before and After . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6
TIBCO BusinessWorks™ Container Edition Migration
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.
The following documents for this product can be found on the TIBCO Documentation site:
● TIBCO BusinessWorks™ Container Edition Application Development
● TIBCO BusinessWorks™ Container Edition Application Monitoring and Troubleshooting
● TIBCO BusinessWorks™ Container Edition Bindings and Palettes Reference
● TIBCO BusinessWorks™ Container Edition Concepts
● TIBCO BusinessWorks™ Container Edition Error Codes
● TIBCO BusinessWorks™ Container Edition Getting Started
● TIBCO BusinessWorks™ Container Edition Installation
● TIBCO BusinessWorks™ Container Edition Migration
● TIBCO BusinessWorks™ Container Edition Performance Benchmarking and Tuning
● TIBCO BusinessWorks™ Container Edition Release Notes
● TIBCO BusinessWorks™ Container Edition REST Implementation
● TIBCO BusinessWorks™ Container Edition Samples
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
TIBCO BusinessWorks™ Container Edition Migration
Introduction
TIBCO BusinessWorks™ Container Edition architecture provides a migration path for TIBCOBusinessWorks Container Edition 5.x projects with a few exceptions. This document explains how tomigrate from TIBCO BusinessWorks Container Edition 5.x to TIBCO BusinessWorks Container Edition ,and lists differences between the two. There are many new features in TIBCO BusinessWorks ContainerEdition that advance integration, but are not covered in this document.
Migration Queries Resolution
TIBCO BusinessWorks Container Edition 5.xconstructs migrating to equivalent TIBCOBusinessWorks Container Edition constructs.
The value Supported is mentioned in the"Migration Support" for this category.
Supported does not mean defect free.
TIBCO BusinessWorks Container Edition 5.xconstructs are not migrating to TIBCOBusinessWorks Container Edition , becausecorresponding TIBCO BusinessWorksContainer Edition construct is available withcorresponding migration support, withcorner case limitations.
The value Supported with limitations is mentionedin the "Migration Support" for this category.
The corresponding TIBCO BusinessWorksContainer Edition constructs are notcurrently available.
1. This implies a feature parity gap for TIBCOBusinessWorks Container Edition comparedwith TIBCO BusinessWorks Container Edition5.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 TIBCO BusinessWorksContainer Edition construct is available, butTIBCO BusinessWorks Container Edition 5.xto TIBCO BusinessWorks Container Editionmigration extension is currently notavailable.
1. This means a user can create such a constructusing TIBCO Business Studio™ forBusinessWorks™, but automated migration fromTIBCO BusinessWorks Container Edition 5.x isnot yet supported.
2. After migration, re-factor and re-create theconstruct using TIBCO Business Studio forBusinessWorks.
3. The value BWCE migration not supported ismentioned in the "Migration Support" for thiscategory.
8
TIBCO BusinessWorks™ Container Edition Migration
Migration Queries Resolution
Fundamental design improvements inTIBCO BusinessWorks Container Editionrenders automated migration.
1. You can achieve better results in TIBCOBusinessWorks Container Edition compared toTIBCO BusinessWorks Container Edition 5.x, butonly when the construct is created in TIBCOBusiness Studio for BusinessWorks.
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
TIBCO BusinessWorks™ Container Edition Migration
Migrating TIBCO ActiveMatrix BusinessWorks Projects toTIBCO BusinessWorks Container Edition
After migration, the following should be deleted from your projects:
● Activities from the RV palette
● Signal-In activities (except Wait activity in the Genaral Activity tab)
● Checkpoint activity
10
TIBCO BusinessWorks™ Container Edition Migration
ActiveMatrix BusinessWorks 5.x and TIBCOBusinessWorks™ Container Edition Type Columns Legend
The following values are used in the "Type" columns.
Values used in Type columns Description
.<resource extension> The file extension used to describe its type. Forexample, .xml, .xsd, and .wsdl resources.
Adapter Specific Resource Special resources used only for configuration of Adapters.
Shared Configuration Resource configuration that has associated a transport statethat you can lifecycle.
Shared Resource Re-usable configuration that does not have a transport statethat you can lifecycle.
Process Starter Activity1. One of the three activity types supported by ActiveMatrix
BusinessWorks™ 5.x and TIBCO BusinessWorks ContainerEdition .
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
BusinessWorks™ 5.x and TIBCO BusinessWorks ContainerEdition .
2. This type of activity processes its input in-memory.
Built-in1. 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 theeditor feature (for example, TIBCO BusinessWorksContainer Edition Process Design Editor).
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 TIBCO BusinessWorks Container Edition.
11
TIBCO BusinessWorks™ Container Edition Migration
Values used in Type columns Description
Plug-in1. In ActiveMatrix BusinessWorks™ 5.x, a TIBCO
BusinessWorks Container Edition Plug-in is an add-onextension that contains both design-time and runtimeextensions of TIBCO BusinessWorks Container Editionactivities.
2. In ActiveMatrix BusinessWorks™ 5.x, a TIBCOBusinessWorks Container Edition Plug-in is offered as anadd-on product to TIBCO BusinessWorks ContainerEdition.
3. For the purpose of this documentation, a plug-in is fordescribing a TIBCO BusinessWorks Container Edition add-on product.
Binding1. 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 ofTIBCO BusinessWorks Container Edition core features.
12
TIBCO BusinessWorks™ Container Edition Migration
Standard Constructs
The supported standard TIBCO BusinessWorks™ Container Edition constructs are listed here.
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
DTD .dtd XSD .xsd Supported● TIBCO BusinessWorks
Container Edition currentlydoes not support DTDnatively.
● TIBCO BusinessWorksContainer Edition Migrationtool converts DTD resourceto 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.
13
TIBCO BusinessWorks™ Container Edition Migration
TIBCO BusinessWorks™ Container Edition CoreConstructs
The following table displays the supported Core TIBCO BusinessWorks Container Edition constructs.
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
Design-timeLibrary
ApplicationModule
ApplicationModule
Supported
Start Start Start Supported Applies to a Sub Process. Ifthe Sub Process refers to aninline schema it will beexternalized.
ProcessStarter
ProcessStarterActivity orService
ProcessStarterActivity orService
Supported If the TIBCO BusinessWorksContainer Edition 5.xactivity is a SOAP EventSource or a Service Bindingthen the Service will becreated. For all otherProcess Starter it will createthe Process Starter only.
End End End Supported Applies to a Sub Process. Ifthe Sub Process refers to aninline schema it will beexternalized.
14
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
GlobalVariable
.substvar ProcessProperty
ModuleProperty
ApplicationProperty
.substvar Supported As TIBCO BusinessWorksContainer Edition 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.
15
TIBCO BusinessWorks™ Container Edition Migration
Groups
BW 5.x BW 5.x Type BWCE BWCE Type Migration Support
Group Built-In Scope Built-In Supported
Group : If Built-In 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 Group : PickFirst
Built-In Currently notsupported
Group : WhileTrue
Built-In Group : While Built-In Supported
16
TIBCO BusinessWorks™ Container Edition Migration
Mapper
BW 5.xBW 5.xType BWCE BWCE Type
MigrationSupport Comments
XPATH XPATH inDesignerMapper
XPATH XPATH inEclipseMapper
Supported XPATH support in TIBCOBusinessWorks™ ContainerEdition 5.x is limited toXPATH 1.0.
TIBCO BusinessWorksContainer Edition 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 TIBCOBusinessWorks ContainerEdition 5.x is limited to XSLT1.0.
TIBCO BusinessWorksContainer Edition alsosupports 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.
17
TIBCO BusinessWorks™ Container Edition Migration
Transitions
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
ProcessDefinition
.process Process .bwp Supported TIBCOBusinessWorks™Container Edition5.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
18
TIBCO BusinessWorks™ Container Edition Migration
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.
19
TIBCO BusinessWorks™ Container Edition Migration
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.
For more information about conversations, see the TIBCO BusinessWorks™ Container Edition ApplicationDevelopment guide.
Output
The following is the output of the activity.
20
TIBCO BusinessWorks™ Container Edition Migration
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.
21
TIBCO BusinessWorks™ Container Edition Migration
BusinessWorks Palettes
General Palette
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
AliasLibrary
SharedConfiguration
ApplicationModulewith JavaNature orEclipse JavaPlug-InProject
EclipsePlug-inProject
NotSupported
EnterpriseArchiveResource
SharedConfiguration
ActiveMatrixBusinessWorks 6Application
EclipsePlug-inProject
NotSupported
Only 5.x source projectmigration is supported.
Folder GenericResource
Folder EclipseFolder
Supported
GenericImageResource
GenericResource
GenericResource
Identity SharedConfiguration
Identity SharedConfiguration
Supported
LibraryBuilder
.projlib SharedModule
EclipsePlug-inProject
Supported BusinessWorks ContainerEdition MigrationFramework, ActiveMatrixBusinessWorks 5.x Design-time Libraries aremigrated inline, as part ofregular resources inApplication Module.
If the BusinessWorksContainer Editiondeveloper wants to reusethe contents of the DTLibrary, the migratedresource can be manuallyre-factored into SharedModule.
22
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
Task List .taskList Task List .taskLis
t
Currentlynotsupported
TextDocument
.txt TextDocument
.txt Supported
General Activities Shared Resources
TIBCO BusinessWorks™ Container Edition 5.x: General Activities Shared Resources
Type: Palette
TIBCO BusinessWorks Container Edition : Shared Resources Wizards
Type: Shared Resources
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
CustomActivity
SharedConfiguration
CustomActivity
SharedConfiguration
Currentlynotsupported
JNDIConfiguration
SharedConfiguration
JNDIConfiguration
SharedConfiguration
Supported
Job SharedVariable
SharedConfiguration
Module : JobSharedVariable
SharedConfiguration
Supported
23
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
Lock Object SharedConfiguration
Module : JobSharedVariable
SharedConfiguration
Supported In TIBCOBusinessWorksContainerEdition 5.x,Lock Object isused with theCriticalSection group.This constructis alsosupported forcross enginescritical section.
In TIBCOBusinessWorksContainerEdition , theCriticalSection groupis configuredwith ModuleSharedVariable.
In TIBCOBusinessStudio™ forBusinessWorks™ , modulesharedvariables areconfiguredthroughModuleDescriptors >SharedVariableseditor. Thisconstruct isalso supportedfor AppSpaceswith multipleAppNodes inTIBCOBusinessWorksContainerEdition , if theAppSpace isconfiguredwith EngineGroup active/activeconfiguration.
24
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
Migration Toolmigrates theTIBCOBusinessWorksContainerEdition 5.xLock Object asa ModuleSharedVariable andthe CriticalSection group.
NotifyConfiguration
SharedConfiguration
Process :WSDL/Interface/Operation
SharedConfiguration
Supported
SharedVariable
SharedResource
Module :ModuleSharedVariable Type:SharedResource
SharedResource
Supported TIBCOBusinessWorksContainerEdition 5.xshared variablewith multi-engine optionis now aModule SharedVariable withPersistentoption.
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 Type BWCE BWCE TypeMigrationSupport Comments
Assign RegularActivity
Basic : Assign RegularActivity
Supported
Call Process RegularActivity
Call ProcessActivity
RegularActivity +Binding Type
Supported
25
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
Catch RegularActivity
Scope withCatch Block
Built-in Supported
Checkpoint RegularActivity
Checkpoint RegularActivity
Not Supported
Confirm RegularActivity
Confirm RegularActivity
Supported
EngineCommand
RegularActivity
EngineCommand
RegularActivity
Supported
ExternalCommand
RegularActivity
ExternalCommand
RegularActivity
Not 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
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
Notify RegularActivity
Invoke Process RegularActivity
Supported InActiveMatrixBusinessWorks™ 5.x, Notify,and Waitactivities areused for inter-processcommunication.
In TIBCOBusinessWorksContainerEdition , aprocess nowsupportsinterface 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
27
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
On EventTimeout
ProcessStarterActivity
Currently notsupported
OnNotificationTimeout
ProcessStarterActivity
Supported
OnShutdown
ProcessStarterActivity
ActivatorProcess
Process Supported Process with aspecial TIBCOBusinessWorksContainerEdition definedservice thatsupports anoperation foronShutdownfunctionality.This processcan beconfigured perapplication.
Close, re-open,and clean themigratedproject toresolveunresolvedschemareferences.
On Startup ProcessStarterActivity
ActivatorProcess
Process Supported Process with aspecial TIBCOBusinessWorksContainerEdition definedservice thatsupports anoperation foronStartup anbe configuredperapplication.
Close, re-open,and clean themigratedproject toresolveunresolvedschemareferences.
28
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
ReceiveNotification
ProcessStarterActivity
Basic : Receive ProcessStarterActivity
Supported
Rethrow RegularActivity
Basic :Rethrow
RegularActivity
Supported
Set SharedVariable
RegularActivity
Set SharedVariable
RegularActivity
Supported
Sleep RegularActivity
Sleep RegularActivity
Supported
Timer RegularActivity
Timer RegularActivity
Supported
Wait Signal-InActivity
Receive ProcessStarter
Supported
Write To Log RegularActivity
Log RegularActivity
Supported
ActiveEnterprise Palette
TIBCO BusinessWorks™ Container Edition 5.x: ActiveEnterprise Palette
Type: Palette
TIBCO BusinessWorks Container Edition : ActiveEnterprise Plug-in
Type: Plug-in
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 TypeMigrationSupport
AdapterRequest-Response Server
Process StarterActivity
Adapter Request-Response Server
Process StarterActivity
Supported
AdapterSubscriber
Process StarterActivity
AdapterSubscriber
Process StarterActivity
Supported
Invoke anAdapter Requestresponse Service
Request/ReplyActivity
Invoke anAdapter Requestresponse Service
Request/ReplyActivity
Supported
Publish toAdapter
Regular Activity Publish toAdapter
Regular Activity Supported
29
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport
Respond toAdapter Request
Regular Activity Respond toAdapter Request
Regular Activity Supported
Send Exceptionto AdapterRequest
Regular Activity Send Exception toAdapter Request
Regular Activity Supported
Wait for AdapterMessage
Signal-In Activity Wait for AdapterMessage
Signal-In Activity Not Supported
Wait for AdapterRequest
Signal-In Activity Wait for AdapterRequest
Signal-In Activity Not Supported
Adapter Resources Palette
TIBCO BusinessWorks™ Container Edition 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 TypeMigrationSupport Comments
GenericAdapterConfiguration
SharedConfiguration
GenericAdapterConfiguration
SharedConfiguration
Supported
Message Filter AdapterSpecificResource
MessageFilter
AdapterSpecificResource
Supported
AdapterArchive
AdapterSpecificResource
AdapterArchive
AdapterSpecificResource
Supported
Advisory AdapterSpecificResource
Advisory AdapterSpecificResource
Supported
Client AdapterSpecificResource
Client AdapterSpecificResource
Supported
Generic LogSink
AdapterSpecificResource
Generic LogSink
AdapterSpecificResource
Supported
30
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
GenericTransactionControl Pool
AdapterSpecificResource
GenericTransactionControl Pool
AdapterSpecificResource
Supported
GenericSession
AdapterSpecificResource
GenericSession
AdapterSpecificResource
Supported
Load URL AdapterSpecificResource
Load URL AdapterSpecificResource
Supported
Log Sink Role AdapterSpecificResource
Log Sink Role AdapterSpecificResource
Supported
PublicationService
AdapterSpecificResource
PublicationService
AdapterSpecificResource
Supported
Publisher AdapterSpecificResource
Publisher AdapterSpecificResource
Supported
Request-ResponseInvocationService
AdapterSpecificResource
Request-ResponseInvocationService
AdapterSpecificResource
Supported
Request-ResponseService
AdapterSpecificResource
Request-ResponseService
AdapterSpecificResource
Supported
Server AdapterSpecificResource
Server AdapterSpecificResource
Supported
Subscriber AdapterSpecificResource
Subscriber AdapterSpecificResource
Supported
SubscriptionService
AdapterSpecificResource
SubscriptionService
AdapterSpecificResource
Supported
Timer AdapterSpecificResource
Timer AdapterSpecificResource
Supported
31
TIBCO BusinessWorks™ Container Edition Migration
BPEL Extension Palette
BW 5.x BW 5.x Type BWCEBWCEType
MigrationSupport Comments
OrchestrationProcess
.orchestration Built-In :Process
.bwp Supported The .orchestrationresource is availablein the BPEL Palette.
TIBCOBusinessWorks™Container EditionProcess is nativelybased on BPEL.
Assign RegularActivity
Basic:Assign
RegularActivity
Supported
Catch RegularActivity
Scope withCatch Block
Built-In Supported
Checkpoint RegularActivity
GeneralActivities:Checkpoint
RegularActivity
NotSupported
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
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCEBWCEType
MigrationSupport Comments
ReceiveStarter
ProcessStarterActivity
Basic:Receive(CreateInstance =true)
Type:ProcessStarterActivity
ProcessStarterActivity
Supported
Receive Signal-InActivity
Basic:Receive(CreateInstance =false)
Signal-InActivity
NotSupported
Reply withFault
RegularActivity
Basic : Replywith Faultconfigured
RegularActivity
Supported
Reply RegularActivity
Basic: Reply RegularActivity
Supported
Rethrow RegularActivity
Basic:Rethrow
RegularActivity
Supported
Sleep RegularActivity
GeneralActivities:Sleep
RegularActivity
Supported
Throw RegularActivity
Basic:Throw
RegularActivity
Supported
Write To Log RegularActivity
GeneralActivities:Log
RegularActivity
Supported
File Palette
TIBCO BusinessWorks™ Container Edition 5.x: File Palette
Type: Palette
TIBCO BusinessWorks Container Edition : File Palette
Type: Palette
33
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
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
Notsupported
Write File RegularActivity
Write File RegularActivity
Supported
FTP Palette
TIBCO BusinessWorks™ Container Edition 5.x: FTP
Type: Palette
TIBCO BusinessWorks Container Edition : FTP Palette
Type: Palette
BW 5.xBW 5.xType BWCE BWCE Type
MigrationSupport Comments
FTPConnection
SharedResource
FTP ConnectionType: SharedResource
SharedResource
Supported
FTP ChangeDefaultDirectory
RegularActivity
FTP ChangeDefaultDirectory
RegularActivity
Supported
34
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE BWCE Type
MigrationSupport Comments
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 BusinessWorks™ Container Edition 5.x: HTTP
Type: Palette
TIBCO BusinessWorks Container Edition : HTTP Palette
Type: Palette
35
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
HTTPConnection
SharedResource
HTTPConnector
SharedResource
Supported HTTP Connectionshared resource ismigrated to TIBCOBusinessWorksContainer Edition asan HTTP Connectorshared resource. Thisis for the HTTPService.
TIBCO BusinessWorksContainer Edition usesJetty Server and doesnot support Tomcatand HttpComponentimplementation fromTIBCO BusinessWorksContainer Edition 5.x.
ProxyConfiguration
SharedResource
ProxyConfiguration
SharedResource
Supported
HTTPReceiver
ProcessStarter
HTTPReceiver
ProcessStarter
Supported
36
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
Send HTTPRequest
RegularActivity
Send HTTPRequest
RegularActivity
Supported TIBCO BusinessWorksContainer Edition 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 TIBCOBusinessWorksContainer Edition ).Using the Thread Poolshared resource youcan configureMinimum Pool Size,Maximum Pool Sizeand a number of othertuning parameters.
Send HTTPResponse
RegularActivity
Send HTTPResponse
RegularActivity
Supported
Wait ForHTTPRequest
Signal-InActivity
Wait ForHTTP Request
Signal-InActivity
Notsupported
JAVA Palette
TIBCO BusinessWorks™ Container Edition 5.x: JAVA
Type: Palette
TIBCO BusinessWorks Container Edition : JAVA Palette
Type: Palette
37
TIBCO BusinessWorks™ Container Edition Migration
If the TIBCO BusinessWorks Container Edition 5.x project has an activity from the Java palette, theTIBCO BusinessWorks Container Edition application module gets converted to a Java project. Theadditional src and lib folders are seen in the project. The src folder contains the Java source files. Thelib folder contains the Java libraries (JAR Files). Java Nature is also added to the project.
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
JavaCustomFunction
SharedConfiguration
CustomXPATHFunction
SharedConfiguration
Supported
Java GlobalInstance
SharedResource
Java GlobalInstance
SharedResource
Supported
JavaSchema
SharedConfiguration
XSDSchema
.xsd Supported In TIBCOBusinessWorksContainer Editionthe Java To XMLand XML To Javaactivities do not useJava Schema. Aftermigration thecorrespondingSchema equivalentto the Java Schemais generated andassociated with theactivity.
Java Code RegularActivity
JavaInvoke
RegularActivity
Supported The source code forthe Java Codeactivity which wasin-lined in theTIBCOBusinessWorksContainer Edition5.x now gets createdexternally in the srcfolder of theAppModule andthen it is referred bythe Java Invokeactivity withMultiOutput checkbox selected.
38
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
Java EventSource
ProcessStarterActivity
JavaProcessStarter
ProcessStarterActivity
Supported The Source code forJava Event Sourceactivity which wasin-lined in theTIBCOBusinessWorksContainer Edition5.x now 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 TIBCOBusinessWorksContainer Edition5.x referring to anexternal class needsto change this.
JavaMethod
RegularActivity
JavaInvoke
RegularActivity
Supported
Java ToXML
RegularActivity
Java ToXML
RegularActivity
Supported
XML ToJava
RegularActivity
XML ToJava
RegularActivity
Supported
JDBC Palette
TIBCO BusinessWorks™ Container Edition 5.x: JDBC
Type: Palette
TIBCO BusinessWorks Container Edition : JDBC Palette
Type: Palette
39
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE BWCE Type
MigrationSupport Comments
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 BusinessWorks™ Container Edition 5.x: JMS Palette
Type: Palette
TIBCO BusinessWorks Container Edition : JMS Palette
Type: Palette
BW 5.x BW 5.x Type BWCEBWCEType
MigrationSupport Comments
JMSApplicationProperties
SharedConfiguration
XSD Schema .xsd Supported JMS ApplicationProperties is migratedas XML Schema (XSDFile) in TIBCOBusinessWorksContainer Edition .
JMSConnection
SharedResource
JMSConnection
SharedResource
Supported
Get JMSQueueMessage
RegularActivity
Get JMSQueueMessage
RegularActivity
Supported
JMS QueueReceiver
ProcessStarterActivity
JMS ReceiveMessage
ProcessStarterActivity
Supported
40
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCEBWCEType
MigrationSupport Comments
JMS QueueRequester
RegularActivity
JMS RequestReply
RegularActivity
Supported
JMS QueueSender
RegularActivity
JMS SendMessage
RegularActivity
Supported
JMS TopicPublisher
Type:RegularActivity
RegularActivity
JMS SendMessage
Type:RegularActivity
RegularActivity
Supported
JMS TopicRequestor
Type:RegularActivity
RegularActivity
JMS RequestReply
Type:RegularActivity
RegularActivity
Supported
JMS TopicSubscriber
ProcessStarterActivity
JMS ReceiveMessage
ProcessStarterActivity
Supported
Reply toJMSMessage
Type:RegularActivity
RegularActivity
Reply toJMSMessage
Type:RegularActivity
RegularActivity
Supported
Wait forJMS QueueMessage
Signal-InActivity
Wait for JMSMessage
Signal-InActivity
Notsupported
Wait forJMS TopicMessage
Signal-InActivity
Wait for JMSMessage
Signal-InActivity
Notsupported
Mail Palette
TIBCO BusinessWorks™ Container Edition 5.x: Mail Palette
Type: Palette
TIBCO BusinessWorks Container Edition : Mail Palette
Type: Palette
41
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE
BWCEType
MigrationSupport Comments
ReceiveMail
ProcessStarterActivity
Receive Mail ProcessStarterActivity
Supported
Send Mail RegularActivity
Send Mail RegularActivity
Supported TIBCO BusinessWorksContainer Editionintroduces a new SMTPshared resource. TIBCOBusinessWorksContainer Edition 5.xSend Mail activityconfiguration migratesto both Send Mailactivity and SMTPshared resource.
Parse Palette
TIBCO BusinessWorks™ Container Edition 5.x: Parse Palette
Type: Palette
TIBCO BusinessWorks Container Edition : Parse Palette
Type: Palette
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
Data Format SharedConfiguration
Data Format SharedConfiguration
Supported
Parse Data RegularActivity
Parse Data RegularActivity
Supported
Render Data RegularActivity
Render Data RegularActivity
Supported
Policy Palette
TIBCO BusinessWorks™ Container Edition 5.x: Policy Palette
Type: Palette
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
SecurityPolicyAssociation
SharedConfiguration
SecurityPolicyAssociation
SharedConfiguration
Currently notsupported
42
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
SecurityPolicy
SharedConfiguration
SecurityPolicy
SharedConfiguration
Currently notsupported
Process Palette
TIBCO BusinessWorks™ Container Edition 5.x: Process Palette
Type: Palette
TIBCO BusinessWorks Container Edition : Built-In
Type: Built-In
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
ProcessDefinition
.process Process .bwp Supported
43
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
ProcessArchive
SharedConfiguration
ApplicationProject
.application Refactorandrecreate
In ActiveMatrixBusinessWorks™ 5.x,Process Archive isconfigured within theEnterprise ArchiveResource. Thisspecifies whichprocesses in theActiveMatrixBusinessWorks™ 5.xproject are to bepackaged to form anEAR file fordeployment.
In TIBCOBusinessWorksContainer Edition , theEnterprise ArchiveResource and ProcessArchive configurationare no longersupported and theirfunctionality arereplaced byApplication andApplication Module,respectively. Anyproject artifacts thatcan be re-used bymultiple Applicationsand multipleApplication Modulesare to be created inShared Modules.
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 theApplication
44
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
Module to SharedModule.
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 TIBCOBusinessWorksContainerEdition , aProcess (say,Process A) in aShared Moduleis not activatedunless aComponent isdefined and isconfiguredwith ProcessA .
3. Repeat Step 2 forthe number ofapplicationsrequired.
REST and JSON Plug-inTIBCO BusinessWorks™ Container Edition 5.x: REST/JSON Plug-in
45
TIBCO BusinessWorks™ Container Edition Migration
Type: Plug-in
TIBCO BusinessWorks Container Edition : REST and JSON Palette
Type: Palette
Migration: Supported
BW 5.xBW 5.xType BWCE BWCE Type
MigrationSupport Comments
Invoke RESTAPI
RegularActivity
Invoke RESTAPI
RegularActivity
Supportedwithlimitations
TIBCOBusinessWorksContainerEdition 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 TIBCOBusinessWorks™ Container Edition REST Reference guide.
Parse JSON RegularActivity
Parse JSON RegularActivity
Supportedwithlimitations
TIBCOBusinessWorksContainerEdition does notsupport theschema typeJava Classes.
46
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE BWCE Type
MigrationSupport Comments
Render JSON RegularActivity
Render JSON RegularActivity
Supportedwithlimitations
The RemoveRoot check boxis not supportedin TIBCOBusinessWorksContainerEdition . Rootelements inTIBCOBusinessWorksContainerEdition areskipped bydefault. You willneed to modifythe input JSONif it containsroot element.
The schematype JavaClasses is notsupported inTIBCOBusinessWorksContainerEdition .
47
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE BWCE Type
MigrationSupport Comments
RESTDispatch andReply
RegularActivity
REST ServiceBinding
ServiceBinding
Supportedwithlimitations
This ThisActiveMatrixBusinessWorks™5.x Dispatchand ReplyREST activity ismigrated toREST ServiceBinding ofTIBCOBusinessWorksContainerEdition .
REST Service ofTIBCOBusinessWorksContainerEdition usesXSD as theresource 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, thenthe TIBCOBusinessWorksContainerEditionMigration Toolcurrently doesnot externalizethe inlineschema before
48
TIBCO BusinessWorks™ Container Edition Migration
BW 5.xBW 5.xType BWCE BWCE Type
MigrationSupport Comments
configuring theREST binding.You canmanuallyexternalize theinline schemaand re-create theREST binding.
TIBCOBusinessWorksContainerEdition alsodoes notsupport thefollowing:
● EnableWADLReference
● EnableOAuth
● Parameterstyles-Templateand Header
For more information about additional restrictions, see Restrictions on XML Schema in TIBCOBusinessWorks™ Container Edition Bindings and Palettes Reference.
RMI Palette
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
RMI Lookup RegularActivity
RMI Lookup RegularActivity
Currently notsupported
None
RMI Server ProcessStarter
RMI Server ProcessStarter
Currently notsupported
None
Service Palette
TIBCO BusinessWorks™ Container Edition 5.x: Service Palette
Type: Palette
TIBCO BusinessWorks Container Edition : Built-In
Type: Built-In
49
TIBCO BusinessWorks™ Container Edition Migration
Migration: Supported
BW 5.x BW 5.x Type BWCEBWCEType
MigrationSupport Comments
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
Process StarterActivity
Basic :Receive
ProcessStarterActivity
Supported
50
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCEBWCEType
MigrationSupport Comments
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 BusinessWorks™ Container Edition 5.x: SOAP Palette
Type: Palette
TIBCO BusinessWorks Container Edition : Basic Palette + SOAP Binding
Type: Binding
Migration: Supported
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
MIME Parser RegularActivity
Parse : MIMEParser
RegularActivity
Currently notsupported
RetrieveResources
RegularActivity
GenerateWSDLService
RegularActivity +SOAP Binding
Currently notsupported
The WSDL inTIBCOBusinessWorks ContainerEdition has tobe generatedin the TIBCOBusinessStudio™ forBusinessWorks™ on theComponentBinding.
51
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
SOAP EventSource
ProcessStarterActivity
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.
HeaderMigrationis notsupported.
SOAPRequestReply
RegularActivity
Basic : InvokeService +SOAPReferenceBinding
RegularActivity +SOAP Binding
Supportedwithlimitations.
The SOAPRequest Replyis migrated asa Process withReference anda SOAPReferenceBinding isadded for thesame. TheBinding isadded underModuleDescriptors/Components/Binding.
HeaderMigrationis notsupported.
SOAP SendFault
RegularActivity
Basic : Replywith Fault +SOAPReferenceBinding
RegularActivity +SOAP Binding
Supported
52
TIBCO BusinessWorks™ Container Edition Migration
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
SOAP SendReply
RegularActivity
BasicActivities:Reply + SOAPReferenceBinding
RegularActivity +SOAP Binding
Supported
TCP Palette
TIBCO BusinessWorks™ Container Edition 5.x: TCP Palette
Type: Palette
TIBCO BusinessWorks Container Edition : TCP Palette
Type: Palette
Migration: Supported
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
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
Not Supported
Write TCPData
RegularActivity
Write TCPData
RegularActivity
Supported
53
TIBCO BusinessWorks™ Container Edition Migration
Transaction Palette
BW 5.x BW 5.x Type BWCE BWCE TypeMigrationSupport Comments
JTA UserTransactionConfiguration
SharedResource
JTA UserTransactionConfiguration
SharedResource
Currently notsupported
XATransactionManagerConfiguration
SharedResource
XATransactionManagerConfiguration
SharedResource
Currently notsupported
TransactionState
RegularActivity
TransactionState
RegularActivity
Currently notsupported
XML Palette
TIBCO BusinessWorks™ Container Edition 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 TypeMigrationSupport Comments
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
54
TIBCO BusinessWorks™ Container Edition Migration
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 TIBCO BusinessWorksContainer Edition . The TIBCO BusinessWorks Container Edition Call Process, Start, and End activitiesare 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 TIBCO BusinessWorks Container Edition .
ActiveMatrix BusinessWorks™ 5.x TIBCO BusinessWorks Container Edition
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.
Start and End Activity Migration
The following table provides information about the Start and End activities migration fromActiveMatrix BusinessWorks™ 5.x to TIBCO BusinessWorks Container Edition .
ActiveMatrix BusinessWorks™ 5.x TIBCO BusinessWorks Container Edition
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 TIBCO BusinessWorks Container Edition , each application module has one Activator process thathas two service operations, On StartUp and On ShutDown. Any TIBCO Designer process linked withthe On Start and On ShutDown activity in ActiveMatrix BusinessWorks™ 5.x after migration issimultaneously changed to a StartUp Operation activity and On ShutDown Operation activity. Theactivator calls the start() and stop() methods to start or stop the process.
55
TIBCO BusinessWorks™ Container Edition Migration
Service and References
Service and References are defined at a process level.
ActiveMatrix BusinessWorks™ 5.x TIBCO BusinessWorks Container Edition
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 BusinessWorks™ Container Edition 5.x projects to TIBCOBusinessWorks Container Edition
You can migrate TIBCO BusinessWorks Container Edition 5.x projects to TIBCO BusinessWorksContainer Edition using the following options:
● Project > Migrate BW Projects option in TIBCO Business Studio™ for BusinessWorks™
● The command-line option
Migrating Projects Using TIBCO Business Studio™ for BusinessWorks™
TIBCO BusinessWorks™ Container Edition provides an easy way to migrate TIBCO BusinessWorksContainer Edition 5.x projects by using the Migrate BW Projects menu option in TIBCO BusinessStudio for BusinessWorks.
Prerequisites
● Perform validation and ensure that TIBCO BusinessWorks Container Edition5.x project does nothave errors.
● Optionally, schemas without namespaces should be refactored before migration.
56
TIBCO BusinessWorks™ Container Edition Migration
● 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 the folder names.
● Global variables with integer values but datatype as String must be updated to data type as Integer.Examples include timeouts, message size, and so on.
Procedure
1. In TIBCO Business Studio for BusinessWorks, choose Project > Migrate BW Projects....
2. In the Project Migration Wizard, click Migrate Single BusinessWorks 5x Project to migrate a singleTIBCO BusinessWorks Container Edition 5.x project, or click Migrate Multiple BusinessWorks 5.xProjects to migrate multiple TIBCO BusinessWorks Container Edition 5.x projects.When migrating single TIBCO BusinessWorks Container Edition 5.x projects, you can also migrateselective processes or subprocesses. Select the Select Processes for Migration check box, andprovide the required information as explained in Step 6, below. After the required information isprovided, 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. This check box can be used only to migratesingle projects.
The list of processes in the selected TIBCO BusinessWorks Container Edition 5.x project aredisplayed in the Project Migration Wizard. The processes can be viewed in the Flat Hierarchy or theTree Hierarchy structures.
3. Click Select Linked Processes to select all the subprocesses under the main process. Deselect thecheck box for the process you do not want to migrate.To view the processes that are selected for migration, click Show Linked Process Hierarchy. Thestatic and dynamic processes to be migrated are displayed.
4. While migrating selective processes, to select or unselect the already migrated existing processes,select the Re-Select Process check box provided on the Select Processes page of the MigrationWizard.
5. Click Migrate Project.
6. Specify the relevant information in the following fields.
57
TIBCO BusinessWorks™ Container Edition Migration
a) Click Browse in the Select Project(s) to be migrated field and provide the location of the TIBCOBusinessWorks Container Edition 5.x project that you want to migrate. Note: History of the lastfive migrated project paths can be retrieved by selecting CTRL+ Spacebar.
b) The Select Migrated Project Location field displays the location of the current open workspacewhere the project will be migrated. Click Browse if you want to provide a different workspace.
c) Click the Select Third Party JAR's folder field to browse for third party jars required for yourproject.
d) 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 customXPath function group plugin project is included in the application project. The classes folder cannow be found in the customXPathFunction.jar file, and is no longer available in the pluginproject. This jar file is also added to the project class path.
e) In the Select ProjectLibs (DTLs) used by Project field, click Browse to select the project librariesto be used for the project.
f) In the Select Java Libraries used by Project field, click Browse and provide the location of theJAR files on disk if the TIBCO BusinessWorks Container Edition 5.x project is using external JARfiles in context with Java activities.It is recommended you place the external JAR files in a single location. These JAR files can thenbe in-lined in the migrated TIBCO BusinessWorks Container Edition project.
7. Click Migrate Project.
8. Click Finish after the migration is complete.
58
TIBCO BusinessWorks™ Container Edition Migration
Project with Subprocess after Migration
Subprocesses in TIBCO BusinessWorks Container Edition use a standardized concept ofreceiving and replying messages through a service.
Before Migration
After Migration
The Call Process is migrated as a Direct Call Process.
59
TIBCO BusinessWorks™ Container Edition Migration
Migrating Project Using Command lineAnother 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 TIBCO BusinessWorksContainer Edition 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 can be found at, <TIBCO_HOME>\bw\6.4\config
\bw6migration_template.properties.
Examples
● bwmigrator -projectDir <BWCE_PROJECTS_HOME>\projects <TIBCO_HOME>\5.9\examples
\activities\file\File (Migrates single TIBCO BusinessWorks Container Edition 5.x project.)
● bwmigrator -projectDir <BWCE_PROJECTS_HOME>\projects <TIBCO_HOME>\5.9\examples
\activities\file\File <TIBCO_HOME>\5.9\examples\activities\ftp\ftp (Migrates File andFTP TIBCO BusinessWorks Container Edition 5.x projects.)
● bwmigrator -projectDir <BWCE_PROJECTS_HOME>\projects <TIBCO_HOME>\5.9\examples
\activities (Migrates all TIBCO BusinessWorks Container Edition 5.x projects in activitiesdirectory.)
● bwmigrator -projectDir <BWCE_PROJECTS_HOME>\projects <TIBCO_HOME>\5.9\examples
\file <TIBCO_HOME>\5.9\examples\ftp (Migrates all TIBCO BusinessWorks Container Edition5.x Projects in File and FTP directories.)
Procedure
● In the command prompt, type the following command:bwmigrator.exe -projectDir c:/temp <BW 5.x Project Path>
For Java migration type the following command: bwmigrator.exe -projectDir c:/temp -classpath <Jar Location Path> <BW 5.x Project Path>
60
TIBCO BusinessWorks™ Container Edition Migration
Command line Configuration File Template
The TIBCO BusinessWorks™ Container Edition 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 on the command prompt and execute the command which has thefollowing format as stated below:
Example: bwmigrator.exe [-data <User_Workspace>] -projectDir <BusinessWorks 6.xTarget directory> <BusinessWorks 5.x Project location> -propFile <.properties
location>
Optionally, you can also modify the path for User_Workspace. If the User_Workspace path has beenmodified, 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 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 mainprocess path will migrate all the processes that aredependent on the main process.
.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,
61
TIBCO BusinessWorks™ Container Edition Migration
Design Time Library Migration (DTL)
Property Description
sharedModule The default value of this property is false, andwill migrate the DTL as an application module.Set the property to true to create an TIBCOBusinessWorks Container Edition sharedmodule.
Mapping DTLs to Shared Modules
Property Description
dtlDir Provide the project lib folder location here.
For example, C:/Users/workspace1/folder/BW5DTLLib.projlib.
sharedModuleDirs You can provide multiple directory locationsusing 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 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, resolve these constraintsby using the Show Check and Repair and the Fix Type-Casting Errors functions.
Show Check and Repair
Procedure
1. To clear the problem markers in the migrated project, click project.bwp.
2. Click the activity in your project and click the Input tab.
3. Click the Show Check and Repair icon .The Mapper Check and Repair window displays.
62
TIBCO BusinessWorks™ Container Edition Migration
4. Perform Check and Repair, click OK and run the project.
Fix Type-Casting Errors
To fix the construct functions errors, click the Fix Type-Casting Errors icon .
If the Project > Clean option does not work to resolve problem markers, close andreopen the project.
HTTP Basic Sample
This topic describes migrating this project from TIBCO BusinessWorks™ Container Edition 5.x toTIBCO BusinessWorks Container Edition .
Prerequisites
Migrate the TIBCO BusinessWorks Container Edition 5.x project.
Procedure
1. Click the Incoming-HTTP-request (HTTP Receiver) activity and then click the General tab.
2. In the Parameter table, change the Parameter Cardinality from Required to Optional.
3. Click the Send-Request-to-Wiki-News (Send HTTP Request) activity and specify the followingthree values on Input tab.
63
TIBCO BusinessWorks™ Container Edition Migration
Input Type Values
RequestURI "/wiki/Main_Page"
Accept-Encoding "text/*, text/html, text/html;level=1"
Content-Type "text/html;charset=UTF-8"
4. Click the Send-Response-from-Wiki-News (Send HTTP Response) activity and specify the valuefor Content-Type on the Input tab as shown in the following image.
Custom XPath MigrationSome manual tasks need to be performed after custom XPath migration. These tasks impactDesigntime.
Design Time
The migrated custom XPath functions need to be provisioned into TIBCO BusinessWorks™ ContainerEdition ™ Container Edition. You can do this in the following way:
64
TIBCO BusinessWorks™ Container Edition Migration
Procedure
1. Export the custom XPath function plug-ins into the Host repository. To do this, right-click on theXPath Function Plug-in, and select Plug-in Development/Deployable Plug-ins and fragments.
2. Select Install into .host Repository and, click Finish.You are prompted to restart TIBCO Business Studio™ for BusinessWorks™ Container Edition.Restart and refresh your workspace. This results in the validation errors related to XPath functionsnot visible.
Migrating Design Time Libraries ( DTL) as Shared ModulesTIBCO BusinessWorks™ Container Edition 5.x design time library source projects can be migrated asTIBCO BusinessWorks Container Edition shared modules.
Migrating Design Time Libraries Using TIBCO Business Studio™ for BusinessWorks™
Using the TIBCO BusinessWorks Container Edition framework, you can migrate TIBCO BusinessWorksContainer Edition 5.x projects where the business process uses design time libraries to define theresources, subprocesses and so on.
You can migrate the design time libraries using the following options:
● Project > Migrate BW Projects option in TIBCO BusinessWorks Container Edition
Procedure
1. In the Project Migration Wizard, click Migrate Single BusinessWorks 5.x Project and select theMigrate 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. Click the Select Third Party JARs folder field to browse for third party jars only if your projectcontains a custom XPath.
4. Click Migrate Project.
Result
After migration, you can 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.
65
TIBCO BusinessWorks™ Container Edition Migration
After migration, do not perform refactoring operations on any of the resources like the schema,TIBCO BusinessWorks Container Edition shared resources, service definitions, and so on. Theproperties, and naming conventions of the resources must be retained as they are. Mappingissues, if any, can be corrected, and resource specific properties of the shared resources can bechanged.Limitations
● Shared module migration does not support TIBCO BusinessWorks Container Edition 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.
● Starter processes in the DTL source projects have to be manually refactored or moved to theTIBCO BusinessWorks Container Edition application module after all the dependentprojects are also migrated, as TIBCO BusinessWorks Container Edition does not supportstarter processes in shared modules.
● DTL migration does not support the Process Name Dynamic Override feature of the CallProcess activity. To use this feature, add the process name manually.
66
TIBCO BusinessWorks™ Container Edition Migration
Migrating Application Modules
TIBCO BusinessWorks Container Edition 5.x projects using design time libraries can bemigrated as application modules by linking the corresponding shared modules to the DTLlibraries.
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 will not link the DTL to the shared module.
67
TIBCO BusinessWorks™ Container Edition Migration
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.
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 BusinessWorks™ Container EditionPerformance 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 icon, and select Configure Contents.The Configure Contents window displays.
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, and click Finish.
6. Clean the project to fix broken mappings that might have occurred. To do this, 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 theseproblems. Ensure the Auto Build is turned off during this process.
68
TIBCO BusinessWorks™ Container Edition Migration
Migration Process Outline
The migration mechanism takes TIBCO BusinessWorks™ Container Edition 5.x projects and convertsthem to their equivalent in TIBCO BusinessWorks Container Edition .
The process flow in the project is migrated as is for the following:
● The activities and their associated mappings● The transitions and their associated conditions● Groups
TIBCO BusinessWorks Container Edition Project Migration
TIBCO BusinessWorks Container Edition5.x Project in TIBCO Designer
TIBCO BusinessWorks Container Edition Projectin TIBCO Business Studio™ for BusinessWorks™
Process TIBCO BusinessWorks Container Edition Process
Schema Schema
WSDL WSDL
Shared Resource TIBCO BusinessWorks Container Edition SharedResource
While migrating projects, if a project rests in a multiple folder hierarchy structure and contains WSDLs,or schemas, or both WSDLs and schemas, the folder names must be unique. If the folder names are notunique the project can run into design time issues due to incorrect namespaces and imports.
TIBCO BusinessWorks Container Edition Project Migration Diagram
The process flow in the project after the migration is shown in the following image. Activities,transitions, and their associated mappings visible in the TIBCO BusinessWorks Container Edition 5.x
69
TIBCO BusinessWorks™ Container Edition Migration
project in TIBCO Designer are displayed in TIBCO BusinessWorks Container Edition project in TIBCOBusiness Studio for BusinessWorks.
TIBCO BusinessWorks Container Edition 5.x Migrated Project - Before and After
70
TIBCO BusinessWorks™ Container Edition Migration
Frequently Asked Questions
What to do... Resolution
When migrated process shows mappingerrors? 1. Go to Menu > Project > Clean and click Clean
All Projects.
2. Go to the Activity Input with the Mapping Error.Click Show Check and Repair and fix existingerrors. Click Fix Type Casting Errors.
3. If the error still persists, check the expressionand do the necessary corrections.
When processes have unresolved WSDLreferences? 1. Close and reopen the project.
2. If this does not fix the references, then check theWSDL Interface value on the General tab of theProcess Service.
When Java Invoke activities show InputConfiguration Error after migration? 1. Go to the General tab of the Java Invoke activity
and check whether the Class Name is availablein the workspace. If available, re-select the Javaclass.
2. If the class is not available, check whether theJAR file packaging the Java class is available.Otherwise, copy the JAR file to the "lib" folderand reselect the Java class.
When activities in the Catch block showMapping errors?
The Catch Block activities does not have thevisibility to the output of the activities from themain process.
Re-map the activity input accordingly. This issimilar to the Java try or catch constructs.
When Variable not defined error forIterate Group Index variable is used outsidethe Iterate scope?
1. In TIBCO BusinessWorks™ Container Edition theIterate Group Index Variable does not have thevisibility outside the Iterate scope.
2. Define a Process Variable of Type integer andmap it to the Iterate Group Index variable. Youcan now you can use this variable in the Processscope.
71
TIBCO BusinessWorks™ Container Edition Migration
What to do... Resolution
When TIBCO BusinessWorks ContainerEdition 5.x activity migrates as Empty orRescue activity in TIBCO BusinessWorksContainer Edition ?
1. The TIBCO BusinessWorks Container Edition 5.xactivity migrates as Rescue activity, if themigration framework fails to migrate.
2. Check the TIBCO BusinessWorks ContainerEdition 5.x project and add the correspondingactivity in the TIBCO BusinessWorks ContainerEdition project and redo the mappings.
After migrating a project using thetib:concat-sequence-format() the outputreturns errors.
The function tib:concat-sequence-format() does notaccept string as return value for node set. Post-migration, replace tib:concat-sequence-format() withstring-join() function.
When a group is around the activities andthe xpath condition over the group is notsatisfied after migration, the error, ExpectedNon Repeating got repeating isdisplayed.
1. Verify the xpath condition and resolve issues ofthe group (eg: 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 and recreate thevariables and add the mappings again. In thiscase the back-end references are also removed.
2. Delete the xpath on the variables one by one andre-correct them. This also resolves the issuesometimes.
When the error Unresolved referenceschema 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 a TIBCOBusinessWorks Container Edition 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 will beresolved.
72
TIBCO BusinessWorks™ Container Edition Migration