Products - XWiki

60

Products are at the heart of Licence Management and are associated with all ongoing data. You create a product from a software version and edition to be licensed. The product should ideally be a balance between the licences purchased and the consumers that represent the actual use of the licences. If these match, you have an optimally licensed product that is also reported in compliance.

8

9

You need to select the metric that matches the licensing form of the product. This must ultimately be the same as the licence metric in order for the licence calculation to be correct.

10

11

In the Products tab you will see all the products that have already been created. You can create new products here using the Add button or in the Software Catalog tab, or you can edit or delete existing products. You can also filter products by metric type.

= Create a product =

In the ribbon bar, click on// Add// in the Products column.

16

17

In the wizard that appears, give the product an appropriate name, e.g. ACMP Suite.

18

19

The next step is to assign a product metric, i.e. the metric must be selected to match the license type of the product.

20

21

22

[[image:63_LicMan_Metriktypen beim Erzeugen eines neuen Produktes_1434.png||height="660" width="905"]]

23

24

25

Selection of metric types when adding a new product

The detection patterns (manual detection pattern/DNA/DNA2) can only be added to the Installation based metric type as an automatic consumer source!

31

32

33

Following metric types are possible:

34

35

(% style="width:1532.99px" %)

36

|**Metric type**|(% style="width:927px" %)**Explanation**|(% style="width:331px" %)Type of consumers

37

|Installation based|(% style="width:927px" %)Counts the number of clients found with corresponding installations (DNA/DNA2 and manual detection patterns)|(% style="width:331px" %)clients, devices

38

|User CAL |(% style="width:927px" %)Counts per user, whereby the decisive factor is how many employees use the respective product |(% style="width:331px" %)user

39

|Devices CAL|(% style="width:927px" %) Counts per device, whereby the decisive factor is how many end devices use the respective product|(% style="width:331px" %)cleints, devices

40

41

Depending on the metric type, three advanced metric properties are available:

42

43

**Concurrent use = all 3 metric types**

44

45

Here the product is always sufficiently licensed if a valid license is linked. The number of consumers is not decisive (e.g. TeamViewer licenses according to channels for simultaneous sessions). As a rule, the programs themselves ensure licence-compliant use, e.g. by only allowing as many users to be logged in simultaneously as there are licenses.

46

47

**Include backup/failover hosts = only Installation based and devices CAL**

48

49

In the event of a failure, backup/failover hosts are automatic replacement systems that step in and allow operations to continue almost seamlessly. In this setting, hypervisors on which a virtual machine could run are also calculated for virtual environments. As a rule, these hosts are not licensed and therefore do not have to be enabled in this option. However, if licensing has been written into your licence agreement, you must enable this setting for the appropriate Client. Only then will the Client be included in the licence balance.

50

51

**Consider consumers that have been added several times = all three metric types**

52

53

If several detection patterns are linked to a product and one consumer is affected by several, this property would ensure that the same consumer consumes two or more licenses.

54

55

Next, you can specify additional product information as well as predecessor and successor products. This setting can play a role in upgrading and downgrading at a later stage.

56

57

In the next step, you have the option of assigning a license to the product directly or you can do this at a later time via the tab// Licences//.

58

59

= Assigning consumers to a product =

60

61

Consumers must be assigned to a product. Consumers are Clients, Users or Devices.

62

63

64

[[image:63_LicMan_Verbraucherquellen angeben_1432.png||height="727" width="997"]]

65

66

67

Specify consumer sources

Consumers are metric-specific, i.e. the metric set determines what kind of consumers are attached to the product. A distinction is made between consumers that are determined automatically or consumers that are added manually. The 3 metric types can have different sources from which the consumers can be determined:

72

73

(% style="width:1415.99px" %)

74

|(% style="width:322px" %)**Metric type**|(% style="width:604px" %)**Automatic consumers**|(% style="width:487px" %)**Manual consumers**

75

|(% style="width:322px" %)Installation based|(% style="width:604px" %)(((

76

Detection Patterns (DNA)

77

78

Detection Patterns (DNA2)

79

80

Detection Patterns (Manual)

ACMP Query (Clients)

ACMP Query (Assets)

[[Terminal Service Access>>doc:||anchor="HTerminalServices"]] (Clients)

87

)))|(% style="width:487px" %)Users, Devices

