Configuration Options for Managed Software

Managed Software offers several configurations to help you tailor your workflow as much as possible. These include, among other things, Scheduled Server Tasks and jobs in the Agent Tasks, as well as the test and release processes you can create for each software package.

4

5

= Jobs and Tasks =

6

7

Managed Software requires server jobs and tasks to run smoothly. These jobs are designed, among other things, to check for software versions that are already installed or available on a client, or that are required (Agent Tasks). Server tasks, among other things, download new versions or update the software catalog. You can assign a [[start condition>>doc:ACMP.610.ACMP-Solutions.Jobs.WebHome||anchor="HStartconditions"]] to both the Agent Tasks job and the server tasks, which you can customize based on your environment. The jobs and tasks run at intervals and sequentially, one after the other. You can check the sequence in the monitors (including the Job, Client, and Server Monitors).

8

9

**[[Agent Tasks>>doc:ACMP.610.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]]** (//Client Management// > //Agent Task//s)

10

11

|**Agent Task**|**Description**|**Recommended Start Condition**

12

|Managed Software Scanner|The Managed Software Scanner scans the managed software installed on the client. Using the scan function, the ACMP Server identifies any discrepancies between the installed version and the available version that the client has installed.|Run daily (maintenance windows are ignored)

13

14

15

Please note that the job is available only in the agent planner templates for the Windows operating system.

16

17

18

**[[Scheduled Server Tasks>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HScheduledServerTasks"]]** (//System// > //Settings //> //acmp// //Server// > //Scheduled Server Tasks//)

19

20

|**Server Task**|**Description**|**Recommended Start Condition**

21

|Managed Software cleanup|The server task deletes the Managed Software versions that are no longer needed, thereby freeing up storage space|Start every day

22

|Managed Software catalog Update|The job downloads new software versions of the managed software included in the subscribed packages.

23

If necessary, the job can also be started manually in the Managed Software Dashboard.|Start every day

24

|Managed Software version download|Updates the software catalog for Managed Software|Start every day

= Customize the Test and Release Process =

29

30

In the section “Defining the Test and Release Process,” learn more about what a test and release process is and why you need it. You’ll also find helpful tips there on what to keep in mind during configuration.

31

32

== Changing Software Package Parameters ==

33

34

Under “Configuring Software Package Parameters,” you’ll find helpful tips on what parameters are in general and how you can change the respective values for a software package.

35

36

= Track Managed Software Jobs in the Monitors =

37

38

Once you have created jobs in Managed Software, you can view the current status and results of finished jobs in the monitors. This info is available specifically through the [[Job monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HJobMonitor"]]. To do so, filter by the content “Managed Software.”

39

40

If, on the other hand, you want to check the status of a specific software package, you can do so via the //Tests// tab in the open Managed Software window. To do this, select the desired software package and version number. A details window will now open on the right-hand side, displaying a table that lists all jobs in which the current software version was executed on a Client within a test ring.

41

42

43

If the selected software version has not yet been executed as a job within a test ring on a Client, the table will not contain any values!

[[Managed Software's Insight>>image:1790151824651-301.png||data-xwiki-image-style-alignment="center"]]

48

49

Once a job is finished, you'll find the result in the corresponding column of the table. Double-click any job in the table to open its log entries. There, in the //Description// column, you may find the reason for the result ([[image:1790151848536-388.png]]) of the execution and an error message.

50

51

52

[[Preview of the job's log entries>>image:1790151854513-490.png||data-xwiki-image-style-alignment="center"]]

53

54

55

**What statuses can a finished Managed Software job have?**

56

57

If a job has been executed and has the status “Finished,” this does not necessarily mean that the job was exited successfully. A distinction is made between the following results:

58

59

60

|=(% style="width: 153px;" %)Result|=(% style="width: 1539px;" %)Causes

61

|(% style="width:153px" %)[[image:1790152023904-355.png]] Failed|(% style="width:1539px" %)The job was executed, but the defined actions could not be completed successfully due to one or more errors.

62

|(% style="width:153px" %)[[image:1790152059056-472.png]] Successful|(% style="width:1539px" %)The job was executed, and the defined actions were successfully completed.

63

|(% colspan="1" rowspan="2" style="width:153px" %)[[image:1790152081055-539.png]] Skipped|(% style="width:1539px" %)(((

64

The job was executed and no error occurred; however, the defined actions were skipped because the intended target of the action already exists. Thus, while it would be possible to perform the action, it is not necessary.

65

)))

66

|(% style="width:1539px" %)(((

67

**Example: **For a software package, the action //Install or Update// is specified in the parameters. This job is then executed and finished. However, the result displayed is not //Successful// but //Skipped//. The reason for this is that the intended goal of the action - in this case, “**The software package is installed on the Client in its current version**” - has already been met. Therefore, there is no error with the //Install or Update// actions; rather, they could have been executed successfully if the action’s target had not already been met.

68

)))

69

|(% style="width:153px" %)[[image:1790152039995-689.png]] Without a License|(% style="width:1539px" %)The job was executed, but the defined actions could not be completed successfully because those actions require one or more specific acmp licenses that you do not have.

70

71

If you want to view detailed information about a software package's job, you can open it by double-clicking on the job. In the new window, you can then double-click on a job in the //Executions// table to open the job's log entries. There you will find the reason for the execution result and, if applicable, an error message.

Wiki source code of Konfigurationsmöglichkeiten für Managed Software

Navigation

author	version	line-number	content
		1	{{aagon.floatingbox/}}
		2
		3	Managed Software offers several configurations to help you tailor your workflow as much as possible. These include, among other things, Scheduled Server Tasks and jobs in the Agent Tasks, as well as the test and release processes you can create for each software package.
		4
		5	= Jobs and Tasks =
		6
		7	Managed Software requires server jobs and tasks to run smoothly. These jobs are designed, among other things, to check for software versions that are already installed or available on a client, or that are required (Agent Tasks). Server tasks, among other things, download new versions or update the software catalog. You can assign a [[start condition>>doc:ACMP.610.ACMP-Solutions.Jobs.WebHome\|\|anchor="HStartconditions"]] to both the Agent Tasks job and the server tasks, which you can customize based on your environment. The jobs and tasks run at intervals and sequentially, one after the other. You can check the sequence in the monitors (including the Job, Client, and Server Monitors).
		8
		9	[[Agent Tasks>>doc:ACMP.610.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]] (//Client Management// > //Agent Task//s)
		10
		11	\|Agent Task\|Description\|Recommended Start Condition
		12	\|Managed Software Scanner\|The Managed Software Scanner scans the managed software installed on the client. Using the scan function, the ACMP Server identifies any discrepancies between the installed version and the available version that the client has installed.\|Run daily (maintenance windows are ignored)
		13
		14	{{aagon.infobox}}
		15	Please note that the job is available only in the agent planner templates for the Windows operating system.
		16	{{/aagon.infobox}}
		17
		18	[[Scheduled Server Tasks>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome\|\|anchor="HScheduledServerTasks"]] (//System// > //Settings //> //acmp// //Server// > //Scheduled Server Tasks//)
		19
		20	\|Server Task\|Description\|Recommended Start Condition
		21	\|Managed Software cleanup\|The server task deletes the Managed Software versions that are no longer needed, thereby freeing up storage space\|Start every day
		22	\|Managed Software catalog Update\|The job downloads new software versions of the managed software included in the subscribed packages.
		23	If necessary, the job can also be started manually in the Managed Software Dashboard.\|Start every day
		24	\|Managed Software version download\|Updates the software catalog for Managed Software\|Start every day
		25
		26
		27
		28	= Customize the Test and Release Process =
		29
		30	In the section “Defining the Test and Release Process,” learn more about what a test and release process is and why you need it. You’ll also find helpful tips there on what to keep in mind during configuration.
		31
		32	== Changing Software Package Parameters ==
		33
		34	Under “Configuring Software Package Parameters,” you’ll find helpful tips on what parameters are in general and how you can change the respective values for a software package.
		35
		36	= Track Managed Software Jobs in the Monitors =
		37
		38	Once you have created jobs in Managed Software, you can view the current status and results of finished jobs in the monitors. This info is available specifically through the [[Job monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome\|\|anchor="HJobMonitor"]]. To do so, filter by the content “Managed Software.”
		39
		40	If, on the other hand, you want to check the status of a specific software package, you can do so via the //Tests// tab in the open Managed Software window. To do this, select the desired software package and version number. A details window will now open on the right-hand side, displaying a table that lists all jobs in which the current software version was executed on a Client within a test ring.
		41
		42	{{aagon.infobox}}
		43	If the selected software version has not yet been executed as a job within a test ring on a Client, the table will not contain any values!
		44	{{/aagon.infobox}}
		45
		46
		47	[[Managed Software's Insight>>image:1790151824651-301.png\|\|data-xwiki-image-style-alignment="center"]]
		48
		49	Once a job is finished, you'll find the result in the corresponding column of the table. Double-click any job in the table to open its log entries. There, in the //Description// column, you may find the reason for the result ([[image:1790151848536-388.png]]) of the execution and an error message.
		50
		51
		52	[[Preview of the job's log entries>>image:1790151854513-490.png\|\|data-xwiki-image-style-alignment="center"]]
		53
		54	{{box}}
		55	What statuses can a finished Managed Software job have?
		56
		57	If a job has been executed and has the status “Finished,” this does not necessarily mean that the job was exited successfully. A distinction is made between the following results:
		58	{{/box}}
		59
		60	\|=(% style="width: 153px;" %)Result\|=(% style="width: 1539px;" %)Causes
		61	\|(% style="width:153px" %)[[image:1790152023904-355.png]] Failed\|(% style="width:1539px" %)The job was executed, but the defined actions could not be completed successfully due to one or more errors.
		62	\|(% style="width:153px" %)[[image:1790152059056-472.png]] Successful\|(% style="width:1539px" %)The job was executed, and the defined actions were successfully completed.
		63	\|(% colspan="1" rowspan="2" style="width:153px" %)[[image:1790152081055-539.png]] Skipped\|(% style="width:1539px" %)(((
		64	The job was executed and no error occurred; however, the defined actions were skipped because the intended target of the action already exists. Thus, while it would be possible to perform the action, it is not necessary.
		65	)))
		66	\|(% style="width:1539px" %)(((
		67	Example: For a software package, the action //Install or Update// is specified in the parameters. This job is then executed and finished. However, the result displayed is not //Successful// but //Skipped//. The reason for this is that the intended goal of the action - in this case, “The software package is installed on the Client in its current version” - has already been met. Therefore, there is no error with the //Install or Update// actions; rather, they could have been executed successfully if the action’s target had not already been met.
		68	)))
		69	\|(% style="width:153px" %)[[image:1790152039995-689.png]] Without a License\|(% style="width:1539px" %)The job was executed, but the defined actions could not be completed successfully because those actions require one or more specific acmp licenses that you do not have.
		70
		71	If you want to view detailed information about a software package's job, you can open it by double-clicking on the job. In the new window, you can then double-click on a job in the //Executions// table to open the job's log entries. There you will find the reason for the execution result and, if applicable, an error message.