Some traces of Centura left.

IFS Delta Engine Properties

The Delta Engine can be configured in several ways. The Delta Engine Properties collects the settings for the behavior  and the language tuning options.

The Delta Engine uses a number of built in parsers to analyze source code. A number of properties tabs are used to tell Delta Engine which parser various file extensions shall use. You can add and remove extensions manually if the default setup isn’t fitting your environment.

Parser specific properties are also included on some of these parser tabs.

Contents

• Starting the Properties Dialog
• General Properties
• Comment Properties

Programming Language/Parser Specific Properties

• SQL & PL/SQL Properties
• ASP Properties
• Text Properties
• Java Properties
• IFM Properties
• XML Properties
• Format Properties

Starting the Properties Dialog

You start the Properties dialog by clicking the Properties icon or by choosing Properties... from the File menu.

The Properties icon

General Properties

The General properties

Merged Files: You can configure how you want to view the result after a delta is applied, using this option.

• Show Merged Output – Decides whether you want to display a successful merge for review or not. The Merged Output window will be used unless you check the sub box to use the Manual Mode window instead.
• Show Manual Mode – Decides whether you want to open Manual Mode or not for merges that could not be completed.

Extract & Apply: You can use this section to configure how DE should handle files without matching files in the Extract & Apply Process. You can also configure how to handle files not supported by DE.

• Copy new revision 1 files - If this is checked new files in the Revision 1 folder will be copied to the output folder
• Copy new revision 2 files -  If this is checked new files in the Revision 2 folder will be copied to the output folder
• Copy file types not supported by DE in revision1 to output – If this is checked files not supported by DE in the revision 1 folder will be copied directly to the output folder without any delta handling.

Log: This section configures the type of messaged displayed in the log and how you want your delta report.

• Inform about equal files – If this is checked a note is displayed in the log window if two files are found to be equal.
• Minimize Delta File- When this is checked DE produces a delta file and report containing only the “top node” of statements not having any changes. (An example would be a PL/SQL procedure that, if not changed, would only display the procedure heading). This drastically reduces the size of delta files and reports, and is especially useful when reading the delta report or distributing deltas. The Delta Report will always state whether it is max- or minimized.

The Default button will clear any changes you have made and return to the default setup. Observe that there is a Default-button per tab in the properties dialog

Comment Properties

In order to provide better DeltaEngine support for Pl/Sql comments certain tags have been created. Tags are described in both Consulting and R&D standards. You should normally not make any changes to these.

The Comments properties

You can exclude all comments handling by checking the “Ignore Comments” option. The DeltaEngine will then ignore comments in the code as well as changes to the File Header History comments.

SQL & PL/SQL Properties

The SQL & PL/SQL properties

Use this tab to define file extensions to be handled by the Sql & Pl/Sql parser.

Pre-processor definitions in PL/Sql files are typically used to control deployment behavior of the file. This could for instance be to ensure that one section of the code is deployed for a Scandinavian customer, and another section for an American customer. These tokens cannot be parsed as part of the PL/Sql programming language, and will therefore give you an error when you attempt to extract the delta from these files. The way around this problem is to tell Delta Engine to ignore these tokens.

The option “Parse PL/SQL Files with parse errors, in Text Mode” tells DE to use the text parser to parse PL/SQL files when a PL/SQL file could not be parsed by the DE parser.

ASP Properties

The ASP properties

Use the ASP tab to define file extensions to be handled by the ASP parser.

Text Properties

The Text properties

Use the Text tab to define file extensions to be handled by the Text parser. This parser is not programming language specific but can handle any file on the ASCII text format. This parser might be useful when it comes to analyzing differences between files but will not keep up with performance and hit rate (i.e. context problems) compared to the programming language parsers.

Use the Radio buttons to tell Delta Engine how to handle white space in files to be compared with this parser.

Java Properties

The Java properties

Use the Java tab to define file extensions to be handled by the Java parser.

IFM Properties

The IFM properties

Use the IFM tab to define file extensions to be handled by the IFM parser. IFM is a format developed by IFS R&D an is typically used for configuration files etc.
 

XML Properties

The XML properties

Use the XML tab to define file extensions to be handled by the Java parser.

Format Properties

The format tab allows you to change the color-coding used in Merged Output, Manual Mode and the Delta Report.

The Format properties

Use the Select button to decide overstrike colour for removed code and background colour for added code and automatically merged code.