This section describes configurations that will be necessary for standard deployment or Citrix/TSE deployment.

Consult your sales representative to obtain a license. You will get a license file and instructions to install it.

 

 

For more details about HOPEX license, see the article 'Must License Installation Guide HOPEX V2 EN'.

When Windows Front-End is run by an end-user:

1. A configuration file (Megasite.ini) is read.

2. If it contains a redirection (ClusterRoot=YYY), a different configuration files (Megasite.ini) is read in the shared folder.

 

• Create and share a folder that will contain configuration files (Example: \\hopex\data\config).

• Manually create a text file called 'megasite.ini'.

 

• The folder must be accessible with full control to all Windows users that should share this configuration.

• If you want to configure smarter permissions, consult the FAQs section p. 22.

• The file megasite.ini should at least contain a section for the license, according to the type of license used. See below:

 

 

If you do not have the technical skills or the authorization required for this step, contact your system administrator.

You need to copy the HOPEX installation programs (often called ‘installation master’) on a network folder. Example: \\Srv001\Master\HOPEX

This folder contains a subfolder \DISK1\HOPEX V2.msi.

 

Choose a folder that persists in time (do not delete it after installation). Indeed this path will be saved in the registry of the machines where HOPEX programs are installed. When such installations are upgraded (CP upgrade), this path can be tested and errors can occur if the master is no longer available.

Installing on several machines requires batching the execution of an installation command line.

The command line should be executed with the privilege 'Run as administrator'.

 

With recent operating system it is required that the installation is performed not only by a user that belongs to the group of 'Administrators' but also that the installation program is executed with the privilege 'Run as administrator'.

 

It is important to verify that, in the procedure used, the .MSI/.MSP program is executed with the privilege 'Run as administrator'. Otherwise, the HOPEX Programs may not be fully installed or upgraded and various problems can occur especially with HOPEX Web Front-end.

 

Different procedures are available and only one is described below:

• Create a text file with the .Bat extension.

• Edit the .Bat file, add the command lines and save the file.

• Select the .Bat file and right-click > Run as administrator.

 

 

<path of msiexec.exe> /package "<Folder of the HOPEX MSI file>\HOPEX V2.msi" /passive /levw "<path of installation log>"

SELECTED_LANGUAGE="<language code>"

ADDLOCAL="<feature list>" REMOVE="<feature list>"

ALLUSERS="1"

INSTALLDIR="<installation path>"

CLUSTERDIR="<configuration folder>"

HOPEXDIR="<installation path of IIS HOPEX application>"

HOPEXMWAS="<installation path of IIS MWAS>"

MSSPDIR="<installation path of IIS SSP>"

IS_NET_API_LOGON_USERNAME_HOPEX="<HOPEX service account name>" IS_NET_API_LOGON_PASSWORD_HOPEX="<HOPEX service account password>"

 

 

You can use such a command line to install HOPEX Windows Front-End and/or HOPEX Web Front-End. The appendix of this document contains:

• Examples of command line for Web Front-End.

• A complete description of installation features.

 

See also Microsoft documentation, for example:

A HOPEX Environment is required to run connection scenarios. To facilitate this step, it is created in the GBMS storage format. It can also be created in the RDBMS storage format. Of course, the HOPEX Environment used for production can be created in the RDBMS storage format.

 

For more details about RDBMS storage format, see the article 'RDBMS Repository Installation guide HOPEX V2 EN'.

 

• 800 MB free space on a shared folder.

On the server disk, create a folder (example \\svrname\data) and share it with a few end-users (full control).

• Local HOPEX installation.

 

From the File Server:

• Run Administration.exe

Example: C:\Program Files (x86)\MEGA\HOPEX V2\Administration.exe

• In the tree, select the 'Environments' folder.

• Right-click > New.

• A window 'Environment installation (Create/Update)' is displayed.

o Enter a value for 'Name:', (example: 'TestEnvironment').

o For 'Location:', select the shared folder (example \\svrname\data).

o For 'Repository storage support', keep 'Gbms'.

o Click 'OK' and wait until installation is complete.

• In the tree, select the 'Environments' folder.

• Right-click > Open.

• In the window Identification, enter the identifier System (no password) and click 'OK'.

• In the tree, below the environment, select the 'Repositories' folder.

• Right-click > New.

• A 'Create repository' window is displayed.

o Enter a value for 'Name:', (example: 'TestRepository').

o For 'Repository storage support', keep 'Gbms'.

o Click 'OK' and wait until installation is complete.

• Exit the Administration Console with Menu File > Exit.

Once HOPEX Programs and HOPEX Licenses are installed, it is important to verify that connection to the Windows Front-End is technically possible.

 

A HOPEX Environment and a HOPEX Repository are required. If no environment or repository is available at this step, see the section 'Installing a test environment' in this document.

 

 

 

(1) Check the type and name of the license in the bottom of the page

 

 

(2) Check that is it possible to select 'Library diagram' and to click 'Create'.

 

 

(3) Change options at environment level, group 'Compatibility > Diagram' and set 'Diagram creation interface' to 'Menu (Compatibility mode)'.