TIB BW Migration 6.1.0

TIBCO ActiveMatrix BusinessWorks
Migration
Software Release 6.1.0
May 2014
Two-Second Advantage
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH
EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY
(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE
EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY
OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND
CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED
SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE
CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD
OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN 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 contains confidential information that is subject to U.S. and international copyright laws
and treaties. No part of this document may be reproduced in any form without the written
authorization of TIBCO Software Inc.
TIBCO, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Enterprise Message Service,
TIBCO Business Studio, TIBCO Enterprise Administrator, TIBCO ActiveSpaces, TIBCO Runtime Agent,
TIBCO Designer, and Two-Second Advantage are either registered trademarks or trademarks of TIBCO
Software Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise
Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle Corporation in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT
ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED
AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE
VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL
ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE
CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO
SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,
INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright
2001-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information
2
Migration
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Migration Process Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Migration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Migrating 5.x Projects to 6.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Migrating Projects Using TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Migrating Projects Using Command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Post-Migration Manual Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
HTTP Persistent Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
HTTP Basic Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
JMS Message Selector Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
JAVA Method Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Mail With Simple Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3
Migration
Figures
TIBCO ActiveMatrix BusinessWorks Project Migration Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
ActiveMatrix BusinessWorks 5.x Migrated Project - Before and After . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4
Migration
TIBCO Documentation and Support Services
All TIBCO documentation is available in the TIBCO Documentation Library, which can be found here:
https://docs.tibco.com
Product-Specific Documentation
The following documents for TIBCO ActiveMatrix BusinessWorks can be found in the TIBCO
Documentation Library:
Concepts
Installation
Getting Started
Application Development
Administration
Bindings and Palettes Reference
Samples
Migration
The following documents provide additional information and can found be in the TIBCO
Documentation Library:
TIBCO Enterprise Administrator User's Guide

How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, contact TIBCO Support as
follows:
For an overview of TIBCO Support, and information about getting started with TIBCO Support,
visit this site:
http://www.tibco.com/services/support
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user name, you can
request one.
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a
place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers
forums, blogs, and access to a variety of resources. To register, go to:
http://www.tibcommunity.com
5
Migration
Introduction
This Migration Guide provides guidance and assistance to migrate the TIBCO ActiveMatrix
BusinessWorks 5.x projects to TIBCO ActiveMatrix BusinessWorks 6.x. "Migration" also refers to the
basic differences in both these ActiveMatrix BusinessWorks versions, projects post-migration, and the
limitations of the migration process.
Intended Audience
This guide is intended for anyone involved in migrating an existing ActiveMatrix BusinessWorks 5.x
TIBCO Designer based project to ActiveMatrix BusinessWorks 6.x in TIBCO Business Studio, using the
Eclipse Modeling Framework.
Prerequisite
You must be familiar with TIBCO ActiveMatrix BusinessWorks 5.x concepts, and with TIBCO
ActiveMatrix BusinessWorks in particular. In addition, introductory knowledge of creating and
running the TIBCO ActiveMatrix BusinessWorks samples is required. For a project migration to be
successful, you should have a detailed understanding of the current ActiveMatrix BusinessWorks
Eclipse design-time tooling, including working knowledge of ActiveMatrix BusinessWorks 5.x projects
in TIBCO Designer.
Migration Process Outline
The Migration mechanism takes ActiveMatrix BusinessWorks 5.x projects and coverts then to their
equivalent in ActiveMatrix BusinessWorks 6.x.
The process flow in the project is migrated as is, for example:
The activities and their associated mappings
The transitions and their associated conditions, and
Groups
TIBCO ActiveMatrix BusinessWorks Project Migration
In ActiveMatrix BusinessWorks 5.x
Project in TIBCO Designer
In ActiveMatrix BusinessWorks 6.x Project in TIBCO
Business Studio
Process ActiveMatrix BusinessWorks 6.x Process
Schema Schema
WSDL WSDL
Shared Resource ActiveMatrix BusinessWorks 6.x Shared Resource
TIBCO ActiveMatrix BusinessWorks Project Migration Diagram

6
Migration

The process flow in the project after the migration is shown in the following image. Activities,
transitions, and their associated mappings visible in the ActiveMatrix BusinessWorks 5.x project in
TIBCO Designer are displayed in ActiveMatrix BusinessWorks 6.x project in TIBCO Business Studio.
ActiveMatrix BusinessWorks 5.x Migrated Project - Before and After
7
Migration
Migration Scenario
The migration scenarios show the core construct migration of TIBCO ActiveMatrix BusinessWorks 5.x
projects. After migration, these projects get converted to their equivalent in the TIBCO ActiveMatrix
BusinessWorks 6.x. There are notable changes in Call Process, Signal-in, and Start and End activities in
TIBCO ActiveMatrix BusinessWorks 6.x. that differ from the TIBCO 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 ActiveMatrix BusinessWorks 6.x.
TIBCO ActiveMatrix BusinessWorks 5.x TIBCO ActiveMatrix BusinessWorks 6.x
Call Process is literal. It calls a process with
process pipeline data mapped into it and
generates an output that is in essence the
output of the called process.
Call Process mechanism is based on the standard
Invoke activity. It abstracts out the actual Call
Process configuration to the reference that the
Invoke activity is calling.
After Migration: Call Process activity converts to an
Invoke activity which calls a reference that holds
the Call Process activity configuration.
Signal-in Activity Migration
The following table provides information about the Signal-in activity migration from ActiveMatrix
BusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x.
8
Migration
Signal-In activities join an existing job by
comparing the key generated by mapping
process pipeline data to the key field of the
signal-in activity. The value is matched with
the value that is generated for the candidate
event key field of the signal-in activity by
mapping the signal-in output data.
Conversations, a new mechanism, is introduced to
join an existing process instance, which is based on a
correlation mechanism. It applies to all the activities
receiving a message after the process instance is
created.
A process instance can initialize a conversation
using an activity by initializing a conversation key
with the values mapped from the process pipeline
data. If the join activity generates a conversation key
value by evaluating the expression against the
message data, that matches the value of the
initialized conversation key, a message can join the
conversation.
Input key mapping migrates as Conversation

Initiate
Candidate Event Key migrates as Conversation

Join.
After Migration: Signal-in activity is migrated to an
Activematrix BusinessWorks 6.x equivalent Signal-
in activity with a dummy conversation with Initiate
and Join as "true". This mechanism initiates the
conversation based on the process data mapped to a
key and matches it with a value that is generated by
mapping the activity output data.
Start and End Activity Migration
The following table provides information about the Start and End activities migration from
ActiveMatrix BusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x.
9
Migration
The Start activity is a receiver that starts a
process on receiving a message that may be
empty. The End activity is in essence an
activity that sends an reply.
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.
The Start activity is changed to a Receive activity
and the End activity is changed to Reply activity.
After Migration:
The Start activity converts to a Receive activity.

The input is wrapped inside a WSDL message
that listens on a generated port type which acts
as the interface for the process.
The End activity converts to a Reply activity.

The output is wrapped inside a WSDL message
that listens on a generated port type that acts as
the interface for the process.
If the ActiveMatrix BusinessWorks 5.x
process had an Event Source activity
instead of a Start activity, then the End
activity gets migrated to an Empty
activity.
Activator
In TIBCO ActiveMatrix BusinessWorks 6.x, each application module has one Activator process that
comprises two service operations: On StartUp and On ShutDown. Any TIBCO Designer process
linked with the On Start and On ShutDown activity in TIBCO ActiveMatrix BusinessWorks 5.x after
migration is changed simultaneously to a StartUp Operation and On ShutDown Operation. 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.
10
Migration
SOAP services are used for exchanging
information in the implementation of web
services relying on XML message format sent
over HTTP and JMS.
Along with HTTP and JMS, includes REST
compliant services, where the primary purpose of
the service is to manipulate XML representations of
web resources using a uniform set of stateless
operations. When using a stateless operation, the
state is managed by the job itself instead of by the
engine.
Migrating 5.x Projects to 6.x
You can migrate the ActiveMatrix BusinessWorks 5.x projects to ActiveMatrix BusinessWorks 6.x using
the following options:
Project > Migrate BW Projects... option in TIBCO Business Studio.
The command-line option.

Migrating Projects Using TIBCO Business Studio
TIBCO ActiveMatrix BusinessWorks 6.x provides an easy way to migrate TIBCO ActiveMatrix
BusinessWorks 5.x projects by using the Migrate BW Projects menu option in TIBCO Business Studio.
You can also use the Eclipse import mechanism to migrate the projects.
Procedure
1. In TIBCO Business Studio, go to Project > Migrate BW Projects....

11
Migration
2. In the BusinessWorks Migration Tool wizard, specify the relevant information in the following
fields.
a) Click Browse in the BusinessWorks 5 Project Folder field and provide the location of the
ActiveMatrix BusinessWorks 5.x project that you want to migrate. The tool scans the
ActiveMatrix BusinessWorks 5.x projects in the specified folder location and displays the list of
projects.
b) In the Migrated Project Folder field, click Browse and provide the location where you want to
migrate the project.
c) Select the Add External JARs check box if the ActiveMatrix BusinessWorks 5.x project is using
external JAR files in context with Java activities.
It is a best practice to place the external JAR files in a single location. These JAR files can then be
in-lined in the migrated ActiveMatrix BusinessWorks 6.x project.
d) Click Browse in the Jar Location field and provide the location of the JAR files on disk.
3. In the BusinessWorks 5 Projects area, select the projects you want to migrate and click Migrate.
The migrated projects are visible in the Migration Output area.
4. Click Close after the migration is complete.
You can alternatively migrate the projects using the File > Import menu option. Select
Migrate BW Projects... > Next in the Import dialog.
12
Migration
Project with Subprocess after Migration
Subprocess in BusinessWorks 6.x uses standardized concept of receiving and reply messages
via a service.
Before Migration

