To remediate the packaging alerts found while packaging.

In Delivery Manager Tool,while packaging the project,there might be alerts.If these alerts are not remediated,some of the files will not be analyzed in CAST-MS

Alerts can be for different reasons like:

1. Undefined variable
2. Missing Project
3. Missing file
4. Missing folder
5. Missing resource

  Alerts generally indicate that the source code package is incomplete, that there is something wrong in the source code.

The steps to remediate the alerts are:

1. Altering the source code package configuration (for example the root path defined in may be incorrect)
2. By creating additional source code packages that target the missing projects
3. You may need to alter your original source code.       

Using CAST remediation items:

If you know that an alert can be resolved because a missing item is located in another source code package, you can create a remediation item that will "tell" the CAST Delivery Manager where the missing items are located. When you next use the Package action, the CAST Delivery Manager Tool will use the remediation item to fix the missing item. The alert will then be cleared.     

 There are two methods of creating remediation items:

• You can use the targeted option in the Package generation alerts section.To add dlls in .Net,add a package targeting the folder containing all the dlls by choosing " Automated extraction of required .NET assemblies".To add jar files in Java,add a package targeting the folder containing the jar files by choosing "Automated extraction of required jar files".

• You can create them manually in this section.

For undefined variable,select the variable you want to create a remediation item for->Enter a value for the selected variable->Repeat for all undefined variables.

For missing resource reference,select the missing reference you want to create a remediation item for-> Select the reference that corresponds to the missing reference(place a tick in the check box)->Choose whether you want the reference to be applied to all projects in which the missing reference was identified, or whether you want it to apply to specific projects (select the projects in the table using the check box).       

To locate the list of alerts other than in GUI of DMT:

If there are lots of packaging alerts,you can find the alerts saved in a report file validation_report.pmx located in Delivery Folder of that Application.

Example of location of the file:
C:\CASTMS\Delivery\data{4a1d6a49-9b05-47e7-9cb0-1e158d34779d}{9562e9ec-3a61-4b39-bbec-9844bfdf83bf}{0c9c9252-42f3-49ad-919d-4ed261cb6bb0}

If you navigate to each package folder you can find this validation_report.pmx file.You can edit it with one of the editor which will list all the alerts corresponding to that particular package.
If you have multiple packages you will have to look into each packages validation_report.pmx file to find the list.

Example:

<alerts>
        <delivery.Alert project="entry:projectid:Common/core_framework/.project" symbol="entry:invalidrefid:Common/core_framework/.project:C:/Oracle 10G R2/j2ee/home/applib/log4j-1.2.8.jar"/>
        <delivery.Alert project="entry:projectid:Common/.project" symbol="entry:invalidrefid:Common/.project:C:/Oracle 10G R2/j2ee/home/applib/log4j-1.2.8.jar"/>
        <delivery.Alert project="entry:projectid:Common/.project" symbol="entry:invalidrefid:Common/.project:C:/Oracle 10G R2/j2ee/home/applib/eaglesecurity.jar"/>
        <delivery.Alert project="entry:projectid:Common/.project" symbol="entry:invalidrefid:Common/.project:Common/docroot/jsp/vim/log4j.jar"/>
        <delivery.Alert project="entry:projectid:Common/.project" symbol="entry:invalidrefid:Common/.project:C:/Oracle 10G R2/j2ee/home/applib/eaglesecurity.jar"/>
</alerts>