88

|(% style="width:322px" %)User CAL|(% style="width:604px" %)(((

89

LDAP Queries (Users)

90

91

ACMP Query (Contacts)

92

93

[[Terminal Service Access>>doc:||anchor="HTerminalServices"]] (Contacts)

94

)))|(% style="width:487px" %)Users

95

|(% style="width:322px" %)Devices CAL|(% style="width:604px" %)(((

96

LDAP Queries (Computers)

ACMP Query (Clients)

ACMP Query (Assets)

[[Terminal Service Access>>doc:||anchor="HTerminalServices"]] (Clients)

103

)))|(% style="width:487px" %)Users, Devices

104

105

A usage can take place directly in the product as well as be granted via a downgrade in the license. However, the latter is only possible if this consumer has been automatically or manually assigned to the downgrade product. The best way to see which product is used for usage is in the //Direct Product// column in the [[Compliance >>doc:ACMP.64.ACMP-Solutions.Lizenzmanagement.Compliance.WebHome]]view.

106

107

== **Terminal Services** ==

108

109

A terminal server is a very powerful server on which programs and data are centrally stored, processed and executed. Clients are connected to the Server and function as terminal devices. When clients log on to the Server, separate sessions are opened for each client. The Client only receives graphical info and presents it to the user. The applications themselves are therefore installed on the Server and all data is also stored there.

110

111

In ACMP, the recording of access from the Client to the Server is configured in the settings under Remote Desktop Services. These accesses are in turn mapped in License Management via the Terminal Services Queries. These queries can be specified as the source for the automatic consumers.

Wiki source code of Produkte

Navigation

