Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A successful import will result in the following message displayed in the CMD console:

Image RemovedImage Added

Login to the AIP Console - the imported application will now be listed with any others, all versions and snapshots will be available. If not, then please refresh the AIP Console page. Repeat the process for any additional applications you need to import.

...

Click to enlarge

Image RemovedImage Added

Click NEXT to define any folder exclusions (usually this is not necessary):

Click to enlarge

Image RemovedImage Added

Click NEXT to define any Objectives. If User Input Security options were enabled in the imported Application in CAST Management Studio, ensure that you enable the Security assessment option (this will enable User Input Security):

Click to enlarge

Image RemovedImage Added

Click FINISH to generate the consistency snapshot.

...

Expand

When the original source code is configured in one single parent folder with sub-folders corresponding to each Delivery Manager Tool package, for example:

Code Block
languagetext
R:/Source/AppName
		|----DMT------|
			|---- Analyzed (source code)
			|---- DB
			|-----helping folder1---(with subfolders)
			|-----helping folder2---(with subfolders)

Then you should copy all folders under "DMT" and paste into a new folder as shown below. Finally:

  • if using a ZIP file, zip the folders in the "temp" folder - but do not ZIP the "temp" folder, nor create any intermediary folders. The Path matching option for source code delivery rescan will then detect the differences in the uploaded ZIP file.
  • or upload the contents of the temp folder into your source code delivery folder.
Code Block
languagetext
D:/temp
	|-----Analyzed (source code)
	|-----DB
	|-----helping folder1--(with subfolders)
	|-----helping folder2--(with subfolders)

Alternative method - use the DEPLOY/<application_name> folder

Alternatively, if your DEPLOY/<application_name> folder still contains the deployed source code (i.e. you have not manually removed it following the most recent snapshot), you can re-use contents of this folder and use it for the new version you are delivering via the AIP Console:

Image RemovedImage Added

When using this method, there should be no differences in the source code paths that AIP Console already has for the imported Application version, and therefore the Path matching option for source code delivery rescan should not detect any differences.

...

Expand

If the imported Application contains source code packages for SQL databases such as Oracle Server, Microsoft SQL or Sybase ASE created in the CAST Delivery Manager Tool (DMT) using the "live" database extractor built into the DMT then you will need to include the uaxdirectory/uax files or the .castextraction file in the source code ZIP file or the source code delivery folder. You can obtain these files either by running the standalone CAST Database Extractor again on your target database, or by locating the files in the DEPLOY/<application_name> folder. When code is delivered for the new version, CAST AIP Console will detect that the "live" SQL database packages are missing (assuming that the Path matching option for source code delivery rescan is enabled) and display the missing packages dialog. When this occurs, you must delete any paths that correspond to these "live" SQL database packages.

The "live" SQL database packages would have been created in the CAST Delivery Manager Tool using the following options:

Click to enlarge

Image RemovedImage Added

Anchor
trouble
trouble
Troubleshooting

...