• mstore – new message store type, which designed for quick EMS recover after failover;
• new parameters for incoming message size, swapping and redelivery delay;
• cursoring through topics and queues lists in tibemsadmin tool;
• new startup script to quickly start with default configuration;
• host id and message size now included in message tracing;
• new methods in APIs for failover notification and message recovery.

This release requires database schema update when migrating database store from EMS version 5.x.

• Spotfire 3.1
• BusinessEvents 4.0, with an improved Eclipse-based development environment including a rule debugger, and a multi-threaded engine
• BEViews (BusinessEvents Views) for creating real-time customizable dashboards for monitoring the high-speed events (as opposed to Spotfire, which can include data from a much broader context)
• ActiveSpaces Suite for in-memory processing, grid computing and events, with the new AS Transactions and AS Patterns components
• Silver Suite for cloud deployment, including Fabric, Grid and CAP (Composite Application Platform)
• PeopleForms, which I saw a brief view of yesterday: a lightweight, forms-based application development environment
• tibbr, their social microblogging platform; I think that they’re pushing too much of the social aspect here, when I think that their sweet spot is in being able to “follow” and receive messages/events from devices rather than people
• Silver Analytics
• ActiveMatrix 3.0, which is an expansion of the lightweight application development platform to make this more of an enterprise-ready
• ActiveMatrix BPM, which he called “the next generation of BPM within TIBCO” – I’ll have more on this after an in-depth briefing
• Silver BPM, the cloud-deployable version of BPM
• Design Collaborator, which is a web-based design discovery tool that will be available in 2011: this appears to be their version of an online process discovery tool, although with more of a services focus than just processes; seems late to be introducing this functionality to the market

Here the list of my info sources for this great event:

• TUCON LIVE
• Press Releases
• Column 2
• #tucon on Twitter
• Google Alerts

There was a hope to try tibbr, but this thing for TUCON attendees only :(

Can not create/access pager directory [d:\tibco\tra\domain\tibcolb-inttra-com\application\TRCAdapter\working\tibcolb-inttra-com.tibcolb-inttra-com-TRCAdapter.TRC Adapter Processes2Epar\pager.TRCAdapter-TRC_Adapter_Processes-1\TRCAdapter\CoreObjects\SecuritiesTrade\Resubmit SecuritiesTrade.process]

As you can see, domain name and application name are repeated several times in the working folder path and definitely affect the length, which can exceed the file system limit. So, choose the names in TIBCO as short as possible.

message={_data_=[521 opaque bytes]}

I know that TIBCO Support experts have some tools to display and save these Rendezvous opaque bytes of AE messages, but my quick solution was to create small BusinessWorks process, which will do capture and store job. There are two activities: Rendezvous Subscriber and Write File. Rendezvous Subscriber will listen appropriate subject and has only one output complex element to represent message body. Write File has “write as binary” option and Rendezvous Subscriber’s output body is input for a file binary content. There is a formula error, but in this case it can be ignored. File name will form from Process ID to save each message in a separate file.

When this process are running, binary files will appear in the specified folder. One file per message. You can open it in your favorite binary editor/viewer and have fun!

The versions of Hawk and TRA being used are listed below,
Hawk – 4.5.1
TRA – 5.2.0.

Any suggestions greatly appreciated.

• Prepare credentials file using obfuscate utility:
  > vi cred.txt
user=admin
pw=#!tibco

  > ./obfuscate cred.txt

  > cat cred.txt
user=admin
pw=#!L3myZM9vfgr/3GAEybDLLRzX9kcdAJxZ

• Use AppManage to stop a deployed application:
  > ./AppManage -stop -app <application> -domain <domain> -cred cred.txt
• Use AppManage to start a deployed application:
  > ./AppManage -start -app <application> -domain <domain> -cred cred.txt

<application> is “Application” in TIBCO Administrator, not “Service Instance”

The user, defined in the cred.txt file, mush have appropriate rights to start and stop an application. You can operate as “admin”, or better to define new user in TIBCO Administrator with write access rights.

Also possible to redirect the stdout and stderr output to any file. Please set in deployed cmd:
"/<install-path>/tibco/bw/<version>/bin/bwengine.exe" --run --propFile "/<install-path>/tibco/tra/domain/application/<application>.tra" > "/tmp/trace.out" 2>&1
then start this cmd from command shell.

You can also enable higher tracing to Hawk, set -tsm_tracelevel -1 in your <install-path>\tibco\tra\domain\<domain-name>\hawkagent.cfg and restart your Hawk Agent. The logs will be under <install-path>\tibco\tra\domain\<domain-name>\logs\tsm.log by default, you can define it using -tsm_traceLogFile parameter.