Modules/Triggers/Constraints - Intergraph Smart Materials - Version 2020 (10.0) - Administration & Configuration - Hexagon PPM

Intergraph Smart Materials Classic Administration (2020)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Materials/Smart Reference Data Version
2020 (10.0)

The A.60.70.13 Modules/Triggers/Constraints screen can be used to check the size and timestamp of installed modules (screens and reports), triggers, and constraints.

On the Modules tab, you can find an overview about the current installed modules (screens and reports) and their deviations from the installation/service pack delivery. All modules delivered with the software have the Standard indicator checked, a nominal create date, and a nominal size shown in bytes. The content of the Nominal section or the underlying table is inserted via script by the service pack installation. If no modifications were made to the modules since the last service pack installation, the actual and the nominal status should be identical.

If a standard module is installed, fmx (screen) files in the fmx directory and rdf (report) files in the rep directory, its information is present within the Actual block. If the module is not installed in the appropriate directory, the actual size will be set to 0.

Differences between the nominal size and the actual size indicate that the module is not present in the version delivered with the installed service pack. For example, if you install a hot fix, the nominal data will not be updated and differences will occur for all modules involved in that hot fix.

To get the correct actual date and size for the installed modules, you must set two application server specific settings on the A.60.04 DBA Settings screen:

REL_MAN_MODULE_PATH - Must point to the application server directory, where the Smart Materials fmx files are stored.

REL_MAN_REPORT_PATH - Must point to the application server directory, where the Smart Materials rdf files are stored.

Tick the Show only deviations check box to display only modules with deviating dates/sizes. If you select this check box, only modules are shown where:

  • the nominal size differs from the actual size

  • information in the Nominal block is missing, but information is present in the Actual block

  • information in the Actual block is missing, but information is present in the Nominal block

On the Triggers tab, you can find an overview about the current installed triggers and their deviations from the installation/service pack delivery. All triggers delivered with the software have the Standard indicator checked, a release date, and a checksum. The content of the Nominal section or the underlying table is inserted via script by the service pack installation. If no modifications were made to the triggers since the last service pack installation, the actual and the nominal status should be identical.

If a standard trigger is installed, its information is present within the Actual block.

Differences between the nominal size and the actual size indicate that the trigger is not present in the version delivered with the installed service pack. For example, if you install a hot fix, the nominal data will not be updated and differences will occur for all triggers involved in that hot fix.

If there is no information present in the Nominal block, the selected trigger was not part of the standard delivery for the installation/service pack.

If there is no information present in the Actual block for a standard trigger, this trigger is missing within your installation and you should contact Support.

Tick the Show only deviations check box to display only triggers with deviating dates/checksums.

If you select this check box, constraints are shown where:

  • the nominal checksum differs from the actual checksum

  • information in the Nominal block is missing, but information is present in the Actual block

  • information in Actual block is missing, but information is present in the Nominal block

  • the installed trigger differs from the originally delivered trigger in the Trigger Type, Trigger Event, Owner, and/or Status.

The differing information will be displayed with a cyan background.

On the Constraints tab, you can find an overview about the current installed constraints and their deviations from the installation/service pack delivery. All constraints delivered with the software have the Standard indicator checked, a release date, and a checksum. Only constraints of Constraint Type CHECK have a checksum; all others will show 0 in the Checksum field. The content of the Nominal section or the underlying table is inserted via script by the service pack installation. If no modifications were made to the constraints since the last service pack installation, the actual and the nominal status should be identical.

If a standard constraint is installed, its information is present within the Actual block.

Differences between the nominal size and the actual size indicate that the constraint is not present in the version delivered with the installed service pack. For example, if you install a hot fix, the nominal data will not be updated and differences will occur for all constraints involved in that hot fix.

If there is no information present in the Nominal block, the selected constraint was not part of the standard delivery for the installation/service pack.

If there is no information present in the Actual block for a standard constraint, this constraint is missing within your installation and you should contact Support.

Tick the Show only deviations check box to display only constraints with deviating dates/checksums. If you select this check box, constraints are shown where:

  • the nominal checksum differs from the actual checksum

  • information in the Nominal block is missing, but information is present in the Actual block

  • information in the Actual block is missing, but information is present in the Nominal block

  • the installed constraint differs from the originally delivered constraint in the Constraint Type, Table Name, and/or Status

The differing information will be displayed with a cyan background.