Several administration tools can be used:

 

 

Reference:

• See online documentation, HOPEX Administration

To maintain good performances, it is recommended to exclude certain file extension from antivirus scanning (on access scanning)

 

Authentication is implemented at HOPEX Environment level.

Several authentication models can be implemented:

 

 

Password values storage, encryption and update vary with the configuration chosen.

 

 

With Standard authentication, user passwords are initialized by the functional administrator. Then, they can be retrieved and reset without intervention of an administrator. With other authentication models, passwords are checked in the external directory and of course never updated through Web Front-End.

 

Reference:

• See online documentation, Authentication in HOPEX.

• Article 'Web connection overloading and configuration'.

 

This document contains metrics for a small deployment. Sizing is a complex matter that is closely linked to infrastructure and can be impacted by security policy. As a consequence, medium or large deployments need specific studies:

• Initial sizing according to load hypothesis.

• Load tests in the final infrastructure to check that sizing is appropriate.

 

To implement load balancing, various solutions are available on the market. In all cases the solution must be qualified and supported by customers and/or third parties.

Access to data is mainly controlled using profiles (repository access, data permissions, and GUI permissions).

Other features are available:

• Writing access management: control of updates on existing objects.

• Reading access management: control of visibility regarding existing objects.

• Data access rules: computed control of visibility regarding existing objects.

 

Reference:

See online documentation.

• Authentication in HOPEX.

• Profiles.

• Managing Data Writing Access.

• Managing Data Reading Access.

Each HOPEX Environment consists of one system repository and one/several data repositories.

By default data is stored in a database server (SQL Server, Oracle). This is called RDBMS storage. RDBMS storage is mandatory Web Front-End.

 

 

Reference:

• Article 'RDBMS Repository Installation guide HOPEX V2'

• See online documentation, Products.

 

A document management system is available through a solution or a pack. RDBMS storage is required.

 

 

If document management is enabled, web users can add, update and consult documents.

 

Reference:

• See online documentation, Managing Business Documents.

 

 

 

 

(3) Generated for the web application server

Reference:

See online documentation

• Enabling and Customizing Repository Indexing

• Performing a Quick Search

Products and solutions of HOPEX platform are protected by Must licenses. Must licenses can be shared between multiple users.

 

Must licensing is not server-based (there is no Windows process for a license server). At runtime with HOPEX Web Front-end, a set of files are generated dynamically by service account.

 

However a domain user (Active directory) is required for:

• Each service account running the HOPEX (IIS) application.

• Each user running the Administration Console (system administrator, functional administrator).

• Each user running the Windows Front-end (developer, functional administrator, user associated to a scheduled task).

 

To obtain a license, contact your sales representative. A UNC will be requested and a .must license file (locked on this UNC) will be sent with installation instructions.

 

Reference:

• Article 'Must License Installation Guide HOPEX V2'.

A mail server needs to be configured so that mail notifications can be used within workflows.

 

Web Front-End enables to work with multiple languages.

 

In case you face a real disaster recovery scenario, presence of a valid and restorable backup is very important.

 

 

(1) For HOPEX Environment used by an active project

(2) In particular before a major update concerning data. E.g.: system repository customization, data reprocessing, CP/RP upgrade of MEGA data

 

Specific recommendations

 

 

 

 

Reference:

See online documentation

• Managing repositories

• Managing logfiles

• Optimizing Repository Access Performance.

A few tasks need to be run and can often be automated:

 

 

 

There are three main categories of reports:

 

 

To open a report from the web client, a reader corresponding to the format should be installed.

Example: MS Excel to read .XLS documents, Adobe reader to read .PDF documents, Open Office/MS Word to read .RTF documents.

 

(1) Web Front-End does not enable to design Report templates (MS Word): templates must be developed on Windows Front-End with MS Word 32-bit and delivered using a specific procedure.

 

 

Reference:

See online documentation

• HOPEX Power Studio, Report DataSet Definition

• HOPEX Power Studio, HOPEX Studio - Report Studio

• HOPEX Power Studio, Customizing Reports (MS Word)

 

All ports used in the HOPEX platform are either configurable or set elsewhere. No specific port is required or hard-coded. To configure firewall ports, see the 'Communications' section earlier in this document.

 

MEGA strongly recommends configuring HTTPS to improve the security of flows between the Web Client and the Web Server. This requires a specific configuration of IIS and HOPEX.

 

If a local enterprise proxy is used, it should be configured by adding an excluding rule on the proxy. The rule refers to the IP address of the HOPEX web server involved.

 

File permissions should enable access to:

• Error and trace logfiles (see section 'Error and trace logfiles' in this document).

• License folder.

• Environment folder.

 

Reference:

Several caches are created on the Windows client. For Citrix/TSE deployment, the Citrix/TSE server is considered as the Windows client.

 

 

(1) For one HOPEX environment

 

Two Windows services are created by the installation on the SSP application server:

 

At runtime, several processes can be created.

 

 

(1) Can be configured