Reconfiguration Process

Reconfiguration is a two-pass operation, acting on either a complete Database (DB) or on specified parts of one.

In the first pass, RECONFIGURER scans a named source DB and copies the data for some or all existing elements and their attributes into intermediate files.

In the second pass, the contents of the intermediate files are transferred to a specified destination DB.

This mode of operation has the following features:

• Only existing elements are copied to the intermediate files; deleted items and corrupt data are ignored. The destination DB created from these files is therefore both compact and uncorrupted.

• The reference and non-reference attributes of the elements are held in different intermediate files. The method of transfer of data to the destination DB makes sure that all referencing is complete and consistent.

• The source and destination DBs may have different DDLs. This enables existing data to be restructured to conform to a new DB structure and so, for example, to be used with a new version of the AVEVA base product.

• Reconfiguration can be used to transfer a Project to different hardware. The intermediate files produced by the first stage can be decoded into a portable format (typically ASCII), and transferred, and then the second stage carried out.

A similar technique is used to convert whole Projects to new versions of the AVEVA base product, though in this case the intermediate files need not be decoded.