Using one MUST license file for a stage AND production system

[hendrikdoerr]

Hello everybody,

we are using Hopex V1R2 web-front end and have a production and a stage system with 1xapplication server and 1xdatabase server each. Since we only have one license file, how can we share the license between the two systems.

The idea is to access the license folder (UNC path on production system) of the production system already running from the stage system. How is that possible and must the megasite.ini of the production system be shared as well?

In case the megasite.ini must be shared also, how can be ensure that patches on the stage system do not compromise our production system?

Thanks and regards, Hendrik

[jhorber · Accepted solution]

This is technically possible that several HOPEX installations use the same must licence

This is not recommended if the HOPEX installations are not in the same version. Indeed

• If the list of products is not understood by both version, problems could occur.
• If the behavior of must licence is different, problems could occur.

You need to:

1) Associate the installation to the licence folder

See http://community.mega.com/mega/attachments/mega/HOPEXV1R2/9/29/Must%20License%20Installation%20Guide...

Section Configuring the license folder in the shared configuration folder (indirect reference)

2) Configure file permissions for the appropritate users on the licence folder

Certain user should have the modify permission on the licence folder

• HOPEX Web Front-end: Only the service account for the HOPEX (IIS) web application should be configured (ex: D01\hopex).
• HOPEX Windows Front-end: Each end-user can be configured (D01\u0001, D01\u0002…). It is therefore recommended that a group is created for users of the Windows Front-end.

With HOPEX Web front end, if the licence folder is not located on the machine where the SSP is running, additional configuration is required

See http://community.mega.com/t5/custom/page/page-id/mega-kb-solution?sid=501D00000012aUwIAI