
Application name	Defines the name of your Application. It is not possible to change the name of an Application in the CAST Delivery Manager Tool - this can only be done by the CAST AI Administrator using the CAST Management Studio.
Application ID	A unique identification number for your Application. This ID is managed entirely by the CAST Management Studio and cannot be modified.

DMT - Folders

Mon, 01 Jan 0001 00:00:00 +0000

Folders

The Folder option is designed for target source code that is already expanded in a folder (local or network). The option has two functions:

To package any type of source code supported by CAST (see the CAST Release Notes) stored in a file folder
This option is also displayed for the following options, mainly to resolve packaging alerts:
- OSGi plugins on your file system > choose the Eclipse “plugins” folder
- Maven repository on your file system > choose the Maven repository folder
- .NET Assemblies on your file system > you need to create multiple packages to package the .NET framework and to resolve packaging alerts, as follows:

Package name/type

Mandatory?

Location/path

When to create this package

External assemblies (third party DLL)

No, only if required: one package per vendor.

N/A: depends on the third party

This package should only be created when your application uses third party assemblies.

.NET framework (system assemblies)

Yes

DMT - MS SQL Server

Mon, 01 Jan 0001 00:00:00 +0000

CAST extractor for MS

Configures a connection to a live Microsoft SQL Server database and will perform an extraction to file using CAST’s own SQL extractor.

Note that:

the database does not need to be online during the analysis process in the CAST Management Studio.
Note that you do NOT need to install a compatible client connection layer (for the target RDBMS) on the machine on which you are running the CAST Delivery Manager Tool.

Host name

Used to configure the host name of your database server. You can also enter an IP address if required.

Instance identification

Used to configure the database server access mode type (Port or Instance).

Select an appropriate access mode for your database.

DMT - Oracle

Mon, 01 Jan 0001 00:00:00 +0000

Oracle

CAST extractor for Oracle
Reuse existing CAST extractor/delivery output

CAST extractor for Oracle

Configures a connection to a live Oracle database and will perform an extraction to file using CAST’s own SQL extractor.

Note that:

the database does not need to be online during the analysis process in the CAST Management Studio.
Note that you do NOT need to install a compatible client connection layer (for the target RDBMS) on the machine on which you are running the CAST Delivery Manager Tool.

Host name

Used to configure the host name of your database server. You can also enter an IP address if required.

Port

Used to configure the port number for accessing your database. This field will only be displayed if you selected Port from the Instance identification option.

Default RDBMS port settings are as follows:

DMT - Package Alert tab

Mon, 01 Jan 0001 00:00:00 +0000

Package Alert tab

The Package Alert tab displays a list of any “alerts” that were raised during the Package action and allows you to either ignore or remediate the alerts. The tab is only populated with data once you have packaged a Source Code Package.

The tab contains various sub sections and each differs slightly for each type of Source Package you can define. Select the section you want to know more about:

DMT - Package Alert tab - Any manual remediations to apply for alerts?

Mon, 01 Jan 0001 00:00:00 +0000

Package Alert tab - Any manual remediations to apply for alerts?

This section will list any alerts for which you have created a Manual Remediation and that will be taken into account when the Package action is run:

You can edit or delete any manual remediations if required.

DMT - Package Alert tab - Packaging alerts

Mon, 01 Jan 0001 00:00:00 +0000

Package Alert tab - Packaging alerts

Note that this section will only be populated once you have used the Package action on a Version or Source Package.

This section displays a list of any “alerts” that were raised during the Package action:

Alerts come in various different types (non-exhaustive list):


