Wiki source code of Unix Scripts verwalten
Last modified by jklein on 2025/07/28 08:51
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{aagon.floatingbox/}} | ||
| 2 | |||
| 3 | In the Solution Desktop Automation > Unix Scripts, you can create and manage Unix scripts. The ribbon bar allows you to add ([[image:Ico_UnixScript_Script_Add.png||height="“24”" width="24"]]), edit ([[image:Ico_UnixScript_Script_Edit.png||height="“24”" width="24"]]), or delete ([[image:Ico_UnixScript_Script_Delete.png||imageico_unixscript_script_duplicate.pngheight="“24”" scripts_solution.pngalt="“Overview" height="“24”" width="24"]]) Unix scripts. | ||
| 4 | |||
| 5 | = Add Unix Script = | ||
| 6 | |||
| 7 | You can add a new Unix script via the ribbon bar or the context menu. The Script Wizard will open. | ||
| 8 | |||
| 9 | {{aagon.warnungsbox}} | ||
| 10 | The default test and network share process moves the Unix script directly to the first test ring. This makes it potentially available to all Unix Clients assigned to this test ring. | ||
| 11 | {{/aagon.warnungsbox}} | ||
| 12 | |||
| 13 | You can now configure the Unix script as follows: | ||
| 14 | |||
| 15 | 1. Select the output directory and assign a name to the Unix script. | ||
| 16 | 1. Specify the script language in which you want to write the Unix script. | ||
| 17 | 1. Add a description if necessary and click the Continue button. | ||
| 18 | 1. Add the code for the Unix script in the code editor.{{aagon.infobox}}The script editor does not currently have auto-complete. However, you can access variables by pressing Ctrl+Space. {{/aagon.infobox}} | ||
| 19 | 1. Click on the Continue button. | ||
| 20 | 1. Set the rights for groups and users for the Unix script.{{aagon.infobox}}Further information on rights can be found in the Access Lists section. {{/aagon.infobox}} | ||
| 21 | 1. Click on the Done button. | ||
| 22 | |||
| 23 | You have now created a new Unix script in its first version. | ||
| 24 | |||
| 25 | [[Adding a Unix script>>image:Unix Scripts_Script hinzufügen.png||alt="“Adding"]] | ||
| 26 | |||
| 27 | Depending on the assigned test and release process, the script is assigned to one of the distribution rings. You can see which distribution ring a version is currently in directly from the icon. | ||
| 28 | |||
| 29 | |||
| 30 | |=(% style="width: 155px;" %)Icon|=(% style="width: 921px;" %)Bedeutung | ||
| 31 | |(% style="width:155px" %)[[image:ACMP.63.ACMP-Solutions.Client-Management.Managed Software.Managed Software einrichten.Abonnierte Software verwalten.WebHome@TestRing_NoRing.svg||height="24" width="24"]] No Ring|(% style="width:921px" %)The software version has not yet been assigned to a ring and is therefore not deployed. | ||
| 32 | |(% style="width:155px" %)[[image:ACMP.63.ACMP-Solutions.Client-Management.Managed Software.Managed Software einrichten.Abonnierte Software verwalten.WebHome@TestRing_One.svg||width="24"]] Test Ring 1|(% style="width:921px" %)The software version is in Test Ring 1 and can be used via appropriately configured containers. | ||
| 33 | |(% style="width:155px" %)[[image:ACMP.64.ACMP-Solutions.Patch Management.Managed Software.Managed Software einrichten.Abonnierte Software verwalten.WebHome@TestRing_Two.svg||height="24" width="24"]] Test Ring 2|(% style="width:921px" %)The software version is in Test Ring 2 and can be used via appropriately configured containers. | ||
| 34 | |(% style="width:155px" %)[[image:ACMP.65.ACMP-Solutions.Patch Management.Managed Software.Managed Software einrichten.Abonnierte Software verwalten.WebHome@TestRing_Release.svg||height="24" width="24"]] Released|(% style="width:921px" %)The software version is released and can be deployed to all Clients via appropriately configured containers. | ||
| 35 | |(% style="width:155px" %)[[image:ACMP.63.ACMP-Solutions.Client-Management.Managed Software.Managed Software einrichten.Abonnierte Software verwalten.WebHome@ClientCommandProperties_Condition.ico||height="24" width="24"]] Denied|(% style="width:921px" %)The software version is denied and must be approved again before it can be used again. | ||
| 36 | |||
| 37 | = Versioning Unix scripts = | ||
| 38 | |||
| 39 | Select a Unix script from the script list and click on the arrow to the left of the script icon to open the list of versions. You will now see all available versions of the Unix script. Select the version you want to manage. The details of the selected version are displayed in the window on the right next to the script list. | ||
| 40 | |||
| 41 | Using the ribbon bar or the context menu, you can now create a new version based on the selected version or edit the selected version. | ||
| 42 | |||
| 43 | {{aagon.infobox}} | ||
| 44 | After creating a new version, the old version can no longer be changed. | ||
| 45 | {{/aagon.infobox}} | ||
| 46 | |||
| 47 | [[Adding a version to a Unix script>>image:Unix Scripts_Versionierung.png||alt="“Adding"]] | ||
| 48 | |||
| 49 | You can also deny the version completely, reapprove a denied version, or delete the version. | ||
| 50 | |||
| 51 | {{aagon.infobox}} | ||
| 52 | Deleting a Unix Script version is only possible if another version is available for the script. No Unix Script can exist without a subordinate version. | ||
| 53 | {{/aagon.infobox}} | ||
| 54 | |||
| 55 | If you have not yet defined a user-defined test and release process, you can do so in the next step. For continuing information, refer to the section [[Configuring the test and release process for Unix scripts>>doc:ACMP.68.ACMP-Solutions.Desktop Automation.Unix Scripts.Test- und Freigabeprozess von Unix Scripts konfigurieren .WebHome]]. |