Mega administrator

[Arunas]

Hi Community ,

How the license has been allocated for mega administrator (customizer)? According to this below screenshot command line is blank , but it utilized all the licese product (incuding MTS2 and SUP ) when i login with Mega administrator profile ,

  we cleaned up the selected SUP product in licensing.exe , but still utilized the SUP if we login with mega administrator . 

 We have to exclude SUP from mega administrator,  but  How ? 

Appreciated if you would support !

[jhorber]

This is apparently a must license
If I undertand, you have one token of SUP (MEGA Supervisor) and on of MTS2 (MEGA Studio 2013) and you want to keep them for specific users.
SUP is required for most administration tasks
MTS2 is required for customization tasks

As said before,
By default with Must license and common profiles (ex Enterprise Architect, HOPEX Administrator), when login to Windows Front-end or Web Front-end a token is used for each product of the license if available

You can use the utility licensing.exe to control the assignement of these rare token
Ex:
assign the token SUP to an administrator user (profile HOPEX administrator)
assign the token MTS2 to an customizer user (profile HOPEX customizer)
You can also specify explicitely a command line with the product you want to use (usually at login level)
Ex: /RW'LAN,ARC,PMN,RSQ'

[Arunas]

Hi jerome,

These are the components

MEGA Process BPMN Edition=
MEGA Architecture
MEGA System Blueprint
MEGA Database Builder
MEGA Control & Risk
MEGA Lan
Repository Storage 
Repository Storage (SQL Server)
MEGA Business Data
MEGA Simulation BPMN Edition
MEGA Supervisor=  1 license 
MEGA Studio 2013 = 1 license
HOPEX Explorer
Web Front-End
MEGA Compliance
MEGA Enterprise Risk Management Lite
HOPEX Collaboration Manager
HOPEX Productivity Pack
ARC_F

When Person A connect with profile "Mega customiser" , it allocated the product ( Mega studio and MEGA LAN ) , at the sametime person B is also connected with "mega customiser" ( now  mega studio product will not be availabe for person B) , but it allocating automatically to "Mega Supervisor" product instead.. 

[jhorber]

What is the name of the license file?

It is is a .must file what is the content of the section [MEGAComponentInfo]?

[Arunas]

Hi Jerome,

1) What is the console/front-end used to login

Windows Front-end (Hopex.exe), Windows Administration Console (administration.exe),  Web Front-end?

           - Windows Front End 

2) What is the profile used

          - Mega Administrator

3) What is the type of license used.

       -    LAN , MTS 2

Scenario ,

   - Consider there are 2 logins ( Person A and Person B)  are connected to "mega administrator".

The Person A transaction/session is already connected in mega with LAN ,MTS 2 product (Mega administrator) ,

Now Person B is trying to connect mega with the same profile ( mega administrator ) .

In this case , LAN and SUP product is allocated  for person B . It should not be the case . If no possible connection availabe on MTS2, product  it should allocate only LAN product , not SUP product.

Could you please advise us why its connected to SUP product automatically ? Where to customize that ? 

[jhorber]

Hello Arunas

It is not clear

1) What is the console/front-end used to login

Windows Front-end (Hopex.exe), Windows Administration Console (administration.exe),  Web Front-end?

2) What is the profile used

3) What is the type of license used.

By default with Must license and common profiles (ex Enterprise Architect), when login to Windows Front-end or Web Front-end , a token is used for each product of the license if available.

[Arunas]

Any Suggestions how to proceed this profile ?

[Arunas]

Hi Community ,

Would be greatfull if you provide any suggestions ?