Undefined variable	A variable has been discovered in the source code in the source package. The CAST Delivery Manager Tool cannot detect a value for this variable and therefore an alert has been created.
Missing project	A reference to project, library file, folder or resource has been discovered in the source code package. The CAST Delivery Manager Tool cannot detect this specific item anywhere in the source code package and therefore an alert has been created.
Missing library file
Missing folder
Missing resource
Please note that if you exclude a folder and subsequently during the Package action the discoverer finds a reference to the excluded folder, then a Package Alert will be generated. There is no way to resolve this alert with a standard remediation (see Handling alerts below), as such, if you still need to exclude the folder and want to avoid an alert, you can exclude its contents only using a specific Regular Expression: For example, you have a subfolder entitled “unittests” that you do not want to include in the Package - you exclude this folder. However, other code in the Package references this folder and as such a Package Alert will be generated when the Package action is run. Use forward slashes around the folder name in your Regular Expression to force the CAST Delivery Manager Tool to ignore the contents of the folder but keep the folder itself: /unittests/ No Package Alert should be generated. See also: Package Configuration tab - Where is your source code? (Advanced Extraction settings).

Alert summary by type

This section lists all the alerts that have been raised for all the projects discovered in the source code package. Selecting an alert type will display the details of the alerts raised in the section below.

DMT - Package Alert tab - Packaging alerts - Creating a Manual Remediation

Mon, 01 Jan 0001 00:00:00 +0000

Package Alert tab - Packaging alerts - Creating a Manual Remediation

If you know that an alert can be resolved because a missing item is located in another source code package, you can create a manual remediation item that will “tell” the CAST Delivery Manager where the missing items are located. In the same way, missing variables can be manually remediated by defining the variable that is required.

When you next use the Package action, the CAST Delivery Manager Tool will use the remediation item to fix the alert. The alert will then be cleared from the Packaging alerts panel.

DMT - Package Alert tab - Packaging alerts - Ignoring an alert

Mon, 01 Jan 0001 00:00:00 +0000

Package Alert tab - Packaging alerts - Ignoring an alert

If you know that an alert is false or will not impact the source code analysis, then it is possible to ignore the alert as follows:

Select the alert (1) and then click the ignore button:

A new dialog will be displayed:

Enter a Justification (1) for ignoring the alert. This is for information only and will be displayed in the Any alert to ignore? panel.
Now choose (2) whether you want the ignored alert setting to be applied to all projects in which the alert was identified, or whether you want it to apply to specific projects only (select the projects in the table using the check box).
Click Finish to save the ignored alert.
The ignored alert will then be displayed in the Any alert to ignore? panel. Next time you run a Package action, the ignored alert you created will be taken into account and the alert will be removed from the Packaging alerts panel.

DMT - Package Configuration tab

Mon, 01 Jan 0001 00:00:00 +0000

Package Configuration tab

The Package Configuration tab allows you to define what source code will be extracted and therefore included in the Source Code Package. The tab contains various sub sections and each differs slightly for each type of Source Package you can define. Select the section you want to know more about:

DMT - Package Configuration tab - Is the source code deployed in a specific folder in the development environment?

Mon, 01 Jan 0001 00:00:00 +0000

Package Configuration tab - Is the source code deployed in a specific folder in the development environment?

Note that this is not visible for Database and Specific Repository Source Packages.

This section is to be used in a specific situation: when the source code you have available for packaging is not in the development environment.

For example, you have been told to package the code from D:\App\DevCode but the code is developed in D:\App\ProdCode. In this situation the CAST Delivery Manager Tool may not be able to resolve all the files and folder references in the source code and you may see “Missing File” or “Missing Folder” alerts after running the package action. In this situation you can specify the “real” development root folder of your source code so that file and folde references can be resolved correctly.

DMT - Package Configuration tab - Where is your source code?

Mon, 01 Jan 0001 00:00:00 +0000

Package Configuration tab - Where is your source code?

Note that changes you make to this section once the source package has been packaged will require you to regenerate the source package.

This section defines how the CAST Delivery Manager Tool accesses the source code you want to extract and include in a Source Code Package for analysis. It differs depending on the type of Source Code Package you are configuring:

DMT - Package Configuration tab - Which project should we take into account for the analysis?

Mon, 01 Jan 0001 00:00:00 +0000

Package Configuration tab - Which project should we take into account for the analysis?

Note that this is not visible for Database and Specific Repository Source Packages.

Note that part of this section is designed to be configured once the source package has been packaged, thus changes you make to this section once the source package has been packaged will require you to re-run the Package action.

