This documentation is not maintained. Please refer to doc.castsoftware.com/technologies to find the latest updates.
Summary: This page explains how to prepare and configure the analysis of your TIBCO source code.

Source code

Source code requirements

Only files with following extensions will be analyzed:

  • *.aeschema
  • *.sharedjdbc
  • *.javaschema
  • *.sharedhttp
  • *.sharedjmscon
  • *.process
  • *.wsdl
  • *.sharedjmsapp

Source code preprocessing and Java extraction 

TIBCO 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 typeDMT - option to useCMS - Analyzer that will be used
TIBCOFiles on your system optionUniversal Analyzer
JavaTIBCO Library extractor optionJ2EE Analyzer

Note:

  • The TIBCO code source needs to preprocessed so that CAST can understand it and analyze it correctly. In this release and all future releases, 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 from CAST Management Studio "deployment" folder.

Application Source code delivery and Snapshot generation 

When delivering your source code for analysis with CAST, you need to follow the same process as for technologies that are supported by CAST "out of the box". In other words:

Embedded Java Source code

  • When you create and configure the new package for Java Embedded source codein the CAST Delivery Manager Tool, choose the option TIBCO Library extractor as the source location in the Add package wizard:


  •  The packaging of this package will generate a Java project that will be analyzed later with J2EE 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):

 

 Standard TIBCO source code

  • When you create and configure the second package for TIBCO code source, in the CAST Delivery Manager Tool, choose the option Files on your file system as the source location in the Add package wizard:

  • The packaging of this package will generate a TIBCO UA project:

Analysis Results 

The following table lists the objects produced by the legacy TIBCO Analyzer and the TIBCO Langage pack 1.0 for comparison purposes:

IconObject TypeTIBCO Legacy AnalyzerTIBCO Langage pack 1.0

TIBCO Activity

(tick)

(tick) Example:

<pd:activity name="CData">
<pd:type>com.tibco.plugin.mapper.MapperActivity</pd:<pd:resourceType>ae.activities.MapperActivity</pd:resourceType>
<pd:x>400</pd:x>
....
</pd:activity>

Depends on the subnode <pd:type> - this determines the activity type:

  • Java Code Activity
  • Java Method Activity
  • JDBC Call Procedure Activity
  • JDBC Query Activity
  • JDBC Update Activity
  • JMS Queue Receiver Activity
  • JMS Queue Requestor Activity (RequestReplyyActivity?)
  • JMS Queue Sender Activity - JMSQueueSendActivity
  • JMS Reply to Message Activity - JMSReplyActivity
  • JMS Topic Publisher Activity - JMSTopicPublishActivity
  • JMS Topic Subscriber Activity
  • Soap Event Source Activity
  • Soap Request Reply Activity
  • Soap Send Reply Activity
  • Rendezvous Send Request Activity
  • Rendezvous Subscriber Activity
  • XML to Java Activity

Activity Ender

(tick)(error)

Activity Input

(tick)(tick)

Activity Output

(tick) (tick)

Activity Starter

(tick)(tick)

AE Class

(tick) (tick)

AE Field

(tick) (tick)

AE Schema

(tick)(tick)

Directory/Folder

(tick) (tick)

External Command

(tick) (error)

Group

(tick) (tick)

Variable

(tick)(tick)

Java Code Activity

(tick)See TIBCO Process Activity

Java Method Activity

(tick) See TIBCO Process Activity

Java to XML Activity

(tick) See TIBCO Process Activity

JDBC Call Procedure Activity

(tick) See TIBCO Process Activity

JDBC Query Activity

(tick) See TIBCO Process Activity

JDBC Update Activity

(tick) See TIBCO Process Activity

JMS Queue Receiver Activity

(tick) See TIBCO Process Activity

JMS Queue Requestor Activity

(tick) See TIBCO Process Activity

JMS Queue Sender Activity

(tick) See TIBCO Process Activity

JMS Reply to Message Activity

(tick) See TIBCO Process Activity

JMS Topic Publisher Activity

(tick) See TIBCO Process Activity

JMS Topic Subscriber Activity

(tick) See TIBCO Process Activity

Process

(tick) (tick)

Process Variable

(tick) (tick)

Process Definition

(tick) (error)

TIBCO Project

(tick) (error)

Rendezvous Publish Message

(tick) (error)

Rendezvous Reply to Request

(tick) (error)

Rendezvous Send Request Activity

(tick) (error)

Rendezvous Subscriber Activity

(tick) (error)

Shared Connection

(tick) (tick)

Shared HTTP Connection

(tick) (error)

Shared Java Schema

(tick) (error)

Shared JMS Connection

(tick) (tick)

Soap Event Source Activity

(tick) See TIBCO Process Activity

Soap Request Reply Activity

(tick) See TIBCO Process Activity

Soap Send Reply Activity

(tick) See TIBCO Process Activity
 
TIBCO Process Transition(error)

(tick) This is a statement that seems to link certain internal activities to eachother. See code example below. callee of the transition.

Example:

<pd:transition>
<pd:from>Start</pd:from>
<pd:to>Log</pd:to>
<pd:lineType>Default</pd:lineType>
<pd:lineColor>-16777216</pd:lineColor>
<pd:conditionType>always</pd:conditionType>
</pd:transition>

Variable Group

(tick) (tick)

XML to Java Activity

(tick) See TIBCO Process Activity