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 type | DMT - option to use | CMS - Analyzer that will be used |
---|---|---|
TIBCO | Files on your system option | Universal Analyzer |
Java | TIBCO Library extractor option | J2EE 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:
- Registering new domains and applications in the CAST AIC Portal
Add and Deliver Application code source
For a TIBCO application, you need to create two different packages in the CAST Delivery Manager Tool depending on the type of source code you have:
Embedded Java Source code
When you create and configure the new package for Java Embedded source code, in 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:
- Once both packages have been created, packaged and delivered, return to the CAST Management Studio and:
Analysis Results
The following table lists the objects produced by the legacy TIBCO Analyzer and the TIBCO Langage pack 1.0 for comparison purposes:
Icon | Object Type | TIBCO Legacy Analyzer | TIBCO Langage pack 1.0 |
---|---|---|---|
TIBCO Activity | 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:
| ||
Activity Ender | |||
Activity Input | |||
Activity Output | |||
Activity Starter | |||
AE Class | |||
AE Field | |||
AE Schema | |||
Directory/Folder | |||
External Command | |||
Group | |||
Variable | |||
Java Code Activity | See TIBCO Process Activity | ||
Java Method Activity | See TIBCO Process Activity | ||
Java to XML Activity | See TIBCO Process Activity | ||
JDBC Call Procedure Activity | See TIBCO Process Activity | ||
JDBC Query Activity | See TIBCO Process Activity | ||
JDBC Update Activity | See TIBCO Process Activity | ||
JMS Queue Receiver Activity | See TIBCO Process Activity | ||
JMS Queue Requestor Activity | See TIBCO Process Activity | ||
JMS Queue Sender Activity | See TIBCO Process Activity | ||
JMS Reply to Message Activity | See TIBCO Process Activity | ||
JMS Topic Publisher Activity | See TIBCO Process Activity | ||
JMS Topic Subscriber Activity | See TIBCO Process Activity | ||
Process | |||
Process Variable | |||
Process Definition | |||
TIBCO Project | |||
Rendezvous Publish Message | |||
Rendezvous Reply to Request | |||
Rendezvous Send Request Activity | |||
Rendezvous Subscriber Activity | |||
Shared Connection | |||
Shared HTTP Connection | |||
Shared Java Schema | |||
Shared JMS Connection | |||
Soap Event Source Activity | See TIBCO Process Activity | ||
Soap Request Reply Activity | See TIBCO Process Activity | ||
Soap Send Reply Activity | See TIBCO Process Activity | ||
TIBCO Process Transition | 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 | |||
XML to Java Activity | See TIBCO Process Activity |