Page tree
Skip to end of metadata
Go to start of metadata
Purpose (problem description)

This page provides information on the structure of the files used by the Delivery Manager Tool to allow for assistance with debugging issues.

Do not modify the contents of the DMT files, since doing so may cause your DMT configuration to become inconsistent and result in errors in the DMT.


Observed in CAST AIP
Release
Yes/No
8.2.x (tick)
8.1.x (tick)
8.0.x  (tick)
7.3.x (tick)
7.2.x (tick)
7.0.x (error)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server (tick)
Microsoft SQL Server (tick)
CSS2 (tick)
CSS1 (error)



Details

Delivery Folder Structure

This section is provided for reference.

  • First, go to the defined source code delivery directory in CMS (you can see this in CMS by going to Windows->Preferences, and then Platform Settings).


  • At the source code delivery directory level there will be a data sub-directory as well as a version.xml file.  The version.xml file provides information on the CAST version used for this delivery.
  • Next, go into the data sub-directory
  • The hierarchy in the data directory is application level, then version level, and then package level.

Application folders

Note that there can be more than one Application folder depending on the number of applications delivered in Delivery.


Data Folder Contents

  • You are at the Application Level at this point.  The directory should contain:
    • An index.xml file which lists a series of entry keys for each application being managed by the DMT.
    • An <uuid>.entity.xml file for each application
    • A sub-directory for each application


  • In the index.xml file in the data sub-directory, you should see a series of entry keys for each application being managed by DMT.  An example of this section of the file is here:



You can see that each entry is prefaced by the application uuid which is also presented as a specific entry.  The application uuids in the case above are:  5a920394-0e82-4cd9-aa46-e90150057bf0 (application name is 3634) and d0170d8f-8d64-4208-9a6a-122d605831a5 (application name is J2EE training)

  • For each application uuid in the index.xml file, there should also be a <uuid>.entity.xml file which contains discovery plugins information and the associated directory name. An example of the file is here:

 


In CAST Management Studio

Note that the application id is also defined in CAST Management Studio :

1. Open CAST Management Studio.
2. Open the Application, go to Notes tab : 


Application Folder Contents

  • If you then go into the directory indicated in the <uuid>.entity.xml file, then you are at the version level.  In this case the directory is 29fc33be-f5c6-4bb9-84f9-b9339a7a54a7, there should be the following files:
    • an index.xml file which lists a series of entry keys for each version of the application (current version, previous version, ...)
    • an <uuid>.xml file for each version.
    • a sub-directory for each version.

  • In the index.xml file in the data sub-directory, you should see a series of entry keys for each version of the application.  An example of this section of the file is given here:

 

You can see that each entry is prefaced by the version uuid which is also presented as a specific entry.  The version uuids in the case above are:  d792db386e89e1e8fb0ad0c5f04c1764, 7599b86c-4fcc-4028-b38a, e6bb50a7-39da-47d1-9722-465c7aa64188

The main entry that are important are :

<entry key="7599b86c-4fcc-4028-b38a-8311914c5de7_date">2015-11-20 00:00:00</entry> : Date of creation
<entry key="7599b86c-4fcc-4028-b38a-8311914c5de7_name">KBUPDATE</entry> : Name of the Version
<entry key="7599b86c-4fcc-4028-b38a-8311914c5de7_serverStatus">delivery.StatusReadyForAnalysis</entry> : Status of the version.


Version Status

The delivery version status are :

delivery.StatusReadyForAnalysis : The version is set as current version and can be analyzed

delivery.StatusPurged : The version has been deleted (as you can see in the below screenshot)


delivery.StatusOpened : The version is accepted


<entry key="7599b86c-4fcc-4028-b38a-8311914c5de7_uuid">7599b86c-4fcc-4028-b38a-8311914c5de7</entry> : ID of the Version


For each version uuid in the index.xml file, there should also be a <uuid>.entity.xml file which contains the version uuid, discovery plugins information and the associated directory name.  An example of this file is here:

 Version Folder Contents

  • If you then go into the directory indicated in the <uuid>.entity.xml file, then you are at the package level.  In this case the directory is 17475ceb-116d-40ee-9d53-434b07860452, there should be the following files:
    • an index.xml file which lists a series of entry keys for each package of that version of the application.
    • an <uuuid>.xml file for each package.
    • a sub-directory for each package.


  •  In the index.xml file in the data sub-directory, you should see a series of entry keys for each package of the version.  An example of this section of the file is here:

  

 You can see that each entry is prefaced by the package uuid which is also presented as a specific entry.  The version uuid in the case above is:  58b49fce-c4a3-4a66-914a-76c4c1c8f686 

 The main entry in the package are :

 <entry key="756ddea5-a578-4efe-b528-7dc67b996e49_name">My Package</entry> : Package Name
<entry key="756ddea5-a578-4efe-b528-7dc67b996e49_type">delivery.SourceFilesPackage</entry> : Type of Package

Type of Package

The type of package are the one defined at the creation of the package :



<entry key="756ddea5-a578-4efe-b528-7dc67b996e49_uuid">756ddea5-a578-4efe-b528-7dc67b996e49</entry> : The Package ID

For each package uuid in the index.xml file, there should also be a <uuid>.entity.xml file which contains specific details about the package that will be specific to the technology associated with that package.

  • In the package uuid directory, you will find:
    • logs related to that specific package
    • files which contain specific files and reports for the packages


Delivery Manager Tool Content

Package Folder


sources.CastSourcePackage

Archived file of the extracted sources. This file is not fetched by CST if Allow Source code is not selected

sources.CastSourceTreeDump File

This file is in the Package folder. It is the structure of the folder packaged and its content (source files). It contains the name of the folders and the name of the files that have been packaged.

discovery.CastProjects

This file can be used to validate the data generated by the discoverer on this project.  

Project selection status in the tag <Project> is:

selectionStatus="Selected"

Selection.CastProjects

Project selection statuses in the tag <Project> are:

selectionStatus="Selected"

selectionStatus="Ignored"

Validation.CastProjects

Project selection statuses in the tag <Project> are:

selectionStatus="Selected"

selectionStatus="Ignored"

selectionStatus="Referenced"


Delivery Manager Tool Log files


As described in the section Delivery Manager Tool content, the Delivery Manager Tool log files are stored in the Packages folder.


Here are the list of the Delivery Manager Tool log file : 

  • Extraction log file : extraction.castlog2

  • Scan log file : scan.CastLog2

  • Dicovery log file : discovery.CastLog2

  • Selection log file : selection.CastLog2

  • Validation log file : validation.CastLog2

  • Remediation log file : remediation.CastLog2

Notes/comments


Related Pages





  • No labels