This section defines which projects in your chosen source code the CAST Delivery Manager Tool should:

DMT - Package Content tab

Mon, 01 Jan 0001 00:00:00 +0000

Package Content tab

The Package Content tab displays information about what the CAST Delivery Manager has identified in the source code package according to the configuration settings set in the Package Configuration tab - as such, it is only populated with data once you have packaged a Source Code Package.

The tab contains various sub sections and each differs slightly for each type of Source Package you can define. Select the section you want to know more about:

DMT - Package Content tab - Any alert to ignore?

Mon, 01 Jan 0001 00:00:00 +0000

Package Alert tab - Any alert to ignore?

This section will list any alerts that you have ignored and that will be taken into account when the Package action is run:

You can edit or delete any ignored alerts if required.

DMT - Package Content tab - Files found

Mon, 01 Jan 0001 00:00:00 +0000

Package Content tab - Files found

Note that this section is not visible if you are working with a Database or Specific Repository type of Source Package.

This section displays a list of files that have been discovered and extracted by the CAST Delivery Manager Tool. These are the files that will be packaged when the Version is delivered:


File extension	Displays the file extension discovered by the CAST Delivery Manager Tool.
Total files	Displays the total number of files with the specific extension that have been discovered, extracted and included in the Source Package.
Added files	This column displays the number of files with the specific extension that are “new” in the current Source Package in comparison to a Source Package in the previous Version.
Removed files	This column displays the number of files with the specific extension that are no longer present in the current Source Package in comparison to a Source Package in the previous Version.
Modified files	These columns display the number of files with the specific extension that have either been modified or are unchanged in the current Source Package in comparison to a Source Package in the previous Version. The CAST Delivery Manager Tool compares the sizes (not the checksum) of files in the current Version with those in the previous Version - a file is therefore only marked as Modified when its size has changed between the two Versions. In some rare cases when a file has actually changed in the current Version, but its size is identical to the size in the previous version, it will be marked as Unchanged.
Unchanged files
Total size(bytes)	This column displays the total size (in bytes) of all the files with the specific extension that have been discovered, extracted and included in the Source Package.
Folder	Indicates the folder in which the content is located.

Other options

Detailed content report

Displays a status message about the Detailed content report (see option below). When the report is ready to be generated, the status will say "Ready to export".

Export detailed content report

This option allows you to export the list of extracted files to a CSV file:

DMT - Package Content tab - Log summary

Mon, 01 Jan 0001 00:00:00 +0000

Package Content tab - Log summary

This section displays a log of the most recent Package action. The table lists each step in the Package action, the date and time the step was completed and whether any errors or warnings were encountered.

Log viewer

Use the icon to launch the CAST integrated log viewer:

This can provide more information about any errors or warnings that were encountered during the Package action. In the above example, the Package action did not complete successfully - the Log viewer indicates that this was due to an issue with the selected RDBMS.

DMT - Package Content tab - Projects found

Mon, 01 Jan 0001 00:00:00 +0000

Package Content tab - Projects found

This section displays a list of projects that have been discovered and extracted by the CAST Delivery Manager Tool when a Source Package has been Packaged.

Note that:

for database source packages, a project is equivalent to a database.
Projects that have been discovered by the CAST Delivery Manager Tool will become Analysis Units in the CAST Management Studio: one project = one Analysis Unit. If no projects have been discovered you can still Deliver the source code, but no Analysis Units will be created automatically for you.

Project summary by type

Project type

This indicates what project type the CAST Delivery Manager Tool has assigned to the projects identified in the source code package.

Technology

Indicates what technology type the CAST Delivery Manager Tool has assigned to the project. This is mirrored in the Analysis/Production tabs in the Application editor within the CAST Management Studio.

#Selected

Indicates the total number of projects identified by the CAST Delivery Manager Tool in the most recent Source Package and which will be packaged for Delivery.

Projects that are marked as Selected will be transformed into Analysis Units in the CAST Management Studio. If no projects are marked as Selected, then no Analysis Units will be created: you may need to review your package configuration.