author	version	line-number	content
		1	{{aagon.priorisierung}}
		2	60
		3	{{/aagon.priorisierung}}
		4
		5	{{aagon.floatingbox/}}
		6
		7	Products are at the heart of Licence Management and are associated with all ongoing data. You create a product from a software version and edition to be licensed. The product should ideally be a balance between the licences purchased and the consumers that represent the actual use of the licences. If these match, you have an optimally licensed product that is also reported in compliance.
		8
		9	You need to select the metric that matches the licensing form of the product. This must ultimately be the same as the licence metric in order for the licence calculation to be correct.
		10
		11	In the Products tab you will see all the products that have already been created. You can create new products here using the Add button or in the Software Catalog tab, or you can edit or delete existing products. You can also filter products by metric type.
		12
		13	= Create a product =
		14
		15	In the ribbon bar, click on// Add// in the Products column.
		16
		17	In the wizard that appears, give the product an appropriate name, e.g. ACMP Suite.
		18
		19	The next step is to assign a product metric, i.e. the metric must be selected to match the license type of the product.
		20
		21	{{figure}}
		22	[[image:63_LicMan_Metriktypen beim Erzeugen eines neuen Produktes_1434.png\|\|height="660" width="905"]]
		23
		24	{{figureCaption}}
		25	Selection of metric types when adding a new product
		26	{{/figureCaption}}
		27	{{/figure}}
		28
		29	{{aagon.infobox}}
		30	The detection patterns (manual detection pattern/DNA/DNA2) can only be added to the Installation based metric type as an automatic consumer source!
		31	{{/aagon.infobox}}
		32
		33	Following metric types are possible:
		34
		35	(% style="width:1532.99px" %)
		36	\|Metric type\|(% style="width:927px" %)Explanation\|(% style="width:331px" %)Type of consumers
		37	\|Installation based\|(% style="width:927px" %)Counts the number of clients found with corresponding installations (DNA/DNA2 and manual detection patterns)\|(% style="width:331px" %)clients, devices
		38	\|User CAL \|(% style="width:927px" %)Counts per user, whereby the decisive factor is how many employees use the respective product \|(% style="width:331px" %)user
		39	\|Devices CAL\|(% style="width:927px" %) Counts per device, whereby the decisive factor is how many end devices use the respective product\|(% style="width:331px" %)cleints, devices
		40
		41	Depending on the metric type, three advanced metric properties are available:
		42
		43	Concurrent use = all 3 metric types
		44
		45	Here the product is always sufficiently licensed if a valid license is linked. The number of consumers is not decisive (e.g. TeamViewer licenses according to channels for simultaneous sessions). As a rule, the programs themselves ensure licence-compliant use, e.g. by only allowing as many users to be logged in simultaneously as there are licenses.
		46
		47	Include backup/failover hosts = only Installation based and devices CAL
		48
		49	In the event of a failure, backup/failover hosts are automatic replacement systems that step in and allow operations to continue almost seamlessly. In this setting, hypervisors on which a virtual machine could run are also calculated for virtual environments. As a rule, these hosts are not licensed and therefore do not have to be enabled in this option. However, if licensing has been written into your licence agreement, you must enable this setting for the appropriate Client. Only then will the Client be included in the licence balance.
		50
		51	Consider consumers that have been added several times = all three metric types
		52
		53	If several detection patterns are linked to a product and one consumer is affected by several, this property would ensure that the same consumer consumes two or more licenses.
		54
		55	Next, you can specify additional product information as well as predecessor and successor products. This setting can play a role in upgrading and downgrading at a later stage.
		56
		57	In the next step, you have the option of assigning a license to the product directly or you can do this at a later time via the tab// Licences//.
		58
		59	= Assigning consumers to a product =
		60
		61	Consumers must be assigned to a product. Consumers are Clients, Users or Devices.
		62
		63	{{figure}}
		64	[[image:63_LicMan_Verbraucherquellen angeben_1432.png\|\|height="727" width="997"]]
		65
		66	{{figureCaption}}
		67	Specify consumer sources
		68	{{/figureCaption}}
		69	{{/figure}}
		70
		71	Consumers are metric-specific, i.e. the metric set determines what kind of consumers are attached to the product. A distinction is made between consumers that are determined automatically or consumers that are added manually. The 3 metric types can have different sources from which the consumers can be determined:
		72
		73	(% style="width:1415.99px" %)
		74	\|(% style="width:322px" %)Metric type\|(% style="width:604px" %)Automatic consumers\|(% style="width:487px" %)Manual consumers
		75	\|(% style="width:322px" %)Installation based\|(% style="width:604px" %)(((
		76	Detection Patterns (DNA)
		77
		78	Detection Patterns (DNA2)
		79
		80	Detection Patterns (Manual)
		81
		82	ACMP Query (Clients)
		83
		84	ACMP Query (Assets)
		85
		86	[[Terminal Service Access>>doc:\|\|anchor="HTerminalServices"]] (Clients)
		87	)))\|(% style="width:487px" %)Users, Devices
		88	\|(% style="width:322px" %)User CAL\|(% style="width:604px" %)(((
		89	LDAP Queries (Users)
		90
		91	ACMP Query (Contacts)
		92
		93	[[Terminal Service Access>>doc:\|\|anchor="HTerminalServices"]] (Contacts)
		94	)))\|(% style="width:487px" %)Users
		95	\|(% style="width:322px" %)Devices CAL\|(% style="width:604px" %)(((
		96	LDAP Queries (Computers)
		97
		98	ACMP Query (Clients)
		99
		100	ACMP Query (Assets)
		101
		102	[[Terminal Service Access>>doc:\|\|anchor="HTerminalServices"]] (Clients)
		103	)))\|(% style="width:487px" %)Users, Devices
		104
		105	A usage can take place directly in the product as well as be granted via a downgrade in the license. However, the latter is only possible if this consumer has been automatically or manually assigned to the downgrade product. The best way to see which product is used for usage is in the //Direct Product// column in the [[Compliance >>doc:ACMP.64.ACMP-Solutions.Lizenzmanagement.Compliance.WebHome]]view.
		106
		107	== Terminal Services ==
		108
		109	A terminal server is a very powerful server on which programs and data are centrally stored, processed and executed. Clients are connected to the Server and function as terminal devices. When clients log on to the Server, separate sessions are opened for each client. The Client only receives graphical info and presents it to the user. The applications themselves are therefore installed on the Server and all data is also stored there.
		110
		111	In ACMP, the recording of access from the Client to the Server is configured in the settings under Remote Desktop Services. These accesses are in turn mapped in License Management via the Terminal Services Queries. These queries can be specified as the source for the automatic consumers.