This documentation is not maintained. Please refer to doc.castsoftware.com/technologies to find the latest updates.


Summary: This document provides information about the extension that provides TIBCO support.

Extension ID

com.castsoftware.tibco

What's new?

Please see TIBCO 1.2 - Release Notes for more information.

Description

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.

Supported Versions of TIBCO

This version of the extension provides partial support for:

TIBCOVersionSupported
TIBCO BusinessWorks5.1 - 5.13(tick)
TIBCO ActiveMatrix6.0 - 6.2(tick)

Function Point, Quality and Sizing support

This extension provides the following 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
Function Points
(transactions)
(tick)
Quality and Sizing(tick)

AIP Core compatibility

This extension is compatible with:

AIP Core release

Supported

8.3.x

(tick)

Supported DBMS servers

This extension is compatible with the following DBMS servers:

DBMSSupported
CSS / PostgreSQL(tick)

Prerequisites

(tick)An installation of any compatible release of AIP Core (see table above)

Download and installation instructions

The extension will be automatically downloaded and installed in AIP Console when you deliver TIBCO code. You can also manually install the extension using the Application - Extensions interface.

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 5TIBCO ActiveMatrix BusinessWorks 6
  • *.aeschema
  • *.sharedjdbc
  • *.javaschema
  • *.sharedhttp
  • *.sharedjmscon
  • *.process
  • *.sharedjmsapp
  • *.bwp
  • *.MF
  • *.substvar
  • *.httpclientresource
  • *.httpconnresource
  • *.jmsconnresource
  • *.jdbcresource;
  • *.mf
  • *.xsd

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)

As such, two analyzers will be used to handle the different source code. When using the legacy CAST Management Studio/Delivery Manager Tool (DMT), you should also deliver each type of code in a specific way as shown below (this does not apply when using AIP Console):

Source code typeAnalyzer that will be usedLegacy DMT - option to use
TIBCOUniversal AnalyzerFiles on your system option
JavaJEE AnalyzerTIBCO Library extractor option

In BusinessWorks 5.x the source code for the Java Code activity is embedded in the ActiveMatrix and therefore requires specific extraction and preprocessing, as such, .process and .aeschema files need to be preprocessed. The LISA folder will be used to analyse the preprocessed files.

TIBCO ActiveMatrix BusinessWorks 6

TIBCO ActiveMatrix BusinessWorks 6 source files are parsed with the SDK and do not need any preprocessing, therefore when using the legacy CAST Management Studio/Delivery Manager Tool (DMT) there is no need to specifically extract Java code. 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

Using AIP Console

All source code should be packaged and delivered together. See Application onboarding for more information.

Using CAST Management Studio

Click here to expand...
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

There are no analysis/technology configuration options available for Shell, however you should check that at least one TIBCO analysis unit has been created as shown below.

AIP Console exposes the technology configuration options once a version has been accepted/imported, or an analysis has been run. Click Universal Technology (3) in the Config (1) > Analysis (2) tab to display the available options for your TIBCO source code:

Then choose the relevant Analysis Unit (1) to view the configuration:

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:

Objects

The following table lists the objects produced by the TIBCO extension:

IconObject Type TIBCO ActiveMatrix BusinessWorks 6TIBCO BusinessWorks 5

TIBCO Activity

(tick)(tick)

TIBCO Process End

(tick)(tick)

Activity Input

(error)(tick)

Activity Output

(error)(tick)

Activity Starter

(tick)(tick)

AE Class

(error)(tick)

AE Field

(tick)(tick)

AE Schema

(tick)(tick)

Directory/Folder

(tick)(tick)

Group

(error)(tick)

Variable

(error)(tick)

Process

(tick)(tick)

Process Variable

(error)(tick)

Shared Connection

(tick)(tick)

Shared JMS Connection

(tick)(tick)
 
TIBCO Process Transition(error)

(tick)

Variable Group

(tick)(tick)

TIBCO Service

(tick)(error)

TIBCO Service Operation

(tick)(error)

Structural Rules

The following structural rules are provided:

You can also find a global list here: https://technologies.castsoftware.com/rules?sec=t_1018000&ref=||.