DMT - Source Code Package page

Mon, 01 Jan 0001 00:00:00 +0000

Source Code Package page

Note that the Version page is visible from wherever you launch the CAST Delivery Manager Tool. See CAST Delivery Manager Tool modes.

The Source Code Package page enables you to define your Source Code Package.

Fields

Package name

The Name field does not belong to either of the available tabs, but is used solely to identify your Source Code Package. Use a name that easily and quickly identifies what your Source Code Package contains.

Displays the name of your Source Code Package. You can modify the name of an existing Source Code Package in this page if required:

DMT - Subversion

Mon, 01 Jan 0001 00:00:00 +0000

Subversion

The Subversion option is designed for target source code that resides in a Subversion SCM system. In other words, it does not reside in a folder nor in an archive file (zip, jar etc.).

It allows you to specify the location and access credentials for your Subversion repository. The extraction process relies on the Java based svnkit extractor.

The Subversion repository does not need to be available during the analysis process in the CAST Management Studio because the CAST Delivery Manager Tool will extract the source code and retain it before deployment to a specific location (defined in the CAST Management Studio).

DMT - Sybase

Mon, 01 Jan 0001 00:00:00 +0000

Sybase

CAST extractor for Sybase
Reuse existing CAST delivery output

CAST extractor for Sybase

Configures a connection to a live Sybase database and will perform an extraction to file using CAST’s own SQL extractor.

Note that:

the database does not need to be online during the analysis process in the CAST Management Studio.
Note that you do NOT need to install a compatible client connection layer (for the target RDBMS) on the machine on which you are running the CAST Delivery Manager Tool.

Host name

Used to configure the host name of your database server. You can also enter an IP address if required.

Port

Used to configure the port number for accessing your database server.

Default RDBMS port settings are as follows:

DMT - Techno - Generic extraction

Mon, 01 Jan 0001 00:00:00 +0000

Techno - Generic extraction

Use this option only if you are using the CAST Universal Importer to import .UAX (and optionally .SRC) files that have been generated by an external tool or analyzer.

GUI - Generic extraction

Extraction file

Enter the location of the .UAXDIRECTORY file that defines information about the .UAX (and optionally .SRC) files you are importing.

Project type

Enter the Project name as defined in your .UAXDIRECTORY and xxx_PROJECT.UAX files as follows:

.UAXDIRECTORY

DMT - Techno - Mainframe PDS dump

Mon, 01 Jan 0001 00:00:00 +0000

Techno - Mainframe PDS dump

The Mainframe PDS dump option is designed for target Mainframe source code (Cobol, JCL etc.) that is the result of a PDS (Partitioned Data Set) dump.

A PDS is a type of “library” containing elements known as “members” exported from a z/OS system (eg. Cobol programs, copybooks, JCL etc.) Each member in the PDS is preceded by a banner containing the member’s name (among other information) and is concatenated with other elements in text format. The CAST Delivery Manager Tool package for PDS dumps only supports one type of members and one banner prefix per file. If there are several types of members they must be delivered through multiple dump files and if several banner prefixes are used for the same type of members, then the source code delivery must be done through multiple dump files.

DMT - Techno - Oracle Forms/Reports

Mon, 01 Jan 0001 00:00:00 +0000

Techno - Oracle Forms/Reports

Forms/Reports on file system
Reuse existing CAST delivery output
Note about Oracle Reports

Reuse existing CAST delivery output

Note about Oracle Reports

Reuse existing CAST delivery output

This option enables you to package output from the standalone CAST Oracle Forms Extractor. This option requires you to input the location of a .uaxdirectory file that was created by the standalone CAST Oracle Forms Extractor:

Note that the Oracle Reports files (.rex) should be placed in the same folder as the output from the standalone CAST Oracle Forms Extractor and delivered together.The CAST Delivery Manager Tool is capable of distinguishing them.

DMT - Techno - SAP

Mon, 01 Jan 0001 00:00:00 +0000

