| 7 | | == Change Product Properties for all Clients on a Depot Server == |
| | 8 | {{{ |
| | 9 | opsi-admin |
| | 10 | }}} |
| | 11 | |
| | 12 | method names start with get or set are compability methods for opsi 3 calls. |
| | 13 | Opsi 4 method names start with the object type, eg: |
| | 14 | {{{ |
| | 15 | method host_getIdents |
| | 16 | method product_getIdents |
| | 17 | method product_getHashes |
| | 18 | productOnClient_getObjects |
| | 19 | }}} |
| | 20 | |
| | 21 | == Product Properties == |
| | 22 | |
| | 23 | Packages have defined default values for there properties. |
| | 24 | |
| | 25 | === Client Product Properties === |
| | 26 | |
| | 27 | Product properties can be set individually on every client using the Opsi-Gui. |
| | 28 | |
| | 29 | |
| | 30 | === Depot Product Properties === |
| | 31 | |
| | 32 | A Depot Server can have its own set of product properties. |
| | 33 | When a new Opsi is added to a depot server, these depot values are also used for the client, |
| | 34 | if the client does not overwrite these properties. |
| | 35 | |
| | 36 | The depot defaults can be defined when installing a new package: |
| | 37 | {{{ |
| | 38 | opsi-package-manager -i -p ask PAKET.opsi |
| | 39 | }}} |
| | 40 | |
| | 41 | Additionally, these properties can be quering and modified using the Opsi-JSON-RPC API calls. |
| | 42 | |
| | 43 | Example: |
| | 44 | |
| | 45 | |
| | 46 | {{{ |
| | 47 | # query the properties of the product "winxppro" on the server DEPOT-SERVER-ID |
| | 48 | opsi-admin -d method getProductProperties_hash winxppro DEPOT-SERVER-ID |
| | 49 | |
| | 50 | # change the property "productkey" of the product winxppro on the server DEPOT-SERVER-ID |
| | 51 | opsi-admin -d method setProductProperty winxppro "productkey" "ABCDE-FGHIJ-KLMNO-QRTUV-WXYZ1" DEPOT-SERVER-ID |
| | 52 | }}} |
| | 53 | |
| | 54 | ==== Change Product Properties for all Clients on a Depot Server ==== |