Introduction to Repositories
An environment includes:
• a system repository
• one or several HOPEX repositories
Repository management is carried out in the HOPEX Administration application (not available in the Web Administration Desktop).
System Repository (SystemDb)
The system repository (SystemDb) contains the configuration required to run HOPEX:
• the metamodel, constituting the structure of repositories
• programmed queries and macros
• users and their rights.
A system repository exists for each environment, automatically created in the Sysdb folder at creation of the environment.
HOPEX Repository
A HOPEX repository constitutes the workspace in which modeling data is stored. Several users can connect to it and work simultaneously on the same project.
A repository depends on an environment. Different policies of data distribution can be implemented. You can, for example, work on two repositories:
• a Development repository, which groups all projects
• a Production repository, which groups stable states of each project.
Any user of an environment can access a single repository or all of the repositories of the environment according to his/her profile assignment definition.
Storage type
The HOPEX Repository storage type has an impact on the functionalities available.
The HOPEX repository is stored in RDBMS format (Relational Database Management System):
• SQL Server
• Oracle
The GBMS format (MEGA proprietary) in only supported in Windows Front-End and restricted to HOPEX Power Studio product, see GBMS Repositories.
Certain recommendations may concern only RDBMS or GBMS type storage. Absence of a warning indicates that the recommendation is valid for all types of storage.
For more details on structure and advantages of RDBMS storage, see RDBMS Repository Installation deployment guide.
Repository Structure
The files enabling use of a repository are all in the same folder, the location of which is stored in the system repository (SystDb).
A repository comprises "RepositoryName".XXX files of which type and XXX format depend on the repository storage type:
|
Information type
|
Storage type
|
|
|---|---|---|
|
Oracle
|
SQL Server
|
|
|
Repository evolution logfile
(creation, update, etc.)
|
.EMV
|
.EMV
|
|
Data
|
.EMO*
|
.EMQ*
|
*: this file does not contain data; it is a pointer to data stored on the relational database server.
For each repository, folders are created dynamically while the user is working:
• Approve: contains validated reports (MS Word) detached from HOPEX.
• Data: contains all business documents created in HOPEX.
• Document: contains all reports (MS Word) generated from HOPEX.
• RepositoryName.ix: contains the result of indexing for full-text search.
• RepositoryName.Log (repository backup logfile): contains repository backup logfiles (enabled by default).
Each private workspace is saved in logfile, .MGL format.
See Backup logfile.• RepositoryName.Transactions (private workspace backup logfile: contains files linked to active private workspaces of repository users.
The presence of these files depends both on the server type used and on the options enabled for this repository. These files are:
"CCC.MGL"
where CCC is the code associated with the user (the repository Backup logfile option is enabled).
See Backup logfile.• USER: contains a folder for each user, in which all work files generated by the user are stored. It groups the files created by backup and extraction procedures, as well as control files.
Each folder is named "CCC", where CCC is the code associated with the user.• WORK: contains work files created by administration operations carried out using the administration application.
Accessing Repositories
To access a repository:
1. Connect to HOPEX Administration and select the environment concerned.
2. Expand the Repositories folder.
The list of the repositories in the environment appears.
Each repository is represented by:
• an icon that represents its storage type
• SQL Server repository 
• Oracle repository 
• its installation language.