Techno - SAP

Use this option ONLY if you are using the legacy CAST SAP Extractor (version 7.0.3 or earlier) to extract the SAP tables/programs.

If you are using the new generation CAST SAP Extractor (version 8.0.0 or higher), then you cannot use this option and you should use the Others > Files on your systemoption instead.

The SAP option is designed to connect to a SAP instance and extract and package SAP tables and programs for analysis.

DMT - Techno - Team Foundation Server

Mon, 01 Jan 0001 00:00:00 +0000

Techno - Team Foundation Server

The Team Foundation Server option is designed for target source code that resides in a Team Foundation Server SCM system. In other words, it does not reside in a folder nor in an archive file (zip, jar etc.).

It allows you to specify the location and access credentials for your Team Foundation Server repository. The extraction process relies on the Team Foundation Server using Web Service API extractor.

DMT - Version page

Mon, 01 Jan 0001 00:00:00 +0000

Version page

Note that the Version page is visible from wherever you launch the CAST Delivery Manager Tool. See CAST Delivery Manager Tool modes.

The Version page enables you to manage all aspects of your Version.

Fields

Version name

Field

Displays the name of your Version. You can modify the name of your existing Version in this page if required:

When working with a CAST AIC Portal > Following a change of Version name, you need to use the Deliver action to force the change to be uploaded to the Source Code Delivery Folder.
When working directly from the CAST Management Studio > The change is implemented when you use the Save action.

The new version name can then be seen in the CAST Management Studio (Application editor > Delivery tab) after using the Refresh option. For other Delivery Managers working via the CAST AIC Portal, a Refresh/Refresh All will be required so that the change is downloaded to their local CAST Delivery Manager Tool workspace.

DMT - Interface - an explanation of each page on Documentation - V2

DMT - Application page

Application page

Fields

Versions section

DMT - Folders

Folders

DMT - MS SQL Server

MS SQL Server

CAST extractor for MS

DMT - Oracle

Oracle

CAST extractor for Oracle

DMT - Package Alert tab

Package Alert tab

DMT - Package Alert tab - Any manual remediations to apply for alerts?

Package Alert tab - Any manual remediations to apply for alerts?

DMT - Package Alert tab - Packaging alerts

Package Alert tab - Packaging alerts

Alert summary by type

DMT - Package Alert tab - Packaging alerts - Creating a Manual Remediation

Package Alert tab - Packaging alerts - Creating a Manual Remediation

DMT - Package Alert tab - Packaging alerts - Ignoring an alert

Package Alert tab - Packaging alerts - Ignoring an alert

DMT - Package Configuration tab

Package Configuration tab

DMT - Package Configuration tab - Is the source code deployed in a specific folder in the development environment?

Package Configuration tab - Is the source code deployed in a specific folder in the development environment?

DMT - Package Configuration tab - Where is your source code?

Package Configuration tab - Where is your source code?

DMT - Package Configuration tab - Which project should we take into account for the analysis?

Package Configuration tab - Which project should we take into account for the analysis?

DMT - Package Content tab

Package Content tab

DMT - Package Content tab - Any alert to ignore?

Package Alert tab - Any alert to ignore?

DMT - Package Content tab - Files found

Package Content tab - Files found

Other options

DMT - Package Content tab - Log summary

Package Content tab - Log summary

Log viewer

DMT - Package Content tab - Projects found

Package Content tab - Projects found

Project summary by type

DMT - Source Code Package page

Source Code Package page

Fields

DMT - Subversion

Subversion

DMT - Sybase

Sybase

CAST extractor for Sybase

DMT - Techno - Generic extraction

Techno - Generic extraction

GUI - Generic extraction

DMT - Techno - Mainframe PDS dump

Techno - Mainframe PDS dump

DMT - Techno - Oracle Forms/Reports

Techno - Oracle Forms/Reports

Reuse existing CAST delivery output

DMT - Techno - SAP

Techno - SAP

DMT - Techno - Team Foundation Server

Techno - Team Foundation Server

DMT - Version page

Version page

Fields