Summary: This document provides information about the extension that provides TIBCO support.
Please see TIBCO 1.2 - Release Notes for more information.
This extension provides support for TIBCO BusinessWorks and ActiveMatrix BusinessWorks applications.
In what situation should you install this extension?
If your application contains TIBCO source code and you want to view these object types and their links with other objects, then you should install this extension.
This version of the extension provides partial support for:
|TIBCO BusinessWorks||5.1 - 5.13|
|TIBCO ActiveMatrix||6.0 - 6.2|
Function Point, Quality and Sizing support
- Function Points (transactions): a green tick indicates that OMG Function Point counting and Transaction Risk Index are supported
- Quality and Sizing: a green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist
|Quality and Sizing|
CAST AIP compatibility
CAST AIP release
Supported DBMS servers
This extension is compatible with the following DBMS servers:
|Microsoft SQL Server|
|An installation of any compatible release of CAST AIP (see table above)|
Download and installation instructions
The latest release status of this extension can be seen when downloading it from the CAST Extend server.
CAST Transaction Configuration Center (TCC) configuration
A set of TIBCO Transaction Entry Points for use in the CAST Transaction Configuration Center is delivered in the extension via a .TCCSetup file. Therefore If you are using TIBCO ≥ 1.2.x:
- with CAST AIP ≥ 8.3.x, there is nothing for you to do: these entry / end points will be automatically imported during the extension installation and will be available in the CAST Transaction Configuration Center under "Entry Points > Free Definition".
- with CAST AIP ≤ 8.2.x, you can manually import the file %PROGRAMDATA%\CAST\CAST\Extensions\com.castsoftware.tibco.<version>\Configuration\TCC\Base_Tibco.TCCSetup to obtain your entrypoints in the "Free Definition" section (see instructions below).
Manual import action for CAST AIP ≤ 8.2.x
Locate the .TCCSetup file in the extension folder: %PROGRAMDATA%\CAST\CAST\Extensions\com.castsoftware.tibco.<version>\Configuration\TCC\Base_Tibco.TCCSetup
In the CAST Transaction Configuration Center, ensure you have selected the Templates node:
This .TCCSetup file is to be imported into the CAST Transaction Calibration Center using either the:
File > Import Configuration menu option:
- Or right clicking on the Template node and selecting Import Configuration:
- The import of the Base_Tibco.TCCSetup file will provide you with a sample Transaction Entry point in the Free Definition node under Templates.
- Now right click the "Standard Entry Point" item and select copy:
- Paste the item into the equivalent node under the Application, for example, below we have copied it into the Application MEUDON:
- Repeat for any additional items or generic sets that have been imported from the .TCCSetup file.
Prepare and deliver the source code
Once the extension is downloaded and installed, you can now package your source code and run an analysis. The process of preparing and delivering your source code is described below:
Source code preparation
Only files with following extensions will be analyzed:
|TIBCO BusinessWorks 5||TIBCO ActiveMatrix BusinessWorks 6|
TIBCO BusinessWorks 5.x
TIBCO BusinessWorks 5.x applications contain two types of source code:
- standard TIBCO source code
- embedded Java source code (i.e. .process files)
The TIBCO extension has been designed so that the CAST Delivery Manager Tool (DMT) and the CAST Management Studio (CMS) can handle both types of source code:
|Source code type||DMT - option to use||CMS - Analyzer that will be used|
|TIBCO||Files on your system option||Universal Analyzer|
|Java||TIBCO Library extractor option||JEE Analyzer|
The TIBCO code source needs to preprocessed so that CAST can understand it and analyze it correctly. The code preprocessing is actioned automatically when an analysis is launched or a snapshot is generated (the code is preprocessed before the analysis starts).
Only .process and .aeschema files need to be preprocessed. The CAST Management Studio will use the LISA folder to analyse the preprocessed files (see CAST Management Studio help for more information about this folder). The remaining files will be analyzed direct from the CAST Management Studio "Deploy" folder.
TIBCO ActiveMatrix BusinessWorks 6
TIBCO ActiveMatrix BusinessWorks 6 source files are parsed with the SDK and do not need any preprocessing, therefore there is no longer any need to specifically extract Java code using the CAST Delivery Manager Tool. This is because in BusinessWorks 6.x, Java code is now created externally in the "src" folder of the AppModule and is then referred to by the Java Invoke Activity when the MultiOutput check box is selected. In BusinessWorks 5.x the source code for the Java Code activity is embedded in the ActiveMatrix and therefore requires specific extraction and preprocessing.
Deliver the source code
For a TIBCO application, you need to create package(s) in the CAST Delivery Manager Tool according to the source code you have:
Embedded Java Source code for TIBCO BusinessWorks 5.x only
Using the CAST Delivery Manager Tool:
- create a new Version
- create a new Package for your TIBCO source code using the TIBCO option and choose the location of your source code:
- Run the Package action. The packaging of this package will generate a Java project that will be analyzed later with the JEE analyzer - note that if your selected TIBCO source code contains no embedded Java, then no projects will be detected by the CAST Delivery Manager Tool and there is no need to deliver the package for analysis):
- Before delivering the source code, check the packaging results
Standard TIBCO source code (TIBCO BusinessWorks 5.x and TIBCO ActiveMatrix BusinessWorks 6.x)
Using the CAST Delivery Manager Tool:
- create a new Package (using the Files on your file system option) in your existing Version (if you have already packaged Embedded Java Source code), or create a new Version and Package (using the Files on your file system option) if you have not already created a Version.
- Run the Package action. The packaging of this package will generate a TIBCO UA project:
- Before delivering the source code, check the packaging results.
Analysis configuration and execution
Refer to Analysis Configuration and Execution for more information.
What results can you expect?
For any TIBCO Process, Start and End activity will have special icons and will be used for Start and End points of the transaction.
For Processes including Groups such as as the following:
The analysis result will look like this:
Access to database objects will be resolved with typed links:
For Processes with services which are implemented using onMessage:
The result will look like this:
The following table lists the objects produced by the TIBCO extension:
|Icon||Object Type||TIBCO ActiveMatrix BusinessWorks 6||TIBCO BusinessWorks 5|
TIBCO Process End
Shared JMS Connection
|TIBCO Process Transition|
TIBCO Service Operation
The following structural rules are provided:
You can also find a global list here: