tib bw migration 6.1.0

8/12/2019 TIB BW Migration 6.1.0

http://slidepdf.com/reader/full/tib-bw-migration-610 1/20

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 SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

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

This document contains confidential information that is subject to U.S. and international copyright laws

and treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

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

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

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

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

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

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)

AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

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

TIBCO Software Inc. Confidential Information

2




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




Figures

TIBCO ActiveMatrix BusinessWorks Project Migration Diagram .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . 6

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

4




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 TIBCODocumentation 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 TIBCODocumentation 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 asfollows:

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

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

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

https://support.tibco.com

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

How to Join TIBCOmmunity

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

http://www.tibcommunity.com

5


http://www.tibcommunity.com/

http://www.tibcommunity.com/

https://support.tibco.com/

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

https://docs.tibco.com/



Introduction

This Migration Guide provides guidance and assistance to migrate the TIBCO ActiveMatrixBusinessWorks 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 thelimitations of the migration process.

Intended Audience

This guide is intended for anyone involved in migrating an existing ActiveMatrix BusinessWorks 5.xTIBCO Designer based project to ActiveMatrix BusinessWorks 6.x in TIBCO Business Studio, using theEclipse Modeling Framework.

Prerequisite

You must be familiar with TIBCO ActiveMatrix BusinessWorks 5.x concepts, and with TIBCOActiveMatrix BusinessWorks in particular. In addition, introductory knowledge of creating andrunning the TIBCO ActiveMatrix BusinessWorks samples is required. For a project migration to besuccessful, you should have a detailed understanding of the current ActiveMatrix BusinessWorks

Eclipse design-time tooling, including working knowledge of ActiveMatrix BusinessWorks 5.x projectsin TIBCO Designer.

Migration Process Outline

The Migration mechanism takes ActiveMatrix BusinessWorks 5.x projects and coverts then to theirequivalent 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.xProject in TIBCO Designer

In ActiveMatrix BusinessWorks 6.x Project in TIBCOBusiness 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




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

ActiveMatrix BusinessWorks 5.x Migrated Project - Before and After

7




Migration Scenario

The migration scenarios show the core construct migration of TIBCO ActiveMatrix BusinessWorks 5.xprojects. After migration, these projects get converted to their equivalent in the TIBCO ActiveMatrixBusinessWorks 6.x. There are notable changes in Call Process, Signal-in, and Start and End activities inTIBCO 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 ActiveMatrixBusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x.

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

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

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

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

Signal-in Activity Migration

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

8





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

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

The End activity is the last activity in aprocess definition.

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

After Migration:

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

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

If the ActiveMatrix BusinessWorks 5.xprocess had an Event Source activityinstead of a Start activity, then the End

activity gets migrated to an Emptyactivity.

Activator

In TIBCO ActiveMatrix BusinessWorks 6.x, each application module has one Activator process thatcomprises two service operations: On StartUp and On ShutDown. Any TIBCO Designer processlinked with the On Start and On ShutDown activity in TIBCO ActiveMatrix BusinessWorks 5.x aftermigration is changed simultaneously to a StartUp Operation and On ShutDown Operation. Theactivator calls the start() and stop() methods to start or stop the process.

Service and References

Service and References are defined at a process level.

10





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

Along with HTTP and JMS, includes RESTcompliant services, where the primary purpose ofthe service is to manipulate XML representations ofweb resources using a uniform set of statelessoperations. When using a stateless operation, thestate is managed by the job itself instead of by theengine.

Migrating 5.x Projects to 6.x

You can migrate the ActiveMatrix BusinessWorks 5.x projects to ActiveMatrix BusinessWorks 6.x usingthe following options:

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

● The command-line option.

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

Procedure

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

11




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

a) Click Browse in the BusinessWorks 5 Project Folder field and provide the location of theActiveMatrix BusinessWorks 5.x project that you want to migrate. The tool scans theActiveMatrix BusinessWorks 5.x projects in the specified folder location and displays the list ofprojects.

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

c) Select the Add External JARs check box if the ActiveMatrix BusinessWorks 5.x project is usingexternal JAR files in context with Java activities.

It is a best practice to place the external JAR files in a single location. These JAR files can then bein-lined in the migrated ActiveMatrix BusinessWorks 6.x project.

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

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

4. Click Close after the migration is complete.

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

12




Project with Subprocess after Migration

Subprocess in BusinessWorks 6.x uses standardized concept of receiving and reply messagesvia a service.

Before Migration

After Migration

You will see the Subprocess moves to a chevron.

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

Usage: bwmigrator [-options] BW5Project...

13




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 andFTP 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 TasksIt is possible that you may encounter problem markers that relate to activity input mapping especiallyXPath constructor function errors due to mapping elements of different types in your project postmigration. 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




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 andreopen 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 informationabout 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




HTTP Basic Sample

Migrating this project from TIBCO ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrixBusinessWorks 6.x involves certain manual steps to be performed. This topic provides informationabout the manual steps involved for a successful migration.

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 following3 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




4. Click on the activity Send-Response-from-Wiki-News (Send HTTP Response) and specify thevalue 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 Advancedtab.

17




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

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




JAVA Method Project


Prerequisites


Procedure

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

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

3. Run the sample.

Mail With Simple Attachment


Prerequisites


19




Procedure

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

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

20

tib bw migration 6.1.0

Documents