Archive for the ·


· Category...

TIBCO Product Stack and New Releases

no comments

I decided to repost here full list from this article. Sandy, thank you!

  • 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

TUCON 2010

no comments

Unfortunately, I have not had the opportunity to visit TUCON this year. Thanks to the Internet, which allows me to monitor events in real time, although this is difficult because of the time difference between Moscow and Las Vegas.

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

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

TIBCO job trends


The picture on the right is one of the many charts from the site. On the other graphs there we can see the requirement for specific experience and knowledge, but salary comparison chart speaks volumes :)
Anyway, I suppose that can be useful if you are looking for IT job or just estimate for example TIBCO direction as one of the career development ways.

Long names could become a big issue

no comments

When you choose a name for TIBCO domain or BusinessWorks application, please keep in mind that long names could become a big issue. In the future, you may encounter such a problem like this (it was on Windows 2003 NTFS disk):

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.

Saving the contents of TIBCO Rendezvous binary messages

1 comment

Once a situation may arise when there is need to view or save the contents of TIBCO Rendezvous Active Enterprise binary messages. If you just get them using tibrvlisten, then messages appear like this:

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!

HMA startup issue on AIX – Hawk 4.5.1


I have encountered an error on AIX box, related to start up of hma. When the box is re-started, there is a script that runs to start hawk agent and the agent then should bring up hma automatically.
What is observed is that, when the box is restarted, agent comes up correctly but the hma does not. After I kill the agent and run the same script again, it starts both agent and hma correctly, i.e. agent starts hma automatically.
Script does nothing more than running the hawkagent_domain command.

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

Any suggestions greatly appreciated.

How to use AppManage utility to stop and start BW applications


AppManage utility can be used to create a BusinessWorks application using EAR file, export and import deployment configuration, deploy, undeploy, start, stop, delete an application. It can operate in batch mode. You can run AppManage utility on any machine in the TIBCO Domain. It is placed in /<tibco_home>/tra/<version>/bin/ folder. Log file will be in the domain log folder. I will show the most simple use of AppManage utility for stop and start one BW application. This can be used for scheduled restart, for example.

  • Prepare credentials file using obfuscate utility:
    > vi cred.txt

    > ./obfuscate cred.txt

    > cat cred.txt

  • 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.