Modifying the Hub Location

The Name will appear on the Admin Elements window. For the newly created Hub, it will be set to PROJECTHUB.

The Location ID is a three-letter code that identifies the location. For the newly-created Hub, this will be set to HUB.

The Description is optional.

Connection will normally be on-line.

Hostname is the identifier of the machine on which the Global daemon will be running at the Hub.

This can be any one of three things:

The hostname, which is found by typing hostname in a command window.

The IP address:

Select Control Panel > Network

Select the Protocols tab

Select TCP/IP Protocol

Select Properties to see the IP address.

The fully-qualified domain name e.g. hub.domain.com.

Parent is the name of the location which will be the Parent of the new location in the communications network.

Note:
The Hub (and off-line locations) do not have a parent. The parent of the Hub is shown as Unset.

Group is used if the user wants the location to belong to a Location Group. Groups are discussed in Location Groups.

Admin Loc identifies the administering location. If the location is administered locally, at the location itself, this should be set to Local. If the location is administered from another location, this should be set to the name of the administering location. The Local button will set the administering location to Local.

The Overwrite DB Users check box allows locked database files to be overwritten, the default is unchecked. Global will not overwrite database files while there are users in the project (as recorded in the COMMS database) even when Overwrite DB Users check box is selected. However once users have left the project or been expunged and the check box is selected, Global will overwrite any files which remain locked.

It is advised not to enable overwriting in projects that are to be used as foreign projects, as users of foreign projects are not recorded in the session data for the current project and users run the risk of crashes as a result of the unexpected replacement of the foreign database file while in use.

The Disable Extract Creation check box allows extract creation for the current location, the default is unchecked. If the check box is selected, then remote extract creation cannot be issued from the location. This means contractors are prevented from creating extracts.

Extract creation is always permitted at the project hub, when creating extracts at a satellite, the Disable Extract Creation check box will be selected, whether creating an extract for itself or another location.

All Global extracts are given an identifying number when they are created. Before starting create extracts, work out an extract numbering system.

Databases can be given numbers in the range 1-6999 and 10,000-250,000, and for each of these, working extracts numbered in the range 1-6999 and 10,000-250,000 can be allocated. However, a working extract can only be seen at its location (not globally), so to avoid database working extract num-ber clashes a working extract number range needs to be set for each location.

Note:
The split range 1 - 6999 and 10,000 - 250,000 is to allow legacy projects to be upgraded and to continue to work with new versions of PDMS and AVEVA Everything 3D Number between 7000 - 9,999 and 250,001 - 255,000 can be used but the user is warned that these are reserved for use by AVEVA.

The Global extract range must be modified before setting working extract ranges. To set the Global Extract Range select Settings > Global Extract Range.

For each database master:

Note:
This is an example extract number range for illustration purposes. For a more detailed explanation of extract numbers refer to Extract Numbers.

The Working Extract Number Range settings allow the extract number ranges to be specified as explained above.

Below the heading Transaction Database the user can specify a DataBase Number for the Transaction database and its description. Click System to allow the software to automatically generate a free database number.

An example of a completed Modify Location window is shown:

Make any changes needed and click Apply. A prompt is displayed asking whether to initialize the Hub now:

Click Yes, the Hub will be initialized with the current settings on the window. These settings can be changed later, if necessary. Make sure that the Hub has a transaction database before its initialized.

Note:
Once the Hub is initialized, you cannot normally change the following settings:

• Location ID

• Hostname

  However, if required to transfer the Hub to a different machine, (for example, because of a systems crash) un-initialise the Hub and change these settings. In this case, the Global database must be copied down to each Satellite before daemons are restarted.

Click No, the values entered on the window is stored, and are still editable to change them.

Click Dismiss, the window is closed and any changes lost, as normal.

If you decide not to initialize the Hub at this stage, it can be initialized later by using the Project > Initialise Location option. This option will generate an error if the location is already initialized.

Note:
Initialization of a location initializes the Global daemon at that location.