About HOPEX Administration
HOPEX Administration is managed via Administration (Windows Front-End) application and via Administration (Web Front-End) desktop.
The Administration application (Windows Front-End) is the HOPEX administration application accessible from the Windows desktop. This application contains the tools required for management of environments and repositories. It is also used to manage scheduling and data accesses (writing access as well as confidentiality using reading access management).
To perform HOPEX administration tasks from the Administration application (Windows Front-End), see About HOPEX Administration.This guide is for the person responsible for administrating users and repositories from the HOPEX Administration desktop (Web Front-End).
The Administration desktop (Web Front-End) is the HOPEX Administration application accessible via an internet browser. This application is used to manage users (persons, person groups), and repositories (workspaces, locks, repository health, repository activity, repository snapshots). This application also provides access to tools (Scheduler, Import/Export of command files).
Some actions, like user management, can be performed by functional Administrators from a restricted Administration desktop accessible from other HOPEX desktops (Web Front-End).
Certain features, like object management are only available with specific technical modules (HOPEX Power Studio or HOPEX Power Supervisor). These are indicated by a note.
HOPEX structure:
Some basic knowledge is required to understand the architecture and operation of HOPEX.
HOPEX (Web Front-End) is organized on the following levels:
• site
A site groups together everything that is shared by all HOPEX users on the same local network: the programs, standard configuration files, online help files, standard shapes, workstation installation programs, and version upgrade programs.
• environment
An environment groups a set of users, the repositories on which they can work, and the system repository. It is where user private workspaces, users, and system data are managed.
• user
A user is a person (or person group) with a login and a profile assigned. A user:
• has a specific workspace in each repository.
• has a specific configuration and is authorized to access specific product functions and repositories in the environment.