PLATFORM - Installation and Deployment > MUST Licence Installation Guide > Inside
6. Inside
 
Licence check at login
Token requested at runtime
Files access
 
6.1. Licence check at login
 
When HOPEX is run by user U0001:
1. Configuration is read to identify the licence folder mapped to the HAS instance.
2. Licence folder is read to identify
• The authorized licence file for this user.
• The definition of the licence
• The possible products for this user
• The available tokens for each product of the license
3. Command line is read at both profile and login level to identify the requested products
4. Connection is refused if:
• Command line is inconsistent
• Products tokens are not available
5. Connection is allowed otherwise
Possible user files can be created dynamically
Token files are created according to product used
 
6.2. Token requested at runtime
 
Web Front-End (HOPEX Application Server)
 
Context
Must licence checked
Main counter used
Tokens requested
Command line considered
HOPEX Main users
(Common situation)
Yes
LAN
One token per Product
One token LAN (2)
Yes
HOPEX Main users (controlled multi front-end)
Yes (1)
LAN
One token per Product
One token LAN (2)
Yes
HOPEX Contributor
Yes
CBTR
One token for CBTR
Yes
HOPEX Viewer
Yes
VIEW
One token for VIEW
Yes
Web Service API
No (3)
-
-
-
 
(1) ANW product should be programmed.
Ex: ANW is required to run ARC (controlled multi front-end).
(2) LAN or LAN_D, or LAN_F.
(3) UAS token is requested
 
With Windows Front-end (customization or Administration)
 
Context
Must licence checked
Tokens requested
Command line considered
Administration.exe
Yes
One token SUP
One token LAN (1)
No
HOPEX.exe with HOPEX Power Studio (MTS2)
Yes
One token MTS2
One token LAN (1)
Yes
 
 
6.3. Files access
 
A licence folder can contain one or more licences.
For each licence, a hidden folder is created with the licence name
 
Ex:
<licence folder>\Licence-Y9999.must licence file
<licence folder>\Licence-Y9999 hidden folder
 
The hidden folder contains 2 subfolders.
 
Folder
Description
Example
TOKENS
Enables to count product tokens used at runtime
Each product has a subfolder
1 token = 1 file
When user U0001 opens a session with product APM, a file TOKEN-CA58CCE4613838E4-u-U0001.tkn-APM is created automatically in <hidden folder>\TOKENS\APM
Where
• U0001 is login name
• APM is product code
• CA58CCE4613838E4 is an ID generated at runtime
This file will be deleted automatically when users U0001 logs out (end of session)
USERS
Enables to configure possible user
Flat list
1 possible user seat = 1 file
When U0002 is set as possible user of HBPA, a file U0002.usr-HBPA-MEGA is created in <hidden folder>\USERS where
• U0002 is login name
• HBPA is product code
This file is not deleted automatically
 
A file Router.ini is created in the licence folder.
It saves:
• The default licence if any
• The assignment of users (logins) to licences