REPLICATE (Project definition)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : REPLICATE (Project definition)

REPLICATE (Project definition)

Saves the project in a file so it can be replicated.

This command can be used:

•

To replicate the complete Project, including all data (except the ISO subdirectories), to a new project. You use the REPLICATE command to do this.

•

To replicate the structure of a standard (non-global) project to file. You use the REPLICATE SYSTEM command to do this.

•

To replicate the structure of a global project to file:

•

Use REPLICATE SYSTEM to replicate the structure of the project at the current location.

•

Use REPLICATE SYSTEM STANDALONE to replicate the project as a standard project, omitting references to Locations and communications.

•

Use REPLICATE SYSTEM SATELLITE at a Satellite in a global project to replicate the project as represented in the local System database. That is, the local information about Users, MDBs and Communication Events will be stored, but not the elements which can only be created and deleted at the Hub.

The file created by REPLICATE SYSTEM can be run as a macro in ADMIN. The REPLICATE SYSTEM command causes ADMIN to scan the System database (and Global database) and output to the named file all the commands necessary to recreate the project structure.

In a Global project, the file created contains macros that should be run in two stages:

The first stage creates the basic project structure and generates the satellite locations. The macro then terminates.

You should then edit the remainder of the file into a new file to be run as a separate macro, which should not be run until satellites have been created and initialised.

The second stage allocates databases to satellites and makes the relevant databases primary at satellites.

Before you run the macro to recreate the project structure, make sure that suitable project variables have been defined. In a Global project, this must include transfer directories for each satellite (for more details, see the TRANSFER command).

Note:

It is strongly recommended that this is only done in a newly created project, otherwise results could be unpredictable.


REPLICATE XYZ Copies all data from the current project directories into directories for a project named XYZ. In a Global project, a new UUID value for the Project is set (stored in ADUUID of /*GL; this is because each project requires a unique value of this attribute. This is used by Global daemons to distinguish between projects at the same location).
REPLICATE F123 In this case the long project identifier (%ABC000ID%) has been specified. This will replicate to the underlying project path of which this variable is associated, i.e the path that %ABC000% maps to.

Note:

A new UUID value may be queried at /*GL using Q NEWUID. The administrator may use this value to set ADUUID manually if a Global project has been copied externally to AVEVA E3D™.

If ADUUID is left unchanged, there may be data corruption since daemons may send data to the wrong project.

The ADUUID attribute is essential to distinguish between Global projects. Each project should have a unique value of ADUUID. This value is what the Global daemon uses to select the correct project.

For example if the user copies a project using the file system, rather than by using the REPLICATE command, then the ADUUID attribute in both projects will be the same, and this may cause commands from one Global project to be received by the wrong Global project.

It is therefore essential that the AVEVA E3D™ Administrator resets the ADUUID attribute of the project. The NEWUID attribute provides a way to get a new value, since it makes a 'uuidgen' query. The Administrator can then use the result of the NEWUID attribute query to set the ADUUID attribute. Note that NEWUID is not an attribute of the database. It is a pseudo-attribute provided for the purpose of generating a new uid value for ADUUID.
/*GL
!N=NEWUID
ADUUID=$!N


REPLICATE SYSTEM filename Generate macro to replicate the project structure. If the current project is Global, the macro will include Location and Communication details.
REPLICATE SYSTEM /filename FILENUMBERS Generate macro in a file /filename to replicate the complete data in the current project, maintaining the same file numbers.
REPLICATE SYSTEM /filename OVERWRITE Generate macro to replicate the complete data in the current project. The data will be saved in the named file. If the file exists, it will be overwritten.
REPLICATE SYSTEM STANDalone filename Generate macro to replicate the project setup for a stand-alone (non-Global) project. This omits all references to Locations and Communication elements. REPLICATE SYSTEM SATELLite filename Generate macro to replicate the project setup for a satellite of a Global project. Outputs the commands for building the System database only, not the Global database, that is, Teams, DBs and Locations are omitted.

Command Syntax for a Standard (non-global) project:


>-- REPLICATE -+- code ----------------------------. \| \| ‘- SYSTEM filename -+- FILENumbers -\| \| \| ‘---------------+- OVERwrite -. \| \| ‘-------------+--> Command Syntax for a Global project: >- REPLICATE -+- code ----------------------------------------- . \| \| ‘- SYSTEM -+- STANDalone -. \| \| \| \| \|- SATELLite --+------------------------ \| \| \| \| ‘------------+- filename -+- FILENumbers -\| \| \| ‘-------------+- OVERwrite --. \| \| ‘------------+-->

The FILENumbers option maintains the same file numbers.

The OVERWRITE option overwrites an existing file of the same name.

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.