Galaxy Repository
- Last UpdatedAug 12, 2024
- 2 minute read
The Galaxy Repository is a database that contains the configuration data for your Galaxy. Galaxy data is stored in a Microsoft SQL Server database. The following components are installed on a Galaxy Repository (GR node):
-
Bootstrap
-
PCS Runtime
-
PCS Service Repository
-
Galaxy Repository (requires Microsoft SQL Server)
-
System Monitor
-
AVEVA License Server
While AVEVA Licensing is automatically installed when the GR component is selected for installation, you do not need to load licenses onto the node if you are using a different node as the License Server.
-
AVEVA License Manager
In addition to the components listed above, the following System Platform components and applications are also installed:
-
Historian Search
-
Historian Client
-
Operations Control Management Console
-
Operations Control Logger
-
AVEVA Communications Drivers Pack
-
AVEVA Application Manager
A Galaxy Repository node can be combined with other types of Application Server nodes, such as:
-
System Platform IDE (Development Node)
-
Object Server
-
I/O Server
-
OMI Client (visualization node)
The GR can be installed on a dedicated node, in combination with the System Platform IDE, or with other System Platform components, depending on your system size.
Note: For information on installing the GR on the same node with any other components, see Single Node System implementation.
The Galaxy Repository manages the configuration data associated with one or more Galaxies. This data is stored in individual databases, one for each Galaxy in the system. Microsoft SQL Server is the relational database used to store the data.
During run-time, the GR communicates with all nodes in the Galaxy to keep them updated on global changes such as security model modifications, etc. Even though it is possible to disconnect the GR from the Galaxy and still keep remaining nodes in production, it is recommended to maintain the GR connection to the Galaxy in order to transfer all global changes when they occur.
The Galaxy Repository is accessed when the objects in the database are viewed, created, modified, deleted, deployed, or uploaded. The Galaxy Repository is also accessed when a running object attempts to access another object that has not been previously referenced.