After Migration
You will see the Subprocess moves to a chevron.

Migrating Projects Using Command line
Another option for a speedy migration is migrating the projects using the command-line.
Usage: bwmigrator [-options] BW5Project...
13
Migration
where options include:
-projectDir Location where ActiveMatrix BusinessWorks 6.x projects are to be generated.
BW5Project..
.
Location\locations of ActiveMatrix BusinessWorks 5.x projects.
Examples
bwmigrator -projectDir <BW6_PROJECTS_HOME>\projects <TIBCO_HOME>\5.9\examples
\activities\file\File (Migrates single ActiveMatrix BusinessWorks 5.x project.)
\activities\file\File <TIBCO_HOME>\5.9\examples\activities\ftp\ftp(Migrates File and FTP
ActiveMatrix BusinessWorks 5.x projects.)
\activities(Migrates all ActiveMatrix BusinessWorks 5.x projects in activities directory.)
bwmigrator -projectDir <BW6_PROJECTS_HOME>\projects <TIBCO_HOME>\5.9\examples\file
<TIBCO_HOME>\5.9\examples\ftp (Migrates all ActiveMatrix BusinessWorks 5.x Projects in File and
FTP directories.)
Procedure
In the command prompt, type the following:
bwmigrator.exe -projectDir c:/temp <BW 5.x Project Path>
For Java migration: bwmigrator.exe -projectDir c:/temp -classpath <Jar
Location Path> <BW 5.x Project Path>
Post-Migration Manual Tasks
It is possible that you may encounter problem markers that relate to activity input mapping especially
XPath constructor function errors due to mapping elements of different types in your project post
migration. You can resolve these constraints by using the Show Check and Repair and Fix Type-
Casting Errors functions.
Show Check and Repair
Procedure
1. To clear the problem markers in the migrated project, click the project.bwp.
2. Click the activity in your project and click the Input tab.
14
Migration
3. Click the Show Check and Repair icon .
The Mapper Check and Repair window displays.

