Migration Scenario

The migration scenarios show the core construct migration of ActiveMatrix BusinessWorks 5.x projects. After migration, these projects are converted to their equivalent in ActiveMatrix BusinessWorks™ 6.x. The ActiveMatrix BusinessWorks 6.x Call Process, Signal-in, Start, and End activities are notably different from the activities in ActiveMatrix BusinessWorks 5.x.

Call Process Activity Migration

The following table provides information about the Call Process activity migration from ActiveMatrix BusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x.

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

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.

ActiveMatrix BusinessWorks 5.x	ActiveMatrix BusinessWorks 6.x
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 generated for the candidate event key field of the signal-in activity by mapping the signal-in output data.	Conversations 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, which 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.

ActiveMatrix BusinessWorks 5.x

ActiveMatrix BusinessWorks 6.x

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 generated for the candidate event key field of the signal-in activity by mapping the signal-in output data.

Conversations 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, which 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.

ActiveMatrix BusinessWorks 5.x	ActiveMatrix BusinessWorks 6.x
The Start activity is a receiver that starts a process on receiving a message that may be empty. The End activity sends a 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 and End activity are now supported.

ActiveMatrix BusinessWorks 5.x

ActiveMatrix BusinessWorks 6.x

The Start activity is a receiver that starts a process on receiving a message that may be empty. The End activity sends a 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 and End activity are now supported.

Activator

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

Service and References

Service and References are defined at a process level.

ActiveMatrix BusinessWorks 5.x	ActiveMatrix BusinessWorks 6.x
SOAP services are used for exchanging information in the implementation of web services relying on XML message format sent over HTTP and JMS.	Includes REST compliant services along with HTTP and JMS, where the 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.

Contents