Chapter 2 Project Design Tutorial : Configure an ActiveMatrix BusinessWorks Process for Testing

Configure an ActiveMatrix BusinessWorks Process for Testing
Learning Points
You will use the ActiveMatrix BusinessWorks process you configure here to send Rendezvous messages that trigger the fraud detection rule behavior, when conditions are met.
BusinessEvents customers can download and install ActiveMatrix BusinessWorks for use at design-time. If you want to use ActiveMatrix BusinessWorks at runtime, you must purchase the fully licensed product.
Integration projects  Projects that include BusinessEvents functionality can also include functionality provided by other TIBCO products, resulting in rich interactions with other enterprise software. Integration with ActiveMatrix BusinessWorks is documented in Chapter 11, Out-of-Process ActiveMatrix BusinessWorks Integration and Chapter 12, In-Process ActiveMatrix BusinessWorks Integration in TIBCO BusinessEvents User’s Guide.
What is the Send Event activity?  The Send Event activity sends messages formatted so that BusinessEvents can transform the received message into an event of the type you select in the activity. You can only use this activity in BusinessEvents projects that include the type of event that you want to send.
Task L Configure a ActiveMatrix BusinessWorks Process for Testing
For more information about configuring ActiveMatrix BusinessWorks processes, see TIBCO BusinessWorks Process Design Guide.
1.
2.
Open the TestProcess folder. Right-click in the design panel, and select Add Resource > Process > Process Definition. Name the process DebitAccount and click Apply.
3.
In the design panel, double-click the DebitAccount process to open it.
You see Start and End icons.
4.
From the BusinessEvents Activities palette, add a Send Event resource to the design panel and drop it between the Start and End activity icons. Name the Send Event resource Send Debit Instruction.
5.
a.
Click the Create Transition icon () on the TIBCO Designer toolbar.
b.
Position the cursor over the Start activity and drag the mouse to the Send Event activity. You see a dotted arrow connecting the two activities.
c.
Similarly, position the cursor over the Send Event activity and drag the mouse to the End activity. When focus leaves the dotted arrows they become solid arrows.
d.
Click the Pointer Tool icon () on the TIBCO Designer toolbar.
6.
Click the Start activity and define a simple output schema:
a.
Select the Output Editor tab, click the add () button to add an element, and name the element Transaction.
b.
With the Transaction element selected, click the add button two more times. Two parameters are added to the Transaction element.
c.
Select each parameter in turn and configure it. Define the parameters as AccountId, of type String, and Amount, of type decimal. Click Apply.
The display now looks like the following (showing Amount as an example):
7.
In the design panel, click the Send Debit Instruction activity. In the Event Reference field, click the browse button () and select the Debit event type. Click Apply.
Earlier, you set DebitTransaction as the default destination for the Debit event. Because of this connection, the Send Event activity can send messages to that destination without additional configuration. When the messages arrive, BusinessEvents will transform them into Debit events.
8.
a.
b.
In the Process Data panel, fully expand the $Start variable and in the Activity Input panel, fully expand the BESendEventInput elements.
c.
Drag the cursor from AccountId in the Process Data panel to AccountId in the Activity Input panel. You see a connecting line.
d.
In the same way, connect the Amount parameter in the Process Data panel to the Amount parameter in the Activity Input panel.
e.
In the Activity Input panel, to the right of the TransactionType parameter name, type "debit" (including the quotes). You see a short connecting line within the panel beginning with a dot, indicating that the value is set within the activity and is not mapped.
f.
Click Apply and save the project.
The completed configuration looks like the following:
Summary and Next Steps
You’ve created a simple mechanism for sending test data into the running engine. Next you will deploy the project.