This option is applicable to the following:
JAVA Method Project
Mail With Simple Attachment
simple_attachment
4. Do 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 and
reopen the project..
HTTP Persistent Connection
Migrating this project from TIBCO ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix
BusinessWorks 6.x involves certain manual steps to be performed. This topic provides information
about the manual steps involved for a successful migration.
Prerequisites
Migrate the TIBCO ActiveMatrix BusinessWorks 5.x project.
Procedure
1. In the HTTP Client shared resource, Client.ClientProcess-Send-HTTP-Request-
HttpClientResource, provide the specified details in the following fields.
Field Value
Maximum Total Connections 3
Maximum Total Connections Per Host 2
Connection Timeout (ms) 20000
2. Provide same HTTP Client shared resource Client.ClientProcess-Send-HTTP-Request-
HttpClientResource to the following activities in the process, ClientProcess.bwp.
a) Send-HTTP-Request-1
b) Send-HTTP-Request-1-1
c) Send-HTTP-Request-1-2
d) Send-HTTP-Request-1-3
15
Migration
HTTP Basic Sample
Prerequisites
Procedure
1. Click on the activity Incoming-HTTP-request (HTTP Receiver) and click General tab.
2. In the Parameter table change the Parameter Cardinality from Required to Optional.

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

Input Type Values
RequestURI "/wiki/Main_Page"
Accept-Encoding "text/*, text/html, text/html;level=1"
Content-Type "text/html;charset=UTF-8"
16
Migration
4. Click on the activity Send-Response-from-Wiki-News (Send HTTP Response) and specify the
value for Content-Type on the Input tab as shown in the following image.

JMS Message Selector Project
Prerequisites
Procedure
1. Open QueueMessageSelector.bwp, click on JMS-Queue-Sender activity and click the Advanced
tab.
17
Migration
2. For the Application Properties Type, open the Select Schema Type Definition wizard and select
JMSApplicationProperties.

3. Delete the Body element from Input tab in the JMS Queue Sender activity as 2 body elements will
be generated after migration.

4. Provide value in the Body element.
5. Do Check and Repair to remove all the problem markers.
6. Run the process.
18
Migration
JAVA Method Project
Prerequisites
Procedure
1. Go to PublishBalance.bwp and do Check and Repair for the InvalidAcctExp and
PublishException activities.
2. In the Mapper Check and Repair wizard, check for jmexample.InvalidAccountException.

3. Run the sample.
Mail With Simple Attachment
Prerequisites
19
Migration
Procedure
1. After migrating the project, select theSender.bwp process, click on Send-Mail activity and do
Check and Repair.

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

20
Migration

TIB BW Migration 6.1.0

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TIB BW Migration 6.1.0

Hochgeladen von

Copyright:

Verfügbare Formate

TIBCO ActiveMatrix BusinessWorks

2001-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.

Bindings and Palettes Reference

TIBCO Enterprise Administrator User's Guide

The activities and their associated mappings

The transitions and their associated conditions, and

Input key mapping migrates as Conversation

Candidate Event Key migrates as Conversation

The Start activity converts to a Receive activity.

The End activity converts to a Reply activity.

Project > Migrate BW Projects... option in TIBCO Business Studio.

The command-line option.

Das könnte Ihnen auch gefallen