Wiki source code of Client Command synchronisieren
Last modified by Sabrina V. on 2026/07/31 06:11
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{aagon.floatingbox/}} | ||
| 2 | |||
| 3 | During the Synchronization phase, the data associated with a Client Command is deployed to the individual [[File Repositories>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]. However, this is only necessary if the Client Command requires additional data - such as installation files, configuration files, etc. - to run. The Client Command is not yet available to any client. | ||
| 4 | |||
| 5 | If you have not yet set up a file repository that accepts client commands, a placeholder view is displayed here. All client commands then skip this phase. | ||
| 6 | |||
| 7 | {{figure}} | ||
| 8 | [[image:37_64_Client Commands_Client Commands synchronisieren_1171.png||data-xwiki-image-style-alignment="center"]] | ||
| 9 | |||
| 10 | {{figureCaption}} | ||
| 11 | Synchronization phase | ||
| 12 | {{/figureCaption}} | ||
| 13 | {{/figure}} | ||
| 14 | |||
| 15 | The upper view lists all client commands that have the status “Synchronizing / Ready for Release.” In addition, as in the previous phases, the version, properties, date of the last modification, and the size of the client command files are displayed. Using the Test and Synchronize buttons, you can send a client command back to the test phase or distribute the client command data to the file repositories. | ||
| 16 | |||
| 17 | |||
| 18 | = Client Command Properties = | ||
| 19 | |||
| 20 | |((( | ||
| 21 | [[image:XWiki.Images.WebHome@script_console.png||alt="Script_Console" data-xwiki-image-style-alignment="center" height="32" width="32"]] | ||
| 22 | )))|((( | ||
| 23 | Part of the client command is executed in the ACMP Console. | ||
| 24 | ))) | ||
| 25 | |((( | ||
| 26 | [[image:XWiki.Images.WebHome@script_client.png||alt="Script_Client" data-xwiki-image-style-alignment="center" height="32" width="32"]] | ||
| 27 | )))|((( | ||
| 28 | Part of the Client Command is executed on the client. | ||
| 29 | ))) | ||
| 30 | |((( | ||
| 31 | [[image:XWiki.Images.WebHome@clientcommandphase_release.png||alt="ClientCommandPhase_Release" data-xwiki-image-style-alignment="center" height="32" width="32"]] | ||
| 32 | )))|((( | ||
| 33 | The Client Command has at least one released version. | ||
| 34 | ))) | ||
| 35 | |((( | ||
| 36 | [[image:SelectiveSync.ico||data-xwiki-image-style-alignment="center"]] | ||
| 37 | )))|((( | ||
| 38 | The Client Command can only be synchronized with selected file repositories. | ||
| 39 | ))) | ||
| 40 | |((( | ||
| 41 | [[image:clientcommand_interactive.png||data-xwiki-image-style-alignment="center" height="32" width="32"]] | ||
| 42 | )))|((( | ||
| 43 | The Client Command can be executed via the ACMP Kiosk. | ||
| 44 | ))) | ||
| 45 | |((( | ||
| 46 | [[image:PassWord_Locked.ico||data-xwiki-image-style-alignment="center"]] | ||
| 47 | )))|((( | ||
| 48 | The Client Command is password-protected. | ||
| 49 | ))) | ||
| 50 | |||
| 51 | |||
| 52 | |||
| 53 | = Synchronizing Data = | ||
| 54 | |||
| 55 | To synchronize the data of a Client Command to the file repositories, select the Client Command and click Synchronize. The Client Command will then no longer be displayed in the upper view but will appear in the lower view, and the distribution of the Client Command files will begin. If you now click on a Client Command in the lower view, all file repositories will be displayed to the right of it. For each file repository, a graph shows the percentage of Client Command files that have already been transferred to that repository. | ||
| 56 | |||
| 57 | {{aagon.infobox}} | ||
| 58 | If you have edited an existing Client Command, its data only needs to be deployed to the file repositories if the files themselves have changed. Otherwise, this step is skipped. | ||
| 59 | {{/aagon.infobox}} | ||
| 60 | |||
| 61 | Using the “Open Synchronization Monitor” button, you can open a dialog that allows you to manually start or pause the distribution of data (see [[Verteilte File Repositories>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]) and that displays all updates and client command versions pending synchronization. This also applies to file repositories that are excluded from automatic synchronization. Automatic synchronization can be managed for each existing file repository under System > //Distributed File Repositories// > Manage //File Repositories//. If you stop the synchronization of a file repository, it is also excluded from automatic synchronization. | ||
| 62 | |||
| 63 | As soon as the files associated with a client command are deployed to the file repositories, the client command has the status “Synchronizing.” Such a client command is also automatically in the “Release” phase. |